v0.1.5: standalone-readability pass — delink --strip provenance mode ([TT-NNNN]), Tier-2 dangling refs neutralized, verify/review-code giant skills split into reference/ on-demand files; guards now runtime-neutral (bun|node)

core/rules/testing.md

@@ -6,7 +6,7 @@
 - Test actual implementation, do not duplicate logic into tests
 - Tests cannot run from repo root (guard: `do-not-run-tests-from-root`); run from package dirs.
 - **Local pre-check: run `<test-cmd:changed>`** from the owning package after editing source. It selects only tests affected by your uncommitted + branch changes (path-mapping ∪ CodeGraph direct dependents) and runs them in a single process — seconds, machine stays responsive. Use `--print` to see the selection without running, `--all` to scan beyond the home package.
-- **Before a delivery push: `<test-cmd:changed>` green + `<typecheck-cmd>` clean** — same selector as CI's PR side (local parity, [org-internal #4425]). The full suite (`<test-cmd:parallel>`) stays with nightly / `run-full-tests` / manual pre-merge runs. 实例命令绑定见 core/adapters/TERMINOLOGY.md。
+- **Before a delivery push: `<test-cmd:changed>` green + `<typecheck-cmd>` clean** — same selector as CI's PR side (local parity, [TT-4425]). The full suite (`<test-cmd:parallel>`) stays with nightly / `run-full-tests` / manual pre-merge runs. 实例命令绑定见 core/adapters/TERMINOLOGY.md。
 - Never use the bare single-process test runner for the full suite; `<test-cmd:parallel>` shards it and process-isolates known-corrupting files. Parallelism is controlled by `TEST_SHARDS` (default 3; raise it on beefy CI runners, e.g. `TEST_SHARDS=7`).
 
 ### Pre-existing test failures must be filed, not silently logged
@@ -18,7 +18,7 @@ problem" and do NOT bury it in a report body.
 
 - Classify it: run the failing test on the base commit (see `verify` Phase 2.6).
   Fails there too → pre-existing (BF); passes there → regression you must fix.
-- De-duplicate BEFORE filing (retro [org-internal #2696]): search existing
+- De-duplicate BEFORE filing (retro [TT-2696]): search existing
   `baseline-failure` tickets — open AND closed — by test/file name to surface
   candidates, then match by **failure signature** (error signature + affected
   surface — one root-cause family may span several tests; see the
@@ -40,7 +40,7 @@ it is a **flaky test**. Do NOT silently re-run until it passes and move on.
 
 - Detect: re-run the suite (or use the project's flaky detector). Record every
   test that shows intermittent behavior — name, failure rate, and run count.
-- De-duplicate BEFORE filing (retro [org-internal #2696]): same
+- De-duplicate BEFORE filing (retro [TT-2696]): same
   signature-based procedure as baseline failures above, against existing
   `flaky-test` tickets.
 - File it: the Verifier registers every un-tracked flaky test as a
@@ -55,7 +55,7 @@ it is a **flaky test**. Do NOT silently re-run until it passes and move on.
 NOT fix it in place — classify, file, and return to your task per the
 session-scope-guard rule. A repository-wide flaky test is a shared magnet —
 fixing it in place drifts off-task and collides with its owner
-([org-internal #1803]).
+([TT-1803]).
 
 ### Testing Kobalte components with happydom
 
@@ -74,7 +74,7 @@ render reliably.
 
 A single component MUST NOT carry both a `.test.ts` and a `.test.tsx` test
 file — the two-file split duplicated ~3300 lines of overlapping assertions
-across one UI package [org-internal #1712]. Use exactly one file per
+across one UI package [TT-1712]. Use exactly one file per
 component, chosen by test style:
 
 | Test style                       | Extension      | When to use                                                    |
@@ -129,17 +129,17 @@ expect(source).not.toContain(`@${NAMESPACE}`)
 Each package MUST have exactly ONE test root — no parallel tracks
 (`src/**/__tests__/`, a `tests/` dir alongside colocated `src/`, or a `test/`
 alongside `tests/`); a second root drifts and breaks test discovery
-([org-internal #1711], extended to all packages by [org-internal #1821]).
+([TT-1711], extended to all packages by [TT-1821]).
 
 Rules:
 
 - New tests: create them at the package's single root from the start.
 - Do NOT create `src/**/__tests__/` directories in any package — parallel
-  tracks drift (residuals eliminated by [org-internal #1821]).
+  tracks drift (residuals eliminated by [TT-1821]).
 - For `test/`-root packages: mirror the `src/` path (`test/<src-relative>.test.ts`);
   type-level tests live alongside the behavioral suites in the config area.
 - For colocated-root packages: keep tests next to the source file; one test
-  file per component [org-internal #1712].
+  file per component [TT-1712].
 
 Per-package root tables live in the instance layer (they name concrete
 package paths); the invariant itself — ONE root per package — is universal.