@afokapu/atdd-bun 0.4.0 → 0.6.0

package/conventions/tester.htmx/tester.htmx.covered-train-is-routed.convention.yaml

@@ -0,0 +1,30 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.covered-train-is-routed
+kind: rule
+status: active
+name: A train a browser spec covers is selected by an interlocking route
+statement: A declared train that a journey spec binds to MUST be selected by at least one interlocking route. Bun/htmx
+  realization of `tester.vite.covered-train-is-routed`, strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: A train a browser spec covers is selected by an interlocking route.
+  normative_text: A spec can stay green while exercising a train nothing in the application can reach. Covering
+    an unrouted train proves nothing about the product.
+  fix_hint: Route the train from an interlocking, or bind the spec to a routed train.
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - Undeclared trains are reported by `tester.htmx.e2e-binds-declared-subject`.
+metadata:
+  aliases:
+  - BUN-E2E-COVERED-TRAIN-IS-ROUTED-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.covered-train-is-routed
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.e2e-binds-declared-subject.convention.yaml

@@ -0,0 +1,31 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.e2e-binds-declared-subject
+kind: rule
+status: active
+name: A journey spec binds to a train or journey plan/ declares
+statement: When the repository declares a plan, the train or journey a journey spec binds to MUST be declared under
+  `plan/`. Bun/htmx realization of `tester.vite.e2e-names-valid-train`, strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: A journey spec binds to a train or journey plan/ declares.
+  normative_text: 'A spec bound to an undeclared subject is orphaned: it can pass forever while the plan it claims
+    to cover says nothing about it.'
+  fix_hint: Bind the spec to the declared id, or declare the train or journey.
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - A repository with no plan (no trains, no journeys) is out of scope.
+  - A malformed binding is reported by `tester.htmx.journey-binding-header`, not here.
+metadata:
+  aliases:
+  - BUN-E2E-E2E-BINDS-DECLARED-SUBJECT-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.e2e-names-valid-train
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.e2e-spec-naming.convention.yaml

@@ -0,0 +1,32 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.e2e-spec-naming
+kind: rule
+status: active
+name: Playwright specs are named *.e2e.ts
+statement: A file that imports `@playwright/test` and declares tests (`test(...)`, `test.describe(...)`) MUST be
+  named `*.e2e.ts` (`.js`, `.mjs`, `.tsx` variants allowed). `bun test` collects every `*.test.*` and `*.spec.*`
+  file, so a Playwright spec named that way is executed by the wrong runner and fails, or worse is skipped by a
+  filter nobody remembers. New in the Bun/htmx browser tester, strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: Playwright specs are named *.e2e.ts.
+  normative_text: 'One naming rule keeps the two runners apart: `bun test` runs unit, acceptance and smoke tests,
+    Playwright runs browser specs, and neither ever picks up the other''s files.'
+  fix_hint: Rename `login.spec.ts` to `login.e2e.ts` and point Playwright's `testMatch` at `**/*.e2e.ts`.
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - Files that do not import `@playwright/test` are out of scope.
+  - '`playwright.config.*` and fixture modules that only extend `test` declare no tests and are out of scope.'
+metadata:
+  aliases:
+  - BUN-E2E-E2E-SPEC-NAMING-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.exposed-journey-e2e-coverage.convention.yaml

@@ -0,0 +1,31 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.exposed-journey-e2e-coverage
+kind: rule
+status: active
+name: Every exposed journey has an E2E or SMOKE browser spec
+statement: Every journey whose entrypoint is exposed and whose `surfaces` include `frontend` (or declare none) MUST
+  have at least one journey spec bound to it by `// Journey:` with an E2E or SMOKE test URN. New in the Bun/htmx
+  browser tester, strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: Every exposed journey has an E2E or SMOKE browser spec.
+  normative_text: An exposed journey is what a user can start. The route-level rules prove each routing decision;
+    this proves the journey runs end to end in a browser.
+  fix_hint: 'Add `e2e/<journey>.smoke.e2e.ts` bound with `// Journey: <journey id>`.'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - Internal journeys, and exposed journeys whose entrypoint `surfaces` exclude `frontend` (for example `[backend]`),
+    have no browser surface and are out of scope.
+metadata:
+  aliases:
+  - BUN-E2E-EXPOSED-JOURNEY-E2E-COVERAGE-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.fragment-asserts-returned-markup.convention.yaml

@@ -40,12 +40,8 @@ metadata:
   # contract from the payload into the markup. Stack-native, not inherited.
   - BUN-FRAGMENT-ASSERTS-MARKUP-001
   severity: 3
-  # Core's tester nodes are largely `documentation-only`, which core's
-  # coverage_report treats as never-fails-the-build. That is right for retrofitting
-  # and wrong for a new stack: a coverage-binding rule that cannot fail is a rule
-  # that will not be adopted. Gating dispositions here; a repo adopting on an
-  # existing suite records a ratchet baseline instead.
-  disposition: suppress-and-clean
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
   introduced_in: 0.1.0
 implementation:
   type: validator

package/conventions/tester.htmx/tester.htmx.journey-binding-header.convention.yaml

@@ -0,0 +1,32 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.journey-binding-header
+kind: rule
+status: active
+name: A journey spec binds to exactly one train or journey
+statement: 'A journey spec (a `*.e2e.ts` file, or any test file whose header comments carry a `// Train:`, `// Journey:`
+  or `// URN: test:train|journey:` marker) MUST carry exactly one binding header: `// Train: train:<subject>:<slug>`
+  or `// Journey: journey:<id>`, each matching the planner''s identity grammar. Bun/htmx realization of `tester.vite.journey-train-header`,
+  strict.'
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: A journey spec binds to exactly one train or journey.
+  normative_text: The binding is how a browser test is traced to the plan it exercises. A spec with no binding,
+    two bindings, or an id the planner would reject cannot be traced.
+  fix_hint: 'Add `// Train: train:orders:place-order` (or `// Journey: journey:buy`) to the header block.'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - Unit and acceptance tests carrying none of the journey markers are out of scope.
+metadata:
+  aliases:
+  - BUN-E2E-JOURNEY-BINDING-HEADER-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.journey-train-header
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.journey-layer-assembly.convention.yaml

@@ -0,0 +1,29 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.journey-layer-assembly
+kind: rule
+status: active
+name: 'A journey spec declares Layer: assembly'
+statement: 'A journey spec MUST carry `// Layer: assembly`. Bun/htmx realization of `tester.vite.journey-layer-assembly`,
+  strict.'
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: 'A journey spec declares Layer: assembly.'
+  normative_text: A browser test exercises the assembled application, not a layer of it. A missing or wrong Layer
+    routes the result to the wrong layer bucket.
+  fix_hint: 'Add `// Layer: assembly` to the header block.'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+metadata:
+  aliases:
+  - BUN-E2E-JOURNEY-LAYER-ASSEMBLY-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.journey-layer-assembly
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.journey-no-acceptance-marker.convention.yaml

@@ -0,0 +1,29 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.journey-no-acceptance-marker
+kind: rule
+status: active
+name: A journey spec carries no Acceptance or WMBT header
+statement: A journey spec MUST NOT carry `// Acceptance:` or `// WMBT:` header lines. Bun/htmx realization of `tester.vite.journey-no-acceptance-marker`,
+  strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: A journey spec carries no Acceptance or WMBT header.
+  normative_text: 'Journey and acceptance identities are exclusive: a journey test binds to a train or journey,
+    an acceptance test to an Acceptance/WMBT pair. Carrying both makes the test ambiguous about what it proves.'
+  fix_hint: Move acceptance assertions to an acceptance test, or drop the Acceptance/WMBT lines.
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+metadata:
+  aliases:
+  - BUN-E2E-JOURNEY-NO-ACCEPTANCE-MARKER-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.journey-no-acceptance-marker
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.journey-urn-format.convention.yaml

@@ -0,0 +1,32 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.journey-urn-format
+kind: rule
+status: active
+name: A journey spec carries well-formed test URNs for its own subject
+statement: A journey spec MUST carry at least one test URN `test:{train|journey}:<id>:{E2E|SMOKE|A11Y|VIS|RESP}-NNN-<slug>`,
+  and every URN it carries MUST be well-formed and name the subject its binding header declares. Bun/htmx realization
+  of `tester.vite.journey-urn-format`, strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: A journey spec carries well-formed test URNs for its own subject.
+  normative_text: The URN identifies the test instance and its harness. A malformed URN, or one naming another subject,
+    silently traces the result to the wrong place.
+  fix_hint: Use `test:train:orders:place-order:E2E-001-places-an-order` in the header and the test title.
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - A URN is compared with the binding only when the binding itself is valid; a malformed binding is reported by
+    `tester.htmx.journey-binding-header` alone.
+metadata:
+  aliases:
+  - BUN-E2E-JOURNEY-URN-FORMAT-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.journey-urn-format
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.presentation-smoke-coverage.convention.yaml

