arkgate 4.8.22 → 4.8.23

package/dist/{types-yDNEQ603.d.ts → types-Bdj32QwA.d.ts}

@@ -1,4 +1,4 @@
-import { i as Policy, P as PolicyViolation, I as IntentName, j as IntentCreator, k as IntentRelationship, b as ArchitectureProfile, D as DomainEvent, E as EventMetadata, h as PolicyEnforcementMode, A as ArchitectureLayer, c as ArchitectureRule, d as ArkCheckConfig } from './types-fQ9-KrBj.js';
+import { i as Policy, P as PolicyViolation, I as IntentName, j as IntentCreator, k as IntentRelationship, b as ArchitectureProfile, D as DomainEvent, E as EventMetadata, h as PolicyEnforcementMode, A as ArchitectureLayer, c as ArchitectureRule, d as ArkCheckConfig } from './types-Ik_OakcI.js';
 
 /**
  * PolicyEngine

package/dist/{types-fQ9-KrBj.d.ts → types-Ik_OakcI.d.ts}

@@ -1,4 +1,4 @@
-import { a as ArkConfigRule, f as ArkConfigLayer, A as ArkConfig } from './configTypes-CTELo87-.js';
+import { a as ArkConfigRule, f as ArkConfigLayer, A as ArkConfig } from './configTypes-Bbf_MFGe.js';
 
 /**
  * Policy types for the Ark kernel.

package/docs/README.md

@@ -73,7 +73,8 @@ These are **not** the day-to-day product path. They stay in the repo for evidenc
 | Field adoption kit (scaffolding, not closed) | [field/](field/) |
 | Runtime hardening (experimental) | [production-hardening.md](production-hardening.md) |
 
-Current release: [CHANGELOG](../CHANGELOG.md) (`arkgate@4.8.22`; confirm npm with `npm view arkgate@4.8.22 version`; does not close `K01`).
+Current release: [CHANGELOG](../CHANGELOG.md) (`arkgate@4.8.23`; confirm npm with `npm view arkgate@4.8.23 version`; does not close `K01`).
+Prior published: [CHANGELOG](../CHANGELOG.md) (`arkgate@4.8.22`).
 Prior published: [CHANGELOG](../CHANGELOG.md) (`arkgate@4.8.21`).
 Prior published: [CHANGELOG](../CHANGELOG.md) (`arkgate@4.8.20`). Plain-English history: [arkgate.online/changelog](https://www.arkgate.online/changelog/).
 Prior published: [releases/4.8.11.md](releases/4.8.11.md) (`arkgate@4.8.11`).

package/docs/agent-guide.md

@@ -438,7 +438,14 @@ clusters per anchor directory (concentration, not volume — dispersed hooks nev
 fixed corpus-calibrated thresholds; anchors under `app/`/`pages/` are `fixedByConvention` and
 never move. `reshapePilot.nextPilot` is a **proposed** one-at-a-time card (`moveSample`,
 `movesTotal`, `successSignal`, `killSwitch`, `doNot[]`) and, when proposed, the single
-`pilotLoop` extraction card if no design-weak pattern bet is ahead of it. Run it only via
+`pilotLoop` extraction card if no design-weak pattern bet is ahead of it. A flat file
+at universe level that exactly one child slice imports is a later candidate
+(`doctor.flatParentPilot`, source `flat-parent`): the file, that child, and a
+destination folder inside the child that keeps the file's layer. Two importers,
+or none, produce no card. The sentence is a suggestion with that importer as
+its evidence. It does not change ark-check. `destinationKeepsLayerAndSlice`
+uses the same slice identity as the walls, so `sliceIdentity: "stars"` cannot
+treat two children as one slice. Run a card only via
 `/ark-loop` through the write gate + atomic preflight; merges are `/ark-adopt` /
 `/ark-autopilot` judgment cards. `notAScore`, never a verdict/`designFitness` input; there
 is no apply path.
@@ -1145,6 +1152,7 @@ edges are not denied by that rule.
 - **`sliceFolders`:** optional parent segments (default: inferred from layer globs). A bare name stays an unanchored one-segment match (`features` on `src/features/auth` is `features/auth`). A starred anchored pattern with `sliceIdentity` `path` (the default) includes the literal prefix plus the star bindings (`lib/features/*/*` → `lib/features/projects/rfi`), so parallel trees get different ids.
 - **`sliceIdentity`:** `path` (default, also when the key is absent) or `stars`. `path` keeps today's slice ids. `stars` names a starred prefix as the last literal plus the star bindings (`lib/features/*/*` and `lib/repositories/features/*/*` both yield `features/projects/rfi`). Doctor names both prefixes when they collapse onto one id. Additive — no migration.
 - **Fail-closed:** missing paths, empty/unresolvable slice folders, or unclassifiable either side → **deny** via peerIsolation (cannot prove same-slice).
+- **`childSlices`** (optional): a second wall under the same rule. The universe wall runs first and is unchanged when the block is absent. With it present, a cross-universe deny is `reasonId` `CROSS_PARENT_SLICE` (never advisory). Inside one universe, `commonFolders` and flat files are common; a child may import them; common may import a child only when `parentMayImportChild` is true. Sibling crossings are `CROSS_SIBLING_SLICE` — error when `siblings` is `deny` (the default), warning when `advisory`, and a new one past the baseline still fails. `ruleId` stays `LAYER_IMPORT_VIOLATION`. arkgate 4.8.22 and older reject the key.
 - **`sharedRoots`** (4.8.4): roots the repo declares shared on purpose (`["ui", "hooks", "lib/permissions"]`). A file under a declared shared root is evidence, not an unclassifiable path, so fail-closed stops firing on every shared file. **Anchored** — the root starts the path, optionally after one `src/` or `app/`; write deeper or monorepo roots out (`packages/web/src/ui`) or glob them, and a bare `*` / `**` is refused. A path that still resolves to a slice keeps its slice.
 - **`allowedCrossSlice`** (4.8.4): `[{ "from": "features/checkout", "to": "features/catalog" }]` — one directed slice→slice edge the repo declares on purpose. The reverse still denies.
 - **The denial names its reason:** `cross-slice edge a → b` (a fact about the code) vs `unclassifiable path (…)`, `no slice folders`, `no path evidence` (facts about the evidence ArkGate had).

package/docs/configuration.md

@@ -251,7 +251,7 @@ process module-capability family must be denied.
 Rule fields:
 
 - `from`, `to`, `allowed`, `message`, `peerIsolation`, `sliceFolders`, `sliceIdentity`,
-  `sharedRoots`, `allowedCrossSlice`, `sharedImportsSlice`
+  `sharedRoots`, `allowedCrossSlice`, `sharedImportsSlice`, `childSlices`
 - `peerIsolation: true` + `allowed: false`: deny only when slice ids differ; same-slice allows
   when both paths classify. Applies to **any** declared `from`→`to` pair, not only self-edges.
   Missing paths, empty slice folders, or unclassifiable slices **fail closed** (deny — cannot
@@ -276,6 +276,90 @@ Rule fields:
   same id, and the warning names both paths (`admin/features/*` and `public/features/*`
   both bind as `features/*`). That warning is advisory. Unrelated trees that share a
   last folder name should stay on `path`.
+- `childSlices` is an optional inner wall on a `peerIsolation` rule. Absent means today's
+  universe wall, byte for byte: no `reasonId`, same messages, same doctor output.
+  `sliceFolders` names the children (`lib/features/*/*` under a universe id `features/projects`).
+  `sliceIdentity` is the same `path` | `stars` choice. `commonFolders` (directory names such as
+  `domain`) and a flat file whose child id does not grow past the universe id are universe
+  common. A child may import that common code. Common code may import a child only when
+  `parentMayImportChild` is true (default false). `siblings` is `deny` (default, also when the
+  key is omitted), `advisory`, or `{ "default": "deny" | "advisory", "enforce": [...] }`.
+  The universe wall runs first. A denied cross-universe edge is
+  `reasonId` `CROSS_PARENT_SLICE` and is never advisory. A denied sibling edge is
+  `CROSS_SIBLING_SLICE`: an error when `siblings` is `deny` or `{ "default": "deny" }`,
+  a warning (`failsStrict: false`) when `advisory`. With `{ "default": "advisory", "enforce" }`,
+  a crossing whose importer is listed is an error. Every other sibling crossing stays a warning.
+  `enforce` entries are child slice ids (`features/projects/rfi`) or subtree paths
+  (`lib/features/projects/rfi` or `src/lib/features/projects/rfi`). A child id matches that
+  importer's child id. A path matches when the importer file sits in that directory.
+  Bare names do not match. `*` is not a wildcard on this list. `default: "deny"` denies every
+  sibling crossing; the list cannot loosen it. A new advisory crossing past the recorded
+  baseline still fails, the same ratchet as a string `advisory`. An enforce list does not
+  change that function. The baseline key stays `ruleId|file|fromLayer|toLayer|target` and does
+  not include `reasonId`. `productHonesty.finished` stays false while any child wall is
+  advisory, including `{ "default": "advisory", "enforce": [...] }`. The list does not finish
+  the house. Doctor `slices` is `{ crossParent, crossSibling, pairs }` for the directed universe
+  pairs that occur. A child id that does not extend its universe id warns
+  `CONFIG_CHILD_SLICE_EXTENDS` and is treated as universe common. arkgate 4.8.22 and older
+  reject `childSlices` (`CONFIG_CHILD_SLICES_VERSION`). A build that still types `siblings` as
+  the string enum `deny | advisory` rejects the object at config load
+  (`must be one of deny, advisory` at `$.rules[n].childSlices.siblings`). It does not ignore
+  the object. No published release through 4.8.22 accepts `{ default, enforce }`. Ship that
+  form only on a release that includes it.
+  `childSlices.allowedCrossSlice` is a directed list on the child block only:
+  `{ "from": "features/projects/*", "to": "features/projects/d2d-item" }`.
+  `*` matches one whole path segment. `**` and a partial segment (`feat*`) are
+  rejected at config load. A bare name (no `/`) is rejected, because it is
+  ambiguous across universes. The list clears only a `CROSS_SIBLING_SLICE`,
+  and only after the universe wall has allowed the edge. It never clears
+  `CROSS_PARENT_SLICE` or `CROSS_PARENT_VIA_SHARED`. A pattern that can name
+  two universes (`features/*/*` to `features/management/eos`) leaves the
+  cross-parent finding in place and warns `CONFIG_CHILD_SLICE_CROSS_UNIVERSE`
+  (`failsStrict: false`). The universe `allowedCrossSlice` does not read this
+  list and still treats `*` as a literal slice id, byte for byte with 4.8.22.
+  Adding an entry is a weakening policy delta. Removing one is strengthening.
+  Additions and removals together need a judgment. A wildcard that widens a
+  literal entry is weakening and needs the same acknowledgement. A build that
+  accepts `childSlices` and still rejects unknown fields fails at config load
+  (`unknown field` at `$.rules[n].childSlices.allowedCrossSlice`). It does not
+  ignore the key. No published release through 4.8.22 accepts the wildcard.
+  Ship it only on a release that includes this field.
+  `childSlices.sliceAliases` maps files that sit outside every slice folder onto
+  a child that already exists: `{ "from": "lib/compliance/**", "to": "features/projects/compliance" }`.
+  `to` is the universe id the universe wall already knows, plus one child segment.
+  A bare name, that universe id alone, an unknown universe, and a wildcard in `to`
+  are rejected at config load (`child of an existing universe`). The source glob
+  may cover only files the slice folders do not already classify. Overlap with a
+  universe `sliceFolders` entry or a child `sliceFolders` entry is rejected
+  (`overlaps a slice folder`). Two aliases that can match one file are rejected
+  (`two slice aliases match the same file`). An aliased file takes the target
+  universe id and the target child id for both walls, so an import into another
+  universe is `CROSS_PARENT_SLICE` and an import into another child of the same
+  universe is `CROSS_SIBLING_SLICE`. Same-child imports and imports into that
+  universe's common folders follow the existing child wall. Doctor lists every
+  alias as an owed move: the source glob, the target slice, the destination
+  folder, and the files. The section says the files are not finished. Aliases
+  are debt. `productHonesty.finished` stays false while any alias is set.
+  Adding aliases is a strengthening policy delta (unclassified files come under
+  the walls). Removing them is weakening (those files leave the walls) and needs
+  the same hash-bound acknowledgement as any other weakening. Additions and
+  removals in one change, including a retarget, are judgment-required. A folder
+  edit already asks for a judgment and covers the alias list. The baseline key
+  stays `ruleId|file|fromLayer|toLayer|target` and does not include `reasonId`.
+  The write hook, ESLint, snippet analysis, ark-check, and CI all see the alias
+  through one resolver. There is no skip flag. arkgate 4.8.22 and older reject
+  `childSlices`. A build that accepts `childSlices` and still rejects unknown
+  fields fails at config load (`unknown field` at `$.rules[n].childSlices.sliceAliases`).
+  It does not ignore the key. No published release through 4.8.22 accepts
+  `sliceAliases`. Ship a config that sets it only on a release that includes
+  this field. The write hook, ESLint, snippet analysis, ark-check, and CI all
+  see the per-edge decision.
+
+  Doctor may suggest moving a flat file that sits at universe level when
+  exactly one child slice imports it. The card names the file, that child, and
+  a destination folder inside the child that keeps the file's layer. It is a
+  suggestion. It is not a config field, not a finding, and not an ark-check
+  result. A file two children import stays where it is.
 
 ```jsonc
 {
@@ -346,6 +430,13 @@ is evidence:
   to `"deny"`. That hop is direct only — `allowedCrossSlice` does not excuse it. A green
   `ark-check` prints one line per layer edge (the count and three examples) and says the
   wall is direct-only. Every edge stays in `ark-check --json` and `ark-check --doctor`.
+  `"deny-cross-parent"` does not change that direct hop: it stays a `SHARED_IMPORTS_SLICE`
+  warning. It adds a whole-graph finding when a slice reaches a **different** universe
+  only through a shared root (`reasonId` `CROSS_PARENT_VIA_SHARED` on
+  `LAYER_IMPORT_VIOLATION`). A shared hop that stays inside one universe is not a finding.
+  That pass runs in `ark-check` and CI. The write hook and ESLint see one edge at a time
+  and do not block it. arkgate 4.8.22 and older reject the value at config load (`must be
+  one of deny`). They do not ignore it and they do not treat it as `"deny"`.
 - `allowedCrossSlice` entries match a full slice id (`features/catalog`) or a bare slice name
   (`catalog`), and only in the direction written. The reverse edge still denies. A bare name
   matches that name under **any** slice folder, so in a repo with several slice parents

package/docs/diagnostics.md

@@ -102,6 +102,9 @@ Link form for agents: `docs/diagnostics.md#RULE_ID` (exact-case HTML anchors bel
 | [`CONFIG_UNCLASSIFIED_FILES`](#CONFIG_UNCLASSIFIED_FILES) | config | Unclassified included files |
 | [`CONFIG_LAYER_MISSING_OWNER`](#CONFIG_LAYER_MISSING_OWNER) | config | Layer missing owner |
 | [`CONFIG_SLICE_IDENTITY_COLLISION`](#CONFIG_SLICE_IDENTITY_COLLISION) | config | Starred slice prefixes share one id |
+| [`CONFIG_CHILD_SLICES_VERSION`](#CONFIG_CHILD_SLICES_VERSION) | config | childSlices needs a newer arkgate |
+| [`CONFIG_CHILD_SLICE_EXTENDS`](#CONFIG_CHILD_SLICE_EXTENDS) | config | Child slice id does not extend its universe |
+| [`CONFIG_CHILD_SLICE_CROSS_UNIVERSE`](#CONFIG_CHILD_SLICE_CROSS_UNIVERSE) | config | Child slice allowance cannot cross the universe wall |
 | [`ARK_UNKNOWN`](#ARK_UNKNOWN) | meta | Unknown diagnostic |
 
 ## Layer and dependency graph
@@ -114,6 +117,8 @@ Link form for agents: `docs/diagnostics.md#RULE_ID` (exact-case HTML anchors bel
 
 - **Why:** This file imported a folder it may not reach. The write doesn’t land. The same check fails the pull request.
 - **Fix:** Branch by import kind: constants/types/pure → adopt into DomainModel or SharedKernel (do not invent a port); kernel/events/bootstrap from Persistence → inject a port or move the map to SharedTypes (Persistence must not emit); define a port only when the target is a real use-case. Type-only edges use `import type`. Then preflight again. Do not weaken the layer rule without a hash-bound policy acknowledgement.
+- **Slice reasons:** the ruleId stays `LAYER_IMPORT_VIOLATION`. When a rule sets `childSlices`, the finding may also carry `reasonId` `CROSS_PARENT_SLICE` (this import crosses two universe slices; the child wall cannot allow another universe) or `CROSS_SIBLING_SLICE` (this import crosses two feature slices inside one universe). `siblings` may be `"deny"`, `"advisory"`, or `{ "default", "enforce" }`. An enforced importer (`enforce` entry is that child id or a subtree path of the file) is an error. Every other sibling crossing is a warning, and a new one past the baseline still fails. `default: "deny"` denies every sibling crossing. `childSlices.allowedCrossSlice` may use a whole-segment `*` and clears only a sibling crossing. It does not clear `CROSS_PARENT_SLICE` or `CROSS_PARENT_VIA_SHARED`. The universe `allowedCrossSlice` still treats `*` as a literal. `childSlices.sliceAliases` maps a source path glob onto a child slice id (the universe id plus one child segment). An aliased file takes that universe id and that child id for both walls, so an import into another universe is still `CROSS_PARENT_SLICE`. A bare name, a universe id alone, an unknown universe, and a wildcard in `to` are rejected at config load. A glob that overlaps a slice folder is rejected. Two aliases that can match the same file are rejected. Doctor lists each alias as an owed move — the files, the target slice, and the destination folder — and does not count those files as finished. Adding aliases is a strengthening policy delta. Removing them is weakening. Additions and removals together, including a retarget, need a judgment. The baseline key does not include `reasonId`. Without `childSlices`, `reasonId` is absent on a direct edge. The write hook, ESLint, snippet analysis, ark-check, and CI all see this per-edge decision. arkgate 4.8.22 and older reject `childSlices`. A build that still types `siblings` as a string enum rejects the object at config load (`must be one of deny, advisory`). A build that still rejects unknown `childSlices` fields rejects `allowedCrossSlice` and `sliceAliases` at config load (`unknown field`). No published release through 4.8.22 accepts `sliceAliases`. Doctor may also suggest moving a flat universe-level file that exactly one child imports (`doctor.flatParentPilot`). That suggestion is not a finding, not a `ruleId`, and not part of the baseline key. A file imported by two children, or by none, is not suggested.
+- **`CROSS_PARENT_VIA_SHARED`:** `sharedImportsSlice` is `"deny-cross-parent"`. A slice reaches another universe only through a shared root. The finding's `file` is the slice that imported the shared root and `target` is the file in the other universe. The baseline key stays `ruleId|file|fromLayer|toLayer|target` and does not include `reasonId`. A shared hop that stays inside one universe is not this finding. The direct shared-root hop stays the `SHARED_IMPORTS_SLICE` warning. `"deny"` is unchanged and does not emit this reason. Doctor slice counts stay on `CROSS_PARENT_SLICE` and `CROSS_SIBLING_SLICE`. **ark-check and CI report this path. The write hook and ESLint see one edge at a time and do not block it.** arkgate 4.8.22 and older reject `"deny-cross-parent"` at config load.
 
 <a id="LAYER_INTENT_REFERENCE_VIOLATION"></a>
 
@@ -904,6 +909,33 @@ never opting out of knowing.
 - **Why:** `sliceIdentity` is `stars` and two different `sliceFolders` prefixes bind as the same slice id. Parallel trees of one feature do that on purpose; unrelated trees that share the last folder name merge by accident. The warning names both paths.
 - **Fix:** Keep `stars` when those prefixes are one feature. Otherwise use `path`, or rename the last literal so the prefixes do not bind as the same id. Advisory — it does not fail the check.
 
+<a id="CONFIG_CHILD_SLICES_VERSION"></a>
+
+### `CONFIG_CHILD_SLICES_VERSION`
+
+**childSlices needs a newer arkgate**
+
+- **Why:** The rule schema sets additionalProperties to false. arkgate 4.8.22 and older reject a config that contains childSlices instead of ignoring the key.
+- **Fix:** Pin arkgate newer than 4.8.22 before shipping a config that sets childSlices. This warning does not fail the check.
+
+<a id="CONFIG_CHILD_SLICE_EXTENDS"></a>
+
+### `CONFIG_CHILD_SLICE_EXTENDS`
+
+**Child slice id does not extend its universe**
+
+- **Why:** A path resolved a child id that is not the universe id plus a further segment. The child wall does not treat that id as a child, so the edge is universe common until the folders line up.
+- **Fix:** Point childSlices.sliceFolders at children under the same universe id the outer sliceFolders already names. Doctor names the path. Advisory — it does not fail the check.
+
+<a id="CONFIG_CHILD_SLICE_CROSS_UNIVERSE"></a>
+
+### `CONFIG_CHILD_SLICE_CROSS_UNIVERSE`
+
+**Child slice allowance cannot cross the universe wall**
+
+- **Why:** childSlices.allowedCrossSlice names a pattern that can match two universes. That list clears only a sibling crossing inside one universe. The universe wall still denies the edge.
+- **Fix:** Narrow the pattern so both sides share one universe prefix (features/projects/* to features/projects/d2d-item), or remove the entry. This warning does not fail the check.
+
 ## Meta
 
 <a id="ARK_UNKNOWN"></a>

package/docs/product-voice.md

@@ -80,7 +80,7 @@ On the seven lane openings — `docs/use.md`, `docs/develop.md`, `docs/README.md
 `README.md` is the first-contact module. Its first screen is four beats: what
 (**Contener · Guiar · Ordenar**), why (design the boundary before you implement;
 a green check is **needs a refactor** when leftover mess remains), one command
-(`npx arkgate@4.8.22 start`), and one honest red result (fail-open named; required
+(`npx arkgate@4.8.23 start`), and one honest red result (fail-open named; required
 CI is the hard line). The four paragraphs, the not-that line, the host matrix,
 and the release index sit below `## Appendix`. The not-that line does not lead
 the README.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arkgate",
-  "version": "4.8.22",
+  "version": "4.8.23",
   "description": "When the agent writes a bad import, the write doesn’t land. The same check fails the pull request.",
   "type": "module",
   "main": "./dist/index.cjs",

package/schemas/ark.config.schema.json

@@ -840,8 +840,130 @@
         "sharedImportsSlice": {
           "type": "string",
           "enum": [
-            "deny"
-          ]
+            "deny",
+            "deny-cross-parent"
+          ],
+          "description": "deny blocks every shared-root import of a slice. deny-cross-parent leaves that hop as a warning and, in ark-check and CI only, reports a slice that reaches another universe through a shared root. The write hook and ESLint see one edge and do not block it. arkgate 4.8.22 and older reject deny-cross-parent."
+        },
+        "childSlices": {
+          "type": "object",
+          "additionalProperties": false,
+          "required": [
+            "sliceFolders"
+          ],
+          "description": "Optional inner wall under this rule. Absent keeps today's universe wall. sliceFolders names children. commonFolders and flat files are universe common. siblings is \"deny\" (default), \"advisory\", or { default, enforce }. parentMayImportChild defaults to false. allowedCrossSlice may use a whole-segment *. It clears only a sibling crossing. Cross-parent has no advisory knob. arkgate 4.8.22 and older reject this key. A build that still rejects unknown childSlices fields rejects allowedCrossSlice at config load. A build that still types siblings as a string enum rejects the object at config load.",
+          "properties": {
+            "sliceFolders": {
+              "type": "array",
+              "items": {
+                "type": "string",
+                "minLength": 1
+              },
+              "uniqueItems": true,
+              "minItems": 1
+            },
+            "sliceIdentity": {
+              "type": "string",
+              "enum": [
+                "path",
+                "stars"
+              ]
+            },
+            "commonFolders": {
+              "type": "array",
+              "items": {
+                "type": "string",
+                "minLength": 1
+              },
+              "uniqueItems": true,
+              "minItems": 1
+            },
+            "siblings": {
+              "description": "\"deny\" or \"advisory\", or { default, enforce } so listed subtrees are errors while the default stays advisory. A string-enum build rejects the object at config load (must be one of deny, advisory).",
+              "oneOf": [
+                {
+                  "type": "string",
+                  "enum": [
+                    "deny",
+                    "advisory"
+                  ]
+                },
+                {
+                  "type": "object",
+                  "additionalProperties": false,
+                  "required": [
+                    "default"
+                  ],
+                  "properties": {
+                    "default": {
+                      "type": "string",
+                      "enum": [
+                        "deny",
+                        "advisory"
+                      ]
+                    },
+                    "enforce": {
+                      "type": "array",
+                      "items": {
+                        "type": "string",
+                        "minLength": 1
+                      },
+                      "uniqueItems": true
+                    }
+                  }
+                }
+              ]
+            },
+            "parentMayImportChild": {
+              "type": "boolean"
+            },
+            "sliceAliases": {
+              "type": "array",
+              "minItems": 1,
+              "description": "Maps a source path glob onto a child slice id (universe id plus one child segment) so files outside the slice trees take that universe and child for both walls. A bare name, a universe id alone, an unknown universe, and a wildcard in to are rejected. The glob may not overlap a slice folder, and two aliases may not match the same file. Doctor lists each alias as an owed move. A build that rejects unknown childSlices fields fails at config load (unknown field). arkgate 4.8.22 and older reject childSlices.",
+              "items": {
+                "type": "object",
+                "additionalProperties": false,
+                "required": [
+                  "from",
+                  "to"
+                ],
+                "properties": {
+                  "from": {
+                    "type": "string",
+                    "minLength": 1
+                  },
+                  "to": {
+                    "type": "string",
+                    "minLength": 1
+                  }
+                }
+              }
+            },
+            "allowedCrossSlice": {
+              "type": "array",
+              "minItems": 1,
+              "description": "Directed child-slice allowances. * matches one whole path segment (features/projects/*). ** and a partial segment are rejected. A bare name is rejected. This list clears only CROSS_SIBLING_SLICE. It cannot clear CROSS_PARENT_SLICE or CROSS_PARENT_VIA_SHARED. The universe allowedCrossSlice still treats * as a literal. A build that rejects unknown childSlices fields fails at config load (unknown field).",
+              "items": {
+                "type": "object",
+                "additionalProperties": false,
+                "required": [
+                  "from",
+                  "to"
+                ],
+                "properties": {
+                  "from": {
+                    "type": "string",
+                    "minLength": 1
+                  },
+                  "to": {
+                    "type": "string",
+                    "minLength": 1
+                  }
+                }
+              }
+            }
+          }
         }
       }
     },

package/server.json

@@ -6,12 +6,12 @@
     "url": "https://github.com/pedroknigge/arkgate",
     "source": "github"
   },
-  "version": "4.8.22",
+  "version": "4.8.23",
   "packages": [
     {
       "registryType": "npm",
       "identifier": "arkgate",
-      "version": "4.8.22",
+      "version": "4.8.23",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"

package/templates/agent-skills/README.md

@@ -9,7 +9,7 @@ closed `/ark-*` catalog shipped as flat templates for Ark install.
 **Closed catalog** (`ARK_SKILL_NAMES`) — first-class doors plus one-release
 redirect stubs. Add a name only with a live ROADMAP item.
 
-Package version when last generated context: **arkgate@4.8.22**
+Package version when last generated context: **arkgate@4.8.23**
 Schema: agent-skills package contract `1.0`
 
 ## Skills (closed catalog)