[vanedaltro]

Session deletion can remove the history needed to determine whether legacy Setup already ran. Document a complete owner-resolution candidate for S1 review before marker/schema/init implementation: retain the Store-lifetime epoch and exact stored directory key; distinguish positive historical evidence from unproven history; and let the owner authorize a new attempt or explicitly continue without dispatching Setup. Specify the legacy root-creation compatibility exception, CLI/API proposal, revision fencing, request binding, retry-after-deletion behavior and adversarial acceptance cases.

This publishes a candidate, not an accepted policy or implemented capability. S1 remains unchecked, and recording or mechanically merging this document does not authorize the proposed behavior. The full original Setup contract remains required until the complete migration/support decision is reviewed. Native Linux support and DirectoryAdded review gates remain unchanged.

Also retain merged #90's source-bound Store acceptance receipt and reconcile its implementation/delivery notes. The exact named Store/runtime regressions execute and pass on Linux/macOS/Windows; the tested tree equals accepted main. Linux/macOS pass 5,508 cases (21/23 skips), Windows passes 3,785 selected cases (647 skips) plus metadata/migration/AppContainer checks, and all 16 source-revision checks pass. The Windows messaging leaked-process warning is recorded with its cause unverified. These are accepted #90 results, not claims that this new documentation tree ran the executable suites.

Verification:

• Strict OpenSpec validation: 114 passed, 0 failed.
• Spec lint: 0 errors, 25 warnings.
• Whitespace checks pass; retained receipt JSON parses and its checkout/head/accepted-tree bindings agree with the independently inspected original logs and merge.
• No Rust/Cargo/configuration/workflow inputs change against current main, and no task checkbox changes to complete. Executable tests were not rerun for this documentation-only follow-up; current documentation CI is required.

The full plugins/hooks, daily-coding and binary-editor goal remains incomplete. This change preserves the required policy decisions and provides concrete review material for the next implementation step.

Final documentation verification: OpenSpec and Changes checks passed; six code/build jobs were intentionally skipped by the documentation-only filter. The actual OpenSpec checkout is d6d3e50d8810e5df0d88da7368048527b46bd69b, tree d75eff79b944c0825cf601d912431560dddf7ee9, equal to the reviewed head and final prospective merge. The hosted log confirms 114/0 strict validation and lint 0 errors/25 warnings. Final documentation review found no blocking issue. Publishing this candidate leaves S1 unchecked and does not select the proposed compatibility policy or authorize dependent implementation.