arkgate 4.8.8 → 4.8.9

package/CHANGELOG.md

@@ -3,6 +3,68 @@
 All notable changes to ArkGate (`arkgate`; formerly `ark-runtime-kernel`) are documented here or
 in the immutable pre-2.0 archive linked below.
 
+## 4.8.9 — 2026-09-01
+
+**Patch** over **4.8.8**. Field diagnostic honesty: doctor default homedir, live
+`peerIsolation` walls are not dead rules, skippable CI is `ci-not-fail-closed`
+not `missing-gates`, blocked upgrade JSON carries `reasonCode` + `nextCommand`,
+content identity vs raw `afterHash`, cross-layer `peerIsolation` docs, and
+intent-reference checks share the import classifier. Amarilla ArkOrder:
+`appliesTo`, watchlist vs `maxXiKeys`, `restore`, default clock, `hashOf`,
+`.d.ts` honesty, packaged example URL, and ingest-payload honesty.
+**No required config migration.** No `ark.config.json` schema bump. Does not close `K01` / `Z09`.
+No new skill names.
+
+**Status: prepared** (tree candidate; npm `latest` remains **4.8.8** until the
+signed-tag provenance workflow succeeds).
+
+### Added
+- Optional `arkOrder.appliesTo` globs (same engine as layers). `managedLayers`
+  still required; empty or absent `appliesTo` keeps today's all-files-in-layer
+  emit; a Persistence write outside the globs stays silent.
+- `OrderPlane.restore(release)` installs a previously frozen `Release` (current
+  + version). Hash remains the identity. Not durable. Does not close `K01`.
+- Public `arkgate/order` exports `hashOf` (alias of `hashReleasePayload`) so a
+  stored `Release.hash` can be verified without calling `release()`.
+
+### Fixed
+- `--doctor` no longer throws when `CLAUDE_HOME` / `GROK_HOME` / `ANTIGRAVITY_HOME`
+  are unset (`skillsDirFor` now defaults `os.homedir()`).
+- `contract-dead-rule` skips a live `peerIsolation` wall (`allowed: false` on a
+  same-layer or cross-layer pair). A self-allow stays dead. The fix text never
+  tells an agent to delete that wall.
+- `--strict-merge` / `--require-gates` still fail skippable CI (`if:` other than
+  `true` / `always()`), but as `ci-not-fail-closed` (names the workflow file).
+  `missing-gates` remains only for files that are actually absent.
+- Blocked `ark upgrade --apply --json` includes `reasonCode: managed-consent-required`
+  and a digest-bound `nextCommand` already carrying `--accept-conflicts`. Apply stays
+  atomic.
+- `LAYER_INTENT_REFERENCE_VIOLATION` uses the same `peerIsolation` classifier as
+  imports (`fromPath` + `sharedRoots`). Shared-root files do not inherit the
+  slice-wall message. Cross-slice file imports still deny.
+- Default `createOrderPlane` clock is Kernel `Date.now()` (was `0` with no
+  warning). Domain stays clock-free. Tests that need determinism still inject.
+
+### Changed
+- Public managed-upgrade assets expose `beforeIdentity` / `afterIdentity`.
+  `afterHash` is the SHA-256 of the raw desired bytes; `state: current` is content
+  identity, so stamp-only `arkVersion` drift can be current with unequal raw hashes.
+- Docs: a slice wall on a cross-layer edge is a `peerIsolation` rule on that
+  `from`/`to` pair (`allowed: false`). Domain files without a slice fail-closed
+  unless listed in `sharedRoots`. No new engine mode, key, or skill.
+- `maxXiKeys` caps one `release()` / `assertXiKeyCap` only. `xiKeys` is a
+  repo-wide watchlist; eight named keys with `maxXiKeys` 7 is valid config.
+  Sensor `arkorder-too-many-params` fires on `release()` `keyCount`, not on
+  config list length.
+- Public `dist/order` `.d.ts` no longer says declarations-only / no runtime.
+- Packaged docs point the billing gallery at the GitHub tree
+  (`https://github.com/pedroknigge/arkgate/tree/main/examples/arkorder-billing`).
+  The folder is not in the npm tarball; `examples/` is not added to
+  `package.json` `files`.
+- Ingest payload-dependent escalation stays deliberate: `classifyIngest` uses
+  `kind`; `ConstraintPack` forbids user predicates. "Second week failing a
+  goal" is a domain/projector kind, not a pack function.
+
 ## 4.8.8 — 2026-09-01
 
 **Patch** over **4.8.7**. ArkRun gains an opt-in terminal dashboard and bounded,
@@ -10,8 +72,7 @@ payload-free inspector monitors. ArkOrder and first-contact docs gain honesty co
 **No required config migration.** No `ark.config.json` schema bump. Does not close
 `K01` / `Z09`.
 
-**Status: prepared** (tree candidate; npm `latest` remains **4.8.7** until the
-signed-tag provenance workflow succeeds).
+**Status: published** (on npm `latest`; see `docs/releases/4.8.8.md`).
 
 ### Added
 - Dual **`ark-dashboard` / `arkgate-dashboard`** bins render the loopback ArkRun
@@ -40,7 +101,7 @@ show it when present. Caption-only edits do not change `policyHash`.
 **No required config migration.** No `schemaVersion` bump. Does not close `K01` / `Z09`.
 No new skill names.
 
-**Status: published** (on npm `latest`; see `docs/releases/4.8.7.md`).
+**Status: published** (see `docs/releases/4.8.7.md`).
 
 ### Added
 - Public name for existing `layers[].description`. Example:

package/README.md

@@ -37,7 +37,7 @@ Works with Cursor, Claude, Codex, and Grok.
 
 </div>
 
-> **ArkGate 4.8.8** is prepared on this tree; npm `latest` remains **4.8.7**.
+> **ArkGate 4.8.9** is prepared on this tree; npm `latest` remains **4.8.8**.
 > Write. Check. Ship. Adopted = required GitHub
 > status running `arkgate-check --strict-merge`, or an explicit `advisory-only` stance.
 > Status is compact (`arkgate-check --doctor`; `--all` for Details). Optional **ArkRun**
@@ -45,7 +45,7 @@ Works with Cursor, Claude, Codex, and Grok.
 > (`arkgate/order`) stops the agent rewriting the few slow product decisions as CRUD;
 > later pattern change is `proposeRelease` then `apply`.
 > `@arkgate/runtime` is deprecated.
-> [4.8.8 prepared](docs/releases/4.8.8.md) · [4.8.7 published](docs/releases/4.8.7.md) · [4.8.6](docs/releases/4.8.6.md) · [4.8.5](docs/releases/4.8.5.md) · [4.8.4](docs/releases/4.8.4.md) · [4.8.3](docs/releases/4.8.3.md) · [4.8.2](docs/releases/4.8.2.md) · [4.8.1](docs/releases/4.8.1.md) · [4.8.0](docs/releases/4.8.0.md) · [Docs hub](docs/README.md) · [Voice](docs/product-voice.md)
+> [4.8.9 prepared](docs/releases/4.8.9.md) · [4.8.8 published](docs/releases/4.8.8.md) · [4.8.7](docs/releases/4.8.7.md) · [4.8.6](docs/releases/4.8.6.md) · [4.8.5](docs/releases/4.8.5.md) · [4.8.4](docs/releases/4.8.4.md) · [4.8.3](docs/releases/4.8.3.md) · [4.8.2](docs/releases/4.8.2.md) · [4.8.1](docs/releases/4.8.1.md) · [4.8.0](docs/releases/4.8.0.md) · [Docs hub](docs/README.md) · [Voice](docs/product-voice.md)
 
 ---
 
@@ -321,8 +321,10 @@ PATCHes those keys through Prisma is named. Same npm package.
 In-memory. Not durable. Does not replace ArkRun.
 **ArkOrder freezes the pattern through a valve. ArkRun is how the residual travels.**
 
