Accept 0024, and rewrite the work breakdown around what is actually being done

**0024 accepted.** Model access was decided, built, and proven in the
lab, and two design documents rest on it; only the status had never
moved. The gate is green again.

**The work breakdown rewritten.** It planned a decomposition of the
existing system in place — extract contexts, declared features, shrink
the shared library. That is not the work. A replacement is being built
beside it, and only the old Phase 0 survived contact with reality, so
the one document meant to say what happens next was describing a system
being retired.

Now ordered by what "modules move across one at a time until the old
registry is off" actually requires:

- Phase 0 is marked done against the twenty-two lab assertions, **and
  carries its own limitation**: every module exercised was written to
  test the mechanism, so the vocabulary was shaped by its own fixtures.
- Phase 1 is the vocabulary gaps found by asking what real modules
  need — an object-store provision, a session as a licence consumer, a
  network shape with ordering, public certificate issuance.
- Phase 2 is one module, then a week of running it, because the point of
  going first is to find what Phase 1 missed.
- Phase 3 picks modules that each prove something the first did not; the
  mail system is last because it is the one that may send work back into
  the declaration language.
- Phase 4 is switching the registry off, named as a phase so it is not
  mistaken for the goal.

Keeps the rules of engagement unchanged — they were about how work is
done, not what it is — with one addition: stop and ask before anything
that touches a machine outside the lab.

Adds a section on keeping the list true, since the document it replaces
was wrong for weeks and nothing said so. A claim here is counted, not
reasoned, and a phase is done when the lab says so.

03-DESIGN/01-to-be/01-end-to-end-testing.md

@@ -336,7 +336,10 @@ credential rotation reaches every consumer, that delivery to an absent node is r
 pending rather than done, that a returning node catches up. These are fewer and change
 rarely, but they are where the known production faults get encoded so they stay fixed.
 
-The known faults become mesh tests that fail today. That is the Phase 0 checkpoint.
+The known faults become mesh tests that fail today. Phase 0 of
+[`00-work-breakdown.md`](00-work-breakdown.md) is now complete on this basis — twenty-two
+assertions on real machines — and what it does **not** cover is recorded there: no module
+from the existing system has run against any of it yet.
 
 ---