Operations¶
Operational documentation covers release canaries, workflow terminal-state behavior, conservative local cleanup, downstream validation, and the curated roadmap for rollout work, autonomous mode, and PR recovery readiness.
Runbooks and references¶
| Document | Use it for |
|---|---|
| v0.10.6 Canary Evidence | Evidence contract and current access limitations for install, update, default-workflow, and Azure DevOps checkout validation without leaking secrets. |
| Hygiene Cleanup | Safe disk cleanup for stale worktrees, detached Cargo targets, and old session artifacts. |
| Workflow Publish and Finalize Resilience | Idempotent publish/finalize behavior for no-diff, already-merged, closed-after-merge, and existing-PR states. |
| Prompt Delivery Downstream Validation | Simard/RabbitHole-style delegated workflow validation against prompt delivery behavior. |
| Operational Roadmap | Curated backlog for fleet rollout, Azure DevOps E2E, release contract monitoring, and workflow observability. |
| Auto Mode | Autonomous multi-turn execution. |
| Auto Mode Safety | Safety guardrails and approval boundaries for autonomous execution. |
| PR Recovery Readiness | Existing-PR recovery readiness contract. |
Operating principles¶
- Prefer dry-run and evidence first.
- Treat already-terminal workflow states as success only when they are positively identified.
- Reject ambiguous cleanup candidates instead of guessing.
- Record command shapes and outcomes, not credentials, token values, full environments, or private prompt content.