pi-aia-asf 0.17.3 → 0.17.5

package/CHANGELOG.md

@@ -7,13 +7,97 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-## [0.17.3] - 2026-11-07
-
-### Added
+## [0.17.5] - 2026-11-08
+
+### Fixed — the publish floor could be satisfied by a green that proved nothing
+
+`push-without-recorded-green` asked for "a recorded full-suite green run in this
+session" and accepted **any** green: a run from before the last edit, or a green
+from earlier in the session that a red had since overtaken. It also disagreed
+with the completion floor, which already required a passing run *started after
+the last source change* — so the two ASF floors had different ideas about what
+"green" means, and the weaker one guarded the only irreversible action.
+
+The floor is now the same rule in both places: the **last** full run, green, and
+started after the last source mutation. Passive mode keeps it — "no steering"
+suspends guidance, not the irreversibility floor. The refusal now names which
+condition failed (`no full-suite run recorded` / `the last full suite run exited
+1` / `the last full-suite green predates the most recent source change`), so the
+autonomous exit is the specific action that closes it.
+
+New assertions drive the real `tool_call`/`tool_result` pair rather than a
+hand-built context, which is what pins the *recorder*: a floor whose demanded
+action does not actually close it is the 2026-11-07 bug class, and the previous
+tests could not see that path at all. Six mutations of the new guards (accept a
+red, accept a stale green, take the oldest full run, drop the mutation clock,
+never record the run, never set the clock) each fail at least one test.
+
+### Changed — two modules split to stay inside the limit ASF enforces
+
+`lib/gates/ledger.mjs` (327 lines) and `lib/gates/blockers.mjs` (301) crossed the
+300-line file limit, so the two halves that changed for different reasons were
+separated: `lib/gates/suite-runs.mjs` (suite-run recognition and the green-run
+rule) and `lib/gates/refusals.mjs` (the refusal ladder and its per-rule text).
+Both are imported explicitly — no re-export shim with two ways to reach one
+function.
+
+### Removed — `deriveHealthRun`
+
+It recognised a health run by matching `/asf health` in a command's text, which
+is the class of bug that produced the endless loop of 2026-11-07: a human slash
+command the agent has no tool for. The `asf_health` tool appends the `health-run`
+ledger entry directly, so nothing called it and nothing tested it.
+
+## [0.17.4] - 2026-11-07
+
+### Changed — ASF now passes its own health gate, and the gate measures the right tree
+
+ASF demanded code health of every project and did not meet it itself: 74
+violations across `index.ts` and `lib/`. This release is that debt paid, and two
+real defects the work exposed.
+
+- `index.ts` is 37 lines of wiring. The extension lives in `lib/extension/`
+  (`commands/`, `tools/`, `handlers/`, plus state, specs, evidence, steer, run),
+  so no single file is the whole extension any more.
+- `lib/gates/`: the parameter table moved to `params.mjs` (the table reads as a
+  table), `clamp`/`round2` to `math.mjs` (the table's calibrations use them, and
+  importing them from the resolver was a cycle), `ledger.mjs`/`drift.mjs`/
+  `settle.mjs`/`blockers.mjs`/`config.mjs`/`declarations.mjs`/`authority.mjs`
+  decomposed into named pieces instead of one long function each.
+- `lib/code-health/`: `model-scan.mjs` (file selection and I/O), `model-patterns.mjs`
+  (the pattern tables), `eslint-run.mjs` (config generation and counting),
+  `exec.mjs` (the bounded spawn).
+- Functions that took four or more positional arguments now take one options
+  object (`deriveSuiteRun`, `deriveHealthRun`, `transition`, `evaluateBlockers`,
+  `planMetrics`, `walk`, `resolveParam`'s resolvers, `runBlocker`).
+
+### Fixed — the gate wrote into the repo it was measuring
+
+`jscpd`'s report went to `<project>/.asf-code-health-tmp`, which dirtied the
+measured tree (it tripped ASF's own dirty-tree guards) and shipped a committed
+temp file. It now writes to a `mktemp`-style directory under the OS temp root and
+removes it. A test asserts the `--output` path is outside the project and that
+the directory is gone afterwards.
+
+### Fixed — `asf_health` measured the session's cwd, not the run's project
+
+A session started in `$HOME` measured the whole home directory: 960 "handwritten
+cascade" findings from `site-packages`, and a fail verdict on a healthy repo.
+Every consumer of "the project" (the health tool, `/asf health`, `/asf verify`,
+`/asf config`, the project config read, the git-dirty probe, `PLAN.md`, spec
+traces) now goes through `runRoot()` — the git work-tree root — instead of
+`process.cwd()`. A test fails if any extension module measures
+`process.cwd()` as the project.
+
+### Fixed — the tests stopped covering half the extension
+
+The text-assertion helpers in `test-operator-surface.mjs`, `test-browser-touched.mjs`
+and `test-model-gate.mjs` read `lib/extension/*.ts` non-recursively, so after the
+split the `commands/`, `tools/` and `handlers/` modules were outside every text
+assertion. They read recursively now.
 
-- (describe changes for 0.17.3)
 
-## [0.17.2] - 2026-11-07
+## [0.17.3] - 2026-11-07
 
 ### Fixed — the tools were installed but never found