npm - @afokapu/atdd-bun - Versions diffs - 0.3.2 → 0.5.0 - Mend

@afokapu/atdd-bun 0.3.2 → 0.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (208) hide show

package/conventions/coder.bun/coder.bun.responsive-viewport-meta.convention.yaml ADDED Viewed

@@ -0,0 +1,31 @@
+schema_version: 1.1.0
+rule_id: coder.bun.responsive-viewport-meta
+kind: rule
+status: active
+name: Every HTML document declares a device-width viewport and allows zoom
+statement: Every full HTML document (an `.html`/`.htm` file, a `.tsx`/`.jsx` layout that renders `<html>`, or a
+  `.ts`/`.js` template that builds one) MUST declare `<meta name="viewport">` whose content sets `width=device-width`,
+  and MUST NOT block zoom with `user-scalable=no` or a `maximum-scale` below 2. New in atdd-bun, strict.
+terms:
+- term_id: frontend_settings
+  text: '`atdd-bun.yaml` → `frontend.viewports` (the widths responsive specs render at; the smallest bounds fixed
+    widths) and `frontend.breakpoints` (the widths media queries may use).'
+content:
+  summary: Every HTML document declares a device-width viewport and allows zoom.
+  normative_text: Without a device-width viewport a phone renders the page as a zoomed-out desktop layout, whatever
+    the CSS says. Blocking zoom fails users who need to enlarge text, which is also an accessibility failure.
+  fix_hint: '`<meta name="viewport" content="width=device-width, initial-scale=1">`'
+  exceptions:
+  - Vendored and generated trees (`node_modules`, `dist`, `build`, `_generated`) are never scanned.
+  - HTML fragments that are not full documents (no `<html>`) are out of scope.
+  - A viewport `content` given as a JSX expression (`content={VIEWPORT}`) cannot be read statically; the meta's
+    presence is required, its value is not judged.
+metadata:
+  aliases:
+  - BUN-RESPONSIVE-RESPONSIVE-VIEWPORT-META-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.5.0
+implementation:
+  type: validator
+  ref: bun_responsive_detector

package/conventions/coder.bun/coder.bun.runtime-executes-the-declaration.convention.yaml CHANGED Viewed

@@ -30,23 +30,6 @@ terms:
     a declared `route_id` that appears nowhere in a runtime which does not load the declaration.
     A data-driven runtime serves every declared route by construction and mentions none of them as
     literals, so this is only ever evaluated against a transcribing runtime.
-- term_id: disposition_rationale
-  text: >-
-    advisory because NO consumer satisfies it today, including this package's own fixtures until
-    the commit that introduced this node. The measurement below was TAKEN, not recalled.
-  values:
-    measured_2026_09_07: >-
-      A Bun consumer was built from scratch in this stack's idiom to establish the read
-      vocabulary, because the python heuristic (yaml.safe_load / read_text) matches NOTHING a
-      compliant Bun runtime does — porting it blind would have reported every Bun consumer as
-      plan-blind. Verified: the compliant consumer is silent, a transcribing one fires naming the
-      literals it restated, and a query-loading one that reads nothing and states nothing stays
-      silent.
-    measurement_target: a Bun consumer repo built for the experiment
-    escalate_when: >-
-      Consumer runtimes load their declarations and the check has been wired into
-      gates/interlocking-binding.gate.yaml. Enabling it is a GATE change; the detector is staged
-      (`scan_execution`) and deliberately not called from `scan_root`.
 content:
   summary: >-
     The obligation that makes "the train YAML is the source of truth" true of the RUNTIME and not
@@ -94,7 +77,8 @@ metadata:
   aliases:
   - BUN-RUNTIME-EXECUTES-001
   severity: 2
-  disposition: advisory
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
   introduced_in: 0.1.0
   core_design_refs:
   - afokapu/atdd#1248

package/conventions/coder.bun/coder.bun.runtime-typecheck-enforced.convention.yaml CHANGED Viewed

@@ -25,20 +25,6 @@ terms:
     family AND extends no base config. A tsconfig that `extends` something is NOT judged: this
     rule's detector cannot resolve the base, and reporting what it cannot see would be a false
     positive.
