@rasensio/aidlc-content 1.58.0 → 1.60.0

package/docs/roadmap.md

@@ -108,7 +108,15 @@ also lists every unranked backlog item, so one sitting last is visible rather th
 **Parking from an instance** is `aidlc roadmap park <instance> --reason "<why>"`: it moves the item
 promoted to that instance into `hold/` with a `parked — ` reason. It exists for unattended mode's hard
 stops — see [Skills and platforms](skills-and-platforms.md) — where the agent works in a worktree but
-the item's status lives in the primary checkout.
+the item's status lives in the primary checkout. `aidlc roadmap park --item <item> --reason "<why>"`
+parks an open item by file name or id instead, whatever its `promoted_to` — for an item no instance
+was ever linked to, such as one whose `aidlc start` failed.
+
+**An item keeps its `promoted_to` when it is parked.** Moving it back from `hold/` to `backlog/` by
+hand leaves the link set, and `aidlc start --roadmap-item` refuses an item that is already promoted.
+`aidlc roadmap next` applies the same rule: it leaves such an item out of the order, warns about it,
+and lists it under `skipped` in `--explain` and `--json`, naming the instance. Clear the
+`promoted_to` line to make it ready again.
 
 Keep the raw idea count around a dozen. At the cap, promote or drop before capturing anything new. A
 completed instance queues **at most two** follow-up items and records the rest in its own
@@ -136,7 +144,10 @@ Each item goes through these steps:
 1. **Pick.** `aidlc roadmap next` names the next ready backlog item.
 2. **Build.** `aidlc start … --worktree --roadmap-item <item>` creates the instance in its own
    worktree, then the configured agent runs there with `AIDLC_UNATTENDED=1`. The agent follows the
-   unattended rule and stops at the release boundary, or parks the item on a hard stop.
+   unattended rule and stops at the release boundary, or parks the item on a hard stop. A start that
+   fails parks the item with `parked — could not start: <error>` and autopilot goes straight on to
+   the next ready item; the parked one does not count toward `--items`. Retrying the same item every
+   pass is what held a whole `--all` run on one item for five hours.
 3. **PR and CI.** Autopilot pushes the branch and opens the pull request. Green checks queue it;
    a failure relaunches the agent once with the failing checks, and a second failure parks the item.
 4. **Up to date with main.** Before merging, autopilot merges `origin/main` into the branch in the
@@ -151,8 +162,8 @@ Each item goes through these steps:
    nothing is retried — a half-finished release is for a person.
 
 At most two items build at once, and never more than you asked for. Autopilot never moves anything
-between `inbox/`, `backlog/` and `hold/` except to park what it is building, and never edits a rank or
-a dependency: deciding what is agreed work stays a person's job.
+between `inbox/`, `backlog/` and `hold/` except to park what it is building or could not start, and
+never edits a rank or a dependency: deciding what is agreed work stays a person's job.
 
 **Setup** comes first, once per machine. A plain `aidlc init` ends by asking "Set up autopilot now?"
 (default no); `aidlc init --autopilot` skips that question, and `aidlc autopilot setup` asks the same

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc-content",
-  "version": "1.58.0",
+  "version": "1.60.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",