ArkGate
4.1.0

Published · npm latest

Field honesty + Next monorepo dogfood.

Minor over 4.0.1. Single ship train from real consumer monorepos and SPA trees—no required config migration, no weakened value edges, no false green doctor stories.

Upgrade

Get 4.1.0

npm install -D arkgate@4.1.0
npx arkgate-check --install-agent-gates --force
npx arkgate-check --doctor

Prefer project-local npx arkgate upgrade over a global binary. Optional on brownfield Next with an old config: npx arkgate-check --migrate-contract --write to classify API routes as Application without full re-init.

What changed

In plain English

Next API handlers sit in Application

app/api/** and pages/api/** default to Application; UI routes stay Presentation. Works with overlays and monorepo presets.

Doctor stays honest when work remains

Status stays unfinished when design is weak, coverage is thin, residual debt is open, or related honesty sensors fire—not a vanity “all green” score.

Nested packages find the monorepo contract

Running checks from a package subdirectory still resolves the shared config. Mutative writes stay under that package’s root unless you deliberately widen write scope.

Type-only edges warn; value edges still block

Denied type-only imports surface as placement debt (non-blocking on strict merge). Runtime value edges still fail. Isolation rules for type-only peer imports stay hard where configured.

SPA and library trees classify cleanly

Start/adopt paths reduce empty Application buckets and “everything is Presentation” lies so status lights match the tree.

Retrofit Next API patterns in place

Update an existing contract for the API shell without wiping hand-tuned layers and rules.

Path aliases work in the editor plugin

tsconfig paths / baseUrl (e.g. @/*) resolve so editor checks match CLI analysis.

Config writes stay inside the project

Mutative --config outside the project root is refused. Forced gate reinstall keeps content digests honest for upgrades.

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

Field re-verify on a brownfield cohort (Next monorepos, Vite SPA, thin TS surfaces) passed critical gap assertions. Residual unfinished states are honest product states, not false greens.

Maintainer source: docs/releases/4.1.0.md ↗ · GitHub tag ↗