@cassiomc1/forgeloop 2.0.0 → 2.2.0
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/.cursor/rules/project-loop.mdc +1 -1
- package/.github/copilot-instructions.md +1 -1
- package/AGENTS.md +1 -1
- package/CLAUDE.md +1 -1
- package/ENG/design-code-eng.md +7 -5
- package/ENG/dotnet-aspnetcore-development-eng.md +8 -4
- package/ENG/nodejs-backend-development-eng.md +7 -4
- package/ENG/sql-development-eng.md +5 -4
- package/ENG/taste-frontend-eng.md +19 -5
- package/PROTOCOL_INTEGRATION.md +21 -0
- package/README.md +10 -7
- package/THIRD_PARTY_NOTICES.md +1 -0
- package/completions/_forgeloop +6 -1
- package/completions/forgeloop.bash +11 -1
- package/completions/forgeloop.fish +40 -1
- package/docs/AGENT_PROTOCOL_SUMMARY.md +6 -1
- package/docs/CLI_REFERENCE.md +88 -3
- package/docs/CODE_ATTESTATION.md +7 -0
- package/docs/FORGELOOP_AUDIT.md +1 -1
- package/docs/GETTING_STARTED.md +8 -1
- package/docs/PACKAGE_CONTENTS.md +4 -5
- package/docs/RELEASE_CHECKLIST.md +67 -13
- package/docs/STABLE_2_ACCEPTANCE.md +118 -71
- package/docs/TROUBLESHOOTING.md +167 -0
- package/package.json +1 -5
- package/src/cli.js +26 -0
- package/src/commands/assess.js +36 -0
- package/src/commands/evidence-export.js +17 -0
- package/src/commands/evidence-verify.js +36 -0
- package/src/commands/sync-pull.js +46 -0
- package/src/commands/sync-push.js +49 -0
- package/src/core/assessment/facts.js +146 -0
- package/src/core/assessment/plan.js +133 -0
- package/src/core/cli-command-definitions.js +70 -0
- package/src/core/command-executors.js +26 -3
- package/src/core/error-codes.js +232 -2
- package/src/core/evidence/bundle-format.js +72 -0
- package/src/core/evidence/export.js +179 -0
- package/src/core/evidence/markdown.js +40 -0
- package/src/core/evidence/verify.js +179 -0
- package/src/core/integration-invocation-policy.js +4 -2
- package/src/core/next-action-review-phase.js +14 -5
- package/src/core/parsers/dotnet-project.js +221 -0
- package/src/core/parsers/limits.js +9 -0
- package/src/core/parsers/pubspec.js +307 -0
- package/src/core/parsers/shared.js +4 -0
- package/src/core/project-detection.js +6 -527
- package/src/core/sync/remote.js +124 -0
- package/src/core/sync/snapshot.js +129 -0
package/docs/CLI_REFERENCE.md
CHANGED
|
@@ -158,6 +158,40 @@ destination is never replaced. External attachments are not included.
|
|
|
158
158
|
|
|
159
159
|
<!-- END FORGELOOP GENERATED: cli:storage-backup:options -->
|
|
160
160
|
|
|
161
|
+
### `sync-push`
|
|
162
|
+
|
|
163
|
+
Uploads an encrypted backup of this project's ForgeLoop state to the cloud-sync
|
|
164
|
+
remote so another machine can continue the work. The snapshot is encrypted on
|
|
165
|
+
this machine with `FORGELOOP_SYNC_KEY`; `FORGELOOP_SYNC_TOKEN` authenticates the
|
|
166
|
+
request. A push based on a remote version this machine has not pushed or pulled
|
|
167
|
+
is refused with `E_SYNC_CONFLICT`. See [`CLOUD_SYNC.md`](./CLOUD_SYNC.md).
|
|
168
|
+
|
|
169
|
+
<!-- BEGIN FORGELOOP GENERATED: cli:sync-push:options -->
|
|
170
|
+
|
|
171
|
+
- `--path <directory>`: target project directory (default: current directory)
|
|
172
|
+
- `--remote <url>`: sync endpoint (default: https://forgeloop.monster/api/sync)
|
|
173
|
+
- `--repo <owner/name>`: repository the snapshot belongs to (default: from the git origin)
|
|
174
|
+
- `--json`: emit the push result as JSON
|
|
175
|
+
|
|
176
|
+
<!-- END FORGELOOP GENERATED: cli:sync-push:options -->
|
|
177
|
+
|
|
178
|
+
### `sync-pull`
|
|
179
|
+
|
|
180
|
+
Downloads, decrypts and verifies the repository's snapshot, then activates it
|
|
181
|
+
through `storage-restore`: into a fresh project, or over existing local state
|
|
182
|
+
only with `--replace-active`. Requires `--writers-quiesced`.
|
|
183
|
+
|
|
184
|
+
<!-- BEGIN FORGELOOP GENERATED: cli:sync-pull:options -->
|
|
185
|
+
|
|
186
|
+
- `--path <directory>`: target project directory (default: current directory)
|
|
187
|
+
- `--remote <url>`: sync endpoint (default: https://forgeloop.monster/api/sync)
|
|
188
|
+
- `--repo <owner/name>`: repository the snapshot belongs to (default: from the git origin)
|
|
189
|
+
- `--replace-active`: replace existing local state; the outgoing state is retained and archived
|
|
190
|
+
- `--writers-quiesced`: assert that all writers have been externally stopped
|
|
191
|
+
- `--json`: emit the pull and restore result as JSON
|
|
192
|
+
|
|
193
|
+
<!-- END FORGELOOP GENERATED: cli:sync-pull:options -->
|
|
194
|
+
|
|
161
195
|
## Semantic decision projections
|
|
162
196
|
|
|
163
197
|
### `decision-status`
|
|
@@ -239,6 +273,19 @@ question-set categories.
|
|
|
239
273
|
|
|
240
274
|
<!-- END FORGELOOP GENERATED: cli:semantic-plan:options -->
|
|
241
275
|
|
|
276
|
+
### `assess`
|
|
277
|
+
|
|
278
|
+
Assesses an existing repository read-only and emits a guide-routed review plan
|
|
279
|
+
for frontend and backend code. It never executes target code; see
|
|
280
|
+
[`ASSESSMENT.md`](./ASSESSMENT.md).
|
|
281
|
+
|
|
282
|
+
<!-- BEGIN FORGELOOP GENERATED: cli:assess:options -->
|
|
283
|
+
|
|
284
|
+
- `--path <directory>`: target project directory (default: current directory)
|
|
285
|
+
- `--json`: emit the repository assessment plan as JSON
|
|
286
|
+
|
|
287
|
+
<!-- END FORGELOOP GENERATED: cli:assess:options -->
|
|
288
|
+
|
|
242
289
|
### `test-inventory`
|
|
243
290
|
|
|
244
291
|
Discovers deterministic test units and stable test IDs.
|
|
@@ -327,8 +374,8 @@ error codes. Default output and default JSON remain unchanged.
|
|
|
327
374
|
|
|
328
375
|
| Category | Commands |
|
|
329
376
|
| --- | --- |
|
|
330
|
-
| **Setup & Maintenance** | [`storage-restore-resume`](#storage-restore-resume), [`storage-restore`](#storage-restore), [`storage-migration-status`](#storage-migration-status), [`storage-migration-resume`](#storage-migration-resume), [`storage-rollback`](#storage-rollback), [`storage-rollback-resume`](#storage-rollback-resume), [`storage-migrate`](#storage-migrate), [`storage-backup`](#storage-backup), [`contract-revise`](#contract-revise), [`init`](#init), [`index-setup`](#index-setup), [`index-start`](#index-start), [`index-stop`](#index-stop), [`index-rebuild`](#index-rebuild), [`update`](#update), [`checkpoint-revalidate`](#checkpoint-revalidate), [`task-migrate`](#task-migrate), [`migrate-protocol`](#migrate-protocol), [`task-unlock`](#task-unlock), [`task-recover`](#task-recover), [`task-abandon`](#task-abandon), [`task-repair-contract-bootstrap`](#task-repair-contract-bootstrap), [`task-migrate-contract-bootstrap-repair`](#task-migrate-contract-bootstrap-repair), [`task-repair-legacy-recovery`](#task-repair-legacy-recovery), [`task-resume`](#task-resume) |
|
|
331
|
-
| **Inspection & Diagnostics** | [`protocol-info`](#protocol-info), [`decision-status`](#decision-status), [`decision-show`](#decision-show), [`context-plan`](#context-plan), [`model-route`](#model-route), [`semantic-plan`](#semantic-plan), [`test-inventory`](#test-inventory), [`test-utility`](#test-utility), [`test-prune-plan`](#test-prune-plan), [`doctor`](#doctor), [`index-status`](#index-status), [`search`](#search), [`metrics`](#metrics), [`usage-record`](#usage-record), [`efficiency`](#efficiency), [`eval`](#eval), [`history`](#history), [`trace`](#trace), [`reflect`](#reflect), [`progress`](#progress), [`profile-interview`](#profile-interview), [`inspect`](#inspect), [`status`](#status), [`validate-state`](#validate-state), [`validate-protocol`](#validate-protocol) |
|
|
377
|
+
| **Setup & Maintenance** | [`storage-restore-resume`](#storage-restore-resume), [`storage-restore`](#storage-restore), [`storage-migration-status`](#storage-migration-status), [`storage-migration-resume`](#storage-migration-resume), [`storage-rollback`](#storage-rollback), [`storage-rollback-resume`](#storage-rollback-resume), [`storage-migrate`](#storage-migrate), [`storage-backup`](#storage-backup), [`sync-push`](#sync-push), [`sync-pull`](#sync-pull), [`contract-revise`](#contract-revise), [`init`](#init), [`index-setup`](#index-setup), [`index-start`](#index-start), [`index-stop`](#index-stop), [`index-rebuild`](#index-rebuild), [`update`](#update), [`checkpoint-revalidate`](#checkpoint-revalidate), [`task-migrate`](#task-migrate), [`migrate-protocol`](#migrate-protocol), [`task-unlock`](#task-unlock), [`task-recover`](#task-recover), [`task-abandon`](#task-abandon), [`task-repair-contract-bootstrap`](#task-repair-contract-bootstrap), [`task-migrate-contract-bootstrap-repair`](#task-migrate-contract-bootstrap-repair), [`task-repair-legacy-recovery`](#task-repair-legacy-recovery), [`task-resume`](#task-resume) |
|
|
378
|
+
| **Inspection & Diagnostics** | [`protocol-info`](#protocol-info), [`decision-status`](#decision-status), [`decision-show`](#decision-show), [`context-plan`](#context-plan), [`model-route`](#model-route), [`semantic-plan`](#semantic-plan), [`test-inventory`](#test-inventory), [`assess`](#assess), [`test-utility`](#test-utility), [`test-prune-plan`](#test-prune-plan), [`doctor`](#doctor), [`index-status`](#index-status), [`search`](#search), [`metrics`](#metrics), [`usage-record`](#usage-record), [`efficiency`](#efficiency), [`eval`](#eval), [`history`](#history), [`trace`](#trace), [`reflect`](#reflect), [`progress`](#progress), [`profile-interview`](#profile-interview), [`inspect`](#inspect), [`status`](#status), [`validate-state`](#validate-state), [`validate-protocol`](#validate-protocol) |
|
|
332
379
|
| **Verification & Completion** | [`test-prune-probe`](#test-prune-probe), [`quality-baseline`](#quality-baseline), [`quality-verify`](#quality-verify), [`quality-status`](#quality-status), [`prepare-completion`](#prepare-completion), [`run-check`](#run-check), [`record-check`](#record-check), [`record-terminal-result`](#record-terminal-result), [`audit`](#audit), [`report`](#report), [`validate-receipt`](#validate-receipt), [`verify-scope`](#verify-scope) |
|
|
333
380
|
| **Lifecycle & State** | [`discover`](#discover), [`contract-create`](#contract-create), [`gate-record`](#gate-record), [`gate-revalidate`](#gate-revalidate), [`activate`](#activate), [`route`](#route), [`preflight`](#preflight), [`advance`](#advance), [`next`](#next), [`record-diagnosis`](#record-diagnosis), [`record-intervention`](#record-intervention), [`record-hypothesis-disposition`](#record-hypothesis-disposition), [`record-decision-criterion`](#record-decision-criterion), [`complete`](#complete), [`clear-state`](#clear-state), [`reconcile-closure`](#reconcile-closure), [`task-create`](#task-create), [`task-list`](#task-list), [`task-show`](#task-show), [`task-lock-status`](#task-lock-status), [`task-scope`](#task-scope) |
|
|
334
381
|
| **Cross-Harness Continuity** | [`continuity`](#continuity), [`record-continuity`](#record-continuity), [`reconcile-continuity`](#reconcile-continuity), [`clear-continuity`](#clear-continuity), [`handoff-create`](#handoff-create), [`handoff-list`](#handoff-list), [`handoff-show`](#handoff-show) |
|
|
@@ -337,7 +384,7 @@ error codes. Default output and default JSON remain unchanged.
|
|
|
337
384
|
| **workspace** | [`workspace-bind`](#workspace-bind), [`workspace-status`](#workspace-status) |
|
|
338
385
|
| **task** | [`handoff-accept`](#handoff-accept) |
|
|
339
386
|
| **scope** | [`responsibility-set`](#responsibility-set), [`responsibility-status`](#responsibility-status) |
|
|
340
|
-
| **attestation** | [`attestation-create`](#attestation-create), [`attestation-verify`](#attestation-verify), [`attestation-status`](#attestation-status), [`attestation-verify-range`](#attestation-verify-range) |
|
|
387
|
+
| **attestation** | [`attestation-create`](#attestation-create), [`attestation-verify`](#attestation-verify), [`attestation-status`](#attestation-status), [`evidence-export`](#evidence-export), [`evidence-verify`](#evidence-verify), [`attestation-verify-range`](#attestation-verify-range) |
|
|
341
388
|
|
|
342
389
|
<!-- END FORGELOOP GENERATED: cli-command-index -->
|
|
343
390
|
|
|
@@ -764,6 +811,44 @@ Reports local attestation status and trust level without network access.
|
|
|
764
811
|
forgeloop attestation-status --task task-001 --json
|
|
765
812
|
```
|
|
766
813
|
|
|
814
|
+
### `evidence-export`
|
|
815
|
+
|
|
816
|
+
Exports a completed task's attestation as a portable, redacted evidence bundle
|
|
817
|
+
to commit with the change. See [`EVIDENCE_BUNDLES.md`](./EVIDENCE_BUNDLES.md).
|
|
818
|
+
|
|
819
|
+
<!-- BEGIN FORGELOOP GENERATED: cli:evidence-export:options -->
|
|
820
|
+
|
|
821
|
+
- `--path <directory>`: target project directory (default: current directory)
|
|
822
|
+
- `--task <id>`: task ID to operate on (when omitted, resolved from context or single active task)
|
|
823
|
+
- `--dir <path>`: tracked evidence directory (default: .forgeloop-evidence)
|
|
824
|
+
- `--json`: emit the export result as JSON
|
|
825
|
+
|
|
826
|
+
<!-- END FORGELOOP GENERATED: cli:evidence-export:options -->
|
|
827
|
+
|
|
828
|
+
### `evidence-verify`
|
|
829
|
+
|
|
830
|
+
Verifies committed evidence bundles for a revision range without local
|
|
831
|
+
ForgeLoop state. Unsigned bundles yield `INTEGRITY_ONLY`; signatures under the
|
|
832
|
+
verifier's policy yield `ATTESTED`.
|
|
833
|
+
|
|
834
|
+
<!-- BEGIN FORGELOOP GENERATED: cli:evidence-verify:options -->
|
|
835
|
+
|
|
836
|
+
- `--path <directory>`: target project directory (default: current directory)
|
|
837
|
+
- `--revision-provider <provider>`: revision provider (default: git)
|
|
838
|
+
- `--base <revision>`: base revision of the verified range
|
|
839
|
+
- `--head <revision>`: head revision of the verified range
|
|
840
|
+
- `--dir <path>`: tracked evidence directory (default: .forgeloop-evidence)
|
|
841
|
+
- `--exclude <path>`: changed path or dir/** excluded from coverage (verifier policy) (repeatable)
|
|
842
|
+
- `--allow-partial-coverage`: report uncovered changed paths without failing
|
|
843
|
+
- `--require-signature`: require a valid Sigstore signature for every bundle used
|
|
844
|
+
- `--identity <identity>`: exact signer identity policy
|
|
845
|
+
- `--issuer <issuer>`: exact signer issuer policy
|
|
846
|
+
- `--trusted-root <path>`: trusted signing root path
|
|
847
|
+
- `--format <text|markdown>`: human output format (default: text)
|
|
848
|
+
- `--json`: emit the verification result as JSON
|
|
849
|
+
|
|
850
|
+
<!-- END FORGELOOP GENERATED: cli:evidence-verify:options -->
|
|
851
|
+
|
|
767
852
|
### `attestation-verify-range`
|
|
768
853
|
|
|
769
854
|
Verifies attestation coverage for an opaque revision range through the
|
package/docs/CODE_ATTESTATION.md
CHANGED
|
@@ -140,6 +140,13 @@ distinguished from invalid attestations by the stable exit-code contract:
|
|
|
140
140
|
See [`REVISION_PROVIDERS.md`](./REVISION_PROVIDERS.md) and
|
|
141
141
|
[`SIGNING_PROVIDERS.md`](./SIGNING_PROVIDERS.md) for extension boundaries.
|
|
142
142
|
|
|
143
|
+
## Verifying in pull-request CI
|
|
144
|
+
|
|
145
|
+
Attestations live in the local `.forgeloop/` state. To verify them in CI,
|
|
146
|
+
export each completed task with `forgeloop evidence-export` and commit the
|
|
147
|
+
bundle; `forgeloop evidence-verify` then checks the range without local state.
|
|
148
|
+
See [`EVIDENCE_BUNDLES.md`](./EVIDENCE_BUNDLES.md).
|
|
149
|
+
|
|
143
150
|
## Receipt availability in repository CI
|
|
144
151
|
|
|
145
152
|
The repository audit workflow checks supplied task receipts individually with
|
package/docs/FORGELOOP_AUDIT.md
CHANGED
|
@@ -50,7 +50,7 @@ uploading a repository through the browser.
|
|
|
50
50
|
|
|
51
51
|
These are existing captures of the ForgeShop demo, taken from the production
|
|
52
52
|
renderer at 1440 × 900 in the dark theme, aligned to Audit `0.3.0-rc.3` and
|
|
53
|
-
ForgeLoop `2.0.0
|
|
53
|
+
ForgeLoop `2.0.0`. The demo deliberately includes invalid, stale, blocked and
|
|
54
54
|
unverified scenarios. Its warnings and coverage values do not establish
|
|
55
55
|
completion or production readiness for your project.
|
|
56
56
|
|
package/docs/GETTING_STARTED.md
CHANGED
|
@@ -227,7 +227,7 @@ Discover the deterministic task state path using `task-show`:
|
|
|
227
227
|
forgeloop task-show --task task-contact-form-001 --json
|
|
228
228
|
```
|
|
229
229
|
|
|
230
|
-
|
|
230
|
+
Write the contract to a project-relative input file outside `.forgeloop/task-state/` (for example `contract-input.json`). Writing it directly into the task-state directory creates legacy operational state next to canonical SQLite and makes later commands fail with `E_STORAGE_MIGRATION_REQUIRED`:
|
|
231
231
|
|
|
232
232
|
```json
|
|
233
233
|
{
|
|
@@ -271,6 +271,13 @@ Then write the task contract to `.forgeloop/task-state/<taskKey>/contract.json`:
|
|
|
271
271
|
}
|
|
272
272
|
```
|
|
273
273
|
|
|
274
|
+
Then let ForgeLoop record it transactionally (discovery first, when `next` asks for it):
|
|
275
|
+
|
|
276
|
+
```bash
|
|
277
|
+
forgeloop discover --task task-contact-form-001 --json
|
|
278
|
+
forgeloop contract-create --task task-contact-form-001 --contract-file contract-input.json --json
|
|
279
|
+
```
|
|
280
|
+
|
|
274
281
|
---
|
|
275
282
|
|
|
276
283
|
### Step 2 — Route Guides Deterministically
|
package/docs/PACKAGE_CONTENTS.md
CHANGED
|
@@ -38,10 +38,9 @@ The published tarball includes the following consumer-facing groups:
|
|
|
38
38
|
|
|
39
39
|
- **Runtime and protocol:** every maintained JavaScript module under `src/`,
|
|
40
40
|
the guide registry, protocol templates, JSON schemas, completions, and the
|
|
41
|
-
generic CI verifier.
|
|
42
|
-
|
|
43
|
-
`
|
|
44
|
-
`src/core/gates.js`, and `src/core/workflow-compatibility.js`.
|
|
41
|
+
generic CI verifier. The four retired compatibility helpers that 2.0.0
|
|
42
|
+
excluded (`cli-metadata`, `decision-classification`, `gates`,
|
|
43
|
+
`workflow-compatibility`) were removed from `src/core` in 2.1.0.
|
|
45
44
|
This includes the provider-neutral Repository Index runtime and its pinned
|
|
46
45
|
`src/repository-index/tgrep-manifest.json`; native engine binaries are
|
|
47
46
|
provisioned outside the npm tarball.
|
|
@@ -129,7 +128,7 @@ The tarball intentionally omits repository-only material:
|
|
|
129
128
|
|
|
130
129
|
The package test checks all registered guide paths and these exclusion classes. It
|
|
131
130
|
also enumerates `src/**/*.js` and fails if a maintained runtime module is
|
|
132
|
-
missing from the candidate tarball
|
|
131
|
+
missing from the candidate tarball.
|
|
133
132
|
The repository index remains a catalog: links from `DOCS_INDEX.md` to tests,
|
|
134
133
|
historical plans, and source trees may intentionally resolve only in the full
|
|
135
134
|
repository and are not package dependencies. The canonical documentation and
|
|
@@ -4,20 +4,77 @@ This is the current release checklist for the PolyForm Noncommercial-licensed
|
|
|
4
4
|
`@cassiomc1/forgeloop` package. It is a preparation and verification checklist;
|
|
5
5
|
it does not authorize publication.
|
|
6
6
|
|
|
7
|
-
## Stable 2.
|
|
7
|
+
## Stable 2.2.0 candidate — 2026-11-16
|
|
8
8
|
|
|
9
|
-
|
|
9
|
+
`2.2.0` is a minor release of the core package. It adds `forgeloop assess`,
|
|
10
|
+
`evidence-export` and `evidence-verify` with ledger metrics, and the cloud-sync
|
|
11
|
+
`sync-push` and `sync-pull` commands, with their error codes. Its runtime
|
|
12
|
+
changes are bound by
|
|
13
|
+
[`stable-2.2.0-writer-review.json.gz`](../benchmarks/storage-sqlite/stable-2.2.0-writer-review.json.gz),
|
|
14
|
+
a delta review against 2.1.0:
|
|
15
|
+
|
|
16
|
+
- Every changed module keeps identical filesystem bindings.
|
|
17
|
+
- 23 added bindings, all in new modules, each have an explicit role.
|
|
18
|
+
- `sync-pull` is a tenth explicit maintenance-admission command; a test proves
|
|
19
|
+
that it leaves a project under retained maintenance unchanged.
|
|
20
|
+
|
|
21
|
+
Before dispatching `npm-publish.yml`:
|
|
22
|
+
|
|
23
|
+
1. Merge the release commit to `main`.
|
|
24
|
+
2. Tag it `v2.2.0`.
|
|
25
|
+
3. Dispatch from that tag with channel `latest` and confirmation
|
|
26
|
+
`PUBLISH PUBLIC PACKAGE`.
|
|
27
|
+
|
|
28
|
+
Windows, rollback drills, hosted parity and registry-user audits are recorded
|
|
29
|
+
as not repeated or post-publication. After publication run:
|
|
30
|
+
|
|
31
|
+
```bash
|
|
32
|
+
npm view @cassiomc1/forgeloop version dist-tags --json
|
|
33
|
+
npm run release:identity -- --version 2.2.0 --release-commit <release-tag-commit>
|
|
34
|
+
```
|
|
35
|
+
|
|
36
|
+
## Stable 2.1.0 publication — 2026-11-14
|
|
37
|
+
|
|
38
|
+
`2.1.0` is a minor release of the core package (the published error registry
|
|
39
|
+
gains every emitted code, 159 of them as `PUBLIC_UNCLASSIFIED`). Its runtime
|
|
40
|
+
changes are bound by
|
|
41
|
+
[`stable-2.1.0-writer-review.json.gz`](../benchmarks/storage-sqlite/stable-2.1.0-writer-review.json.gz),
|
|
42
|
+
a delta review against 2.0.0 with identical filesystem bindings and an explicit
|
|
43
|
+
disposition for every changed, added and removed module.
|
|
44
|
+
`scripts/check-release-channel.mjs` selects the review by exact package version
|
|
45
|
+
and never falls back to an earlier report.
|
|
46
|
+
|
|
47
|
+
Published from tag `v2.1.0` (commit `bbf0f2a30d356812834c85098179250f07d78842`)
|
|
48
|
+
through `npm-publish.yml` with trusted OIDC publishing: npm `latest` is `2.1.0`,
|
|
49
|
+
`dist.integrity` is
|
|
50
|
+
`sha512-Kcv3h+k8SUVfohiHOHsvgaXwf8OitwDn6f62Mgm5hu3TKR7WKTOHhuLAf5q+oKPmzZ33pJDP3iXBhOJyCyrRKg==`,
|
|
51
|
+
the provenance statement is in the Sigstore transparency log (index
|
|
52
|
+
3890066512), and `release:identity` returns `RELEASE_IDENTITY_VALID`.
|
|
53
|
+
ForgeLoopAudit vendors this exact archive. Hosted parity, native Windows, rollback drills and
|
|
54
|
+
registry-user audits from 2.0.0 are not carried forward as evidence for these
|
|
55
|
+
bytes; the review records them as not repeated or post-publication. Re-check
|
|
56
|
+
the published identity with:
|
|
57
|
+
|
|
58
|
+
```bash
|
|
59
|
+
npm view @cassiomc1/forgeloop version dist-tags --json
|
|
60
|
+
npm run release:identity -- --version 2.1.0 --release-commit <release-tag-commit>
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
## Stable 2.0.0 publication — 2026-10-18
|
|
64
|
+
|
|
65
|
+
The published core package is `2.0.0` on npm `latest`, with Node.js
|
|
10
66
|
24.19.0+ and built-in `node:sqlite`. The MCP companion retains restricted
|
|
11
67
|
distribution and admits the stable core peer. Canonical SQLite is the sole
|
|
12
68
|
supported operational writer; configuration, portable exports, immutable
|
|
13
69
|
attachments and owner-bound maintenance evidence retain explicit file roles.
|
|
14
70
|
|
|
15
71
|
The [release acceptance record](STABLE_2_ACCEPTANCE.md) identifies source-bound
|
|
16
|
-
writer review, full verification,
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
72
|
+
writer review, full verification, accepted final-source hosted parity, native
|
|
73
|
+
candidate and actual unversioned registry-user checks. Trusted publication and
|
|
74
|
+
release identity are verified. Its retained evidence separates the supported
|
|
75
|
+
writer boundary from physical power-loss, privileged external writers and
|
|
76
|
+
production cutover. Future releases require fresh exact-source checks; earlier
|
|
77
|
+
receipts are not evidence for changed runtime bytes.
|
|
21
78
|
|
|
22
79
|
Verify the live registry and immutable release identity after publication:
|
|
23
80
|
|
|
@@ -134,10 +191,8 @@ never documentation, Git or task artifacts. Confirm the registry result
|
|
|
134
191
|
before reporting success. The version remains an RC; promotion does not
|
|
135
192
|
establish stable SQLite acceptance or production readiness.
|
|
136
193
|
|
|
137
|
-
The
|
|
138
|
-
`
|
|
139
|
-
not an RC4 promotion path; do not dispatch `POINT LATEST TO RC2` for the
|
|
140
|
-
current release. Its exact-identity and tag guards are retained.
|
|
194
|
+
The RC2-bound `promote-latest` operation and its promotion script were retired
|
|
195
|
+
after the stable 2.0.0 publication; `npm-publish.yml` now only publishes.
|
|
141
196
|
|
|
142
197
|
## ForgeLoop 2.0.0 candidate scope
|
|
143
198
|
|
|
@@ -249,8 +304,7 @@ deployment, and live data migration remain separate actions.
|
|
|
249
304
|
other `src/config/guides.json` path; no repository-only guide state is
|
|
250
305
|
packaged.
|
|
251
306
|
- [ ] Every maintained `src/**/*.js` module is present in the candidate
|
|
252
|
-
tarball;
|
|
253
|
-
excluded.
|
|
307
|
+
tarball; no runtime module is excluded.
|
|
254
308
|
|
|
255
309
|
## Protocol and attestation
|
|
256
310
|
|
|
@@ -1,80 +1,127 @@
|
|
|
1
1
|
# Stable ForgeLoop 2.0.0 acceptance
|
|
2
2
|
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
3
|
+
ForgeLoop **2.0.0** is published on npm **latest**. The immutable `v2.0.0` tag
|
|
4
|
+
and registry `gitHead` identify `4ff11bb4bc4be39b095a151a323f1388dad0d819`.
|
|
5
|
+
[PR #229](https://github.com/cassiomc1/forgeloop/pull/229) merged after all six
|
|
6
|
+
required checks passed on that head. The protected merge has the same release
|
|
7
|
+
tree and retains the reviewed commit as an ancestor.
|
|
7
8
|
|
|
8
|
-
##
|
|
9
|
+
## Published identity and native user checks
|
|
9
10
|
|
|
10
|
-
The
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
11
|
+
The [trusted publication](https://github.com/cassiomc1/forgeloop/actions/runs/39133661722)
|
|
12
|
+
passed full verification and published with GitHub OIDC and signed provenance.
|
|
13
|
+
`release:identity` independently verified the version, remote tag, `gitHead`,
|
|
14
|
+
SHA-1 and SHA-512 of the actual registry tarball. npm processing completed
|
|
15
|
+
before user tests began. The archive SHA-256 is
|
|
16
|
+
`326fbd81db54b9164f862a383fba4861817bd31ee325cf07252fb0b1101bc835`.
|
|
17
|
+
|
|
18
|
+
The [fresh latest-install matrix](https://github.com/cassiomc1/forgeloop/actions/runs/39135810569)
|
|
19
|
+
installed the **unversioned** package with separate fresh home, npm cache,
|
|
20
|
+
configuration, prefix and project directories. Each host resolved **2.0.0**,
|
|
21
|
+
with matching registry identity and all sixteen checks passing:
|
|
22
|
+
|
|
23
|
+
| Native host | Runtime | Result |
|
|
24
|
+
| --- | --- | --- |
|
|
25
|
+
| macOS ARM64 | Node 24.19.0 | 16/16 PASS |
|
|
26
|
+
| Windows x64 | Node 24.19.0 | 16/16 PASS |
|
|
27
|
+
| Linux x64 | Node 24.19.0 | 16/16 PASS |
|
|
28
|
+
|
|
29
|
+
Checks cover both bundled companions, live Jev health, initialization and
|
|
30
|
+
persistence, claim conflicts, contract/routing/preflight, eight concurrent
|
|
31
|
+
writers, WAL/SQLite/foreign-key integrity, tamper detection, mixed-state
|
|
32
|
+
refusal, backup/no-overwrite, a real review finding and correction with fresh
|
|
33
|
+
verification, validator-backed completion and completed-task restore into a new
|
|
34
|
+
directory. The temporary GitHub TypeSafe secret was removed after all reports
|
|
35
|
+
were retained and verified. Raw registry/user receipts are retained as
|
|
36
|
+
`benchmarks/storage-sqlite/stable-2.0.0-latest-*.json.gz`.
|
|
37
|
+
|
|
38
|
+
## Supported operational writer boundary
|
|
39
|
+
|
|
40
|
+
The [source review at the release tag](https://github.com/cassiomc1/forgeloop/blob/v2.0.0/benchmarks/storage-sqlite/stable-2.0.0-writer-review.json.gz)
|
|
41
|
+
binds all 511 core/MCP runtime JavaScript modules, 105 literal filesystem
|
|
42
|
+
modules, 457 lexical filesystem/wrapper references and sixteen indirect
|
|
43
|
+
references. Ninety-five filesystem modules retain reviewed bytes; ten deltas
|
|
44
|
+
have explicit dispositions. No nonliteral runtime import is present in that
|
|
45
|
+
inventory. Source hashes and the collector are retained with the review.
|
|
17
46
|
|
|
18
47
|
Supported CLI, Integration API and MCP dispatch select canonical SQLite.
|
|
19
|
-
Operational state, events, receipts, claims and indexed domain records share
|
|
20
|
-
native transaction boundary. Portable writers reject operational namespaces;
|
|
21
|
-
mixed
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
48
|
+
Operational state, events, receipts, claims and indexed domain records share
|
|
49
|
+
the native transaction boundary. Portable writers reject operational namespaces;
|
|
50
|
+
mixed layouts, foreign or expired contexts and actor-supplied persistence
|
|
51
|
+
capabilities fail closed. Explicit migration/restore retain ownership and
|
|
52
|
+
quiescence admission. The package advertises `soleSQLiteWriter: true` for this
|
|
53
|
+
supported boundary.
|
|
54
|
+
|
|
55
|
+
Configuration, installation manifests, portable exports/bundles and backups,
|
|
56
|
+
immutable attachments, owner-bound maintenance journals/archives, repository
|
|
57
|
+
index/cache, transport state and private scratch files remain explicit file
|
|
58
|
+
roles. They are not writable operational mirrors. Legacy data requires explicit
|
|
59
|
+
migration; native projects do not silently fall back to JSON.
|
|
60
|
+
|
|
61
|
+
`scripts/verify-stable-storage-review.mjs` checks complete runtime-module
|
|
62
|
+
membership and normalized source SHA-256 hashes. The stable channel guard
|
|
63
|
+
requires that source check. New modules or changed runtime bytes require review.
|
|
64
|
+
The manifest is not a signature, universal absence proof or substitute for
|
|
65
|
+
behavioral verification. The older call-name inventory retains
|
|
66
|
+
`wholeConsumerClosure: false` and remains discovery-only.
|
|
67
|
+
|
|
68
|
+
## Source-bound release validation
|
|
69
|
+
|
|
70
|
+
Full local pre-push on `780b9338` passed 3,109 tests with zero failures and sixteen
|
|
71
|
+
optional skips, plus coverage, critical coverage, lint, dependency/complexity,
|
|
72
|
+
documentation, package, MCP and Python validators. The final delta at `4ff11bb4`
|
|
73
|
+
corrected only three Markdown formatting errors; exact-head required CI and
|
|
74
|
+
full tag-publication verification passed on that final source. The
|
|
75
|
+
[native candidate matrix](https://github.com/cassiomc1/forgeloop/actions/runs/39128718653)
|
|
76
|
+
also passed 16/16 on each host before publication. All post-merge workflows,
|
|
77
|
+
including full Windows, Node compatibility, package, documentation and CodeQL,
|
|
78
|
+
passed on the identical protected-merge tree.
|
|
79
|
+
|
|
80
|
+
The [final-source hosted pair](https://github.com/cassiomc1/forgeloop/actions/runs/39128716481)
|
|
81
|
+
meets the owner-approved plan §9 criterion: 1,000 canonical-rich-all tasks,
|
|
82
|
+
ordinary ten events, one selected task with 1,000 events, 200 timed/resource
|
|
83
|
+
samples per side, exact output parity, validated closed workers and parent,
|
|
84
|
+
matching before/after source manifests, and successful root cleanup observers.
|
|
85
|
+
|
|
86
|
+
| Operation | Native p95 | Pinned baseline p95 |
|
|
87
|
+
| --- | --- | --- |
|
|
88
|
+
| taskListTool | 2,161.862 ms | 4,361.678 ms |
|
|
89
|
+
| projectTasksResource | 2,141.102 ms | 4,364.023 ms |
|
|
90
|
+
|
|
91
|
+
Both native p95 values are lower than baseline
|
|
92
|
+
`ee9ce11123d4e728d3dbc92f5d62d4bf41bb79c5`. This proves the recorded replacement
|
|
93
|
+
criterion, not every original benchmark dimension. The raw receipt deliberately
|
|
94
|
+
retains `releaseThresholdsVerified: false`; it has not been relabeled as full
|
|
95
|
+
original-matrix acceptance. Final-source artifacts are retained under
|
|
96
|
+
`benchmarks/storage-sqlite/stable-2.0.0-hosted-*`.
|
|
97
|
+
|
|
98
|
+
[Linux and Windows public rollback](https://github.com/cassiomc1/forgeloop/actions/runs/39126195649)
|
|
99
|
+
passed all sixteen cases per host at `61447313`; macOS passed the same sixteen
|
|
100
|
+
cases at that revision with unchanged source. The
|
|
101
|
+
[Linux/Windows old-client exclusion drill](https://github.com/cassiomc1/forgeloop/actions/runs/39125628347)
|
|
102
|
+
passed at `e9139a55`; the macOS drill passed at `61447313` with cleanup. These
|
|
103
|
+
receipts retain their precise source revisions and inventoried installation
|
|
104
|
+
boundary. Later stable metadata and documentation changes do not expand those
|
|
105
|
+
exclusion claims. Current-source full tests and fresh registry checks remain
|
|
106
|
+
separate evidence.
|
|
107
|
+
|
|
108
|
+
## ForgeLoopAudit alignment
|
|
109
|
+
|
|
110
|
+
[ForgeLoopAudit](https://github.com/cassiomc1/forgeloop/tree/main/ForgeLoopAudit) pins the actual public 2.0.0 archive
|
|
111
|
+
and release commit. All 52 shipped schema files were compared with the exact
|
|
112
|
+
release source before regenerating its trusted 31-schema provenance. Its own
|
|
113
|
+
lineage checks and recaptured README images identify stable core 2.0.0. Audit
|
|
114
|
+
retains its separate full verification, native-platform and browser gates; core
|
|
115
|
+
publication does not publish an Audit binary. Audit remains a read-only unsigned
|
|
116
|
+
preview and uses the public Integration API.
|
|
71
117
|
|
|
72
118
|
## Limits
|
|
73
119
|
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
120
|
+
Process-kill drills do not establish physical power-loss behavior. Privileged
|
|
121
|
+
raw SQLite access, arbitrary host providers/external commands and uninventoried
|
|
122
|
+
legacy installations are outside this proof. Production migration still needs a
|
|
123
|
+
named target, backup, writer inventory and operator-enforced quiescence. No live
|
|
124
|
+
user project was migrated by these release tests. Historical migration
|
|
125
|
+
scoreboards retain their original source/date and do not describe current
|
|
126
|
+
release completion. No production deployment or Audit binary publication is
|
|
127
|
+
implied.
|