Extend BF16 video clips to 625 exact frames (26 seconds)

[halfaipg]

Scope

Updated from current main for the owner-requested ~26-second Studio target: BF16 accepts up to 625 frames at 24 fps (26.041667 seconds). The maximum quote is 520834 micro-USD at the unchanged $0.020/second tariff. NVFP4 remains 337 frames, standard Dev 81, Ingredients 121. Defaults, dimensions, concurrency, admission and byte/resource ceilings are unchanged.

Verification

Final committed tree: 2356 local Core tests passed / 693 explicit PostgreSQL, platform and prerequisite skips. Exact-frame normalization, quote/one-hold/replay/ceiling, late keyframe and source-unit tests pass. Full reachable-history Gitleaks: 1722 commits, no leaks. Matching Gallery PR48 has 250 frontend tests, TypeScript, full Go race suite and 13 production-build browser tests, including desktop/mobile 625-frame selection. Core independently produced the new Go golden intent commitment.

Release gates

DRAFT, NOT DEPLOYED. Current serving exporter still caps 337; source-mode media-worker bindings also cap 337. Upgrade and qualify the exporter before any longer clips, and the source adapter before longer A2V/V2V. Fresh owned-rig Tailscale SSH authentication is required for native BF16 capacity proof. Do not claim that CPU codec/browser fixtures qualify GPU memory or source modes. Exact-head Linux/Postgres/security CI, native execution and immutable drained deployment remain required. Preserve long-intent readers on rollback. No paid job, production restart or flag change occurred.

[halfaipg]

Release progress for merged 777c81f: exact main tree equals reviewed PR tree. Native BF16 text and opening-image controls both completed 625 frames at 960x544 and passed independent full decode plus exact video/audio clocks. CPU exporter exact/short-tail controls passed. Qualified manifest-bound exporter is now selected on both owned BF16 instances, with unrelated service identities preserved. Immutable Core staging and a fresh production backup/scratch restore pass at Alembic 0046; live Core is still unchanged pending exact-main integration checks. Source admission remains off: the separate uploaded-source worker adapter is still 337 frames, so this rollout does not enable longer A2V/V2V. NVFP4 remains 337 frames. After a 625-frame intent is accepted, rollback must retain compatible 625-frame receipt readers; do not revert to an old 337-only parser.

[halfaipg]

DEPLOYED: exact protected-main 777c81f selected after all main gates, a fresh production backup/scratch restore at Alembic 0046, public maintenance verification and a quiet drain. Environment, schema, source closure, per-account concurrency, payout/backup timers and nine-worker capacity were preserved. Both owned BF16 runtimes use the manifest-bound native exporter qualified with 625-frame text/opening-image controls. The actual Gallery 625-frame 704x704 clip passed one dispatch, one native prompt, one ledger completion and one 520834-micro settlement; independent output-hash/full-decode/exact-clock review and unchanged reload recovery pass. Exactly one approved paid clip, no replacement or automatic retry. NVFP4 stays337, uploaded-source modes stay closed. Preserve625-aware readers after long receipts exist; close admission rather than selecting an older337-only parser.