pi-aia-asf 0.13.3 → 0.13.5

package/CHANGELOG.md

@@ -7,6 +7,108 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.13.5] - 2026-10-18
+
+### Added
+
+- **`test/test-packaging.mjs` — the artifact gate.** Checks the **packed** file set
+  rather than the working tree: `index.ts`, the `skills/aia-asf` skill, its normative
+  reference files, the `lib/` modules and the declared `obligations.d/` all really ship;
+  every entry `files` allowlists is present in the tarball; `pi.extensions` and
+  `pi.skills` point at entries that ship; and no relative import inside the artifact
+  points outside it. Nothing could previously see a broken `files` allowlist —
+  typecheck reads source files, the suite imports from disk, and `npm publish` only
+  reports that the upload was accepted. An ASF release whose skill did not ship is an
+  empty deliverable that installs without error.
+- **`scripts/verify-published.mjs` — post-publish verification of the published bytes.**
+  Installs the just-published version **from the registry** into a throwaway prefix
+  (with the peer deps the pi host provides), imports the installed extension, requires
+  its default export to be the activate function, and requires the skill and
+  `obligations.d/` to be present in the installed copy. Reachable as
+  `npm run verify:published`; `BMX_SKIP_PUBLISHED_VERIFY=1` skips it in the release.
+- **`scripts/release.sh` now gates instead of announcing.** It used to print
+  "✅ Released" on the strength of `npm publish`'s exit code alone. It now polls the
+  registry until the version is listed **and its tarball is fetchable**, then runs the
+  published-artifact verification, and exits non-zero if either fails.
+
+### Notes
+
+- The import resolver in the artifact gate follows the ESM declaration convention, so a
+  `.d.mts` file naming its sibling as `./x.d.mjs` is not reported as a missing module
+  (`lib/gates/` ships `.mts` + `.d.mts` pairs).
+
+## [0.13.4] - 2026-10-16
+
+### Fixed
+
+- **The model-blind-spot research (D1/D2) could not be verified against its own
+  sources, and now it can.** Both deliverables existed; neither had been audited,
+  and the audit found three real problems.
+  - **Seven quotations attributed to unnamed sources were removed.** The document
+    leaned on block quotes from "a soft-delete design guide", "the tenancy
+    source", "a team that learned it the expensive way" and the BEA book — none
+    carrying a URL. Checked by exact-phrase search and by fetching the cited
+    URLs: `orphans-by-policy`, `humans forget filters … RLS policies forget
+    nothing` and `we paid for the trash folder twice` return **zero results**,
+    and the InfoQ and O'Reilly fitness-function URLs return **404**. An
+    unfindable quotation is worse than no citation — it reads as evidence and
+    invites downstream reuse — so each was deleted, and the claims that still
+    matter were restated as explicitly-labelled **T3** reasoning. Where a primary
+    source says it better, it replaced the paraphrase: the PostgreSQL manual's own
+    default-deny text is stronger and checkable than the quote it replaced.
+    The deletions are listed in a withdrawn table rather than dropped silently.
+  - **What remains is now genuinely T1** — fetched and read this pass, with URLs
+    and page numbers: Vernon's four aggregate rules (ArchiLab, ch. 10 pp.
+    347–388), the OWASP IDOR methodology, PostgreSQL §5.9, the Thoughtworks
+    fitness-function article. `SOURCES.md` gained the Model section with T1/T2/T3
+    classes per 02-research.md, including a row that admits the Rails `dependent:`
+    option list was **not** read and must be checked before any option name
+    reaches normative text.
+  - **The inventory had gone stale.** It was measured against `06a–06i` and never
+    re-derived after `06j`, `06k`, the gate layer and the model fitness level
+    shipped — so it still claimed all 14 classes were invisible. Re-scored against
+    the current gate set with the H/M/S enforcement classes: six classes (3
+    concurrency, 5 time, 6 numeric/unit, 7 locale, 9 unit-of-work, 12 environment)
+    remain **completely uninspected**, and that is now stated as a count instead of
+    a mood.
+  - **The audit covered only half the mandate.** The spec says "ASF **and
+    vigilant**"; vigilant had never been audited. It now has its own table — Loop
+    Guardian, spec verification, completeness guard, obligations container,
+    tool-timeout abort — and the honest conclusion: vigilant inspects the agent and
+    the claim, not the deliverable's design, and by the package boundary it must.
+    So for those six classes, **if ASF does not inspect them, nobody does.** There
+    is no second line of defence in the other package.
+  - **The meta-finding got a status.** "Not one gate asserts the non-effect" was
+    written before 06g §3 added non-effect assertions; it now reports itself as
+    half-closed — the language exists, the compulsion exists only where a blocker
+    was built.
+- **`test/test-model-research.mjs` (42 checks) guards all of the above**, because
+  the failure mode is recurrence rather than novelty: it asserts the inventory is
+  contiguous and fully re-scored, that vigilant is audited, that every sourced
+  subsection resolves to a URL or is labelled T3, and that each withdrawn phrase
+  survives only as a record and never as a quotation. **Negative control verified**
+  — injecting an unattributed quote back into §2.6 makes it fail, and removing it
+  passes.
+
+### Notes
+
+- **`npm audit` triage for this line: accepted, not fixed — and the reason is
+  recorded rather than skipped.** Three advisories report (1 moderate,
+  2 high), all tracing to `undici` and `brace-expansion`. None of them ships
+  with ASF: `dependencies` is `{}` and the packed artifact (50 files) contains
+  no `node_modules` and neither package. They are reachable only through the
+  **peer** host package `@earendil-works/pi-coding-agent`, which is the user's
+  own pi installation and is pinned in `devDependencies` solely so typecheck can
+  run against a known host version (`host types 1.2.0`).
+  - `npm audit fix` would bump that pin. It was deliberately **not** run: it
+    would move the host-types version the entire typecheck and suite are
+    calibrated against, for no change whatsoever in what an installed ASF
+    contains. The fix belongs to the pi release, not to this manifest.
+  - Consequence for anyone reading this: an `npm audit` hit on ASF is a signal
+    about your **pi install**, and should be resolved by updating pi. Checking
+    the shipped surface is the `dependencies: {}` line plus the pack list above,
+    not the audit count.
+
 ## [0.13.3] - 2026-10-16
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-aia-asf",
-  "version": "0.13.3",
+  "version": "0.13.5",
   "description": "Ai Applied Agentic Software Factory — codifies the full software development flow: intake, research, spec capture, adversarial analysis, planning with approval gates, test-first implementation, and release. Requires pi-vigilant, pi-smart-web-search, pi-smart-fetch, and pi-aia-browser.",
   "keywords": [
     "pi-package",
@@ -34,7 +34,8 @@
     "build": "echo 'nothing to build — pi loads .ts via jiti at runtime'",
     "check": "./scripts/typecheck.sh",
     "test": "./test/run-all.sh",
-    "release": "./scripts/release.sh"
+    "release": "./scripts/release.sh",
+    "verify:published": "node scripts/verify-published.mjs"
   },
   "pi": {
     "extensions": [