-- term_id: disposition_rationale
-  text: >-
-    advisory because this states a stack norm rather than a defect, and because the consuming
-    projects have not been surveyed. The measurement below was TAKEN on 2026-09-06, not recalled.
-  values:
-    measured_2026_09_06: >-
-      0 consumer Bun projects surveyed. This hub is a package repository and contains no Bun
-      application to measure — its own .ts files are deliberately-wrong detector fixtures, which
-      is exactly why this rule is authored for consumers and never run against the hub.
-    measurement_target: afokapu/atdd-extensions @ main (the hub itself — deliberately not a consumer)
-    measurement_command: "find official -name '*.ts' -not -path '*/fixtures/*' | wc -l"
-    escalate_when: >-
-      A consumer Bun project has been surveyed, typescript + a wired no-emit typecheck are present,
-      and the team accepts blocking on it. Escalating to strict is a MAJOR change class.
 content:
   summary: >-
     Bun's own gap, stated as a convention. `bun test`, `bun install`, `bun build`, `Bun.serve` and a
@@ -84,7 +70,8 @@ metadata:
   aliases:
   - BUN-TYPECHECK-ENFORCED-001
   severity: 2
-  disposition: advisory
+  # 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/coder.htmx/coder.htmx.swap-no-inline-handler.convention.yaml CHANGED Viewed

@@ -41,8 +41,7 @@ content:
       <button hx-get="/rows/1" hx-on::after-request="track('open')">Open</button>   <!-- ✓ -->
     For behaviour that is genuinely presentational and not request-related, attach it in a delegated
-    listener on a stable ancestor that is never swapped. Disposition is `suppress-and-clean`: existing
-    handlers are held flat by a ratchet baseline while they are migrated.
+    listener on a stable ancestor that is never swapped.
   exceptions:
   - Files containing no `hx-` attribute are never scanned (self-scoping).
   - React/JSX camelCase props (`onClick={…}`, `onSubmit={…}`) are a different mechanism and are out of
@@ -52,7 +51,8 @@ metadata:
   aliases:
   - HTMX-NO-INLINE-HANDLER-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/coder.htmx/coder.htmx.verb-endpoint-is-routed.convention.yaml CHANGED Viewed

@@ -35,7 +35,7 @@ content:
     STATIC PATHS ONLY. An endpoint built by interpolation (`/orders/${id}/void`) cannot be compared
     to a server route by text, and guessing would report on correct code. Those are skipped, exactly
-    as the Vite family treats an unresolvable trainId as advisory rather than inventing a verdict.
+    as the Vite family leaves an unresolvable trainId unjudged rather than inventing a verdict.
     The Station Master is found by the JOURNEY_MAP it DECLARES, never by filename. Matching is on
     the whole path or its distinctive terminal segment: matching any segment was the first attempt
@@ -57,7 +57,7 @@ content:
   exceptions:
     - "`hx-get` endpoints are NOT reported; fetching a fragment is presentation, not a journey."
     - An endpoint written with interpolation is skipped rather than guessed at, preserving the
-      advisory treatment this hub gives statically unresolvable bindings.
+      hub's decision to leave statically unresolvable bindings unjudged.
 metadata:
   aliases:
     - HTMX-VERB-ENDPOINT-ROUTED-001

package/conventions/coder.htmx/coder.htmx.verb-mutation-signals-progress.convention.yaml CHANGED Viewed

@@ -42,7 +42,7 @@ content:
       <form hx-post="/orders" hx-disabled-elt="find button">…</form>  <!-- ✓ prevents re-submit -->
     Prefer `hx-disabled-elt` where a duplicate would be expensive; the indicator alone tells the user
-    to wait but does not stop them. `suppress-and-clean`: a ratchet holds existing cases flat.
+    to wait but does not stop them.
   exceptions:
   - "`hx-get` is not scoped by this rule (idempotent)."
   - An element declaring both signals is fine; only declaring neither is a violation.
@@ -52,7 +52,8 @@ metadata:
   aliases:
   - HTMX-MUTATION-PROGRESS-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/planner.docs/planner.docs.adr-registry-derived.convention.yaml CHANGED Viewed

@@ -32,17 +32,6 @@ terms:
   text: >-
     `index.adoc` in the decisions directory, whose entries are computed from the set of ADR files and
     their `:decides:` targets. It contains references to the decisions, never the decisions themselves.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: 'The decisions directory does not exist and there are 0 ADR files. Spec 2 §6 names the first two: ADR-20260906-001 (shared control root) and ADR-20260906-002 (the documentation system itself, authored as current documentation — the proof the system works).'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: 'ls -d docs/architecture/decisions 2>&1 ; find . -name ''adr-*.adoc'' | wc -l'
