[vanedaltro]

A worktree relocation can commit its destination before the previous Location owner acknowledges settlement. The runtime must preserve that durable transition without emitting a successful CwdChanged observation when settlement is uncertain. Add a runtime/Store regression that compares acknowledged and unacknowledged settlement, verifies durable identity and hook suppression, requires recovery before further entry/idle-exit, and checks admission release without a delayed success hook after call completion and shutdown. The test uses a simulated lease owner; no production behavior, API, schema or native support floor changes.

Reconcile FileChanged acceptance after merged #85 and #88 in the same follow-up. Retain the final source-bound platform receipt and accepted-main composition, distinguish superseded historical receipts, and remove stale CI-pending ledger claims. The audit directly checks all 14 table regressions plus eight queue/lifetime/privacy/unknown-outcome cases in the actual Linux/macOS/Windows logs. Close only bounded FileChanged task 5.2; the full producer matrix, native enforcement/protocols, daily coding and binary editor remain open. Update delivery notes to this single active follow-up PR.

Verification:

• cargo test -p cyber-server --test location_activity: all 12 cases passed on macOS.
• Scoped Clippy for the changed test target with --no-deps -- -D warnings: passed.
• Behavioral negative control: allowing failed settlement to fall through executes the exact new case and fails with an unacknowledged transition emitted CwdChanged. Production source was restored, and the complete test target passed again.
• The Rust test file remains byte-identical to locally tested f7db7edb after current-main integration and evidence consolidation. It is the only Rust/Cargo/configuration/workflow input changed against main.
• Final combined revision: formatting and whitespace pass; strict OpenSpec 114 passed/0 failed; spec lint 0 errors/25 warnings; all retained FileChanged JSON receipts parse. Only task 5.2 changes checkbox status.
• Accepted FileChanged evidence: Verify FileChanged acceptance and specify directory admission #85 passed all 19 current-head checks, all three focused jobs, 5,504 Linux and 5,504 macOS workspace cases (21/23 skips), and 3,775 selected Windows cases (648 skips) plus metadata/migration/AppContainer checks. The actual merged tree equals the reviewed composition with accepted Run CwdChanged lifecycle regressions on Windows #88. These are accepted prior results, not claims about this PR's new current-head CI.
• The accepted Windows run reported one leaked-process warning in messages_cli::an_exec_session_refuses_messages_unless_it_accepts_them; cause unverified. Platform exclusions and intentional helper ignores are explicit in the receipt.
• Current-head hosted acceptance is required after resolving the genuine main task-ledger conflict and consolidating this evidence. Previous-head checks are superseded, not used as current acceptance. Native Windows/Linux execution of the new case and the full local Rust workspace suite were not run locally.

Task 5.3 stays open. The new case does not prove native confinement or uncertain Store-commit handling. Explicit Linux support and Setup/DirectoryAdded design-review gates are preserved.

Final current-head acceptance: all 16 checks passed. The named new Location-settlement case actually executes and passes on Linux, macOS and Windows. Broad Linux/macOS each pass 5,505 cases (21/23 skipped); Windows passes 3,781 selected cases (648 skipped), metadata (4), migration (9) and AppContainer (18). Windows reports one leaked-process warning in the messaging case already identified above; its cause remains unverified. All actual checkout logs bind to db443ee1e468e055fa040196948936eaff267afb, whose tree equals the reviewed head and current prospective merge. Source review found no blocking issue in the final nine-file diff. The full workstream and task 5.3 remain open.