pi-aia-asf 0.13.4 → 0.13.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +30 -0
- package/package.json +3 -2
package/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,36 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
## [Unreleased]
|
|
9
9
|
|
|
10
|
+
## [0.13.5] - 2026-10-18
|
|
11
|
+
|
|
12
|
+
### Added
|
|
13
|
+
|
|
14
|
+
- **`test/test-packaging.mjs` — the artifact gate.** Checks the **packed** file set
|
|
15
|
+
rather than the working tree: `index.ts`, the `skills/aia-asf` skill, its normative
|
|
16
|
+
reference files, the `lib/` modules and the declared `obligations.d/` all really ship;
|
|
17
|
+
every entry `files` allowlists is present in the tarball; `pi.extensions` and
|
|
18
|
+
`pi.skills` point at entries that ship; and no relative import inside the artifact
|
|
19
|
+
points outside it. Nothing could previously see a broken `files` allowlist —
|
|
20
|
+
typecheck reads source files, the suite imports from disk, and `npm publish` only
|
|
21
|
+
reports that the upload was accepted. An ASF release whose skill did not ship is an
|
|
22
|
+
empty deliverable that installs without error.
|
|
23
|
+
- **`scripts/verify-published.mjs` — post-publish verification of the published bytes.**
|
|
24
|
+
Installs the just-published version **from the registry** into a throwaway prefix
|
|
25
|
+
(with the peer deps the pi host provides), imports the installed extension, requires
|
|
26
|
+
its default export to be the activate function, and requires the skill and
|
|
27
|
+
`obligations.d/` to be present in the installed copy. Reachable as
|
|
28
|
+
`npm run verify:published`; `BMX_SKIP_PUBLISHED_VERIFY=1` skips it in the release.
|
|
29
|
+
- **`scripts/release.sh` now gates instead of announcing.** It used to print
|
|
30
|
+
"✅ Released" on the strength of `npm publish`'s exit code alone. It now polls the
|
|
31
|
+
registry until the version is listed **and its tarball is fetchable**, then runs the
|
|
32
|
+
published-artifact verification, and exits non-zero if either fails.
|
|
33
|
+
|
|
34
|
+
### Notes
|
|
35
|
+
|
|
36
|
+
- The import resolver in the artifact gate follows the ESM declaration convention, so a
|
|
37
|
+
`.d.mts` file naming its sibling as `./x.d.mjs` is not reported as a missing module
|
|
38
|
+
(`lib/gates/` ships `.mts` + `.d.mts` pairs).
|
|
39
|
+
|
|
10
40
|
## [0.13.4] - 2026-10-16
|
|
11
41
|
|
|
12
42
|
### Fixed
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pi-aia-asf",
|
|
3
|
-
"version": "0.13.
|
|
3
|
+
"version": "0.13.5",
|
|
4
4
|
"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.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"pi-package",
|
|
@@ -34,7 +34,8 @@
|
|
|
34
34
|
"build": "echo 'nothing to build — pi loads .ts via jiti at runtime'",
|
|
35
35
|
"check": "./scripts/typecheck.sh",
|
|
36
36
|
"test": "./test/run-all.sh",
|
|
37
|
-
"release": "./scripts/release.sh"
|
|
37
|
+
"release": "./scripts/release.sh",
|
|
38
|
+
"verify:published": "node scripts/verify-published.mjs"
|
|
38
39
|
},
|
|
39
40
|
"pi": {
|
|
40
41
|
"extensions": [
|