pi-aia-asf 0.14.1 → 0.15.0

package/CHANGELOG.md

@@ -7,11 +7,86 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.14.1] - 2026-11-04
+## [0.15.0] - 2026-11-06
 
 ### Added
 
-- (describe changes for 0.14.1)
+- **ASF is an active process for all software work.** The first source change in a
+  session opens a `small` run automatically. That includes edit/write tools, bash
+  writes into source (heredoc, `sed -i`, scripted `open(...,'w')`, redirect, `tee`,
+  `patch`, `cp`/`mv` into source) and hand-spawned `pi -p --no-extensions` workers
+  that have write tools. It works in non-git directories too. Docs, assets,
+  `node_modules` and loose `/tmp` scratch never activate it.
+- **Completion floor.** A run that changed source cannot settle until a passing test
+  run that started *after the last change* is recorded. A lint or typecheck does not
+  count, and neither does a green run from before the edit. A spec marked met during
+  the run must carry `trace.outcome` + `trace.codePath`; specs met in earlier runs
+  are not re-checked.
+- **Run card.** A compact card (≤1.5 KB, registered in the load budget) with the
+  phase, the open items and the single next step. It is shown when a run opens and
+  again at `session_start` and `session_compact`.
+- **`/asf passive`** silences steering for the current run only. The next source
+  change re-arms ASF.
+- **Refusal ladder.** The same refusal escalates: refuse → refuse with the rule
+  text → park for the PO. `/asf status` shows when a run is parked or passive.
+- A long stretch of untested source edits gets exactly one steer naming the files.
+  It never blocks.
+- `test/test-active-process.mjs`: an end-to-end suite that drives the real handlers,
+  with a negative control per guard.
+
+### Changed
+
+- **No stops.** The fixed continuation cap (`MAX_CONTINUATIONS = 2`) is replaced by
+  de-duplication: each gap is raised once, an identical steer is never issued again,
+  and after `MAX_STEERS` (12) gaps are reported as unverified instead of re-asked.
+  The run only parks for plan approval, an irreversible step with no safe path, an
+  unobtainable credential, or a deliverable-shaping choice.
+- `test-subset-without-impact` now steers instead of refusing (71 blocks in 18 days,
+  64 of them repeats). The secret, push-without-green and destructive-git refusals
+  are unchanged and still apply in passive mode.
+- **Run state is keyed by the git work-tree root** (absolute path outside git), not
+  the cwd basename. `cd` into a subdirectory no longer loses the run, and two
+  checkouts with the same folder name no longer share one. A run saved under the old
+  key is migrated once. Spec memory is still read under pi-vigilant's key.
+
+### Fixed
+
+- Deleting or corrupting `state.json` no longer silently ends enforcement. The
+  active run is restored from memory and the deletion is recorded. `/asf abort`
+  remains the way to end a run.
+- A malformed `agent_before_settle` event no longer requests a continuation.
+- The test harness ignored a suite's `false` return value, so a suite that reported
+  failures still counted as passed.
+
+## [0.14.1] - 2026-11-04
+
+### Fixed
+
+- **The completion gate's continuation now actually runs** (pi 1.5.0). pi 1.5.0 validates
+  boundary continuations instead of trusting them: it commits the entries an extension
+  returns, rebuilds the context, and only continues when `canContinue` holds. The gate
+  returned a bare `{ continue: true }`, which at settle time means an assistant-terminated
+  context with nothing queued, so pi refused it —
+  `agent_before_settle requested continuation without runnable model context` — the agent
+  was never told what was missing, and the gate's one bounded continuation logged an error
+  and did nothing. It now returns a `custom_message` entry (pi projects it to role `user`,
+  which is what makes the next provider request runnable) carrying the missing list.
+- **The gate only judges ASF runs.** `currentScale()` had no "no ASF run" state, so every
+  session that loaded ASF was held to the delivery evidence bar. While the continuation was
+  inert this was invisible; once it resumed runs, a plain `pi -p` in a scratch directory
+  went from 3s to 181s and was told to close its missing evidence. The gate now reads the
+  project's ASF state and stays silent unless a run is active.
+
+### Changed
+
+- The pi peers are pinned to 1.5.0, the version that actually loads the extension.
+- `jiti` is declared as a devDependency; the test harness imported it without ever
+  declaring it, so a clean `npm install` broke the suite.
+- The typecheck gate no longer reuses a cached peer at the wrong version. It printed
+  `host types 1.2.0` against a manifest declaring 1.5.0 and still reported OK — the failure
+  its own header exists to prevent.
+- `scripts/verify-published.mjs` polls for the tarball instead of taking one HEAD request,
+  which 404s transiently while a fresh release sits in npm's staging queue.
 
 ## [0.14.0] - 2026-11-02
 

package/README.md

@@ -19,9 +19,15 @@ It turns "let's build something" into a gated pipeline where nothing is implemen
 
 ## Activation
 
-The skill activates when the user's request is a **new software project, significant feature, major bugfix, or architectural refactor**. It does **not** activate for Q&A, one-liners, casual conversation, or non-software tasks. When in doubt, it asks.
+**ASF is always on when software is being changed.** The extension watches tool calls: the first change to a source file (an edit/write, a bash heredoc / `sed -i` / scripted write into source, or a `pi -p --no-extensions` worker with write tools) opens a `small` run automatically. Docs, assets and loose `/tmp` scratch never activate it, and nothing activates for Q&A or research.
 
-You can also force/start a session explicitly:
+An automatic run is held to a **floor**, not a ceremony: it cannot settle until a passing test run that started after the last source change is recorded (a lint or typecheck does not count), and any spec marked met during the run must carry `trace.outcome` + `trace.codePath`. Missing evidence is **steered**, never stopped: each gap is raised once, an identical steer never repeats, and an unclosable gap is reported as unverified. The run only parks for input ASF cannot obtain itself (plan approval, an irreversible step with no safe path, a credential, a deliverable-shaping choice).
+
+Three refusals always hold, including in passive mode: a secret written into a tracked file, a push/publish without a recorded full-suite green, and a destructive git command on a dirty tree. A repeated identical refusal escalates from refuse, to refuse with the rule text, to parking for the PO.
+
+Run state is stored per git work-tree root (or absolute path outside git), so `cd` into a subdirectory keeps the run. Deleting the state file does not end a run — it is restored and the deletion is recorded.
+
+Large work (new project, significant feature, major bugfix, architectural refactor) runs the full gated flow above. You can also start a session explicitly:
 
 ```
 /asf new          — start a new software project
@@ -31,7 +37,8 @@ You can also force/start a session explicitly:
 /asf status       — show current phase + state
 /asf health       — run the code health gate (function/module/architecture)
 /asf approve      — mark PLAN.md as approved (Gate 5)
-/asf abort        — end the session
+/asf abort        — end the session (the legitimate way to end a run)
+/asf passive      — silence steering for THIS run only (the three refusals stay)
 ```
 
 ## Dependencies (required)