docs: plan — resource construction: the catalog mediates everything - #588

The graph's resource catalog represents input intent — what must exist when the graph runs. Ruled 2026-08-20
and planned in six phases under epic #444: at plan time a resource-typed parameter's string value mints a
pending entry with no existence check, a promise value records the promise and nothing else, and a product is
a runtime fact with no plan-time presence; the catalog serializes with the graph as a mandatory section that
is present even when empty, a document without it does not load, and a catalog-less graph fails pre-flight
hard; identity is the slash-canonical root-relative path under git-model plan-space semantics -- a leading
slash anchors at the fsroot -- and the fsroot is a run parameter unknown until execution, binding per account
for home scope and per host for system scope; schema stays 1 and existing documents are rewritten by
re-planning.

The plan converges the record to the design as authored: docs/sketches/resource-construction.md is the
source, 4-resource-management.md absorbs it as body (Appendix A deleted as rejected; its output-shadowing
variant superseded by the products-are-runtime-facts ruling), 4.1's file-URI ruling amends to rel identity,
and the sketches retire when integration is complete. Acceptance is the pair of demonstration pins that
forced the rulings, corrected to assert the source pending and the destination absent.

Feature #581 with tasks #582-#587 (phase 2 under the existing #546, closing the #547 family and with it the
last three Windows known-failures).

Refs #444, #581, #546, #547.

… named resource

The scenarios the feature is judged by: authored as predictions before implementation, graduating to
devlore-test cases, correct when the harness observes exactly the prediction. Scenario 1: two operations on
one named resource -- delete, then copy from it. The graph catalog holds exactly one pending entry (the same
string dedups to one identity; the copy's destination is a product and therefore absent); pre-flight passes
because intent was satisfied at the starting line; the run fails at the copy node and the delete compensates;
the trace records pending to Active with captured content identity to Gone, and no product. The graph says
what must be true; the trace says what happened; the gap between them is the run's story.

Refs #581.