jobtrackingapp/docs/automation/TODO.md

Autonomous roadmap follow-up

30 October AUTO-ACTIVATION-01: pre-Phase-10 preparation is conditionally closed at published handoff 5cb903b; proposed product baseline remains its parent fc5b9d3. Existing owner key/authentication and real-key isolation are verified. Activation remains blocked by the real command-running composite runtime. See ACTIVATION_01.md for current evidence and safe commands; the historical provisioning bullets below do not supersede that report.

AUTONOMOUS-ROADMAP-02 adds the normal-login route in SINGLE_USER.md. Single-user setup and native canary qualification are implemented; the real owner key, same-account sign-in and Phase 10 authorization remain owner actions. The separate-account provisioning below is now optional; single-user MXC qualification is the alternative.

Implementation checkpoints AUTO-00–08 are complete in the qualified scope described in ACCEPTANCE.md. The following are deliberately not authorized/completed by installing the controller:

• Finish current Pre-Phase-10 acceptance; owner records final accepted baseline and candidate-specific cleanup entry.
• Publish and independently verify the final pre-Phase-10 development ref (last verified remote still 994bf8f, local reported 5032ccb).
• Provision dedicated non-production runner/signing identities and protected control-plane installation; resolve/qualify native sandbox failure and actual read/egress/tool/resource boundaries.
• Qualify checkpoint-specific provider/browser/Python/PDF/security/preservation adapters, exact suite membership and synthetic runtime fixtures. Do not flip configured merely to bypass this gate.
• Review the packs' substage/finding branch preferences and resolve the exact authorized branch policy explicitly.
• Sign the proposed enabled policy, environment and roadmap grants plus phase10-development-entry only after explicit owner authorization. No real stage has run.
• Later, provide mandatory Product Review, provider rights, locale/native, four-concept homepage, security findings and release-evidence decisions at their actual gates.
• Optionally provision Task Scheduler under the qualified runner; no schedule is installed now.

Production/main merge remains outside this queue, requiring a separate explicit owner process.