Read Infrastructure Intent and generate the node contract from it #337

Parent

#324

What

Read Infrastructure Intent and generate the node contract from it (chapter 15, 0048):

• the reader, schema and model: Infrastructure, one Cluster, Node, Gpu, Disk, Taint; E_UNKNOWN_SITE, E_DUPLICATE_NODE, E_RESERVE_EXCEEDS_TOTAL, and a schema refusal for a second cluster; the three codes come off the Implement the Stable Address, the derived Move and Infrastructure Intent #324 pending list in scripts/lint-codes.ts;
• the document composed as an Intent Fragment, published by nix-config, the repository that owns the machines (chapter 15, confirmed by the maintainer 2026-10-27); nix-config gains the Publish Fragment workflow for it;
• a worked Infrastructure document for the seven nodes chapter 60 enumerates;
• the node contract generated from it, with labels under labelPrefix by the rule chapter 15 states; placement keeps reading the contract by digest;
• the node facts decided since: a Gpu carries hard vendor and model (#355); a node dataset binds to its node and derives the pin (Decide how the model meets soft scheduling, spread, anti-affinity and parked replicas #355); the host-privileged Node Agents are derived from node facts through the Platform catalog, owned by the node project (#356);
• REQ-034 moves its source to the document;
• chapter 15's "Open in this chapter" item 1 closes.

The NixOS generator is not part of this ticket.

Lands in TypeScript only. emf/ stays frozen at mde-task-3 until #666 and is not edited. Regenerate the goldens it affects rather than dropping any, with the rendered-tree and diagnostics oracles, in one pull request.

Behaviour (draft ledger row)

An authored Infrastructure document parses, a node on an undeclared site, a duplicated node or a reserve above its totals is refused at the node, and the node contract generated from it publishes the facts placement reads.

Blocked by

1.0.0 (#379). It must land before the node handover (#659), so that node and data hand over on the Infrastructure document rather than migrating twice; it runs alongside the mail, utility and agents handovers.