[Draft] Pin an immutable Research Execution Profile to every run

[justsml]

Parent

#81

What to build

Resolve one immutable Research Execution Profile before a run begins. It contains coordinator and per-stage model URIs, provider options, context/output limits, capability manifest revision, selected skill revisions, target mode, network policy, tool/time budgets, UI collection, and policy versions.

The main controller, stage agents, and background work inherit this exact profile generation. They inherit capability availability, never approval grants or widened Target Authorization.

Acceptance criteria

• The effective profile is persisted and linked to the Research Run.
• Model construction, controller configuration, subagent configuration, and forensic reporting consume the same resolved values.
• Per-stage model overrides remain effective under the production AgentController path.
• Configuration changes affect later runs and do not silently mutate an active run.
• Missing or invalid capability/model revisions fail before the run is published.
• Requested and effective model envelopes remain separately inspectable.

Blocked by

• [Draft] Derive runtime tool behavior from one Security Capability Manifest #82
• [Draft] Persist a reconstructable Research Turn Ledger #83

[justsml]

Progress landed on dan/wayfinder-durable-passive-launch in d4d10a8. New runs now fail before ledger publication on unknown capability IDs or stale/unknown selected skill revisions; the exact Workspace skill refs are captured; resumed profiles configure native controller subagent provider/model identities; background scheduler contexts and handoffs carry the pinned profile identity, model/capability/skill refs, and intersect capability availability without inheriting approval or command grants. Focused integration coverage passes (23/23). Leaving #87 open: Mastra AgentController subagent model selection currently accepts provider/model identity only, and this branch does not yet prove that per-stage URI query parameters/providerOptions survive the production subagent path, which is required by the same-resolved-values acceptance criterion.

[justsml]

PR #157 has been updated with two council repair commits and marked draft after the third review loop still found P1 immutability blockers. The issue remains open. Remaining work: make pinned target config authoritative, claim scheduler tasks by run/profile identity, remove caller-grant acceptance from the background service boundary, preserve remote compute target identity, and reject unavailable model routes before run publication. See the latest PR comment for resolved work and verification.