-    escalate_when: '`docs/architecture/decisions/` exists and its index.adoc matches the derived projection exactly on a full scan.'
 content:
   summary: >-
     A hand-maintained list of decisions drifts from the decisions — precisely the failure class ATDD
@@ -76,7 +65,8 @@ metadata:
   aliases:
   - DOCS-ADR-001
   severity: 2
-  disposition: advisory
+  # 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/planner.docs/planner.docs.area-index-required.convention.yaml CHANGED Viewed

@@ -18,17 +18,6 @@ terms:
     `index.adoc` — the area's entry point and the node the rendered site navigates to. For
     `docs/architecture/decisions/` it is additionally a DERIVED registry, governed by
     `planner.docs.adr-registry-derived`.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: '`docs/` exists and holds 71 markdown files; none of purpose/, architecture/, delivery/ or archive/ exists, and there is no index.adoc anywhere. 0 of 6 canonical areas are present, so the rule currently reports nothing and will begin reporting as the tree is created.'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: 'ls -d docs docs/purpose docs/architecture docs/delivery docs/archive 2>&1'
-    escalate_when: 'The canonical tree exists in the consuming repository and every existing authored area carries an index.adoc.'
 content:
   summary: >-
     An area without an index is an area the rendered site cannot navigate into and a reader cannot
@@ -60,7 +49,8 @@ metadata:
   aliases:
   - DOCS-TREE-001
   severity: 3
-  disposition: advisory
+  # 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/planner.docs/planner.docs.artifact-path-shape.convention.yaml CHANGED Viewed

@@ -17,17 +17,6 @@ terms:
   text: >-
     one entry of `artifacts:` — an `action` (`create`, `modify`, `archive`), a `path`, and for
     `archive` a `from` naming the document being retired.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: '0 declarations exist to check. The `documentation:` block lands with the core unit (companion spec, work item B) and this rule has an empty input until it does. Advisory is the only honest disposition for a rule whose subject does not exist yet.'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: '(the declaration is core''s, companion §3, and is not yet implemented)'
-    escalate_when: 'Documentation declarations are being recorded at RATIFY in the consuming repository and a full pass over recent plans reports zero malformed artifact paths.'
 content:
   summary: >-
     The declaration is a promise about paths. This rule checks the promise is well formed BEFORE the
@@ -75,7 +64,8 @@ metadata:
   aliases:
   - DOCS-DECLARATION-001
   severity: 2
-  disposition: advisory
+  # 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/planner.docs/planner.docs.asciidoc-only.convention.yaml CHANGED Viewed

@@ -17,18 +17,6 @@ terms:
   text: >-
     everything beneath `docs/dist/`. It is rendered by the build (spec 2 §7), normally excluded from
     git, and never subject to the authored-format rule.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: '71 markdown beneath docs/, 18 non-dotfile markdown at the repository root (89 total; 90 counting .atdd-launch-prompt.md), 0 .adoc anywhere. The corpus is 0% compatible, which is why this rule ships advisory.'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: 'find docs -name ''*.md'' -type f | wc -l ; find . -maxdepth 1 -name ''*.md'' -type f | wc -l ; find . -name ''*.adoc'' -not -path ''./.git/*'' | wc -l'
-    escalate_when: 'No authored `.md` remains beneath `docs/` outside `docs/dist/` in the consuming repository — i.e. the migration of spec 2 §1 has landed and the corpus is compatible with `strict`.'
-    measurement_note: 'Spec 2 §1 records 71 + 18 = 89 as of the same date and this run reproduces it exactly for the non-dotfile corpus. Re-take this measurement at the escalation checkpoint; do not escalate on the number recorded here (spec 2 §8, and companion §7 on stale measurements).'
 content:
   summary: >-
     One authored format, mechanically checked. The rule exists because a mixed corpus cannot carry a
@@ -64,7 +52,8 @@ metadata:
   aliases:
   - DOCS-FORMAT-001
   severity: 2
-  disposition: advisory
+  # 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/planner.docs/planner.docs.doc-id-unique.convention.yaml CHANGED Viewed

@@ -12,17 +12,6 @@ terms:
   text: >-
     every authored `.adoc` beneath `docs/`, across all areas, excluding `docs/dist/`. Uniqueness is
     global — `archive/` is part of the corpus, not a separate id space.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: '0 .adoc files, therefore 0 declared ids and 0 collisions. Not evidence of health: the corpus does not exist yet. Re-measure after migration, which is exactly when collisions appear.'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: 'find . -name ''*.adoc'' -not -path ''./.git/*'' | wc -l'
