Files
callstack__agent-device/scripts/layering/zone-policy.ts
Michał Pierzchała 76453add71 refactor: pnpm workspace + @agent-device/kernel pilot (#1490 W0) (#1494)
* refactor: pnpm workspace + @agent-device/kernel pilot (#1490 W0)

Extend the workspace with packages/* and move the kernel behind an
enforced public API: packages/kernel with nine consumer-earned subpath
exports (errors, device, snapshot, contracts, collections, rect,
redaction, daemon-error, bounds — the last absorbed from utils as Rect
vocabulary). Every kernel import repo-wide becomes the
@agent-device/kernel/<sub> specifier; kernel tests move to
src/__tests__/kernel/ and exercise the package surface. The root
declares the package in devDependencies (workspace:*), tsdown bundles
it (noExternal) so the published artifact and its runtime dependency
manifest are unchanged.

Gate rewiring in the same change, per the W0 brief:
- R1 kernel-sink retires (physically subsumed); new R11
  package-boundaries guards no-root-back-imports, relative tunnelling
  past exports maps, undeclared workspace deps, and non-exported
  subpaths, with runtime resolution pins via import.meta.resolve.
- resolveImportEdges and mutation ownership follow workspace
  specifiers through exports maps, keeping R4 cycle checks, depgraph,
  and derived test ownership connected across the seam (kernel-errors
  still owns 495 tests). listSourceFiles includes packages/*/src.
- kernel becomes an unranked zone; mutation registry, stryker mutate
  globs, and the mutation-affected workflow path filter move to
  packages/kernel/src/errors.ts.
- check:affected gains packages/ ownership (manifests fail open);
  vitest and coverage include packages/*/src; fallow ignores
  packages/** (its resolver cannot follow workspace specifiers).
- The affected-selector CI job installs dependencies: its closure now
  crosses workspace specifiers, and the R8 relative exception is
  unsafe for production src files (Node ESM does not realpath, so dual
  specifier/relative loads would instantiate modules twice). The R8
  zero-dep set is pinned empty with that rationale.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUv7bvbWNryuXgSBuqTtep

* fix: address W0 review — mutation sandbox, exports-map resolution, tsc -b

Review findings on #1494, all five:

1. contracts-schema-public.test.ts reads the kernel source at its
   packages/ path (fs access invisible to the codemod and typecheck).
2. Mutation lane: Stryker sandboxes the tree but pnpm's node_modules
   symlink resolves @agent-device/* back to the real repo, so mutants
   in the sandbox never load and vitest.related finds no tests.
   vitest.mutation.config.ts now aliases each EXPORTED specifier to
   its source (derived from exports maps, never a wildcard), keeping
   resolution inside the mutated tree. Validated: kernel-errors module
   runs end to end (dry run 3,984 tests, mutants killed, exit 0).
3. Layering/depgraph resolve workspace specifiers through the
   exports-derived map (workspaceSpecifierTargets) instead of
   reconstructing paths, so '.'-facade packages resolve; the
   positional fallback remains only for map-less fixtures (P0 pin).
4. Per-package project references implemented: packages/kernel is
   composite (emitDeclarationOnly -> dist-types, gitignored), the root
   references it, and typecheck becomes tsc -b — probed to catch type
   errors on both sides under TypeScript 7 native.
5. R11's relative-route exception now requires membership in an actual
   R8 zero-dep job closure (zeroDepClosureFiles walks entries), not
   mere scripts/ placement — closing the dual-instantiation bypass.

Also from review discussion: daemon-error moves out of the kernel
package to src/client/ — its consumers (cli, client facade) rehydrate
wire DaemonErrors client-side; the daemon only produces them. Kernel
drops to 8 exported subpaths before any of them ship.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUv7bvbWNryuXgSBuqTtep

* refactor: one exports-map reader for mutation alias and ownership

Fallow flagged workspaceExportAliases (cognitive 15, CRAP 90). The
manifest-reading logic already exists as workspaceSpecifierTargets in
scripts/layering/package-boundaries.ts, so both the Stryker sandbox
alias table and the mutation ownership walker now consume it instead
of carrying near-clones. Behavior unchanged; mutation suite 45/45 and
changed-code fallow green.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUv7bvbWNryuXgSBuqTtep

* fix: composite kernel without a root references edge

FreeRange runs plain `tsc -p tsconfig.json`, and a root `references`
entry makes non-build-mode TypeScript demand the referenced project's
built declarations (TS6305) — a standing "build first" tax on every
plain -p consumer (fr, editors). Keep the per-package composite
project and build it in typecheck (`tsc -b packages/kernel` before the
root and examples/sdk passes), but drop the root references edge: root
consumption resolves through exports to source, identical to runtime
and to the bundler. Probed: plain -p green with no prebuilt output;
kernel-side type errors still caught by its own build.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUv7bvbWNryuXgSBuqTtep

* fix: R11 uses the layering parser; mutation config is a fallow entry

Review blockers on #1494:

- R11's private single-quote regex could miss a double-quoted or
  re-export route into packages/*/src. specifierSites now delegates to
  the layering model's parseImports (both quote styles, side-effect
  imports, re-exports, dynamic imports), with direct regressions for
  each formerly-invisible form.
- vitest.mutation.config.ts becomes a declared fallow entry instead of
  a tolerated unused-file finding: the full-repo audit now reports it
  reachable (unused files 2 -> 1; the remainder predates this PR).

FreeRange clean-checkout evidence: with packages/kernel/dist-types and
every *.tsbuildinfo deleted, `pnpm check:freerange` reports 0 findings
on this head — the TS6305 topology died with the root references edge
in the previous commit; check:freerange has no build precondition.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUv7bvbWNryuXgSBuqTtep

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-07-30 12:12:46 +02:00

108 lines
4.6 KiB
TypeScript

import type { ImportEdge } from './model.ts';
/**
* R1-R3 as data: which zone may import which, and on what terms.
*
* These three rules used to be three hand-written predicate functions. They were short, but each
* one buried its boundary in control flow — you had to read the early-returns to learn that R3
* tolerates dynamic imports, or that R1 opens exactly one door. Stating them as a table means the
* policy is readable without reading code, and a fourth boundary is a table entry rather than a
* fourth function to keep consistent with the other three.
*
* The evaluator is deliberately small. Everything a policy can say is in `ZonePolicy`, so a rule
* that needs more than these fields does NOT belong here: R4 (cycles), R5/R6 (spine ranking),
* R7 (field ownership), R8 (CI job closure) and R9 (cycle size) are whole-graph or non-import
* properties, and each keeps its own checker.
*/
/** Edge kinds a boundary can tolerate. Both are erased or deferred, so both can be legitimate. */
export type ToleratedKind = 'type-only' | 'dynamic';
export type ZonePolicy = {
/** Rule id reported on violation, e.g. `R1 kernel-sink`. */
rule: string;
/** Source zones this policy governs. Omit for "every zone". */
from?: readonly string[];
/** Target zones this policy forbids importing. Omit and use `exceptTo` for "everything but". */
to?: readonly string[];
/** Target zones this policy does NOT govern — the complement form of `to`. */
exceptTo?: readonly string[];
/**
* Edge kinds that do not violate this boundary. A type-only edge costs nothing at runtime; a
* dynamic edge defers the cost past startup. Omitted means the boundary is closed to every kind.
*/
tolerates?: readonly ToleratedKind[];
/** Path prefixes allowed to cross regardless: the declared seam. */
seam?: readonly string[];
/** Subtrees of `seam` that are NOT part of it (a seam owner with a non-owning child). */
seamExcept?: readonly string[];
/** Why the boundary exists and what to do instead. ADR 0010: every error carries a hint. */
hint: string;
};
/**
* The policy table. Order is presentation only — every policy is evaluated against every edge.
*
* R1 kernel-sink retired 2026-07-30 (#1490 W0): the kernel moved to
* packages/kernel, where package resolution and R11 package-boundaries enforce
* the sink property physically — a package cannot import root src at all.
*/
export const ZONE_POLICIES: readonly ZonePolicy[] = [
{
rule: 'R2 commands-floor',
from: ['platforms', 'core', 'daemon'],
to: ['commands'],
hint:
'commands/ is the command surface, above these zones. Depend on shared kernel/contracts ' +
'instead; if two zones need the same rule, put the rule below both of them.',
},
{
rule: 'R3 platforms-seam',
to: ['platforms'],
tolerates: ['type-only', 'dynamic'],
seam: ['src/core/interactors/', 'src/daemon/', 'src/sdk/'],
seamExcept: ['src/daemon/client/'],
hint:
'Only src/core/interactors/, the daemon server and the sdk barrel may statically import ' +
'platforms/; elsewhere use a dynamic import() or a type-only import to preserve CLI ' +
'cold-start.',
},
];
function kindOf(imp: ImportEdge): ToleratedKind | 'value' {
if (imp.dynamic) return 'dynamic';
if (imp.typeOnly) return 'type-only';
return 'value';
}
function crossesSeam(policy: ZonePolicy, file: string): boolean {
if (!policy.seam?.some((prefix) => file.startsWith(prefix))) return false;
return !policy.seamExcept?.some((prefix) => file.startsWith(prefix));
}
/**
* Whether `policy` governs this edge AND the edge violates it. Returns the hint on violation so
* the caller can build the message, or `null` when the policy is silent about this edge.
*/
export function policyViolation(
policy: ZonePolicy,
edge: { file: string; fromZone: string; toZone: string; imp: ImportEdge },
): string | null {
if (policy.from && !policy.from.includes(edge.fromZone)) return null;
if (policy.to && !policy.to.includes(edge.toZone)) return null;
if (policy.exceptTo?.includes(edge.toZone)) return null;
const kind = kindOf(edge.imp);
if (kind !== 'value' && policy.tolerates?.includes(kind)) return null;
if (crossesSeam(policy, edge.file)) return null;
return policy.hint;
}
/** The one-line lead every zone-policy violation shares, before its rule-specific hint. */
export function policyLead(edge: { fromZone: string; toZone: string; imp: ImportEdge }): string {
const kind = kindOf(edge.imp);
const qualifier = kind === 'value' ? '' : `${kind} `;
return `${edge.fromZone}/ must not ${qualifier}import ${edge.toZone}/ (imports '${edge.imp.spec}').`;
}