-Copy [examples/arkorder-billing/](examples/arkorder-billing/) and rename the
-three keys. Compact starters leave it off. Details:
+The billing gallery (`plan` / `cycle` / `tenancy`) lives on GitHub, not in the
+npm tarball:
+[examples/arkorder-billing](https://github.com/pedroknigge/arkgate/tree/main/examples/arkorder-billing).
+Rename the three keys. Compact starters leave it off. Details:
 [ArkOrder](docs/arkorder.md) · [configuration](docs/configuration.md) ·
 [package surface](docs/package-surface.md).
 
@@ -340,8 +342,9 @@ three keys. Compact starters leave it off. Details:
 | Config · package surface · TS | [configuration](docs/configuration.md) · [package-surface](docs/package-surface.md) · [typescript-support](docs/typescript-support.md) |
 | Brownfield | [docs/brownfield-adoption.md](docs/brownfield-adoption.md) |
 | Security | [SECURITY.md](SECURITY.md) |
-| Prepared (4.8.8; not published) | [docs/releases/4.8.8.md](docs/releases/4.8.8.md) · [CHANGELOG](CHANGELOG.md) |
-| Current published (4.8.7 on npm `latest`) | [docs/releases/4.8.7.md](docs/releases/4.8.7.md) · [CHANGELOG](CHANGELOG.md) |
+| Prepared (4.8.9; not published) | [docs/releases/4.8.9.md](docs/releases/4.8.9.md) · [CHANGELOG](CHANGELOG.md) |
+| Current published (4.8.8 on npm `latest`) | [docs/releases/4.8.8.md](docs/releases/4.8.8.md) · [CHANGELOG](CHANGELOG.md) |
+| Prior published (4.8.7) | [docs/releases/4.8.7.md](docs/releases/4.8.7.md) · [CHANGELOG](CHANGELOG.md) |
 | Prior published (4.8.6) | [docs/releases/4.8.6.md](docs/releases/4.8.6.md) |
 | Prior published (4.8.5) | [docs/releases/4.8.5.md](docs/releases/4.8.5.md) |
 | Prior published (4.8.4) | [docs/releases/4.8.4.md](docs/releases/4.8.4.md) |

package/bin/ark-check-runtime.mjs

@@ -47,6 +47,7 @@ import {
   REQUIRED_GATE_FILES,
   detectWritePathCapabilities,
 } from './lib/agent-gates.mjs';
+import { ciNotFailClosed } from './lib/gate-files.mjs';
 import { syncBaselineIntoCheckSurfaces } from './lib/field-install.mjs';
 import {
   detectEnforcement,
@@ -1307,6 +1308,27 @@ async function main() {
       process.exitCode = 1;
       return;
     }
+    if (args.requireGates) {
+      const ci = ciNotFailClosed(args.root);
+      if (ci) {
+        const payload = {
+          ok: false,
+          error: ci.error,
+          message: ci.message,
+          workflowFile: ci.workflowFile,
+          nextAction: ci.nextAction,
+          ...(writeRequest?.host ? { writeHost: writeRequest.host } : {}),
+        };
+        if (args.json) {
+          console.log(JSON.stringify(payload, null, 2));
+        } else {
+          console.error(`${color.red('\u2716')} ${ci.error} ${ci.message}`);
+          console.error(`Next: ${ci.nextAction}`);
+        }
+        process.exitCode = 1;
+        return;
+      }
+    }
     // Gates present. This is a precondition, not a standalone report: stay quiet
     // in --json mode so the architecture check below owns the single JSON output.
     // When --require-gates is the only intent (no config/architecture run needed),

package/bin/ark-layer-match.mjs

@@ -362,15 +362,27 @@ export function crossSliceEdgeAllowed(allowedCrossSlice, fromSlice, toSlice) {
  * Fail-closed stays fail-closed: absent evidence denies. What changed in 4.8.4
  * is what counts as evidence — a declared shared root, or a declared directed
  * cross-slice edge, is the repo telling us its design, so it is no longer
- * "unclassifiable". Order: no paths → no slice folders → a side that is neither
- * in a slice nor declared shared → same slice → declared cross edge → deny.
+ * "unclassifiable". Order: no fromPath → no slice folders → intent (no toPath):
+ * shared-root allow / slice fail-closed → a side that is neither in a slice nor
+ * declared shared → same slice → declared cross edge → deny.
+ *
+ * Intent/event names are not files. Callers pass fromPath only and must not
+ * invent a toPath (that would mis-slice). A declared shared root is classified
+ * the same way as on import edges.
  */
 export function peerIsolationDecision(input) {
-    if (!input.fromPath || !input.toPath)
+    if (!input.fromPath)
         return { denied: true, reason: 'missing-path' };
     if (input.folderCount <= 0)
         return { denied: true, reason: 'no-slice-folders' };
     const fromClassified = Boolean(input.fromSlice) || input.fromShared === true;
+    if (!input.toPath) {
+        if (!fromClassified)
+            return { denied: true, reason: 'unclassifiable-path' };
+        if (!input.fromSlice)
+            return { denied: false };
+        return { denied: true, reason: 'missing-path' };
+    }
     const toClassified = Boolean(input.toSlice) || input.toShared === true;
     if (!fromClassified || !toClassified)
         return { denied: true, reason: 'unclassifiable-path' };
@@ -387,8 +399,9 @@ export function peerIsolationDecision(input) {
 /**
  * Boolean face of {@link peerIsolationDecision}, kept for parity consumers.
  *
- * Fail-closed: missing path, no classifiable folders, or unclassifiable either
- * side → deny. Same-slice → allow (return false). Cross-slice → deny unless the
+ * Fail-closed: missing fromPath, no classifiable folders, or unclassifiable
+ * either side → deny. Intent refs (no toPath) allow only a declared shared
+ * root. Same-slice → allow (return false). Cross-slice → deny unless the
  * rule declared that directed edge.
  */
 export function peerIsolationMustDeny(input) {
@@ -426,9 +439,11 @@ export function peerIsolationDenyExplanation(reason, context) {
  *   Same-layer is always allowed (historical short-circuit).
  * - `peerIsolation: true` + `allowed: false`: deny only when importer and importee
  *   resolve to **different** slice ids (same or cross layer). Same-slice → allow.
- *   Missing paths, no slice folders, or unclassifiable slices → **fail-closed**
- *   (deny): isolation is configured, so insufficient evidence must not silently
- *   allow a possible cross-slice edge.
+ *   File imports pass fromPath + toPath. Intent references pass fromPath only.
+ *   A declared shared root is classified (no denial). Missing fromPath, no slice
+ *   folders, or unclassifiable slices → **fail-closed** (deny): isolation is
+ *   configured, so insufficient evidence must not silently allow a possible
+ *   cross-slice edge.
  */
 export function findDeniedEdgeRule(rules, from, to, options) {
     return findDeniedEdgeDecision(rules, from, to, options)?.rule;
@@ -448,8 +463,8 @@ export function findDeniedEdgeDecision(rules, from, to, options) {
             const fromPath = options?.fromPath;
             const toPath = options?.toPath;
             const folders = resolveSliceFolders(rule, from, options?.layers);
-            const fromSlice = fromPath && toPath ? sliceIdForPath(fromPath, folders) : undefined;
-            const toSlice = fromPath && toPath ? sliceIdForPath(toPath, folders) : undefined;
+            const fromSlice = fromPath ? sliceIdForPath(fromPath, folders) : undefined;
+            const toSlice = toPath ? sliceIdForPath(toPath, folders) : undefined;
             const decision = peerIsolationDecision({
                 fromPath,
                 toPath,

package/bin/lib/agent-homes.mjs

@@ -108,7 +108,7 @@ function usesDefaultHome(spec, env, homeDir) {
 
 function skillsDirFor(host, env = process.env) {
   const spec = HOSTS[host];
-  return path.join(resolveHomeDir(spec, env), 'skills');
+  return path.join(resolveHomeDir(spec, env, os.homedir()), 'skills');
 }
 
 function readHomeCatalogFloor(skillsDir) {