Slice 6: render the composed estate and the edge #203

Parent

#195

What to build

The composed estate: the estate-scoped paths as their own artifact, the edge example, the composition invariants as an enumerable registry, and the negative/ fixtures rewritten with diagnostics (0156, SC-19, SC-30, SC-33, SC-36).

Acceptance criteria

• The estate-scoped tree and the edge oracles equal committed files; every negative fixture's diagnostics are committed and met.

Folded in from #46

The identity and reference invariants over the composed union, evaluated order-independently with every collision an error.

• Identity: duplicate Application id, project, Process name within a project, host, exposure name, route path and match.
• References: unresolved Application, unknown surface on a dependency edge, provider without coordinates, a cycle over required edges, an audience no tier carries.

Each fires on its own negative fixture, whose committed diagnostics.json both implementations meet, for every fragment order. The Java counterpart is #89.

Blocked by

• Slice 4: model and render the knowledge platform #201