[hyfdev]

Summary

• define a demand-driven complexity boundary for tools/api-codegen
• record and vouch the accepted tooling decision
• update the PCR index so the decision remains discoverable

Why

The current schema, input validation, compiler, and emitters protect distinct guarantees. Future generator capabilities should be added only for concrete outputs implemented in the same change, rather than for hypothetical reuse or to shorten generated files.

Validation

• vp run check:format
• git diff --check
• focused independent adversarial review: PASS

[Copilot]

Pull request overview

This PR records a clear, demand-driven complexity boundary for tools/api-codegen in the Project Context Records, and ensures the decision is discoverable through the PCR index and tooling decision ledger.

Changes:

• Added a new vouched ruling to the tooling decisions ledger defining a demand-driven boundary for API codegen complexity.
• Added a “Complexity boundary” section to the API code generation PCR doc clarifying when generator capabilities may expand.
• Updated the PCR index entry to reflect that tooling decisions now also cover demand-driven API code generation.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
.agents/docs/tooling-decisions.md	Adds a new vouched tooling decision (“Code generation remains demand-driven”) and links it to the detailed boundary in the API codegen PCR doc.
.agents/docs/README.md	Updates the PCR index description for “Tooling decisions” to include demand-driven API code generation.
.agents/docs/api-codegen.md	Introduces a dedicated “Complexity boundary” section documenting constraints on adding generator machinery without concrete implemented demand.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.