Settings ownership P42: command readers (E2992 minimum v8) #2996

Parent epic: #2992

This is the approved P04 delivery unit of the settings-owner plan.
Technical consensus is complete. Implementation awaits explicit user plan review and coordinator authorization; no branch or product change has started.

Situation and intended behavior

The epic centralizes settings operations for app and CLI/daemon while preserving source composition, authorization, failures and durability. This child implements only its approved phase below, after its dependencies have landed.

Replace productive direct state reads and physical loaders with fallible current_snapshot or the exact owner fresh-authority projection. ac_discovery:1721 and entity_creation:4390 also bypass State today. Every user operation propagates unavailable/invalid through its existing Result; void background hooks log the existing operational error and skip that action. Do not default missing owner to settings defaults. Keep ordinary try_state absence behavior when no state exists; a present Invalid owner is an error, not the absence branch. Keep filesystem identity/authorization checks at point of use. Settings data is obtained before unrelated locks. No new resource domain is adopted.

Only listed files may change. Preserve unrelated formatter debt and user data. Shared-file handoff is merged main, owned by the next authorized phase; never private scratch.
Main must compile/test using only landed code. Before P20 the new authority stays inactive with legacy transactional behavior; P20 removes staging and activates only the completely migrated set.
No intermediate cut publishes a second active memory authority or promises sole-writer memory freshness while legacy writers remain.

Approved identity and ownership

• Phase: P04
• Class: design-bearing
• Owner: ac-dev-rust-v5
• Depends on phase IDs: P03
• Files: 8
• Canonical phase: D:/0_repos/AgentsCommander_iac/.ac/plans/2992-settings-owner/P04-v5-readers-commands.md
• Phase-SHA256: 38E346C19E77675FB05DED8C818EEDE3728B75FC241B20E97749BDBE4E4F1650
• Master: D:/0_repos/AgentsCommander_iac/.ac/plans/2992-settings-owner/plan-v5-settings-owner.md
• Plan-SHA256: C142BB7BF5EDC96C5E88AA70A5A217B54D37E41F2E0B04ABD4A4AD9D8A69B0A5
• Source reference: f6e5d08882ba9b208b56afe1fec44efb04925205

The canonical phase file is the sole cold-start implementation specification. This issue is tracking and a review summary, not permission to make new design choices. Child/branch/execution identity belongs in the separate coordinator mapping; no certified Markdown is edited.

Planned modified files

• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/ac_discovery.rs
• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/co_managed.rs
• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/entity_creation.rs
• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/pty.rs
• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/repos.rs
• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/resource_monitor.rs
• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/role_templates.rs
• D:/0_repos/AgentsCommander_iac/.ac/room-18-ac-dev-team-v5/repo-AgentsCommander/src-tauri/src/commands/screenshot.rs

No tracked source files are added or removed. The phase's explicit preserve sets, protected behavior and budgets remain binding; P01 alone has the approved constructor-only mechanical exception.

Acceptance and verification (future work)

All following cases are FUTURE, owner-executed tests using existing inline modules, tempdirs, saver fault seams, controlled clocks/barriers. Prefix new cases e2992_p04_ in each named module. No generic harness/dependency or runtime execution during planning. Execute focused commands only after the Cold start block has initialized R/EVIDENCE and captured the actual authorized phase base.

From R/src-tauri after authorization:

cargo +1.98.1 test --locked --lib --bins e2992_p04_ -- --list > "$EVIDENCE/focused-list.txt"
rg "e2992_p04_" "$EVIDENCE/focused-list.txt"
cargo +1.98.1 test --locked --lib --bins e2992_p04_ -- --nocapture

Every named case must appear in the list and execute; zero matches is failure, not PASS. Full applicable regression and integration guards below remain mandatory.

Preserve existing source/permission/error contracts. Failed, absent or timed-out evidence stops delivery and returns the exact discrepancy to architecture; no widening of the frozen file table.

Execute the phase's complete local verification, structural and exact-head CI gates from its canonical file only after authorization. Every dependency must be merged into main; one sequential phase/PR at a time. A phase PR closes only this child. The epic remains open through all phases and the requested final shipper build. No installation, release/version bump or other persistence-domain migration is authorized.