Published · npm latest
Agent contract surface.
Minor over 4.2.1. Catalog, status, agent projection, skills packaging, finding refs—a guardrail for agents, not an autonomous architect. No required config migration.
Upgrade
Get 4.3.0
Prefer project-local npx arkgate upgrade over a global
binary. Optional agent surfaces:
npx arkgate status --json and
npx arkgate agents-md --write. Skills also install via
npx skills add ./node_modules/arkgate/templates/agent-skills
(same 13 names).
What changed
In plain English.
Diagnostic code catalog
Every public ruleId has why/fix text and a
docs/diagnostics.md anchor agents can open.
Unified status snapshot
ark status --json / MCP ark_status:
identity, write-path honesty, last check, residual counts—not a
score.
Version-matched agent projection
ark agents-md stamps package version and contract
summary into AGENTS.md. Non-authoritative: hooks and CI still
enforce.
Agent Skills packaging
The same 13 skills ship as Agent Skills–compatible layout for
npx skills add. No new skill names.
Stable finding refs
Diagnostics carry findingRef + baseline-compatible
targetKey so multi-turn agent loops re-address the
same debt.
Guardrail, not architect
Green edges ≠ finished design. Structure sensors are heuristics.
Soft hosts stay advisory at write; required CI
--strict-merge is the hard merge boundary.
Honesty notes
What did not change
- Write gate and CI fail-closed semantics for value layer edges
- ArkRules remain opt-in—no map means the same inter-layer verdict as 4.0.x
- Host hardness claims (hard vs advisory) are unchanged
- Plan B reshape remains judgment—never mechanical-safe by default
Skills and AGENTS projection never decide pass/fail. Residual design debt and soft-write hosts remain honest product states—not false greens.
Maintainer source: docs/releases/4.3.0.md ↗ · GitHub tag ↗