UI Persistence

Persistence and repeat-run contract

VERIFIED HISTORICAL READBACK: receipt.json and requirements.json record the Word Pairs / PROD-WORDPAIRS / layer-1 scope from that historical documentation pass. Original documentation snapshot and all hostile receipts remain historical evidence. The product serializer limitation and first-party readback qualification remain recorded in product-receipt.json.

That historical scope was30FR,42TR,93TEST and30native mappings,421structured entries. This implementation updated17records:13UI gap statuses/criteria/notes,2existing recovery-case notes and2contest notes. It created1contestTR/TEST pair with10unsatisfied entries, and1wiki-publicationTR/TEST pair with6entries verified per publication run. All58case files exactly match owned QBrain notes;9received scoped execution updates. Original148record bodies/statuses/criteria/evidence and every prior mapping link are preserved. TEST-ROOMSYNC-139 remains in_progress and LIVE-07 remains false. No pending import is claimed.

For current authoritative requirements and publication status, use the QBrain-backed requirements wiki. Its generated records and publication receipts supersede this historical snapshot; the inventory above is not a live requirements count.

On rerun, read the same verified workspace/product/layer before writing. Preserve stable record/criterion IDs and non-owned notes/evidence. Merge only exact BEGIN UI-CASE / END UI-CASE or owned UI-IMPLEMENTATION blocks. Skip unchanged content, compare complete substantive fields and mapping unions, persist confirmed deltas and read them back. A changed obligation cannot inherit stale satisfaction. Update case files, matrices, dependencies and source hashes together. Execution evidence does not turn isolated fixtures into real hosted/provider/phone/private-push evidence.

Export through the supported plugin and verify canonical archive bytes. Wiki manifest lists publishable pages. The operator requires publishing the GitHub export to https://github.com/sharpninja/wordpairs.wiki.git after refresh-docs; preserve unrelated pages, record any publication-only link/asset transforms, verify the pushed commit and keep private runtime files out. This does not authorize pushing the application repository or submitting the contest. TR-DOCS-WIKIPUBLISH-042#WIKI-01..03 and TEST-WIKIPUBLISH-148 make this recurring publication contract authoritative in QBrain. Preserve all rejected/superseded hostile reports and refresh the HV hash index.