@@ -0,0 +1,31 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.presentation-smoke-coverage
+kind: rule
+status: active
+name: Every presentation component is covered by a SMOKE browser spec
+statement: Every `.tsx`/`.jsx` component under a `presentation/` path segment MUST be covered by a SMOKE browser
+  spec whose path names the component's wagon (the segment before `presentation`). Bun/htmx realization of `tester.vite.presentation-smoke-coverage`,
+  strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: Every presentation component is covered by a SMOKE browser spec.
+  normative_text: Structural tests stay green while a rendered feature is blank; only rendering it in a browser
+    proves it appears.
+  fix_hint: Add a SMOKE spec whose file name contains the wagon, for example `e2e/checkout-cart.smoke.e2e.ts`.
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - Components outside a `presentation/` segment are out of scope.
+metadata:
+  aliases:
+  - BUN-E2E-PRESENTATION-SMOKE-COVERAGE-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.presentation-smoke-coverage
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.responsive-harness.convention.yaml

@@ -0,0 +1,33 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.responsive-harness
+kind: rule
+status: active
+name: A RESP spec renders at every declared viewport and asserts no horizontal overflow
+statement: 'A spec identified as responsive (a `RESP` test URN, or a `responsive`/`resp` token in its file name)
+  MUST render the page at every viewport width declared in `atdd-bun.yaml` under `frontend.viewports` (default 375,
+  768, 1280), through `page.setViewportSize({ width })`, a `viewport: { width }` option, or a list of widths it
+  iterates (`for (const w of [...])`, `LIST.forEach`, `LIST.map`); picking one element of a list renders one width.
+  It MUST pass `scrollWidth`, directly or through a variable measured from it, to an `expect(...)` so the test fails
+  when the page overflows horizontally. New in the Bun/htmx browser tester, strict.'
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: A RESP spec renders at every declared viewport and asserts no horizontal overflow.
+  normative_text: A screen that works on a desktop can be unusable on a phone. Rendering at each declared width
+    and asserting the document never scrolls sideways is the least that proves it fits.
+  fix_hint: '`for (const width of [375, 768, 1280]) { await page.setViewportSize({ width, height: 900 }); ... expect(scrollWidth
+    - clientWidth).toBeLessThanOrEqual(0); }`'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+metadata:
+  aliases:
+  - BUN-E2E-RESPONSIVE-HARNESS-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.responsive-journey-coverage.convention.yaml

@@ -0,0 +1,30 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.responsive-journey-coverage
+kind: rule
+status: active
+name: Every exposed journey has a RESP browser spec
+statement: Every journey whose entrypoint is exposed and whose `surfaces` include `frontend` (or declare none) MUST
+  have a journey spec bound to it by `// Journey:` with a RESP test URN. New in the Bun/htmx browser tester, strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: Every exposed journey has a RESP browser spec.
+  normative_text: Every screen a user can reach should be proven to fit from mobile to desktop; exposed journeys
+    are exactly those screens, and new ones appear here as soon as the plan declares them.
+  fix_hint: 'Add `e2e/<journey>.responsive.e2e.ts` bound with `// Journey: <journey id>`.'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - Internal journeys, and exposed journeys whose entrypoint `surfaces` exclude `frontend`, have no screen to fit
+    and are out of scope.
+metadata:
+  aliases:
+  - BUN-E2E-RESPONSIVE-JOURNEY-COVERAGE-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.swap-oob-asserts-destination-id.convention.yaml

@@ -41,7 +41,8 @@ metadata:
   # ADDED for this stack: core has no node for out-of-band swap testing.
   - BUN-OOB-TARGET-ASSERTED-001
   severity: 3
-  disposition: suppress-and-clean
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
   introduced_in: 0.1.0
 implementation:
   type: validator

package/conventions/tester.htmx/tester.htmx.train-e2e-coverage.convention.yaml

