Skip to content

arkgate v3.1.0

Latest
Latest

Choose a tag to compare

View all tags
@pedroknigge pedroknigge released this 15 Jul 14:32
v3.1.0
This tag was signed with the committer’s verified signature.
pedroknigge Pedro Knigge
SSH Key Fingerprint: 2yMsN35E9VkcNVMh2wC6EpqMuPtKy66aFf1IJB932WU
Verified
Learn about vigilant mode.
cad0382
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ArkGate 3.1.0

ArkGate 3.1 closes the deterministic change-integrity loop: it guards policy transitions,
evaluates complete multi-file patches before writes, and measures structural convergence against
an optional architecture change map. No breaking CLI or ark.config.json changes. No gate
weaken.

Highlights

Area 3.1.0 result
Policy transitions Classifies contract changes as strengthening, neutral, judgment-required, or weakening; risky changes require an acknowledgement bound to exact hashes and findings
Atomic preflight ark preflight, preflightChange(...), and MCP ark_prepare_change validate one complete create/update/delete batch before writes
Change map Optional schema 1.0 records planned files, layers, and edges without adding a required planning artifact
Convergence Stable satisfied, missing, contradictory, and unplanned structural findings; behavioral completion is explicitly not evaluated
Enforcement honesty Doctor and hook repair distinguish supported, installed, active, bypassable, and CI-verification state per operation
Context independence Fixed eval proves equivalent CLI/MCP/hook/final verdicts without relying on AGENTS.md, skill prose, or a live LLM
Release resilience First-push null SHAs are safe; npm publication can resume checksum and release-asset attachment after a partial workflow failure

Try the release

npm install -D arkgate@3.1.0
npx ark start
npx ark preflight --changes ./change-set.json --json
npx ark-check --doctor --json

The MCP registry descriptor is version-aligned in server.json; registry publication remains a
separate maintainer step after npm is visible on latest.

Compatibility and honesty

  • Existing projects that do not supply a change map keep their current workflow.
  • New JSON fields and schemas are additive within ArkGate 3.x.
  • The analysis-result envelope advances from schema 1.0 to 1.1; nextAction is additive and
    optional for consumer-owned TypeScript values, while ArkGate producers emit it deterministically.
  • MCP registration is advisory unless the host makes that path non-bypassable.
  • A hard local write claim is operation-scoped and requires an active supported hook.
  • Required CI status cannot be proven locally and remains labeled unverified there.
  • Structural convergence does not claim tests, acceptance criteria, or behavior are complete.

Maintainer publication checklist

Run only from clean main after the release commit lands, with explicit authorization:

npm run release:npm -- --dry
git tag -s v3.1.0 -m "arkgate v3.1.0"
git push origin v3.1.0
gh release create v3.1.0 --verify-tag \
  --title "arkgate v3.1.0" \
  --notes-file docs/releases/3.1.0.md
gh workflow run publish-npm.yml -f tag=v3.1.0 -f dry_run=false
npm view arkgate@3.1.0 version
gh release view v3.1.0
Assets 12
Loading