refactor(architecture): move regex import rules into the import graph (12-10, 12-08)

Icon vendor, design-system deep import and realtime composition were regular
expressions beside graph rules, and the regex missed relative deep imports
inside presentation. They are graph rules with fixtures now, with the
components/ui facades and page-templates named. package-script-graph.ts stays;
the reason is recorded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
DongHyeonka
2026-09-25 22:33:14 +09:00
co-authored by Claude Opus 5.5
parent f8b6a3613c
commit 7f2a1607f3
19 changed files with 122 additions and 35 deletions
+15
View File
@@ -1,3 +1,18 @@
/**
* Package-script graph for the CI contract (D-12, 12-10). Kept after checking
* whether `--ignore-scripts` on the workflow install and `allowBuilds` in
* pnpm-workspace.yaml already close the same risks. They do not:
*
* - Gate commands run installs themselves (`verify:lockfile`, removal
* fixtures). `allowBuilds` limits dependency build scripts under pnpm only;
* the root project's own install hooks and npm/yarn installs still run
* unless the command says `--ignore-scripts`.
* - A gate names a root package script. `--prefix`, `--filter`, `-C`, npm
* pre/post hooks and `npm_config_*` scope variables can make that name run a
* different manifest's script, which no install flag affects.
* - `reachablePackageScripts` is also how the ungated-test check (12-04) finds
* which Vitest paths a gate runs.
*/
type PackageManager = "pnpm" | "npm" | "yarn";
type ManagerParseResult = Readonly<{