@@ -0,0 +1,32 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.train-e2e-coverage
+kind: rule
+status: active
+name: Every declared train has a browser spec
+statement: Every human-facing train declared under `plan/` (one in which a `user:` participant takes part) MUST
+  have at least one journey spec bound to it by `// Train:`. Bun/htmx realization of `tester.vite.train-e2e-coverage`,
+  strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: Every declared train has a browser spec.
+  normative_text: 'A train with no browser spec is a silent gap: the journey it declares can regress with nothing
+    turning red.'
+  fix_hint: 'Add `e2e/<train-slug>.e2e.ts` bound with `// Train: <train id>`.'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - The rule reports at the train's plan file, where the gap was declared.
+  - Trains in which no person takes part (only wagons and systems) have no screen to drive and are out of scope.
+metadata:
+  aliases:
+  - BUN-E2E-TRAIN-E2E-COVERAGE-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.train-e2e-coverage
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/tester.htmx/tester.htmx.verb-endpoint-coverage.convention.yaml

@@ -47,7 +47,8 @@ metadata:
   # ADDED for this stack: core has no node for hypermedia endpoint coverage.
   - BUN-ENDPOINT-COVERAGE-001
   severity: 2
-  disposition: suppress-and-clean
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
   introduced_in: 0.1.0
 implementation:
   type: validator

package/conventions/tester.htmx/tester.htmx.visual-harness.convention.yaml

@@ -0,0 +1,28 @@
+schema_version: 1.1.0
+rule_id: tester.htmx.visual-harness
+kind: rule
+status: active
+name: A VIS spec compares a screenshot
+statement: A spec identified as visual (a `VIS` test URN, or a `visual`/`vis` token in its file name) MUST call
+  `toHaveScreenshot()` or `toMatchSnapshot()`. Bun/htmx realization of `tester.vite.visual-harness`, strict.
+terms:
+- term_id: browser_spec
+  text: 'a `*.e2e.ts` file run by Playwright, or any test file whose header comments carry a journey marker (`//
+    Train:`, `// Journey:`, `// URN: test:train:…`, `// URN: test:journey:…`), so a misnamed one is still judged.
+    A unit test that merely mentions a journey URN in a string is not one.'
+content:
+  summary: A VIS spec compares a screenshot.
+  normative_text: A visual spec that captures nothing performs no visual regression.
+  fix_hint: '`await expect(page).toHaveScreenshot("checkout.png");`'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+metadata:
+  aliases:
+  - BUN-E2E-VISUAL-HARNESS-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+  mirrors: tester.vite.visual-harness
+implementation:
+  type: validator
+  ref: htmx_e2e_detector

package/conventions/traceability/traceability.plan.executable-acceptance-has-test.convention.yaml

@@ -1,2 +1,7 @@
 rule_id: traceability.plan.executable-acceptance-has-test
 statement: Every declared acceptance is bound by at least one Bun test.
+metadata:
+  disposition: strict
+implementation:
+  type: validator
+  ref: atdd_traceability_closure

package/conventions/traceability/traceability.source.tested-by-present.convention.yaml

@@ -1,2 +1,7 @@
 rule_id: traceability.source.tested-by-present
 statement: Each identified implementation component declares a testing witness.
+metadata:
+  disposition: strict
+implementation:
+  type: validator
+  ref: atdd_traceability_closure

package/conventions/traceability/traceability.source.tested-by-resolves.convention.yaml

@@ -1,2 +1,7 @@
 rule_id: traceability.source.tested-by-resolves
 statement: Each implementation testing witness resolves to an identified Bun test.
+metadata:
+  disposition: strict
+implementation:
+  type: validator
+  ref: atdd_traceability_closure

package/conventions/traceability/traceability.test.binding-resolves.convention.yaml

@@ -1,2 +1,7 @@
 rule_id: traceability.test.binding-resolves
 statement: Each identified Bun test names a plan acceptance, WMBT, or train that resolves.
+metadata:
+  disposition: strict
+implementation:
+  type: validator
+  ref: atdd_traceability_closure

package/detectors/atdd_topology/atdd.implementation.yaml

@@ -0,0 +1,13 @@
+kind: implementation
+subtype: guard
+implementation_id: atdd_topology
+emits_rule_ids:
+- planner.wagon.features
+- planner.feature.wagon-link
+- atdd-bun.topology.plan-location
+- atdd-bun.topology.source-location
+- atdd-bun.topology.test-location
+- atdd-bun.topology.e2e-location
+- atdd-bun.topology.feature-source-coverage
+- atdd-bun.topology.feature-test-coverage
+entrypoint: detect.mjs