-    escalate_when: 'The corpus has been migrated and a full scan reports zero duplicate ids — the scale test spec 2 §1 names, since 89 documents is the first corpus large enough to collide.'
 content:
   summary: >-
     A duplicated id makes edge resolution ambiguous: `:supersedes: architecture.foo` cannot say which
@@ -58,7 +47,8 @@ metadata:
   aliases:
   - DOCS-IDENTITY-002
   severity: 2
-  disposition: advisory
+  # 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/planner.docs/planner.docs.graph-target-resolves.convention.yaml CHANGED Viewed

@@ -22,17 +22,6 @@ terms:
   text: >-
     creating a graph node for a target no document declares, so that an edge appears to resolve. The
     defect this rule exists to make impossible.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: '0 .adoc files, so 0 authored edges and 0 unresolved targets. The number that motivates this rule is the OTHER graph''s, quoted in full under normative_text and measured on the same date: 147 of 168 containment edges invented, 44 fabricated nodes out of 3208.'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: 'find . -name ''*.adoc'' -not -path ''./.git/*'' | wc -l'
-    escalate_when: 'A full corpus scan reports zero unresolved relationship targets. The no-fabrication half is NOT subject to escalation — it is a property of the resolver, true from the first commit, and is asserted by the #1758 regression test rather than deferred to a disposition flip.'
 content:
   summary: >-
     Resolve or report — never invent. The graph is DERIVED from the `.adoc` attributes and rebuilt on
@@ -80,7 +69,8 @@ metadata:
   aliases:
   - DOCS-GRAPH-001
   severity: 1
-  disposition: advisory
+  # 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/planner.docs/planner.docs.identity-required.convention.yaml CHANGED Viewed

@@ -17,17 +17,6 @@ terms:
   text: >-
     the value of the `:status:` attribute — `current`, `superseded`, or `historical`. It answers "is
     this accepted truth today?" and is the flag issue #1782 exists to introduce.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: '0 .adoc files exist, so 0 documents declare a doc-id and the rule currently has an empty corpus to check. It ships advisory because it will fire on every file the moment conversion begins and before the attributes are backfilled.'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: 'find . -name ''*.adoc'' -not -path ''./.git/*'' | wc -l'
-    escalate_when: 'Every authored `.adoc` beneath `docs/` declares both attributes — reachable only after the migration lands, since the attribute is authored during conversion.'
 content:
   summary: >-
     Identity and currency, declared in the document itself. Without `doc-id` there is no graph:
@@ -61,7 +50,8 @@ metadata:
   aliases:
   - DOCS-IDENTITY-001
   severity: 2
-  disposition: advisory
+  # 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/planner.docs/planner.docs.journey-view-current.convention.yaml ADDED Viewed

@@ -0,0 +1,53 @@
+schema_version: 1.1.0
+rule_id: planner.docs.journey-view-current
+kind: rule
+status: active
+name: The journey documentation is generated from plan/ and matches it
+statement: >-
+  When a repository documents itself (`docs/` exists) and its plan declares journeys or interlockings,
+  `docs/purpose/journeys/` MUST contain exactly what `atdd-bun docs journeys` generates from `plan/`:
+  `index.adoc` and one SVG per journey map, per journey's nominal path, and per routed train. A missing,
+  stale, hand-edited, or extra file is a violation.
+terms:
+- term_id: journey_view
+  text: >-
+    the generated page, top down: each journey as a map (entry action, interlockings, the routes they
+    choose, the trains they run, continuations and terminal outcomes); the journey's nominal path walked
+    end to end as one sequence across its interlockings; every path as a table; each interlocking's
+    routes with their guards; each train as a sequence diagram; and a table of what the plan leaves
+    unconnected.
+- term_id: generated
+  text: >-
+    byte-for-byte what the installed package renders from the current `plan/`. The output carries no
+    timestamp and no package version, so it changes only when the plan (or the renderer) does.
+content:
+  summary: >-
+    A journey page drawn by hand drifts from the plan it describes the moment either changes. Generating
+    it, and failing when the committed copy differs, keeps the documented journeys the planned journeys,
+    and keeps the plan's gaps (unreached interlockings, open routes, unrouted trains) visible.
+  normative_text: |
+    The view renders planned behaviour, not acceptance evidence. It is generated so that reviewing a
+    decomposition does not require reading interlocking YAML: who hands what to whom, which guard
+    selects which route, and where each path ends.
+    The gaps table is part of the contract. A plan with interlockings but no journey still gets a page;
+    it shows every interlocking as unreached, which is the truthful state of the decomposition.
+  fix_hint: |
+    Regenerate and commit:
+      bun run atdd-bun docs journeys
+    If `docs/purpose/journeys/index.adoc` is a hand-written page, move its content elsewhere (the
+    generator refuses to overwrite it without --force). Change the plan, never the generated files.
+  exceptions:
+  - A repository with no `docs/` directory is not in scope.
+  - A plan with no journey and no interlocking is not in scope.
+metadata:
+  aliases:
+  - DOCS-JOURNEY-VIEW-001
+  severity: 3
+  disposition: strict
+  introduced_in: 0.4.0
+implementation:
+  type: validator
+  ref: docs_capability

