T-GLDL-boundary-verification-lint-overrides-guard-script-project
State: planning/proposed · Impact: medium · Complexity: medium
The package boundary is only real if something fails when it is crossed.
Proposed
Section titled “Proposed”Per-package oxlint overrides ban @lib/* and ../../ climbs.
scripts/guard-definition-boundary.ts runs in lefthook. moon project-graph is asserted acyclic.
Each package has a tsc -p tsconfig.build.json task run with the product tree absent. A CI job
packs the definition tarball, installs it alone under plain Node, and runs
sdlc-def entities validate, harness export --pack definition, and docs generate.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: An import from the definition package into an execution module fails lint, the guard, and the standalone build.
- AC-2: The round-trip install job is green on main.
Out of scope
Section titled “Out of scope”- none
Dependencies
Section titled “Dependencies”- T-D5PC-sdlc-def-bin-export-map-lockstep-guard-and-the-second
- T-ARSV-harness-export-pack-definition-emits-the-agent-context-pack
- T-TJUP-dashboard-and-worktree-services-settle-in-the-execution
Depends on
Section titled “Depends on”T-D5PC-sdlc-def-bin-export-map-lockstep-guard-and-the-second, T-ARSV-harness-export-pack-definition-emits-the-agent-context-pack, T-TJUP-dashboard-and-worktree-services-settle-in-the-execution