[adrianwebb]

Outcome

Prevent disabled retained development selections from repeatedly restarting healthy source services. An active completed boot worker now reads authoritative host component enablement before deciding whether recovery is needed.

Work authority

• Work item / Issue: Disabled development targets repeatedly restart healthy source services during reconciliation #883; coordination Coached Atlas delivery continuation — agent products, layout and live data sdk#428
• Proposal / decision: Operator-authorized owning-boundary repair under the coached development maintenance plan.
• Assignment / checkpoint: Authenticated Chrome Atlas returned repeated HTTP502 during original resume-service restarts on dev-5007e344-493.
• Actor: Codex integrator through adrianwebb.
• Human authority: Restore stable Atlas testing while preserving existing services, selections, credentials and acceptance obligations.
• Agent / capacity provider: Integrator boundary repair; further delegation is held after two separately retained clock failures pending Agent495 diagnostic adoption.
• Exact base ref: staging29fb1ca9c6a439595c976641d69899744bceb5fb
• Exact head ref: codex/development-disabled-resume644576a6336157e5c9d92991cd1aabd24508ddef
• Exact head tree: d0a837e1894b7d43cb7d5579187054a114b633c3

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Reproduce the supervisor/CLI mismatch before repair. Retain disabled candidate selections while excluding them from automatic recovery; preserve enabled failure recovery. Verify original native process identity and persisted authority, complete native owner suites and coded scenes before checked adoption and repeated live browser validation.

Changes and commits

• 3e87636: test-only regression extends the existing selected stopped-candidate assertion. Healthy Admin plus three disabled AI targets must not request global recovery. Re-enabled stopped targets, enabled failed peers, unspecified selections, original generations and input immutability remain checked.
• edd2164: test-only native Docker/process and original DevelopmentSessionStore/strict HostConfiguration read coverage. Three unchanged reads retain healthy process identity and exact saved bytes. Existing component scene and verifier registry select the native case.
• 644576a: bounded development-boot repair uses existing host configuration and the existing AI target-to-component mapping. No configuration schema, status model, runner or execution path is added.

Verification

Original journal shows the manager stopping/restarting the resume service roughly every minute; its cgroup kills package watchers, UI/Core rebuild and Admin restarts underneath the authenticated browser. Public host configuration explicitly disables ai-inference, ai-training and ai-lab; the existing CLI skips those components while the old supervisor counts them as needing recovery.

Focused BASE RED:4passed/1intended expected-false/got-true failure. An earlier preparation script indentation guard failed before changing tests; the resulting unchanged baseline pass is retained and is not credited as RED. Final focused owning checks:29passed, zero failed/pending. Strict TypeScript and source-shape checks pass.

Native Verify https://github.com/treeseed-ai/deployment/actions/runs/39183851536 passed on tested merge df91cab. Independently audited fresh complete prerequisites:1343Deployment and200Reviewer checks, zero failed/skipped/todo;265coded steps,265assertion receipts and57source-file digests match the exact candidate. Selected archive assets match source; archive SHA256 a86b714175eed78d315f360118fb32b90a28ac8e43ce39500e99dfbf49f49de5; report SHA256 acf2943bd7560f8000fd681f1c8e6f4ef11ada3c4f1678ff8fecd086b9a222d5. The compiled boot module matches the private source build at SHA256 b2a2a0871aabf07869c615b36c0f8a482397d69172e076d50fb2b31cd06a1404.

Backup39183851370, fault qualification39183851298, secret custody and uninstall checks all passed. Artifact ZIP digests and tested merge parents/tree were verified. The operator audit initially used a multi-ref FETCH_HEAD incorrectly and safely rejected it; split protected-head and merge-ref fetches retained the same assertions and passed without changing the candidate.

Checked staging adoption and actual systemd/browser-cycle proof remain pending. Component proof is not a formal managed acceptance pass.

Risk and rollback

Disabled selections remain stopped and retain their modes/generations. Explicit enabled failures and missing component entries still request recovery. Strict configuration read failures prevent restart. Existing holds, stopped-session rules, unprivileged owner custody and fixed installed worker remain unchanged. No timer disabling, broader stop, session expiry, certificate bypass, allowance increase or unrelated cleanup. Revert through ordinary checked delivery if needed; do not edit installed supervisor files manually.

Completion summary

Ordinarily merged to staging0f09f0672e6658d58d7e39647e63b943c28c5cfe, exact tested tree retained. Supported host activation dev-1792373670254-e43e2170 verified all266compiled modules against the archive and all three selected daemon entrypoints. Three subsequent real development reconciliation cycles retained the same resume InvocationID and healthy target generations, guest93e0584b, host configuration and modes. Authenticated Chrome assignment→exact Engineer artifact works again. Remaining metrics/agent-detail failures are separate under SDK428; no formal acceptance pass.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.

Refs #883.