verification

# Verification Prefer two signals: 1. `read_project` for structure: assets, tracks, items, frame placement, timeline duration. 2. A visual capture path for rendered evidence at exact frames. Use `view_timeline_frames` for composed timeline proof. This verifies the edited OpenChatCut timeline: trims, layers, captions, effects, markers, placeholders, crops, transitions, and layout. For raw source-asset frame inspection, choose the cheapest path based on where the bytes live: - The agent in this build has no local filesystem access; all source bytes live in the project media store (`/media/uploads/`). Use `view_asset_frames` with the project asset id — the server takes an ffmpeg contact-sheet fast path automatically, so it is already the cheapest source-frame route. - `view_timeline_frames` renders the composed timeline (the editor-truth check); `view_asset_frames` samples raw source frames. Pick by what you are verifying. - There is no separate `get_contact_sheet` tool in this build — the contact sheet is what `view_asset_frames` / `view_timeline_frames` already return. Use local/remote source-frame artifacts only for source understanding, moment selection, and rough trim decisions, not as edited output or timeline proof. For local-only or upload-in-progress media, composed timeline proof may be blocked until the asset has bytes available to the renderer. Source-frame inspection via `view_asset_frames` still works as long as the asset's bytes are on disk (`/med...