Add IMPROVEMENT-046 and IMPROVEMENT-047 for the AdminTool

[meketreve]

Two backlog entries for the AdminTool, from the direction given on 2026-08-17. No code, no design —
one file, docs/backlog/improvements.md. Last ID used goes 045 to 047.

IMPROVEMENT-046 — UI/UX pass from a content author's point of view

Deliberately not a list of fixes. The request came with the instruction to think about what should
improve before handing the problem to Claude, and a UX judgement derived from reading XAML would be the
wrong artefact — what matters is the experience of authoring content, which is not visible in the code.
The entry records the request and gives the findings somewhere to land, with a proposed order: author
real content, write the friction down as it happens, and only then design anything.

One observation from using the tool on 2026-08-17 is recorded as a single data point rather than as the
review: DefinitionName shows its validation error inline in red, while CategoryFlags == 0 also
blocks Save but marks nothing at the field — only the italic undefined the description converter
produces, which reads as information rather than as an error.

IMPROVEMENT-047 — export a robot or item as a complete, self-contained SQL script

Measuring the current state changed the shape of this one, so the entry says what is actually true
rather than what the request assumed.

Export is not missing. ItemExporter, RobotExporter and SeasonExporter exist, and
RobotExporter calls ItemExporter for each component definition (Export/RobotExporter.cs:29), so a
robot export already carries its parts rather than just the template row.

The gap is narrower and nameable. Comparing the tables the create wizards write against the tables the
exporters read:

Table	Written by the wizard	Read by either exporter
aggregatemodifiers	yes	no
modulepropertymodifiers	yes	no
productionduration	yes	no
robottemplaterelation	yes, robots only	no

The first two are the entire Property Modifiers tab, the third is the Production tab. So an
item created through the wizard can hold data that re-exporting it will not reproduce. Translations are
absent from every export as well: SeedTranslations() writes to the translation store rather than into
the script, so a script applied elsewhere yields an entity whose name and description do not resolve.

Set to HIGH because the request named damage to the live database as the motivation.

Two things stated as questions rather than fixes

1. Does productionduration belong in an item export at all? The New Item dialog states that duration
   is category-level, so writing it back on import would affect every item in that category and not
   just the exported one. That is a question about intended semantics.
2. Do translations belong in the exported script? If they do, it has to carry the dictionary rows. If
   they do not, the export should say so, because silence reads as completeness.

One observation recorded and deliberately not filed

Nothing in the tool marks a connection as production. The apply mode already defaults to the safe one
(AppSettings.DefaultApplyMode = ApplyMode.SqlScript) and the status bar shows the current mode, so
the default is not the problem — but the tool cannot tell the operator that the server they are pointed
at is the live one. It is in IMPROVEMENT-047's notes rather than as its own entry, because it was not
asked for and it is a maintainer's call.

Measured against cfa0591.

[meketreve]

Both questions answered off the thread on 2026-08-19 — productionduration yes, if applicable; translations not needed. Recording them here so the direction sits on the public record, and folded into the entry in f0b0664.

productionduration. The table is keyed by category rather than by definition (productionduration (category, durationmodifier)), so "if applicable" has to mean guarded: the export emits it through SqlExportBuilder.IfNotExistsInsert, the same rule the wizard already applies through ProductionPanelViewModel.ShouldWriteProductionDuration. A target database that already defines the category keeps its own value; one that does not gets the exported item's. The row travels with the item without changing every other item in its category.

Translations. They stay out of the script. The work left on that point is the statement — the export says that names and descriptions are not carried, because silence reads as completeness.

Still planning only, no code in this pull request.