package/conventions/planner.docs/planner.docs.reference-integrity.convention.yaml CHANGED Viewed

@@ -17,17 +17,6 @@ terms:
   text: >-
     a render failure the capability cannot pin to a document — a crashed renderer, an unreadable
     tree, a toolchain that is not installed. It is reported as `COULD_NOT_CHECK`, which BLOCKS.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: 'ABSENT — `command -v asciidoctor` exits 1 on this machine. The capability therefore returns COULD_NOT_CHECK here today, which BLOCKS, and that is the specified behaviour rather than a defect. Re-take this probe in the CI image before escalating; asciidoctor absence on a developer machine is expected and is not a reason to weaken the rule.'
-    measurement_target: 'this machine (the extension''s own toolchain probe)'
-    measurement_command: 'command -v asciidoctor'
-    escalate_when: 'asciidoctor is available in CI and a full render of the migrated corpus completes with zero unresolvable internal references. Note that the COULD_NOT_CHECK path already BLOCKS at the capability seam regardless of this disposition — advisory governs the reported findings, not the capability''s verdict contract.'
 content:
   summary: >-
     Reference integrity is why asciidoctor (Ruby) is the reference implementation rather than a pure
@@ -67,7 +56,8 @@ metadata:
   aliases:
   - DOCS-RENDER-001
   severity: 1
-  disposition: advisory
+  # 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/planner.docs/planner.docs.undeclared-change.convention.yaml CHANGED Viewed

@@ -17,17 +17,6 @@ terms:
   text: >-
     a changed path equals the `path` of some declared artifact, or the `from` of an `archive`
     artifact. Coverage is exact-path, not prefix or glob.
-- term_id: disposition_rationale
-  text: >-
-    advisory while the consuming corpus is brought into compatibility. The measurement below was
-    TAKEN on 2026-09-06, not recalled — #1782 found this convention's own recorded measurement
-    already stale, so the date lives in the key and the command is recorded beside the result.
-    Re-take it at the escalation checkpoint; never escalate on the number here.
-  values:
-    measured_2026_09_06: '0 declarations exist, so every `docs/**` change in the repository today is undeclared and this rule would fire on all of them. That is the reason it ships advisory rather than strict: escalating before the declaration exists would block every commit touching documentation.'
-    measurement_target: 'afokapu/atdd @ main (/Users/alecfokapu/Github/atdd/main)'
-    measurement_command: '(requires the core declaration, companion §3, which is not yet implemented)'
-    escalate_when: 'Declarations are being recorded at RATIFY and a full pass over recent merges reports zero undeclared `docs/**` changes.'
 content:
   summary: >-
     The enforceable inverse. Detecting that a change SHOULD HAVE BEEN declared is semantic and not
@@ -73,7 +62,8 @@ metadata:
   aliases:
   - DOCS-DECLARATION-002
   severity: 2
-  disposition: advisory
+  # 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.bun/tester.bun.acceptance-binding-declared.convention.yaml CHANGED Viewed

@@ -37,12 +37,8 @@ metadata:
   # shared alias for it, so the lineage is stated here and in the statement.
   - BUN-ACCEPTANCE-BINDING-DECLARED-001
   severity: 2
-  # 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.bun/tester.bun.acceptance-covers-tag-well-formed.convention.yaml CHANGED Viewed

@@ -38,11 +38,7 @@ metadata:
   # shared alias for it, so the lineage is stated here and in the statement.
   - BUN-COVERS-TAG-WELL-FORMED-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.
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
   disposition: strict
   introduced_in: 0.1.0
 implementation:

