@rasensio/aidlc-content 1.53.0 → 1.55.0

package/docs/roadmap.md

@@ -171,12 +171,15 @@ asks four questions, each a list with one choice marked recommended:
 
 Flags skip the questions: `--agent`, `--parallel`, `--cost-cap <usd|none>`, `--release
 <repo-script|merge-only>`. The answers go to `<git-common-dir>/aidlc/autopilot/config.json`, per
-machine and never committed, beside autopilot's `state.json`, `run.json`, `logs/` and `STOP` file.
+machine and never committed, beside autopilot's `state.json`, `run.json`, `logs/`, `STOP` file and, while paused, `paused.json`.
 
 **Watching and stopping.** `aidlc autopilot status` shows the active run and each item's step, pull
 request, CI failure count and last error. `aidlc autopilot stop` (or `/aidlc-autopilot-stop`) ends the
 run at its next step: nothing further is started, merged or released, and agents already running
-finish their item. `aidlc autopilot forget <instance>` stops tracking an item you finished or
+finish their item. `aidlc autopilot pause` freezes the run and its agents where they are —
+for closing a laptop, whose sleep would otherwise cut the agents' network and get their items parked —
+and `aidlc autopilot resume` carries on; a pause waits for a pass in progress rather than freeze a merge or
+release halfway. `aidlc autopilot forget <instance>` stops tracking an item you finished or
 abandoned by hand; a pull request merged by hand is noticed and dropped on its own. A rate limit
 from `gh` or the agent backs off five minutes, doubling to at most
 two hours. `aidlc autopilot tick --dry-run` prints every command one pass would run and runs only the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.53.0",
+  "version": "1.55.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -26,17 +26,17 @@
     "glossary.yaml"
   ],
   "engines": {
-    "node": ">=18.0.0"
+    "node": ">=22.13.0"
   },
   "license": "MIT",
   "dependencies": {
     "yaml": "^2.9.0"
   },
   "devDependencies": {
-    "@types/node": "^20.19.43",
-    "fast-check": "^3.23.2",
-    "typescript": "^5.8.3",
-    "vitest": "^4.1.11"
+    "@types/node": "22.15.32",
+    "fast-check": "4.9.0",
+    "typescript": "5.8.3",
+    "vitest": "4.1.11"
   },
   "scripts": {
     "build": "tsc",

package/skills/03-entry-point.md

@@ -70,6 +70,7 @@ If `.aidlc/state/` is empty or missing, offer just three options: start somethin
 | Browse / promote the roadmap | Follow the **aidlc-roadmap** skill (browse/promote flow) |
 | Start a roadmap item in a new worktree | Follow the **aidlc-roadmap** skill (**Promote into a new worktree**). It ends by handing off to a new session; do not start the phase here |
 | Work the backlog in the background ("do the next 3 items", "do all the items") | Follow the **aidlc-autopilot** skill |
+| Pause or resume autopilot ("I'm closing the laptop") | Follow the **aidlc-autopilot** skill (step 6) |
 | Stop autopilot | Follow the **aidlc-autopilot-stop** skill |
 | Show status | Summarize each instance from its state files — name, template, current phase, completion %, and whether it looks stalled. When the roadmap is non-empty, append the per-status counts (e.g. "roadmap: 3 inbox, 5 backlog, 12 done") |
 | Review an artifact | Follow the **aidlc-review** skill |

package/skills/84-autopilot.md

@@ -1,9 +1,9 @@
 ---
 name: aidlc-autopilot
-description: Works the next backlog items in the background — "do the next 3 items" or "do all the items" — and reports how to watch and stop
+description: Works the next backlog items in the background — "do the next 3 items" or "do all the items" — pauses and resumes that run, and reports how to watch and stop
 phase: implementation
 priority: 60
-trigger: When the user asks to do, work, build or ship the next n backlog items, or all of them, without supervising each one
+trigger: When the user asks to do, work, build or ship the next n backlog items, or all of them, without supervising each one — or to pause or resume that run
 ---
 # Autopilot
 
@@ -28,13 +28,17 @@ The CLI does the work. This skill starts it and says how to watch and stop it. D
 4. **If it refuses:**
    - *not set up* → tell the user to run `aidlc autopilot setup` in their own terminal. It asks which agent to use and what it may do; that choice is theirs, so do not pick it with flags on their behalf.
    - *a run is already active* → report its pid and offer `aidlc autopilot stop` first.
+   - *the run is paused* → offer `aidlc autopilot resume`.
 
-5. **Report**, in four short lines: what it is doing (how many items), the log file it printed, `aidlc autopilot status` to watch, and `/aidlc-autopilot-stop` (or `aidlc autopilot stop`) to stop.
+5. **Report**, in five short lines: what it is doing (how many items), the log file it printed, `aidlc autopilot status` to watch, `aidlc autopilot pause` before the machine sleeps (`aidlc autopilot resume` after), and `/aidlc-autopilot-stop` (or `aidlc autopilot stop`) to stop.
+
+6. **Pause and resume.** When the user is stepping away or closing the laptop, run `aidlc autopilot pause`; when they are back, `aidlc autopilot resume`. Report what each printed. If pause says a pass is in progress — a merge or a release — run it again a minute later rather than stopping the run.
 
 ## What the run does on its own
 
 - Takes items in `aidlc roadmap next` order. Builds at most two at once, and never more than the count asked for.
 - Parks an item (moves it to `hold/` with a reason) when its agent stops short, when CI fails twice, or when it passes the cost cap.
+- An agent that loses the network exits, and is parked. Sleep cuts the network, so a run on a laptop needs `aidlc autopilot pause` first: it freezes the run and its agents where they are, and `aidlc autopilot resume` carries on.
 - Before each merge, brings the item's branch up to date with main and waits for CI on the new head. A conflict with main goes back to the item's agent, twice at most, then the item is parked. A pull request someone merged by hand is dropped from tracking.
 - Halts the merge queue when a step fails. Running `aidlc autopilot run` again retries a failure that came before the merge; a failed release is for a person — `aidlc autopilot status` shows the error. `aidlc autopilot forget <instance>` stops tracking an item finished by hand.
 - Ends when the asked-for items are each released or parked, or, with `--all`, when nothing is ready and nothing is in flight.
@@ -42,4 +46,4 @@ The CLI does the work. This skill starts it and says how to watch and stop it. D
 ## Exit Criteria
 
 - `aidlc autopilot run` has started a run, or its refusal has been reported with the one command that fixes it
-- The user knows where the log is, how to watch, and how to stop
+- The user knows where the log is, how to watch, how to pause, and how to stop

package/skills/85-autopilot-stop.md

@@ -3,7 +3,7 @@ name: aidlc-autopilot-stop
 description: Stops the background autopilot run — nothing further is started, merged or released
 phase: implementation
 priority: 60
-trigger: When the user asks to stop, halt or pause autopilot or the background backlog run
+trigger: When the user asks to stop or halt autopilot or the background backlog run
 ---
 # Stop Autopilot
 
@@ -11,6 +11,8 @@ trigger: When the user asks to stop, halt or pause autopilot or the background b
 
 Stop the background run in one step.
 
+Stopping is not pausing. A user stepping away — closing the laptop — wants `aidlc autopilot pause`, which freezes the run and its agents where they are until `aidlc autopilot resume` (see the **aidlc-autopilot** skill). A stopped run leaves its agents running, and on a sleeping laptop they lose the network, exit, and have their items parked.
+
 ## Instructions
 
 1. Run: