@rasensio/aidlc-content 1.91.0 → 1.94.0

package/docs/cost-tracking.md

@@ -107,6 +107,14 @@ hook installed there is no data, and — the failure that produced two bugfixes
 exactly like an idle one. Hence `capture.log` and `lastCaptureError`, so "captured nothing" can be told
 apart from "was never asked".
 
+**A command that refuses records says so itself.** For a month, `aidlc cost sync` refused the same 124
+records every run, logged each as a bare `validation-rejected` with the reason dropped, and printed
+nothing. The note on `aidlc cost` fired every time, pointing at a log that did not say what failed, so
+the one warning meant to say "capture has gone dark" was trained into noise. Now sync counts what it
+could not append, keeps the ledger's own reason (`invalid cursor`), and prints one `rejected:` line per
+reason. A failed write is logged as `append-failed`, not as a refusal. The count is per record, not
+per attempt, because the attribute and backfill passes both retry a refused Claude Code record.
+
 **How attribution works**, because this is where the surprises are. A usage record gets an instance and
 a phase by intersecting two windows:
 
@@ -165,6 +173,11 @@ Everything is under `packages/cli/src/cost`:
   array order, because array order is only right while response groups stay contiguous and the
   transcript format is internal to Claude Code. If contiguity broke, inferring would send the cursor
   backwards and re-charge a span of transcript.
+  Every provider's output must fit the ledger's closed schema, and `cost-provider-ledger-contract`
+  tests exactly that. It exists because Codex wrote its cursor as `<rollout>#<n>` and the ledger's
+  cursor rule has no `#`: every Codex record was refused, by sync and live capture alike, while each
+  side's own tests passed. The cursor is now `<rollout>:<n>`. The fix went in the provider, not the
+  rule, so ledger lines a new `aidlc` writes stay readable by every older one already installed.
 - `context.ts` — resident-context reading for `aidlc cost context`. Reads token counts only; never
   copies transcript content, so nothing here can carry a prompt or a secret into a report.
 - `dedupe-history.ts` — the corrective pass over existing ledgers. It distinguishes a *proven

package/docs/roadmap.md

@@ -88,6 +88,14 @@ worktree flow disagreed — one linked the item by hand, the other left it in `b
 listed items and never opened as a path, and an item that already has a `promoted_to` is refused before
 anything is created. The move is left uncommitted; committing it is the caller's.
 
+**A start that fails part way leaves nothing behind.** An item with no `promoted_to:` line gets one.
+If the link still fails, `aidlc start` removes the worktree, branch, registry entry and instance
+directory it made, and leaves the item where it was with its text unchanged, so the same command
+works once the cause is fixed. It removes only what that run created, and names anything it could
+not remove. Why: on 2026-10-10 two agent-written items had no `promoted_to:` line. The start failed
+at the link but kept everything it had made, and the retry failed with "already registered".
+Recovery took `git worktree remove`, `git branch -D` and `aidlc doctor` for each item.
+
 **The instance's copy is the fallback when an item loses its link.** When no item names a completing
 instance, `roadmap-done` reads the instance's own `roadmap-item.md`. If that copy's `promoted_to`
 names the instance, every open item with the copy's `id` and `promoted_to: null` is linked and moved
@@ -105,22 +113,31 @@ that picks has no way to write. `priority` is an ordinary extension field (a ran
 project declares in `roadmap.item_fields`.
 
 **Seeing the roadmap** is `aidlc roadmap view`: one self-contained HTML page, opened in the browser,
-with two tabs. **Board** has a column per status — backlog in `roadmap next` order with ranks and ready
-items marked, the latest 20 done items with the rest behind a control, the reason on each hold card —
-and each card links to its item file, its instance folder and retrospective, and its pull requests on
-GitHub when the branch and `origin` are known. Clicking a card opens its executive summary, its
+with three tabs. **Board** has a column per status — backlog in `roadmap next` order with ranks and ready
+items marked, the latest 20 done items with the rest behind a control, hold split into Parked, Declined
+and On hold with the reason on each card — and each card links to its item file, its instance folder and
+retrospective, and its pull requests on GitHub when the branch and `origin` are known. Each open card
+says how long it has sat in its state ("in backlog 9 days", from its last history entry), and inbox,
+backlog and in-progress cards past 30 days are marked stale. Cards and map boxes share a look per status:
+inbox dashed, backlog gray, in progress yellow, done green, hold dotted and faded, with the status word
+kept in each box. Clicking a card opens its executive summary, the rest of the item's text, its
 dependencies and a copy button for its next command (a triage prompt, start in a worktree, rank, or
-`aidlc continue`); the page itself runs nothing. **Dependencies** is a zoomable map of the `depends_on`
-chains, one labelled group per cluster of linked items, packed side by side: each item under its first
-dependency, a link to anything not yet done drawn red and dashed, an unknown id drawn as a red dashed
-node (a typo there silently blocks `roadmap next`), and items with no dependency hidden behind a
-toggle. Each tab has its own status chips, presets (Active work, Needs a decision, Shipped, Parked,
-Everything) and Ready/Blocked toggles. The Board opens on inbox, backlog and in progress, with done and
-hold folded into rails you click to reopen; Dependencies opens on every status but hides clusters that
-are entirely done ("Open chains only"), and dims what its filters exclude rather than removing it. The
-tab and both tabs' filters live in the URL hash, so a reload or a shared link reopens the same view.
-`/` focuses search, `1` and `2` switch tabs, `Esc` closes the panel or clears the search. The page
-opens light; the header button switches to dark, and the browser remembers it across regenerations. The page is written to `<git-common-dir>/aidlc/roadmap.html` — outside every working tree, so
+`aidlc continue`); the page itself runs nothing, and links in item text show as text. **Dependencies**
+is a zoomable map of the `depends_on` chains, one labelled group per cluster of linked items, packed side
+by side: each item under its first dependency in a box that wraps its whole title, a link to anything
+not yet done drawn red and dashed, an unknown id drawn as a red dashed node (a typo there silently blocks
+`roadmap next`), items with no dependency hidden behind a toggle, and a status key in the corner. Done
+boxes start hidden behind a "done hidden — show" switch, and hovering a box lights its whole chain.
+**Shipped** lists done items by week, newest first, with the count each week and a running total.
+Board and Dependencies each have their own status chips, presets (Active work, Needs a decision,
+Shipped, Parked, Everything) and Ready/Blocked toggles. The Board opens on inbox, backlog and in
+progress, with done and hold folded into rails you click to reopen; Dependencies opens on every status
+but hides clusters that are entirely done ("Open chains only"), and dims what its filters exclude rather
+than removing it. The tab, both tabs' filters and the hide-done switch live in the URL hash, so a reload
+or a shared link reopens the same view. `/` focuses search, `j` and `k` move to the next and previous
+item (the open panel follows), `1`, `2` and `3` switch tabs, `Esc` closes the panel or clears the
+search. The page opens light; the header button switches to dark, and the browser remembers it across
+regenerations. The page is written to `<git-common-dir>/aidlc/roadmap.html` — outside every working tree, so
 it is never committed and every worktree shares one copy — or wherever `--out` says; `--no-open` only
 writes it. Nothing rebuilds it on a move: until 2026-10-06 every move rewrote two committed Mermaid
 graphs, so every promotion left two shared generated files modified in whichever checkout ran it.

package/package.json

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