Rename a program, a scan or a directory

[bbfrederick]

An archive built from a template inherits the template's program name, and
the console disambiguates on import rather than complaining. The capabilities
load test was seeded from Potpourri_P1 and arrived on the scanner as
Potpourri_P1 (2) — tidy, and also how a generated protocol ends up named
after whichever export happened to seed it.

What it does

Names are not in the protocol. They hang off Instance.LabelElement_id on an
EdfString node holding a locale table, which is precisely what lets a scan
be renamed without re-hashing the content. So rename rewrites that table and
nothing else, and the test asserts the protocols come back byte-identical
rather than merely that the archive still validates.

It works on any named node, which is three useful things:

Node	What changes
EdfProgram	the protocol name
EdfMeasurementStep	a scan name
EdfDirectory	where it lands in the tree

Two details

Every entry in the locale table is set rather than the one an export happens
to use: most write "" for the default and some write "en", and both
spellings are in the corpus. Reading only one is what once produced a
nameless tree.

It refuses a node whose label is shared with another. No corpus archive shares
one — checked, zero across every example — but the store is content-addressed
and nothing in the format forbids it, so the alternative is renaming two
things while being asked to rename one.

Testing

2351 passed, 17 skipped. Two new tests: renaming a program leaves every scan
name and every protocol byte-identical, and renaming a scan does the same
while a node with no label of its own is refused.

🤖 Generated with Claude Code