# SCENE: recorded agent image-draft verification

Recorded: 8 September 2026. Environment: local test workspace with Supabase; publishing disabled.

## What ran
An actual Codex host (desktop-bundled CLI 0.153.4) read campaign context, searched recipes, read a versioned recipe, prepared creative context, uploaded an existing example image, waited for ready media and submitted a creative version through SCENE’s MCP bridge.

Repeating the identical draft submission returned the same asset and version. Independent local database readback confirmed one asset, one media record, one creative context, the exact asset-to-context link and zero deliveries.

A separate protocol inventory found 13 tools and no approval, scheduling or publication tools. Automated protocol/service regression coverage also checks forbidden scheduling and credential revocation; these are distinct from actual-host acceptance.

## What this does not prove
- The image was existing demonstration media, not a newly generated campaign.
- No real social publication or performance result was produced.
- Actual-host video, human review, changed-payload conflict and host revocation checks remain outstanding.
- Claude and other host compatibility is not confirmed by this run.
- This local fixture is not a permanent production connection or an external-beta acceptance result.

## Evidence provenance
This public summary is derived from the repository record `docs/agent-host-acceptance.md`, sections “Codex connection configured — 8 September 2026” and “Actual Codex image-draft journey: passed”. The underlying implementation is `server/mcp.ts`; protocol/service regression coverage is in `server/local-supabase.test.ts`.

The recorded run has not been repeated as part of this marketing-copy update. Credentials and private workspace identifiers are intentionally omitted.