Skip to content

I0011 — Cross-surface consistency and mutation tests

Prove that the CLI, the generated site data and the GitHub projection describe the same graph, and that changing one canonical dependency changes all of them.

DONE wave 6 · p0 · debugging profile · runs alone

Part of M000 — Milestone and DAG driven development.

Objective

Prove that the CLI, the generated site data and the GitHub projection describe the same graph, and that changing one canonical dependency changes all of them.

Why

One engine is a claim. A test that compares the surfaces is the only thing that keeps it true after the next change.

Current state

Each surface was tested on its own.

Desired state

A case compares the issue set, the READY set and the edge set across surfaces, and a second case mutates a dependency and asserts every surface moved.

Scope

  • test/cases

Out of scope

  • Live GitHub calls in the test suite

Dependencies

What waits on this

Acceptance criteria

  • Canonical issue count equals CLI count equals site data count equals projection count
  • Canonical READY set equals the CLI READY set equals the site data READY set
  • Canonical edges equal Mermaid edges equal site data edges
  • Adding one dependency changes status, waves, Mermaid and site data together

Validation

  • bash test/run.sh 34_cross_surface
  • bash test/run.sh 35_mutation

Evidence required

  • cross_surface
  • mutation

Evidence

coverstypecommandresultat commit
cross_surfacetestbash test/run.sh 46_cross_surface1 passed — the CLI, the JSON output, the Mermaid diagram, the GitHub projection and a freshly generated site-data file agree on the issue set, the READY set, the edge set and the next ready issue, across separate processes05423af
mutationtestbash test/run.sh 47_mutation1 passed — every canonical mutation the case makes moves every surface: an added edge, a completed dependency, a deleted evidence record, a prose-only change, and an induced cycle reaching plan validate, doctor and watch05423af

Risk

Low

Timeline

started
2026-09-04T05:14:46Z
verified
2026-09-04T05:14:48Z
completed
2026-09-04T05:14:50Z

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0011.yaml. Read it back with majordomus plan show I0011.