Skip to content

Forgevena v1.3 Implementation Status

Decision

The software-controlled v1.3.0 E1 implementation and historical release protocol are complete. The signed tag, npm package, GitHub Release, GHCR image, documentation, standalone binaries, checksums, SBOM, provenance, and distribution bundles were published from the approved release commit. This status records historical assurance and does not claim compliance with controls introduced after v1.3.0.

Implemented

Area Evidence Location
CLI decomposition Routing, entry, options, rendering, foundation, platform, ecosystem, governance, and engineering handlers have direct contract tests. src/cli/, test/cli-*-handlers.test.js, test/cli-entry-output.test.js
State recovery Atomic writes, checksums, exclusive locks, stale-lock recovery, journals, bounded retention, snapshots, recovery validation, and fail-closed corruption handling. src/state-engine.js, test/state-engine.test.js
Concurrency Exactly 32 concurrent state writers complete without lost updates. test/state-engine.test.js
Failure injection Disk-full and permission failures remain visible, preserve committed state, and remove owned temporary files. src/state-engine.js, test/state-engine.test.js
Corruption fuzzing 1,000 deterministic malformed journal cases fail without changing state. test/state-engine-fuzz.test.js
Vault lifecycle AES-256-GCM, Argon2id, PBKDF2 fallback, migration, rotation rollback, recovery, tamper rejection, and bounded encrypted history. src/credentials.js, test/credentials.test.js
Mutation testing State, vault, consent, policy, and rollback each exceed the 80% mutation threshold; the deterministic suite kills 19 of 19 safety mutants. scripts/mutation-gate.js, npm run test:mutation
Performance Warm CLI startup and ordinary state reads have enforced budgets of 250 ms and 50 ms. CLI startup uses one warm-up and the median of five measured launches so transient runner contention cannot mask sustained regressions. scripts/benchmark.js, src/performance-metrics.js, npm run benchmark
Coverage enforcement The test runner fails below 90% lines, 85% branches, or 90% functions. scripts/run-tests.js, npm run test:coverage
Managed documentation Canonical generated references update only when their prior content hash proves generator ownership; modified files fail closed as conflicts. src/documentation-generator.js, test/documentation-generator.test.js
Workspace compatibility Published-state fixtures for v1.1 and v1.2 migrate and roll back without losing state. test/fixtures/workspaces/, test/upgrade.test.js
CI Windows, Ubuntu, and macOS run the compatibility suite; Ubuntu additionally runs coverage, mutation, and performance gates. .github/workflows/ci.yml

Latest Local Verification

Gate Result
Node tests 235 passed
Overall line coverage 96.96% (minimum 90%)
Overall branch coverage 85.10% (minimum 85%)
Overall function coverage 92.38% (minimum 90%)
State line / branch / function coverage 98.78% / 94.63% / 97.78%
Credential line / branch / function coverage 99.34% / 92.15% / 100%
Mutation score 100% overall and per measured safety domain (19/19)
Corruption cases 1,000 passed
Concurrent writers 32 passed
Ordinary state read 0.84 ms (maximum 50 ms)
Warm CLI startup 127.66 ms (maximum 250 ms)
Canonical documentation Verified with zero drift

Published Release Evidence

Evidence Result
Signed tag v1.3.0 resolves to 004710388afa7f2888a0e2594ede2d3cde96fe1c
Release workflow Run 30292317567 succeeded
GitHub Release v1.3.0 published with release assets
npm forgevena@1.3.0 published
Container GHCR package published with 1.3.0 and latest tags

There are no remaining software-controlled or publication tasks for v1.3.0. Future corrections use a new immutable version.