Update autopilot workflow and documentation for project cycle completion

- Modified the existing-code workflow to automatically loop back to New Task after project completion without user confirmation.
- Updated the autopilot state to reflect the current step as `done` and status as `completed`.
- Clarified the deployment status report by specifying non-deployed services and their purposes.

These changes enhance the automation of task management and improve documentation clarity.
This commit is contained in:
Oleksandr Bezdieniezhnykh
2026-03-29 05:02:22 +03:00
parent 0bf3894e03
commit aeb7f8ca8c
20 changed files with 1360 additions and 12 deletions
@@ -217,22 +217,18 @@ After deployment completes, the existing-code workflow is done.
**Re-Entry After Completion**
Condition: the autopilot state shows `step: done` OR all steps through 13 (Deploy) are completed
Action: The project completed a full cycle. Present status and loop back to New Task:
Action: The project completed a full cycle. Print the status banner and automatically loop back to New Task — do NOT ask the user for confirmation:
```
══════════════════════════════════════
PROJECT CYCLE COMPLETE
══════════════════════════════════════
The previous cycle finished successfully.
You can now add new functionality.
══════════════════════════════════════
A) Add new features (start New Task)
B) Done — no more changes needed
Starting new feature cycle…
══════════════════════════════════════
```
- If user picks A → set `step: 8`, `status: not_started` in the state file, then auto-chain to Step 8 (New Task).
- If user picks B → report final project status and exit.
Set `step: 8`, `status: not_started` in the state file, then auto-chain to Step 8 (New Task).
## Auto-Chain Rules