feat: manage local development sessions

[adrianwebb]

Outcome

Adds trsd dev local lifecycle, atomic package overlays, rebuild/restart control, candidate freeze/verify receipts, and cleanup.

Work authority

• Work item / Issue: Implement managed development sessions and candidate promotion platform#152
• Proposal / decision: docs/dev-release.md in feat: define managed development and release architecture platform#153
• Assignment / checkpoint: User-directed implementation in the active Admin migration task
• Actor: Codex
• Human authority: adrianwebb
• Agent / capacity provider: Codex / OpenAI
• Exact base ref: staging at 3048aac
• Exact head ref: codex/development-sessions at 9e51144

Contributor mode (select one):

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

Plan

Consume SDK contracts, keep source/build processes unprivileged, delegate leases/routes to the manager, atomically switch only complete package generations, and bind promotion to frozen verification evidence.

Changes and commits

• 9e51144e520746806ce4912101bd6a19badd9cb4 adds the lifecycle, overlay synchronizer, generated docs/completions/schema, and command-boundary tests.

Verification

40 tests pass; full release verification and packed-install bin smoke pass locally. The integrated Platform smoke passed twice and left no process, link, or generation residue. Current GitHub failure is the expected dependency gate: published SDK does not yet export @treeseed/sdk/development.

Risk and rollback

Exact process groups and backed-up package links are restored on stop/failure. Roll back by stopping the session and reverting this commit; released manager reconciliation is not changed by the CLI.

Completion summary

CLI implementation is complete and locally green. It remains draft until SDK #92 publishes an RC and this branch hydrates that exact released range.

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.