Recording through the UI let Grafana generate folder uids, and three write
model gaps then served folders whose address kept the first folder's slug:
- a template around a generated value won over a composed string that also
reads the title's slug; the composed string now wins when it reads a field
besides the template's value
- later creates checked composed strings against their own answers, but not
templates, so coverage served a template a later folder contradicted; a
template is now checked the same way
- a slug dropped `&`, which Grafana's Go slugs spell as the word; a slug rule
or part learns `ampersand: "and"` from the call that shows it, and calls
that slugged no `&` agree with either spelling
An address whose uid equals its title's slug could come from either field.
The entities the type holds now pick the one reading they share, and when
they cannot, a later create that tells the fields apart lends its composed
rule to the first create, whose body contract is learned again with it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>