Skip to content

fix: publish corrected startup coverage in the media demo - #77

Merged
TheCryptoDonkey merged 1 commit into
mainfrom
fix/startup-coverage-sdk-20261027
Oct 27, 2026
Merged

TheCryptoDonkey merged 1 commit into
mainfrom
fix/startup-coverage-sdk-20261027

Conversation

@TheCryptoDonkey

@TheCryptoDonkey TheCryptoDonkey commented Oct 27, 2026 •

Copy link
Copy Markdown
Member

When a room clock advances beyond the held first fragment, the startup reservoir can discard a useful verified prefix before using its existing fourth slot. Pin the media demo to public RelaySwarm source 59575d9c30b44fdf010ce382612224519cbd7ffc, which preserves that prefix and evaluates current verified coverage before release.

Rebuild the SDK bundle, notices and provenance, and update dependent cache queries. The controller, adapter and listener have no functional changes; WASM and dependency versions are unchanged. The four-object/24 MiB startup bound, steady three-object bound and eight-second/parent deadlines remain in place. This pin records controlled startup correctness, without claiming improved cold startup, decoded playback or traffic savings.

Validation: all 371 site unit tests passed on Node 24.21; bundle build, site build, catalogue drift and git diff --check passed. Cache-query normalization confirms unchanged host module logic, and the WASM remains byte-identical (7767f54c…).

RelaySwarm PR #43 is merged after 15 successful hosted checks and two optional skips. The pinned source is the exact reviewed head of that change; this site PR has also passed its hosted build and tests.

@TheCryptoDonkey
TheCryptoDonkey merged commit fd56417 into main Oct 27, 2026
2 checks passed
@TheCryptoDonkey
TheCryptoDonkey deleted the fix/startup-coverage-sdk-20261027 branch October 27, 2026 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant