@afokapu/atdd-bun 0.1.0

package/planner-nodes/nodes/planner.component.type-catalog.convention.yaml

@@ -0,0 +1,436 @@
+schema_version: 1.1.0
+rule_id: planner.component.type-catalog
+kind: pattern
+status: active
+name: 'Component: Type Catalog'
+statement: The canonical component type catalog enumerates every component type by
+  side (backend|frontend), layer, file suffix per language, description, and complexity
+  weight, derived from the coder backend/frontend conventions.
+terms:
+- term_id: backend_catalog
+  label: Backend component types
+  text: All backend component types keyed by layer (presentation, application, domain,
+    integration), each with per-language file suffix, description, and complexity
+    weight.
+  values:
+    presentation:
+      controllers:
+        suffix:
+          python: '*_controller.py'
+          typescript: '*-controller.ts'
+        description: Request/response handlers for external interfaces
+        weight: 1
+      routes:
+        suffix:
+          python: '*_routes.py'
+          typescript: '*-routes.ts'
+        description: Routing configuration and endpoint definitions
+        weight: 0
+      serializers:
+        suffix:
+          python: '*_serializer.py'
+          typescript: '*-serializer.ts'
+        description: Input/output data serialization and formatting
+        weight: 0.5
+      validators:
+        suffix:
+          python: '*_validator.py'
+          typescript: '*-validator.ts'
+        description: Input validation at the edge
+        weight: 0.5
+      middleware:
+        suffix:
+          python: '*_middleware.py'
+          typescript: '*-middleware.ts'
+        description: Cross-cutting request/response processing
+        weight: 1
+      guards:
+        suffix:
+          python: '*_guard.py'
+          typescript: '*-guard.ts'
+        description: Authentication and authorization at transport layer
+        weight: 1
+      views:
+        suffix:
+          python: '*_view.py'
+          typescript: '*-view.ts'
+        description: Server-side rendered templates and UI components
+        weight: 1
+    application:
+      use_cases:
+        suffix:
+          python: '*_use_case.py'
+          typescript: '*-use-case.ts'
+        description: Application-specific business workflows
+        weight: 2
+      handlers:
+        suffix:
+          python: '*_handler.py'
+          typescript: '*-handler.ts'
+        description: Command, query, and event processing
+        weight: 1
+      ports:
+        suffix:
+          python: protocols.py, *_port.py
+          typescript: '*-port.ts'
+        description: Interfaces and protocols for integration layer
+        weight: 0
+      dtos:
+        suffix:
+          python: '*_dto.py'
+          typescript: '*-dto.ts'
+        description: Data transfer objects between layers
+        weight: 0
+      policies:
+        suffix:
+          python: '*_policy.py'
+          typescript: '*-policy.ts'
+        description: Application-level business policies and rules
+        weight: 1
+      workflows:
+        suffix:
+          python: '*_workflow.py, *_saga.py'
+          typescript: '*-workflow.ts'
+        description: Long-running processes and orchestrations
+        weight: 2
+    domain:
+      entities:
+        suffix:
+          python: '*.py'
+          typescript: '*.ts'
+        description: Core business objects with identity and lifecycle
+        weight: 1
+      value_objects:
+        suffix:
+          python: '*_vo.py, *.py'
+          typescript: '*-vo.ts'
+        description: Immutable types with equality-by-value semantics
+        weight: 0.5
+      aggregates:
+        suffix:
+          python: '*_aggregate.py'
+          typescript: '*-aggregate.ts'
+        description: Transactional consistency boundaries
+        weight: 2
+      services:
+        suffix:
+          python: '*_service.py'
+          typescript: '*-service.ts'
+        description: Domain services for cross-entity business logic
+        weight: 1
+      specifications:
+        suffix:
+          python: '*_spec.py'
+          typescript: '*-spec.ts'
+        description: Composable business rules and predicates
+        weight: 0.5
+      events:
+        suffix:
+          python: '*_event.py'
+          typescript: '*-event.ts'
+        description: Domain events representing facts that happened
+        weight: 0
+      exceptions:
+        suffix:
+          python: '*_exception.py'
+          typescript: '*-exception.ts'
+        description: Domain-specific errors and invariant violations
+        weight: 0
+    integration:
+      repositories:
+        suffix:
+          python: '*_repository.py'
+          typescript: '*-repository.ts'
+        description: Data persistence and retrieval adapters
+        weight: 2
+      clients:
+        suffix:
+          python: '*_client.py'
+          typescript: '*-client.ts'
+        description: External API and service clients
+        weight: 1
+      caches:
+        suffix:
+          python: '*_cache.py'
+          typescript: '*-cache.ts'
+        description: Caching implementations
+        weight: 0.5
+      engines:
+        suffix:
+          python: '*_engine.py'
+          typescript: '*-engine.ts'
+        description: Computational and processing engines (ML, graph, optimization)
+        weight: 3
+      formatters:
+        suffix:
+          python: '*_formatter.py'
+          typescript: '*-formatter.ts'
+        description: Output formatting and rendering services
+        weight: 1
+      notifiers:
+        suffix:
+          python: '*_notifier.py'
+          typescript: '*-notifier.ts'
+        description: Communication and notification services
+        weight: 1
+      queues:
+        suffix:
+          python: '*_queue.py'
+          typescript: '*-queue.ts'
+        description: Message queue and event streaming clients
+        weight: 2
+      stores:
+        suffix:
+          python: '*_store.py'
+          typescript: '*-store.ts'
+        description: File and object storage adapters
+        weight: 1
+      mappers:
+        suffix:
+          python: '*_mapper.py'
+          typescript: '*-mapper.ts'
+        description: Data transformation and mapping between layers
+        weight: 0.5
+      schedulers:
+        suffix:
+          python: '*_scheduler.py'
+          typescript: '*-scheduler.ts'
+        description: Background tasks and scheduled jobs
+        weight: 2
+      monitors:
+        suffix:
+          python: '*_monitor.py'
+          typescript: '*-monitor.ts'
+        description: Observability and infrastructure monitoring
+        weight: 1
+- term_id: frontend_catalog
+  label: Frontend component types
+  text: All frontend component types keyed by layer (presentation, application, domain,
+    integration), each with per-language file suffix, description, and complexity
+    weight.
+  values:
+    presentation:
+      views:
+        suffix:
+          dart: '*_page.dart'
+          typescript: '*-page.tsx'
+        description: Full-screen views and pages
+        weight: 1
+      components:
+        suffix:
+          dart: '*_widget.dart'
+          typescript: '*.tsx'
+        description: Reusable UI components
+        weight: 0.5
+      containers:
+        suffix:
+          typescript: '*-container.tsx'
+        description: Smart components connected to state
+        weight: 1
+      controllers:
+        suffix:
+          dart: '*_bloc.dart'
+          typescript: '*-store.ts'
+        description: UI state management and business logic
+        weight: 2
+      routes:
+        suffix:
+          dart: '*_router.dart'
+          typescript: '*-routes.ts'
+        description: Navigation and routing configuration
+        weight: 0
+      layouts:
+        suffix:
+          dart: '*_layout.dart'
+          typescript: '*-layout.tsx'
+        description: Page structure and composition templates
+        weight: 1
+      styles:
+        suffix:
+          dart: '*_theme.dart'
+          typescript: '*.css'
+        description: Design tokens, themes, and styling
+        weight: 0
+      animations:
+        suffix:
+          dart: '*_animation.dart'
+          typescript: '*-animation.ts'
+        description: UI animations and transitions
+        weight: 0.5
+      forms:
+        suffix:
+          dart: '*_form.dart'
+          typescript: '*-form.ts'
+        description: Form state management and validation
+        weight: 1
+      hooks:
+        suffix:
+          typescript: use-*.ts
+        description: Reusable stateful logic (React-style)
+        weight: 0.5
+      directives:
+        suffix:
+          typescript: '*-directive.ts'
+        description: Custom DOM/element behaviors (Vue/Angular)
+        weight: 0.5
+      filters:
+        suffix:
+          typescript: '*-filter.ts'
+        description: Data formatting pipes/filters
+        weight: 0.5
+    application:
+      use_cases:
+        suffix:
+          dart: '*_use_case.dart'
+          typescript: '*-use-case.ts'
+        description: Frontend-initiated workflows
+        weight: 2
+      ports:
+        suffix:
+          dart: '*_port.dart'
+          typescript: '*-port.ts'
+        description: Interfaces for data access and external services
+        weight: 0
+      policies:
+        suffix:
+          dart: '*_policy.dart'
+          typescript: '*-policy.ts'
+        description: Frontend business policies and rules
+        weight: 1
+      dtos:
+        suffix:
+          dart: '*_dto.dart'
+          typescript: '*-dto.ts'
+        description: Application-internal data structures
+        weight: 0
+    domain:
+      entities:
+        suffix:
+          dart: '*.dart'
+          typescript: '*.ts'
+        description: Domain models used on the client
+        weight: 1
+      value_objects:
+        suffix:
+          dart: '*_vo.dart'
+          typescript: '*-vo.ts'
+        description: Immutable typed values
+        weight: 0.5
+      services:
+        suffix:
+          dart: '*_service.dart'
+          typescript: '*-service.ts'
+        description: Pure domain logic services
+        weight: 1
+      specifications:
+        suffix:
+          dart: '*_spec.dart'
+          typescript: '*-spec.ts'
+        description: Composable rules and predicates
+        weight: 0.5
+      exceptions:
+        suffix:
+          dart: '*_exception.dart'
+          typescript: '*-exception.ts'
+        description: Domain-level errors
+        weight: 0
+    integration:
+      repositories:
+        suffix:
+          dart: '*_repository.dart'
+          typescript: '*-repository.ts'
+        description: Data access implementations
+        weight: 2
+      clients:
+        suffix:
+          dart: '*_client.dart'
+          typescript: '*-client.ts'
+        description: HTTP/WebSocket/GraphQL API clients
+        weight: 1
+      stores:
+        suffix:
+          dart: '*_store.dart'
+          typescript: '*-store.ts'
+        description: Local persistence implementations
+        weight: 1
+      serializers:
+        suffix:
+          dart: '*_serializer.dart'
+          typescript: '*-serializer.ts'
+        description: API data transformation
+        weight: 0.5
+      mappers:
+        suffix:
+          dart: '*_mapper.dart'
+          typescript: '*-mapper.ts'
+        description: Data transformation between layers
+        weight: 0.5
+      interceptors:
+        suffix:
+          dart: '*_interceptor.dart'
+          typescript: '*-interceptor.ts'
+        description: HTTP request/response middleware
+        weight: 1
+      caches:
+        suffix:
+          dart: '*_cache.dart'
+          typescript: '*-cache.ts'
+        description: Client-side caching implementations
+        weight: 0.5
+      synchronizers:
+        suffix:
+          dart: '*_sync.dart'
+          typescript: '*-sync.ts'
+        description: Offline sync and conflict resolution
+        weight: 2
+      monitors:
+        suffix:
+          dart: '*_monitor.dart'
+          typescript: '*-monitor.ts'
+        description: Client-side monitoring and telemetry
+        weight: 1
+      validators:
+        suffix:
+          dart: '*_validator.dart'
+          typescript: '*-validator.ts'
+        description: Client-side validation engines
+        weight: 0.5
+      workers:
+        suffix:
+          typescript: '*.worker.ts'
+        description: Background processing and web workers
+        weight: 2
+      connectors:
+        suffix:
+          dart: '*_connector.dart'
+          typescript: '*-connector.ts'
+        description: Real-time and streaming connections
+        weight: 1
+implementation:
+  type: validator
+  ref: test_component_type_catalog::test_component_type_catalog
+source:
+  legacy_path: src/atdd/planner/conventions/component.convention.yaml
+  legacy_sha: sha256:8bfb25fd6c2bdb6e
+  extraction_mode: high_fidelity
+  legacy_section: type-catalog
+content:
+  summary: A single canonical catalog of component types, their file suffixes, and
+    complexity weights lets the planner derive components and estimate effort consistently
+    with the coder conventions, instead of inventing types or weights ad hoc.
+  operational_guidance: Derived from .claude/conventions/coder/{backend,frontend}.convention.yaml.
+    Side and layer values for component URNs are defined by this catalog's structure.
+  examples:
+  - "backend.integration.engines \u2192 *_engine.py, weight 3 (highest complexity)"
+  - "backend.presentation.routes \u2192 *_routes.py, weight 0"
+  - "frontend.presentation.controllers \u2192 *_bloc.dart / *-store.ts, weight 2"
+metadata:
+  severity: 2
+  disposition: advisory
+  introduced_in: 4.28.0
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: true
+  fix_hint_preserved: true
+  reviewed_at: '2026-06-16'

