feat(media): make media completeness durable (#106) - #118
Merged
Conversation
Closes #106 Assisted-by: GPT-5 Co-authored-by: Codex <noreply@openai.com>
jerome-queck
force-pushed
the
codex/106-media-completeness
branch
from
August 16, 2026 13:34
986cf7e to
8f223d3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Media completeness needed durable, human-readable state independent of sync and verify, with safe retry and regeneration semantics.
What changed
Validation
npm test— 328 passednpm run lintnpm run format:checknode --checkon changed modulesmainCloses #106
#106 — Make media completeness durable: 11 of 11 criteria delivered, nothing beyond the brief.
Assisted-by: GPT-5
Co-authored-by: Codex noreply@openai.com