[tracking] OpenAI Agents API gaps blocked on Parsar Core

[sam2tom]

Context

Agents Core Web owns the Web UI and TypeScript client only. Parsar Core, daemon, native harnesses, and Environment providers remain upstream-owned. This tracker records OpenAI Agents API capabilities that Web cannot implement honestly until Parsar exposes a stable, versioned contract.

Current Web task split:

• Agent management: [agent] Complete saved Agent details, edit, and delete flows #1
• Protocol Environment/action/event types: [agent] Sync Parsar Environment, action, and event protocol types #2
• SSE durable recovery and idempotency: [agent] Harden SSE durable recovery and idempotent manual retry #3
• Parsar apply_patch Diff Viewer: [agent] Add protocol-aware Item renderers and Parsar apply_patch Diff Viewer #4
• Environment/Workspace status UI: [agent] Add self-hosted Environment and Workspace status UI #5
• Session metadata/delete: [agent] Add Session rename, metadata, and delete flows #6
• Turn timeline and Usage: [agent] Add Turn timeline, real elapsed time, errors, and Usage #7

Upstream capability groups to track separately in MiniMax-AI-Dev/parsar:

1. A namespaced capability manifest that distinguishes route presence, runtime readiness, executable tools/environments, protocol baseline, and model-source information.
2. Environment retrieve/lifecycle/templates/provider contracts.
3. Environment Files and Artifacts with tenant isolation and safe workspace boundaries.
4. Credential boundaries for environment.env, self-hosted executor keys, and MCP Vault credentials.
5. Complete durable Item/SSE projection for reasoning, agent messages, preparation, approvals, Environment/Subagent events, deltas, and stable server timestamps.
6. Real MCP, Web Search, and Plugin configuration/execution rather than result mapping alone.
7. Real Multi-agent/Subagent scheduling, cancellation, recovery, coordination Items, and Usage attribution.

Acceptance criteria

• Every upstream group has a dedicated Parsar Issue URL, owner/status, and immutable contract commit once filed.
• Each row distinguishes missing API, internal-only implementation, render-only data, and verified executable behavior.
• Web follow-up work is unblocked only after a stable Core API/event shape and raw fixtures exist.
• docs/protocol-coverage.md is updated whenever an upstream capability changes state.
• Environment, Files, Artifacts, Vault, MCP/Web Search/Plugins, Multi-agent/Subagent, timestamps, and tracing remain visibly blocked while unsupported.
• Compatibility evidence records the exact Parsar SHA and OpenAI Agents API baseline instead of referring only to latest/main.
• Unknown or unsupported capabilities continue to fail explicitly or remain hidden; no optimistic capability claims.

Validation

• Re-check the linked Parsar source and public handlers at the recorded immutable SHA.
• Verify every unblocked Web feature has a raw HTTP/SSE fixture and an associated Web acceptance Issue.
• Review docs/protocol-coverage.md against this tracker after each Core upgrade.
• This tracking Issue requires no paid model request and no repository code change by itself.

Non-goals

• Do not implement Parsar Core, daemon, executor, native harness, or Environment Provider code in agents-core-web.
• Do not emulate missing Core resources in browser state, metadata, localStorage, or a mock production endpoint.
• Do not expose caller, executor, provider, env, or Vault credentials to the browser.
• Do not treat a saved configuration, HTTP route, health check, or open SSE connection as proof of runtime execution.
• Do not use this tracker as an agent-ready implementation task or commit any .agents content.