package/conventions/tester.bun/tester.bun.interlocking-train-sequence-is-exercised.convention.yaml CHANGED Viewed

@@ -23,19 +23,6 @@ terms:
     `route-coverage` proves an admissible route is exercised; `trace-binds-declared-route` proves
     the run is attributable to its declared route. Both are statements about SELECTION. A train
     whose sequence is wrong is selected correctly and runs the wrong thing.
-- term_id: disposition_rationale
-  text: >-
-    advisory because no consumer or fixture satisfies it yet, and because the check is staged
-    rather than gated. The measurement below was TAKEN, not recalled.
-  values:
-    measured_2026_09_07: >-
-      On a data-driven consumer whose TrainRunner genuinely reads the train definition, replacing
-      a train's entire wagon sequence in the plan left the consumer's own e2e suite at 4 passed.
-      The runtime obeyed the new plan; no test looked.
-    measurement_target: the python consumer built for the end-to-end experiment; no Bun consumer surveyed yet
-    escalate_when: >-
-      Consumer suites assert executed sequences and the check has been wired into
-      the bun_interlocking_coverage family gate. Enabling it is a GATE change; the detector is staged.
 content:
   summary: >-
     The tester half of `coder.train.runtime-executes-the-declaration (python; the Bun coder half is not yet authored)`. That rule makes the runtime
@@ -67,7 +54,8 @@ metadata:
   aliases:
   - BUN-TESTER-TRAIN-SEQUENCE-001
   severity: 2
-  disposition: advisory
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
+  disposition: strict
   introduced_in: 0.1.0
   core_design_refs:
   - afokapu/atdd#1248

package/conventions/tester.bun/tester.bun.red-behavioral-assertion.convention.yaml CHANGED Viewed

@@ -39,11 +39,7 @@ metadata:
   # shared alias for it, so the lineage is stated here and in the statement.
   - BUN-RED-BEHAVIORAL-ASSERTION-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.
+  # strict: atdd-bun fails on every finding; it has no advisory mode and no ratchet baseline.
   disposition: strict
   introduced_in: 0.1.0
 implementation:

package/conventions/tester.bun/tester.bun.routing-runtime-family.convention.yaml CHANGED Viewed

@@ -34,7 +34,8 @@ metadata:
   # Core obligation: tester.routing.layer-keyword-taxonomy
   - BUN-ROUTING-RUNTIME-FAMILY-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.bun/tester.bun.smoke-no-collaborator-substitution.convention.yaml CHANGED Viewed

@@ -26,19 +26,14 @@ content:
     Let the SMOKE test exercise the real collaborator against real infrastructure, and move the substituted version into a UNIT-phase test where the substitution is honest and expected.
   exceptions:
   - Only SMOKE-phase files are scanned; UNIT tests may substitute freely.
-  - Disposition matches core's `suppress-and-clean`: a ratchet holds existing cases flat.
 metadata:
   aliases:
   # Bun realization of the core obligation `tester.smoke.no-collaborator-substitution`. Core carries no
   # shared alias for it, so the lineage is stated here and in the statement.
   - BUN-SMOKE-NO-COLLABORATOR-SUBSTITUTION-001
   severity: 4
-  # 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.bun/tester.bun.smoke-observable-assertion.convention.yaml CHANGED Viewed

@@ -35,19 +35,14 @@ content:
   exceptions:
   - Only SMOKE-phase files are scanned.
   - Cases with no assertions are skipped — other rules own that.
-  - Disposition is `suppress-and-clean`: a ratchet holds an existing suite flat while it is migrated.
 metadata:
   aliases:
   # Bun realization of the core obligation `tester.smoke.operator-observable-assertion`. Core carries no
   # shared alias for it, so the lineage is stated here and in the statement.
   - BUN-SMOKE-OBSERVABLE-ASSERTION-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.bun/tester.bun.telemetry-emit.convention.yaml CHANGED Viewed

@@ -39,7 +39,8 @@ metadata:
   - TESTER-TELEMETRY-EMIT-001
   - BUN-TELEMETRY-EMIT-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.bun/tester.bun.test-carries-urn-identity.convention.yaml CHANGED Viewed

@@ -39,12 +39,8 @@ metadata:
   # shared alias for it, so the lineage is stated here and in the statement.
   - BUN-TEST-CARRIES-URN-IDENTITY-001
   severity: 2
-  # 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