@warnyin/sdlc 0.7.0 → 0.9.0

package/CHANGELOG.md

@@ -1,228 +1,274 @@
-# Changelog
-
-## 0.7.0 (2026-09-14)
-
-- **Fix (next)**: with several changes open, `/sdlc:next` gave every one of them its own
-  next command and gave the change this session was actually on no precedence — so the
-  agent walked off onto someone else's change mid-flight. Underneath, the active-change
-  pointer was one project-wide file: two sessions overwrote each other's focus, and hooks
-  recorded one session's telemetry against the other's change. The pointer is now kept per
-  session at `sdlc/.state/sessions/<session-id>.json`, with `.state/active.json` still
-  written as the project-wide fallback. `status` lists the current change first and marks
-  it `← this session`, or `← last set for project` when this session has not set one; other
-  changes are marked `(not this session)` only when this session set its own pointer.
-  `status --json` gains `current: {id, source}` and keeps `changes` in their original
-  order. `/sdlc:next` answers for the marked change, and a human who names a different one
-  wins. Hooks take the session from their stdin `session_id`; shell-run commands read
-  `CLAUDE_CODE_SESSION_ID`, which Claude Code does not document, so when it is absent — and
-  in every other tool — the project-wide pointer answers exactly as before. A session's own
-  pointer does not survive resume or `/clear`, which start a new session id. (#4)
-- **Fix (pointers)**: a session id now becomes a filename, so it is refused — not stripped —
-  by the same single-safe-segment rule as change ids; the steering-seen file uses
-  `nosession` for an unsafe id instead of aliasing `a/b` onto `ab`. Pointer reads and
-  writes check that the real path is where it claims to be, so a link planted at `.state`,
-  `.state/sessions` or the pointer file itself — a dangling one included — cannot carry a
-  write out of the project. `set-active` now exits 2 for an id that is not an open change
-  rather than writing a pointer that is then ignored, and reports a refused write instead
-  of claiming success; `archive` removes the pointers naming the change it ships.
-  Journal and `phase.json` writes do not have this check yet. Downgrading to 0.6.0 leaves
-  `.state/sessions/` unread and harmless on disk.
-
-## 0.6.0 (2026-09-10)
-
-- **Fix (auto)**: the Confirm step of an unattended run showed the scope it had settled on
-  and asked for approval, but never how it got there — so a derivation that searched the
-  wrong thing was approved as readily as a right one. It now shows, per scope item, the
-  command that established it and what that command returned; a summary of what a search
-  found does not count. Evidence that searched a term the request did not name is flagged
-  with both terms side by side, a narrowing the request never asked for (a folder pattern,
-  a naming convention) becomes its own refusable item, and an exclusion made on an empty
-  result must name the pattern searched — finding nothing is a claim about the pattern, not
-  a fact about the candidate. This is doctrine the model follows, checked by tests on the
-  doctrine and by the eval rubric; the confirmation is written at runtime, so nothing gates
-  it mechanically. (#2)
-- **Fix (journal)**: telemetry the hooks append lived in `sdlc/changes/<id>/journal.ndjson`,
-  which git tracks, so merely opening a project modified a shared file no human touched —
-  `git pull` and branch switches refused to move until someone discarded it, and two people
-  on one change conflicted on the appended tail for a reason unrelated to the change under
-  review. While a change is open, telemetry now goes to `sdlc/.state/journal/<id>.ndjson`;
-  `.state/` is already git-ignored in every installed project, so no new `.gitignore` entry
-  and no `git rm --cached` is needed. `archive` seals the journal into the shipped change
-  folder in one write at ship, so `/sdlc:observe` still reports cost and verify history for
-  changes a teammate shipped. Projects installed before this keep their in-tree journal: it
-  is read alongside the new stream and consumed at ship, so no recorded event is lost.
-  Two interim states worth knowing: a project that runs `update` mid-change carries telemetry
-  split across the two files until that change ships, and downgrading to 0.5.2 afterwards
-  leaves anything under `.state/journal/` unread by the older code — it is still on disk,
-  but that version does not know to look there. (#3)
-
-## 0.5.2 (2026-08-25)
-
-- **Fix (delta)**: a `### MODIFIED Requirement:` body replaces the requirement wholesale,
-  so one that carried over only some of the spec's scenarios dropped the rest in silence —
-  no error, no warning, `spec merged` printed either way. Both shapes are now reported:
-  the scenario name gone from the replacement body, and the name surviving while WHEN/THEN
-  clauses it promised have no counterpart (the one a name-level comparison cannot see).
-  `archive` prints the report before it writes a byte and counts it in the summary;
-  `validate` reports the same at warn level, so the loss is visible while the change folder
-  is still readable rather than after ship archived it. A warning, never an error — removing
-  a scenario is sometimes the point of the change, and only the silence was ever the bug.
-  A reworded clause reports the same as a deleted one: nothing mechanical can tell "said
-  better" from "promises less". Cosmetic churn — indentation, bullet marker, clause order,
-  heading case, whitespace — is normalized away and never warns. (#1)
-
-## 0.5.1 (2026-08-25)
-
-- **Fix (cost)**: `costUsd()` never charged cache-write tokens, the highest-rate of
-  the four classes the usage parser collects. Every cost `/sdlc:observe` and the
-  session summary have printed was therefore low. A model priced without a
-  `cacheWrite` rate now charges nothing for that class rather than inferring one from
-  `input` — the module's rule is never to guess a price, and a guess reports as
-  confidently as a known rate. Existing journalled costs are left alone: backfilling
-  would rewrite history from a rate that was not in force at the time.
-
-## 0.5.0 (2026-08-25)
-
-- **`--auto` on every pipeline stage.** `/sdlc:auto` already ran the whole pipeline,
-  but it stopped at every escalation — so you were pulled back in three or four times
-  per change and typed each stage anyway. Now all seven stage commands take `--auto`:
-  the run gathers what it needs, confirms once, and goes to ship. The confirmation is
-  decidable item by item — scope as understood, the tier and why, every ambiguity with
-  the assumption to be acted on, and each escalation as its own refusable line, the
-  ship row naming the hard-floor surface it covers instead of hiding behind a general
-  "run without me". Nothing is written before you confirm, down to the active-change
-  pointer, so declining leaves the repository untouched. The approval covers that run
-  only — not config, not the next change, not a resume. Anything outside what you
-  confirmed still stops and asks.
-- Escalations passed unattended are journalled, counted by `/sdlc:observe` as
-  `unattended×N`, and listed in the digest: the record shows where a human would
-  normally have stood and, that run, did not.
-- **Verify and review outcomes now record how they were produced** (`mode=panel|solo`).
-  A journal that says "verify passed" hides the thing a reader most needs later —
-  whether that verdict came from independent reviewers or from the same loop that
-  wrote the code. `observe` marks such changes `self-judged`, and the digest must name
-  self-produced outcomes. Absent provenance reads as unknown, never as `panel`, so
-  older journals are not retroactively dressed up as independently reviewed; where
-  provenance is mixed, the weakest link decides.
-- Where a panel cannot run, the playbooks now say to judge in the main loop and record
-  that — not to skip the stage. A review that never happened is worse than one
-  labelled honestly.
-- The constitution gains a hard rule: human-written text SHALL NOT reach a shell as an
-  argument. It is the defect that got past two separate gates in 0.4.0.
-
-## 0.4.0 (2026-08-25)
-
-- **New stage command `/sdlc:feedback`** — reports a bug, a rough edge, or a missing
-  feature in the framework itself to `warnyin/warnyin-sdlc`, from inside the session
-  where you hit it. It collects the context a maintainer triages by (framework and
-  Node version, OS, tool adapter, active change id and status), redacts it, shows you
-  the complete draft, and files it only after you approve. Submission goes through
-  `gh`; when `gh` is missing, logged out, or authenticated only against an enterprise
-  host, you get a prefilled issue URL instead — a normal path, not an error.
-  Nothing is attached automatically: no logs, no journal, no diff. Redaction is a
-  rule list rather than a guarantee, and the playbook says so — your eyes on the
-  draft are the control.
-- Human-written text never reaches a shell as an argument: the body travels over
-  stdin, while the title and the duplicate-search keywords are written by the agent
-  under a length and character allow-list instead of being pasted raw.
-- **New: `warnyin-sdlc version`** (also `--version` / `-v`). Nothing in an installed
-  project was readable as a version — an npx install leaves no package behind — so
-  every bug report would have carried `unknown` in the field that decides whether a
-  report can be acted on at all.
-- The repository now ships `.github/ISSUE_TEMPLATE/` bug and feature forms asking for
-  the same fields the command collects, so web-filed and command-filed reports read
-  alike.
-
-## 0.3.0 (2026-08-21)
-
-- **`/sdlc:auto` resumes an open change** instead of always starting at `new`. It
-  resolves its entry stage from `sdlc status` first: an argument naming an active
-  change maps that change's status to the entry stage and the pipeline starts
-  there, keeping the tier, Delta and Assumptions it was already triaged with. Only
-  an argument matching no active change starts at `new`. The entry stage is stated
-  in the plan line, so a resume is never silent. The status → stage table stays in
-  `next.md` alone rather than being copied into a second place that can drift.
-- **Fix (ownership)**: `installFile` dropped a file's manifest entry whenever it
-  kept the file. The next run then saw a path it had never installed, which
-  permanently disarmed `update`'s refresh branch — the file froze at its old
-  payload version and every later run relabelled it user-modified. That affects
-  anyone who re-runs `init` to upgrade before `update`. A kept file now carries
-  its recorded hash forward; prune is unaffected (its guard compares the file on
-  disk against that same hash) and in fact strictly safer, since a kept file is no
-  longer even a prune candidate.
-- A file whose content still matches its recorded hash is reported as
-  `kept (ours, older version — run update to refresh)` instead of
-  `kept (user-modified)`, which sent people hunting for an edit they never made.
-
-## 0.2.2 (2026-08-20)
-
-- `init` (and `update`) now drop a `.gitkeep` in `sdlc/changes/archive/`, so the
-  directory survives a commit and is still there after a clone. 0.2.1 made
-  `archive` recover from the missing directory; this stops it going missing.
-  The marker is not payload-owned — prune never reclaims it and the installer
-  never warns about it.
-
-## 0.2.1 (2026-08-20)
-
-- **Fix**: `archive` failed with `ENOENT` on the first change a repo ever ships.
-  `init` scaffolds `sdlc/changes/archive/`, but git does not track empty
-  directories, so the folder is absent for everyone who clones before that first
-  ship. The rename is now preceded by a `mkdir -p` of the archive root.
-
-  The failure landed mid-phase-2, after the delta had been merged into the living
-  specs, evals promoted, `status: shipped` stamped and the ship event journalled —
-  a repo left half-shipped while the CLI reported total failure. The directory is
-  now prepared next to the other destination checks, before phase 1 computes a
-  single merge, so an unusable archive path aborts with the specs untouched.
-
-## 0.2.0 (2026-08-20)
-
-`init` is now an installer you can actually see working — still zero dependencies.
-
-- **Interactive tool picker**: a searchable checkbox list replaces the
-  comma-separated typing prompt. Arrows move, `space` toggles, typing filters,
-  `ctrl+a` selects everything on screen, `enter` confirms, `ctrl+c` cancels
-  without installing anything.
-- **Tool detection**: tools the project already uses (`.claude/`, `.cursor/`,
-  `AGENTS.md`, …) come pre-selected; an empty project still defaults to claude.
-- **Post-install summary**: artifact counts, the adapter path per tool, a
-  written/unchanged/refreshed/kept tally, and Getting-started hints that differ
-  per tool (slash commands for Claude Code, prose for the rest).
-- **Colour** gated on `NO_COLOR` > `FORCE_COLOR` > TTY, with an ASCII glyph
-  fallback for legacy Windows consoles.
-- `--tool` accepts `all` and `none`; `--tools` is an alias. An empty `--tool`,
-  an unknown tool, or `all` mixed with a named tool now fails loudly.
-- **Fix**: `update` read an explicit `tools: []` (what `init --tool none` writes)
-  as "unset" and reinstalled claude. A missing key and a declared-empty one are
-  now distinguished.
-
-## 0.1.2 (2026-08-20)
-
-- Fix: `readStdinJson()` grew a 1s grace timeout — journal and hook utilities no
-  longer hang when stdin is open but idle.
-- Fix: hooks release stdin (pause + unref) so an open-idle stdin cannot keep a
-  hook process alive.
-
-## 0.1.1 (2026-08-20)
-
-- Fix: the entrypoint guard must realpath `process.argv[1]` — npx invokes through
-  a `node_modules/.bin` symlink, which made the CLI a silent no-op.
-- Fix (CI): `node --test` bare discovery; a quoted glob is not expanded on Node 20.
-
-## 0.1.0 (2026-08-20)
-
-Initial release — the full Day-1 SDLC loop:
-
-- CLI: `init` (multi-tool: claude/cursor/windsurf/copilot/cline/gemini/agents-md),
-  `update` (ownership-aware refresh + guarded prune), `validate`, `status`,
-  `observe`, `archive`.
-- Artifact model: constitution (≤30) + steering with inclusion modes + harness
-  (routing/triage/autonomy policy) + living specs + delta-based changes
-  (vibe/standard/deep caps 40/100/150) + contracts (tests ≤60, evals ≤40).
-- Managed Claude Code hooks: static-context injector, spec write-lock with TTL
-  gates, artifact validator + steering pointers, session token/cost journaling,
-  compact-event tracking.
-- 13 stage playbooks + 13 `/sdlc:*` commands + 3 background skills + 8 agents
-  with model routing (cheap/balanced/deepest).
-- Observability: per-change tokens/cost, first-pass rate, lead time, dead
-  steering and residency flags; post-ship learner loop (distill, never bloat).
+# Changelog
+
+## 0.9.0 (2026-09-14)
+
+- **Feature (new)**: `/sdlc:new` now asks its clarifying questions in rounds that follow
+  their dependencies. Before this, it asked every question it could not safely assume in
+  one batch. A question whose answer hinged on another was asked too early, so the human
+  answered it blind or the agent quietly re-decided it later. A round now holds every open
+  question whose prerequisites are already answered. A question that depends on one still
+  open waits for a later round, and one an earlier answer made moot is dropped. Each
+  question is numbered and comes with the agent's recommended answer, so you can reply by
+  number. Anything the repository or tools can answer is looked up instead of asked. After
+  the last round the settled answers are restated for confirmation, and correcting one
+  reopens that question. A change that asked nothing needs no confirmation. The
+  assume-safely policy is unchanged, and `--auto` still puts questions and answers into
+  its single confirmation. The rules card carries a one-line summary for non-Claude tools.
+  Existing installs get the new doctrine with `update`.
+
+## 0.8.0 (2026-09-14)
+
+- **Feature (lenses)**: stages now bring in UX/UI, API or data expertise only when a change
+  needs it. Before this, every change got the same fixed stages: design ran only on deep
+  tier or architecture signals, and review was always the same four reviewers. `/sdlc:new`
+  now reads the Delta, the touched paths and the stack after the Delta is written. It picks
+  lenses from `playbook/lenses.md` (`ux-ui`, `api`, `data`) and records them as
+  `lenses: [<lens>@project:<skill> | <lens>@user:<skill> | <lens>@builtin]`. Each lens
+  names its signals and a ground step: how it reads what exists first (current screens
+  and components, the API contract, the schema). It also names what it contributes and
+  the stages it joins. Design runs for a recorded lens, and contract carries its bars.
+  Review adds one reviewer per lens next to the four core reviewers, which still run.
+  Verify scores the lens bars and sends the change to review. A change with no signal
+  records no lens and loads nothing new. `validate` rejects unknown lenses, malformed
+  sources, a lens recorded twice, and a scalar `lenses`. Lens names live only in
+  `lib/lenses.mjs`, and they are only ever added.
+- **Feature (skills)**: `warnyin-sdlc skills [--json]` lists the Claude skills and agents
+  installed for the project and for the user (`.claude/skills/*/SKILL.md`,
+  `.claude/agents/*.md`). Lenses resolve against this list strictly: project, then user,
+  then builtin. Skill files are third-party content, so the listing reads only the first
+  8 KiB of each and keeps only frontmatter `name` and `description`. It strips control,
+  C1 and bidi characters and cuts descriptions at 160 chars. It stops at 200 entries and
+  opens at most 1000 per directory. It skips project entries whose real path leaves the
+  project. A skill that is missing is suggested and never installed. A skill that is
+  read later is reference material, not directives. `~/.claude/plugins/` and other
+  tools' rule files are not scanned yet.
+- **Harness template**: installing a skill or agent is now an escalation to the human.
+  Existing installs keep their seeded `sdlc/harness.md` unchanged, because `update` never
+  refreshes user-owned seeds. Add the line by hand if you want it.
+
+## 0.7.0 (2026-09-14)
+
+- **Fix (next)**: with several changes open, `/sdlc:next` gave every one of them its own
+  next command and gave the change this session was actually on no precedence — so the
+  agent walked off onto someone else's change mid-flight. Underneath, the active-change
+  pointer was one project-wide file: two sessions overwrote each other's focus, and hooks
+  recorded one session's telemetry against the other's change. The pointer is now kept per
+  session at `sdlc/.state/sessions/<session-id>.json`, with `.state/active.json` still
+  written as the project-wide fallback. `status` lists the current change first and marks
+  it `← this session`, or `← last set for project` when this session has not set one; other
+  changes are marked `(not this session)` only when this session set its own pointer.
+  `status --json` gains `current: {id, source}` and keeps `changes` in their original
+  order. `/sdlc:next` answers for the marked change, and a human who names a different one
+  wins. Hooks take the session from their stdin `session_id`; shell-run commands read
+  `CLAUDE_CODE_SESSION_ID`, which Claude Code does not document, so when it is absent — and
+  in every other tool — the project-wide pointer answers exactly as before. A session's own
+  pointer does not survive resume or `/clear`, which start a new session id. (#4)
+- **Fix (pointers)**: a session id now becomes a filename, so it is refused — not stripped —
+  by the same single-safe-segment rule as change ids; the steering-seen file uses
+  `nosession` for an unsafe id instead of aliasing `a/b` onto `ab`. Pointer reads and
+  writes check that the real path is where it claims to be, so a link planted at `.state`,
+  `.state/sessions` or the pointer file itself — a dangling one included — cannot carry a
+  write out of the project. `set-active` now exits 2 for an id that is not an open change
+  rather than writing a pointer that is then ignored, and reports a refused write instead
+  of claiming success; `archive` removes the pointers naming the change it ships.
+  Journal and `phase.json` writes do not have this check yet. Downgrading to 0.6.0 leaves
+  `.state/sessions/` unread and harmless on disk.
+
+## 0.6.0 (2026-09-10)
+
+- **Fix (auto)**: the Confirm step of an unattended run showed the scope it had settled on
+  and asked for approval, but never how it got there — so a derivation that searched the
+  wrong thing was approved as readily as a right one. It now shows, per scope item, the
+  command that established it and what that command returned; a summary of what a search
+  found does not count. Evidence that searched a term the request did not name is flagged
+  with both terms side by side, a narrowing the request never asked for (a folder pattern,
+  a naming convention) becomes its own refusable item, and an exclusion made on an empty
+  result must name the pattern searched — finding nothing is a claim about the pattern, not
+  a fact about the candidate. This is doctrine the model follows, checked by tests on the
+  doctrine and by the eval rubric; the confirmation is written at runtime, so nothing gates
+  it mechanically. (#2)
+- **Fix (journal)**: telemetry the hooks append lived in `sdlc/changes/<id>/journal.ndjson`,
+  which git tracks, so merely opening a project modified a shared file no human touched —
+  `git pull` and branch switches refused to move until someone discarded it, and two people
+  on one change conflicted on the appended tail for a reason unrelated to the change under
+  review. While a change is open, telemetry now goes to `sdlc/.state/journal/<id>.ndjson`;
+  `.state/` is already git-ignored in every installed project, so no new `.gitignore` entry
+  and no `git rm --cached` is needed. `archive` seals the journal into the shipped change
+  folder in one write at ship, so `/sdlc:observe` still reports cost and verify history for
+  changes a teammate shipped. Projects installed before this keep their in-tree journal: it
+  is read alongside the new stream and consumed at ship, so no recorded event is lost.
+  Two interim states worth knowing: a project that runs `update` mid-change carries telemetry
+  split across the two files until that change ships, and downgrading to 0.5.2 afterwards
+  leaves anything under `.state/journal/` unread by the older code — it is still on disk,
+  but that version does not know to look there. (#3)
+
+## 0.5.2 (2026-08-25)
+
+- **Fix (delta)**: a `### MODIFIED Requirement:` body replaces the requirement wholesale,
+  so one that carried over only some of the spec's scenarios dropped the rest in silence —
+  no error, no warning, `spec merged` printed either way. Both shapes are now reported:
+  the scenario name gone from the replacement body, and the name surviving while WHEN/THEN
+  clauses it promised have no counterpart (the one a name-level comparison cannot see).
+  `archive` prints the report before it writes a byte and counts it in the summary;
+  `validate` reports the same at warn level, so the loss is visible while the change folder
+  is still readable rather than after ship archived it. A warning, never an error — removing
+  a scenario is sometimes the point of the change, and only the silence was ever the bug.
+  A reworded clause reports the same as a deleted one: nothing mechanical can tell "said
+  better" from "promises less". Cosmetic churn — indentation, bullet marker, clause order,
+  heading case, whitespace — is normalized away and never warns. (#1)
+
+## 0.5.1 (2026-08-25)
+
+- **Fix (cost)**: `costUsd()` never charged cache-write tokens, the highest-rate of
+  the four classes the usage parser collects. Every cost `/sdlc:observe` and the
+  session summary have printed was therefore low. A model priced without a
+  `cacheWrite` rate now charges nothing for that class rather than inferring one from
+  `input` — the module's rule is never to guess a price, and a guess reports as
+  confidently as a known rate. Existing journalled costs are left alone: backfilling
+  would rewrite history from a rate that was not in force at the time.
+
+## 0.5.0 (2026-08-25)
+
+- **`--auto` on every pipeline stage.** `/sdlc:auto` already ran the whole pipeline,
+  but it stopped at every escalation — so you were pulled back in three or four times
+  per change and typed each stage anyway. Now all seven stage commands take `--auto`:
+  the run gathers what it needs, confirms once, and goes to ship. The confirmation is
+  decidable item by item — scope as understood, the tier and why, every ambiguity with
+  the assumption to be acted on, and each escalation as its own refusable line, the
+  ship row naming the hard-floor surface it covers instead of hiding behind a general
+  "run without me". Nothing is written before you confirm, down to the active-change
+  pointer, so declining leaves the repository untouched. The approval covers that run
+  only — not config, not the next change, not a resume. Anything outside what you
+  confirmed still stops and asks.
+- Escalations passed unattended are journalled, counted by `/sdlc:observe` as
+  `unattended×N`, and listed in the digest: the record shows where a human would
+  normally have stood and, that run, did not.
+- **Verify and review outcomes now record how they were produced** (`mode=panel|solo`).
+  A journal that says "verify passed" hides the thing a reader most needs later —
+  whether that verdict came from independent reviewers or from the same loop that
+  wrote the code. `observe` marks such changes `self-judged`, and the digest must name
+  self-produced outcomes. Absent provenance reads as unknown, never as `panel`, so
+  older journals are not retroactively dressed up as independently reviewed; where
+  provenance is mixed, the weakest link decides.
+- Where a panel cannot run, the playbooks now say to judge in the main loop and record
+  that — not to skip the stage. A review that never happened is worse than one
+  labelled honestly.
+- The constitution gains a hard rule: human-written text SHALL NOT reach a shell as an
+  argument. It is the defect that got past two separate gates in 0.4.0.
+
+## 0.4.0 (2026-08-25)
+
+- **New stage command `/sdlc:feedback`** — reports a bug, a rough edge, or a missing
+  feature in the framework itself to `warnyin/warnyin-sdlc`, from inside the session
+  where you hit it. It collects the context a maintainer triages by (framework and
+  Node version, OS, tool adapter, active change id and status), redacts it, shows you
+  the complete draft, and files it only after you approve. Submission goes through
+  `gh`; when `gh` is missing, logged out, or authenticated only against an enterprise
+  host, you get a prefilled issue URL instead — a normal path, not an error.
+  Nothing is attached automatically: no logs, no journal, no diff. Redaction is a
+  rule list rather than a guarantee, and the playbook says so — your eyes on the
+  draft are the control.
+- Human-written text never reaches a shell as an argument: the body travels over
+  stdin, while the title and the duplicate-search keywords are written by the agent
+  under a length and character allow-list instead of being pasted raw.
+- **New: `warnyin-sdlc version`** (also `--version` / `-v`). Nothing in an installed
+  project was readable as a version — an npx install leaves no package behind — so
+  every bug report would have carried `unknown` in the field that decides whether a
+  report can be acted on at all.
+- The repository now ships `.github/ISSUE_TEMPLATE/` bug and feature forms asking for
+  the same fields the command collects, so web-filed and command-filed reports read
+  alike.
+
+## 0.3.0 (2026-08-21)
+
+- **`/sdlc:auto` resumes an open change** instead of always starting at `new`. It
+  resolves its entry stage from `sdlc status` first: an argument naming an active
+  change maps that change's status to the entry stage and the pipeline starts
+  there, keeping the tier, Delta and Assumptions it was already triaged with. Only
+  an argument matching no active change starts at `new`. The entry stage is stated
+  in the plan line, so a resume is never silent. The status → stage table stays in
+  `next.md` alone rather than being copied into a second place that can drift.
+- **Fix (ownership)**: `installFile` dropped a file's manifest entry whenever it
+  kept the file. The next run then saw a path it had never installed, which
+  permanently disarmed `update`'s refresh branch — the file froze at its old
+  payload version and every later run relabelled it user-modified. That affects
+  anyone who re-runs `init` to upgrade before `update`. A kept file now carries
+  its recorded hash forward; prune is unaffected (its guard compares the file on
+  disk against that same hash) and in fact strictly safer, since a kept file is no
+  longer even a prune candidate.
+- A file whose content still matches its recorded hash is reported as
+  `kept (ours, older version — run update to refresh)` instead of
+  `kept (user-modified)`, which sent people hunting for an edit they never made.
+
+## 0.2.2 (2026-08-20)
+
+- `init` (and `update`) now drop a `.gitkeep` in `sdlc/changes/archive/`, so the
+  directory survives a commit and is still there after a clone. 0.2.1 made
+  `archive` recover from the missing directory; this stops it going missing.
+  The marker is not payload-owned — prune never reclaims it and the installer
+  never warns about it.
+
+## 0.2.1 (2026-08-20)
+
+- **Fix**: `archive` failed with `ENOENT` on the first change a repo ever ships.
+  `init` scaffolds `sdlc/changes/archive/`, but git does not track empty
+  directories, so the folder is absent for everyone who clones before that first
+  ship. The rename is now preceded by a `mkdir -p` of the archive root.
+
+  The failure landed mid-phase-2, after the delta had been merged into the living
+  specs, evals promoted, `status: shipped` stamped and the ship event journalled —
+  a repo left half-shipped while the CLI reported total failure. The directory is
+  now prepared next to the other destination checks, before phase 1 computes a
+  single merge, so an unusable archive path aborts with the specs untouched.
+
+## 0.2.0 (2026-08-20)
+
+`init` is now an installer you can actually see working — still zero dependencies.
+
+- **Interactive tool picker**: a searchable checkbox list replaces the
+  comma-separated typing prompt. Arrows move, `space` toggles, typing filters,
+  `ctrl+a` selects everything on screen, `enter` confirms, `ctrl+c` cancels
+  without installing anything.
+- **Tool detection**: tools the project already uses (`.claude/`, `.cursor/`,
+  `AGENTS.md`, …) come pre-selected; an empty project still defaults to claude.
+- **Post-install summary**: artifact counts, the adapter path per tool, a
+  written/unchanged/refreshed/kept tally, and Getting-started hints that differ
+  per tool (slash commands for Claude Code, prose for the rest).
+- **Colour** gated on `NO_COLOR` > `FORCE_COLOR` > TTY, with an ASCII glyph
+  fallback for legacy Windows consoles.
+- `--tool` accepts `all` and `none`; `--tools` is an alias. An empty `--tool`,
+  an unknown tool, or `all` mixed with a named tool now fails loudly.
+- **Fix**: `update` read an explicit `tools: []` (what `init --tool none` writes)
+  as "unset" and reinstalled claude. A missing key and a declared-empty one are
+  now distinguished.
+
+## 0.1.2 (2026-08-20)
+
+- Fix: `readStdinJson()` grew a 1s grace timeout — journal and hook utilities no
+  longer hang when stdin is open but idle.
+- Fix: hooks release stdin (pause + unref) so an open-idle stdin cannot keep a
+  hook process alive.
+
+## 0.1.1 (2026-08-20)
+
+- Fix: the entrypoint guard must realpath `process.argv[1]` — npx invokes through
+  a `node_modules/.bin` symlink, which made the CLI a silent no-op.
+- Fix (CI): `node --test` bare discovery; a quoted glob is not expanded on Node 20.
+
+## 0.1.0 (2026-08-20)
+
+Initial release — the full Day-1 SDLC loop:
+
+- CLI: `init` (multi-tool: claude/cursor/windsurf/copilot/cline/gemini/agents-md),
+  `update` (ownership-aware refresh + guarded prune), `validate`, `status`,
+  `observe`, `archive`.
+- Artifact model: constitution (≤30) + steering with inclusion modes + harness
+  (routing/triage/autonomy policy) + living specs + delta-based changes
+  (vibe/standard/deep caps 40/100/150) + contracts (tests ≤60, evals ≤40).
+- Managed Claude Code hooks: static-context injector, spec write-lock with TTL
+  gates, artifact validator + steering pointers, session token/cost journaling,
+  compact-event tracking.
+- 13 stage playbooks + 13 `/sdlc:*` commands + 3 background skills + 8 agents
+  with model routing (cheap/balanced/deepest).
+- Observability: per-change tokens/cost, first-pass rate, lead time, dead
+  steering and residency flags; post-ship learner loop (distill, never bloat).