proof-capture

Use the interactive workflow for video, screenshots, and a PR body. Strict machine proof runs through the proof controller and requires managed Metro ownership, bound-worktree serving-root containment, a signed initial-bundle marker, exact device and install bindings, and the source and dirty digest.

Usage

/rn-dev-agent:proof-capture <feature-slug> [description of flow to execute]
/rn-dev-agent:proof-capture --strict <feature-slug> [description of flow to execute]

Examples

/rn-dev-agent:proof-capture profile-edit navigate to profile, edit name, save, verify update
/rn-dev-agent:proof-capture dark-mode toggle dark mode on settings, check all screens
/rn-dev-agent:proof-capture --strict profile-edit navigate to profile, edit name, save, verify update

Strict Mode

--strict first loads the controller contract. Darwin receipts carry sandbox: 'managed-sandbox-v1' when the Apple-signed absolute-path Seatbelt sandbox and command-chain change detection are available. Other hosts carry sandbox: 'unavailable'; sandbox availability is not a strict-proof precondition. Provenance mismatches fail with their specific refusal code. Do not substitute interactive artifacts when a machine receipt or merge-ready evidence is required. See Parallel session authority for the managed provenance contract.

Interactive Artifacts

Artifact	Path	Description
Video	docs/proof/<slug>/flow-<platform>.mp4	Screen recording of the entire flow
Labeled video	docs/proof/<slug>/flow-<platform>-labeled.mp4	Video with timed step description bar
GIF	docs/proof/<slug>/flow-<platform>.gif	Animated GIF for inline PR display
Screenshots	docs/proof/<slug>/01-<step>.jpg	Numbered screenshots at each state change
PROOF.md	docs/proof/<slug>/PROOF.md	Flow table with step/screenshot/action/verification
PR-BODY.md	docs/proof/<slug>/PR-BODY.md	Ready-to-paste PR description

Interactive Steps

1. Parse arguments — extract feature slug and flow description
2. Environment check — confirm app is running, dismiss Dev Client picker if present
3. Start recording — begin video capture on the active simulator
4. Execute the flow — navigate and interact through each step, capture numbered screenshots
5. Stop recording — end video, convert to GIF
6. Label the video — add timed step descriptions as a text bar
7. Validate — verify recording shows the expected feature, all screenshots exist, no errors
8. Write PROOF.md — date, device info, flow table, state snapshots
9. Generate PR body — ready-to-paste PR description with embedded screenshots

When to Use

• After implementing a feature and wanting PR-ready proof
• To re-record proof after fixing review findings
• Standalone proof capture without the full 8-phase pipeline

Prerequisites

• iOS Simulator or Android Emulator running with the app loaded
• Ready fenced session with the integrated Metro and signed app target
• ffmpeg for GIF conversion and video labeling (brew install ffmpeg)