Publish participant-resource-budget-policy-v1 from compiled scenarios #1528

Problem

participant-resource-budget-policy-v1 is a published contract with no producer. On dev a4357f9a the schema is contracts/schemas/participant-runtime/participant-resource-budget-policy-v1.json, the model is ParticipantResourceBudgetPolicyModel (raes_contracts/contracts/participant_resource_budgets.py:102), and backend manifests reference the contract (raes_contracts/manifest_authority.py:33, :69). Outside the schema bundle, no package code builds the document, and only test_issue_899_participant_resource_budgets.py and the backend-manifest stub fixture use the contract.

#1467 (DSL-121) makes the contract carry the tool scope of a tool_invocations demand, and the reference compiler records the same addresses on the compiled runtime demand. Its DSL-121 nonclaims (specs/formal/participant-semantics/autonomous-execution.md:337-338 at head 6da04a44) say:

The reference implementation does not publish a participant-resource-budget-policy-v1 document from a compiled scenario.

A backend that consumes the contract has to derive the policy itself from the compiled model, and nothing checks that the compiled budgets and the contract agree.

Scope

• Produce a participant-resource-budget-policy-v1 document from a compiled scenario's budgets, through a public facade, and validate it against the published schema.
• Decide where it is published (for example alongside the realization plan or the runtime model) and record that in the contract's documentation.

Done when

• A public function returns the participant-resource-budget-policy-v1 document for a compiled scenario, and the document validates against the published schema.
• A test compiles a scenario with v3 autonomous budgets (and, if feat: make interaction budgets a first-class participant behavior member #1469 has merged, aggregate budgets) and checks the document against the compiled demands, including the tool_invocations scope.
• The DSL-121 nonclaim about publication is removed.

Related

• feat: support authored participant interaction budgets #1467 (noted it), Participant Interaction Budget Surface (DSL-121) #308 (DSL-121), Add participant activity resource budgets and shared-service fairness contracts #899