Render a provider's Service #395

Parent

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

What to build

An edge to a provider resolves to a cluster DNS name, so a provider can move without its consumers changing. Settled in Decide how the model meets the live needs no chapter covers (item 19). ollama-heavy is the live case.

Acceptance criteria

• A provider that some edge resolves to renders a selectorless Service and an EndpointSlice.
• A provider that no edge uses renders nothing.
• Consumers receive the cluster DNS name, and the Stable Address applies to it.
• 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

• Cut what the map cut and release package 1.0.0
• Derive and render the Stable Address, and resolve every dependency coordinate to it