Routes render once the edge is on the estate path #584

Parent

Rewrite the spec and the compiler in place, release 1.0.0, and hand over every Project

What to build

Routes render once edge itself is on the estate path, not only once no Project is legacy. Chapter 60 today says no Project's artifact carries a route until the ledger is empty, so all 48 live routes would flip in the very last change, together with the secrets move. Operator decision of 2026-10-23: routes flip with the edge handover, in the same window as Traefik, and the later secrets move does not touch routes. Legacy Projects' routes stay on the old path until each leaves.

Acceptance criteria

• Chapter 60 states the new condition, and chapters 14 and 55 agree.
• With edge handed over and another Project still legacy, composition renders every estate Project's routes and none of the legacy one's.
• The chapter states the rule and its refusals, with short rationale only, and CONTEXT.md carries each new term in the same pull request.
• A worked example shows it; its resolved artifact and its rendered tree are updated and reviewed by hand, never regenerated in CI.
• Each refusal has a refusal example with its diagnostics file.
• The JSON Schemas and their corpus admit the new shape and refuse a malformed one.
• The behaviour-ledger row lands with its test, and npm run verify passes.

Blocked by

• Split the compiler's mixed modules by concept, with no change of behaviour