Attach model-routing policy references to agent manifests and runtime authority

[mdheller]

Goal

Ensure every registered agent advertises and inherits model-routing constraints before it can execute governed work.

Context

SocioProphet/model-router now defines AgentExecutionModelRoutingPolicy for agent execution chains. Agent Registry owns agent specs, identities, sessions, memories, tool grants, revocation, and runtime authority. That means agent manifests need explicit policy references so AgentPlane and Guardrail Fabric can enforce the right lane constraints.

Required behavior

1. Extend agent manifest/spec examples with:
   • model routing policy ref
   • allowed default lane
   • maximum lane without escalation
   • allowed escalation reasons, if any
   • tool/network/write policy posture
   • prompt evidence mode, hash-only by default
   • ledger/evidence sinks
2. Add validation that rejects agents with:
   • high-end/pro default lanes
   • hosted fallback allowed by default
   • raw prompt evidence by default
   • unrestricted network/write/tool grants
3. Add session/runtime authority checks that pass model-routing refs into AgentPlane and Guardrail Fabric.
4. Define stricter presets for security-sensitive, host-mutating, infra-mutating, and production-release agents.

Acceptance criteria

• Agent manifest example includes AgentExecutionModelRoutingPolicy ref.
• Validator rejects unsafe high-end/pro defaults.
• Docs explain how manifests feed model-router, agentplane, guardrail-fabric, and model-governance-ledger.
• Example low-risk agent defaults to cheap/standard lanes and no-model verification.
• Example high-risk agent requires explicit escalation reason and receipt.

Non-goals

• Do not perform model routing here.
• Do not execute agents here.
• Do not store raw prompts or provider credentials.

[mdheller]

Add optimizer references to agent manifest/runtime authority scope as well.

Agent manifests should not only point at the model-routing policy; they should also declare the applicable optimizer policy:

• AgentExecutionModelRoutingPolicy for allowed lanes and escalation gates
• AgentExecutionBudgetResourceOptimizer for budget/resource/quota/latency/provider-health optimization

Manifest/runtime authority should carry:

• default allowed lane
• max lane without escalation
• budget class or budget pool ref
• quality/risk floor
• local-resource admission requirements
• hosted admission requirements
• provider quota policy
• prompt evidence mode
• ledger sinks for budget and escalation receipts

Validator should reject agents that can silently upgrade lanes, ignore budget windows, use unknown premium quota, or skip required optimizer evidence.