# ReichelAg protocol naming correction

Founder duplicated a protocol and changed its title, but the slug/Markdown file
retained the original-copy default. Rename was undiscoverable inside Edit page.
Founder confirms editing and clipboard copy work. CSOC-WP-0008-T12 registers
and implements this naming gap; complete workflow acceptance remains T09.

## User-visible behavior

- Duplicate page: enter the new title once. Leave the optional filename empty
  to derive its slug/.md filename from the title. An explicit filename overrides
  the default. If title and filename are both empty, keep the original-copy rule.
- Rename page: a visible writer action opens editable Title and File name
  (slug) fields. Title-only edits keep the current filename/address; changing
  the file field renames the .md file and changes the page address.
- Existing duplicates are not changed automatically. Use Rename page on the
  existing duplicate and choose its corrected title/filename, then Save page.
- Notes, subtitle, Visual and imported source metadata survive rename and
  subsequent editing. Existing pages cannot be overwritten; index filename
  stays fixed; readers and outsiders cannot rename.
- Existing references are not rewritten when the address changes.

Milestone: I name the next weekly protocol while duplicating it and can correct
its title/file later without losing notes or modifying the previous call.

## Evidence and release

`make check`:98passed, including mandatory real-browser title-only duplication,
visible rename, file/address change, independent edit/reload/clipboard and
viewer-denied rename. Mandatory fast regression verifies explicit override,
collision safety, original byte preservation, source metadata and Visual asset
preservation through rename/edit, and fixed index. Targeted Ruff/diff checks pass.

Source `b13ba9c5815e`, registry digest
`sha256:dbeaeda1a03622a91683f8db3c1f498e8bf43417cdb077ec740c56f0489baff6`.
Owning production pin committed/synced at22c5695 in railiance-apps. Existing
founder app/interruption go continues this corrective release:
ADMINISTER @ realm:kubernetes/railiance01, activation=APPROVED;
decision8bbce691-a787-4140-9cd4-df06e8635a27. Node92.205.62.239 and single-writer
retained2GiPVC verified. CPU requests3455m/4000m; Recreate avoids writer surge.

Fresh paired database/content recovery capture took56.93seconds; writers were
paused and app resumed. Pre-upgrade database SHA256:
`e625d8a7505efe796a75fb94eafba5cca82583f20885641d13cd14d3cd350089`.
Content archive SHA256:
`87478a65130c9f9a0f84fe1a098b95899f76304cca9dbb036e3862d5f4c42f4d`.
Temporary node-local custody does not complete durable backup operations/T02.

Helm lint/render and guarded server dry-run passed. Parsed manifests differ only
in app image; Helm atomic/wait revision13 deployed. Read-only live checks verify
rename action, editable title/filename, loaded title-derived duplicate logic,
unchanged original clipboard text/template payload and owner access. All75stored
file hashes match the pre-upgrade recovery point. Public health/static200 after
the expected brief Recreate interruption. No live protocol was automatically
renamed or modified for testing. No private notes or credentials enter records.

Implementation taskT12done. T09/T04 remain user naming/workflow acceptance.