package/planner-nodes/nodes/planner.component.urn.convention.yaml

@@ -0,0 +1,86 @@
+schema_version: 1.1.0
+rule_id: planner.component.urn
+kind: rule
+status: active
+name: 'Component: Urn'
+statement: A component URN follows the pattern component:{wagon}:{feature}:{name}:{side}:{layer}
+  with colon hierarchy separators, casing rules, no file extensions, and is built
+  via utils.graph.URNBuilder.component.
+implementation:
+  type: none
+source:
+  legacy_path: src/atdd/planner/conventions/component.convention.yaml
+  legacy_sha: sha256:8bfb25fd6c2bdb6e
+  extraction_mode: high_fidelity
+  legacy_section: urn
+content:
+  summary: A stable, colon-separated component URN ties every component back to its
+    owning wagon and feature and pins its deployment side and architectural layer,
+    so the graph can address components unambiguously and case-sensitively.
+  examples:
+  - component:resolve-dilemmas:choose-option:OptionValidator:backend:domain
+  - component:manage-users:authenticate-user:LoginForm:frontend:presentation
+  - component:maintain-ux:assets-catalog:AssetIndexer:backend:integration
+  - 'component:navigate-domains:browse-hierarchy:composition:backend:assembly  # feature
+    composition (above layers)'
+  - 'component:trains:runner:TrainRunner:backend:assembly  # train infrastructure
+    (always assembly)'
+  counter_examples:
+  - 'component:resolve-dilemmas:choose-option:OptionValidator.py:backend:domain  #
+    file extension'
+  - 'component:Resolve-Dilemmas:choose-option:OptionValidator:backend:domain  # wagon
+    not kebab-lower'
+parity:
+  source_fragments_preserved: true
+  examples_preserved: true
+  implementation_preserved: true
+  fix_hint_preserved: true
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: urn_pattern
+  label: Component URN pattern
+  text: 'Stable component URN with all segments colon-separated: component:{wagon}:{feature}:{name}:{side}:{layer}.
+    Built via utils.graph.URNBuilder.component(wagon_id, feature_id, component_name,
+    side, layer).'
+  values:
+    pattern: component:{wagon}:{feature}:{name}:{side}:{layer}
+    utility: utils.graph.URNBuilder.component(wagon_id, feature_id, component_name,
+      side, layer)
+    hierarchy_separator: ':'
+    facet_separator: .
+- term_id: urn_parts
+  label: URN segment meanings
+  text: Each URN segment has a defined meaning and casing for wagon, feature, name,
+    side, and layer.
+  values:
+    wagon: Parent wagon identifier (kebab-case). Use 'trains' for train infrastructure.
+    feature: Parent feature identifier (kebab-case). Use 'wagon' for wagon entrypoints.
+    name: Logical component name (PascalCase, camelCase, or dot-separated)
+    side: Deployment side (frontend|backend|fe|be)
+    layer: Architectural layer (presentation|application|domain|integration|assembly)
+- term_id: urn_casing
+  label: Casing and case policy
+  text: Wagon and feature segments are kebab/lower; name facets may be kebab/lower
+    or CamelCase. IDs are case-sensitive and stored exactly as written.
+  values:
+    wagon_feature: ^[a-z][a-z0-9-]*$
+    facets:
+    - ^[a-z][a-z0-9-]*$
+    - ^[A-Z][a-zA-Z0-9]*$
+    case_policy: IDs are case-sensitive; store exactly as written.
+- term_id: no_file_extensions
+  label: No file extensions in URN
+  text: Do not include .py/.dart/etc. in a component URN. Use a 'lang-*' facet if
+    a language must be expressed.
+  values:
+    forbidden:
+    - .py
+    - .dart
+    - .ts
+    - .tsx
+    use_instead: lang-* facet
+- term_id: lint_regex
+  label: URN lint regex
+  text: The canonical lint regex a component URN must match.
+  values:
+    lint_regex: ^component:[a-z][a-z0-9-]*:[a-z][a-z0-9-]*:[a-zA-Z0-9.]+:(frontend|backend|fe|be):(presentation|application|domain|integration|assembly)$

package/planner-nodes/nodes/planner.contract.registry-coherence.convention.yaml

@@ -0,0 +1,36 @@
+schema_version: 1.1.0
+rule_id: planner.contract.registry-coherence
+kind: constraint
+status: active
+name: Contract registry producer/consumer coherence
+statement: Every contract URN on a wagon produce/consume must resolve to a contract registered in contracts/_contracts.yaml; no cross-wagon produce/consume edge may carry contract null; every produced contract must have a consumer or be explicitly marked external.
+implementation:
+  type: validator
+  ref: test_contract_registry_coherence::test_contract_registry_coherence
+source:
+  legacy_path: docs/recompose
+  legacy_section: contract-coherence
+  extraction_mode: summary
+content:
+  normative_text: 'The authored registry contracts/_contracts.yaml is the single source of truth for a contract''s identity, path, theme, producers, and consumers. Three coherence invariants hold across the plan/<wagon>/_<wagon>.yaml produce/consume graph and that registry. (1) UNREGISTERED: every non-null contract: URN declared on a produce or consume entry must strip to an identity that exists in the registry. (2) NULL-CROSS-WAGON: whenever an artifact NAME produced by one wagon is consumed by a different wagon (a cross-wagon edge), the producing entry must declare a non-null contract — a contract: null cross-wagon edge is a dangling producer. (3) UNCONSUMED: every produce entry that declares a non-null contract must be consumed by at least one other wagon or be explicitly marked to: external. Closes the dangling-producer / contract: null class from the #250 audit.'
+  constraints:
+  - every non-null contract URN on produce/consume resolves to a registered contract identity
+  - no cross-wagon produce/consume edge carries contract null
+  - every produced contract is consumed by another wagon or explicitly marked external
+  - registry keys are contract identities; the contract: URN prefix is stripped before lookup
+metadata:
+  severity: 3
+  disposition: advisory
+parity:
+  source_fragments_preserved: true
+  examples_preserved: false
+  implementation_preserved: true
+  fix_hint_preserved: false
+  reviewed_at: '2026-07-02'
+terms:
+- term_id: contract_registry
+  text: contracts/_contracts.yaml — the authored source of truth mapping each contract identity to its path, theme, producers, and consumers. Authored by create_contract (#1330); validated for coherence here (#1332).
+- term_id: cross_wagon_edge
+  text: a produce->consume relationship in which an artifact NAME produced by one wagon is consumed by a different wagon, keyed on the artifact name.
+- term_id: dangling_producer
+  text: a producing entry on a cross-wagon edge whose contract field is null, so no contract binds the edge.

package/planner-nodes/nodes/planner.convention.remedy-must-be-followable.convention.yaml

@@ -0,0 +1,92 @@
+schema_version: 1.1.0
+rule_id: planner.convention.remedy-must-be-followable
+kind: rule
+status: active
+name: A convention node's remedy must be followable
+statement: >-
+  Operative prose in a convention node — the fix_hint, operational_guidance,
+  normative_text, statement and term text a reader is expected to ACT on — must
+  name only files that exist in the repo and only CLI verbs that still resolve.
+  A fix_hint is an executable promise: if it names a file, that file must be
+  there; if it names a verb, that verb must run.
+notes: >-
+  #1965: five remedies across four nodes were unfollowable — three named a file
+  that is not there, two instructed `atdd issue`, removed in #1303 — and a sixth
+  turned up while designing the rule. Nothing read a fix_hint, so when the verb
+  was removed and the smoke-acceptance validator renamed, every hint quoting
+  them stayed exactly as written. Same family as #1548, where the authorable
+  exemplar carried a URN scheme retired by #1421 and following the documentation
+  produced an invalid artifact. STRICT, and the disposition is the point: a
+  naive scan finds 179 of 332 paths absent, but decomposed by cause 137 are
+  provenance and 34 illustrative, leaving six real. #1958 and #1943 had to
+  settle for advisory at 369-of-473 and 101-of-229 because the remedy was
+  unaffordable; six is affordable, so this refuses instead of logging.
+implementation:
+  type: validator
+  ref: test_convention_remedies_are_followable::test_every_convention_remedy_is_followable
+metadata:
+  severity: 3
+  disposition: strict
+  introduced_in: 4.83.0
+content:
+  fix_hint: >-
+    The named node's prose sends the reader somewhere that is not there. For an
+    absent path: correct it to the real location, or drop the pointer if the
+    thing it named no longer exists (do not leave a half-repair — a path that is
+    merely plausible is what produced this defect). For a retired verb: replace
+    it with the live one — `atdd issue <N> --status <PHASE>` became `atdd coach
+    transition <N> <PHASE>`, and `atdd issue open` became `atdd coach issues
+    open`. Re-run with `pytest
+    src/atdd/planner/validators/test_convention_remedies_are_followable.py -v`.
+  exceptions:
+  - >-
+    Provenance (`source.legacy_path`) is out of scope — it records where a node
+    was extracted from and carries a `legacy_sha`; the monolith it names was
+    deliberately deleted, and pointing at a deleted file is what provenance IS.
+  - >-
+    Illustrative paths in `examples`/`values` blocks are fictional by design; a
+    naming rule's negative example must NOT exist.
+  - >-
+    A schematic formula (`Formula: ... -> contracts/theme/seg1/...`) is a
+    template whose segments are positions, not directories.
+  - >-
+    A path named as an EXCLUDED mechanism ("no plan/_meta.yaml") is a statement
+    of absence; flagging it would invert the node's meaning.
+  - >-
+    A conditional reference ("if it exists", "when present") is a predicate
+    subject, not a pointer.
+  - >-
+    Gitignored runtime state is excused via `git check-ignore`, so the exclusion
+    cannot outlive the path — the day a path leaves `.gitignore` is the day it
+    stops being excused.
+  - >-
+    A path a node declares RETIRED is a historical record. The test is tense,
+    not the token — "#1270 retired the `.atdd/manifest.yaml` mirror" is a
+    record; "the phase labels live under `.atdd/labels.yaml`" is a defect.
+operational_guidance: >-
+  Runs against the checkout and is `platform`-gated. In a consumer repo the
+  nodes arrive from the installed package while the paths they quote are paths
+  in the TOOLKIT repo, so an ungated rule would flag nearly every path as absent
+  in somebody else's repo — the leak `is_atdd_source_repo()` exists to prevent
+  (#272/#276). The installed package also carries none of `plan/`, `docs/` or
+  `.atdd/`, so it is not a root this rule can resolve against.
+terms:
+- term_id: operative_prose
+  label: Operative prose
+  text: >-
+    a string a reader is expected to act on: `fix_hint`,
+    `operational_guidance`, `normative_text`, `statement`, `text`, `notes`,
+    `description`. Distinguished from provenance (a record) and from examples
+    (illustrations) — only operative prose makes a promise.
+- term_id: unfollowable_remedy
+  label: Unfollowable remedy
+  text: >-
+    operative prose naming a repo path absent from the checkout, or a CLI verb
+    that no longer resolves. The reader is sent nowhere at the exact moment they
+    are blocked, which is when a fix_hint is the one part of a rule they read.
+- term_id: retired_verb
+  label: Retired verb
+  text: >-
+    a CLI verb removed from the toolkit whose spelling survives in prose. Each
+    is recorded with the live verb that replaced it, because a remedy saying
+    only "that verb is gone" is itself unfollowable.

package/planner-nodes/nodes/planner.coverage.bidirectional-coverage-between-trains.convention.yaml

@@ -0,0 +1,33 @@
+schema_version: 1.1.0
+rule_id: planner.coverage.bidirectional-coverage-between-trains
+kind: rule
+status: active
+name: Train - Wagon Coverage
+statement: A train and its wagons must reference each other bidirectionally (wagon->train and train->wagon).
+source:
+  legacy_path: src/atdd/planner/conventions/coverage.convention.yaml
+  legacy_section: rules
+  legacy_sha: 27e800378c584902
+  extraction_mode: high_fidelity
+  legacy_rule_id: planner.coverage.bidirectional-coverage-between-trains
+bidirectional:
+- direction: wagon -> train
+  requirement: Every wagon must appear in at least one train's participants
+  exceptions: wagons_not_in_train allow-list or status:draft
+  validator: test_all_wagons_in_at_least_one_train
+- direction: train -> wagon
+  requirement: 'Every wagon: participant must have a wagon manifest'
+  validator: test_all_train_wagon_refs_exist
+metadata:
+  aliases:
+  - COVERAGE-PLAN-2.1
+  disposition: documentation-only
+parity:
+  source_fragments_preserved: true
+  examples_preserved: false
+  implementation_preserved: true
+  fix_hint_preserved: false
+  reviewed_at: '2026-06-16'
+terms:
+- term_id: bidirectional_coverage
+  text: each side references the other, no orphan.