Use Catalog.Consumer in native JS smoke client

[kixelated]

What

Updates the native JS smoke subscriber (clients/js-native/subscribe.ts) to resolve the .hang catalog via Catalog.Consumer instead of the removed Catalog.fetch helper.

const catalog = new Catalog.Consumer(bc.subscribe("catalog.json", Catalog.PRIORITY.catalog));
let videoTrack: string | undefined;
while (!videoTrack) {
    const root = await catalog.next();
    if (!root) throw new Error("catalog ended without a video track");
    const renditions = root.video?.renditions;
    if (renditions) videoTrack = Object.keys(renditions)[0];
}

Why

The scheduled Smoke run went red on every channel with Catalog.fetch is not a function. The harness pins @moq/hang to latest, which floated to 0.2.10 — that release made @moq/hang/catalog schema-only and dropped the fetch/decode/encode helpers. The native subscriber was the sole consumer of Catalog.fetch, so it was the only client that broke (the others use native bindings with their own catalog APIs). This is exactly the upstream-API drift the freshness test exists to catch.

@moq/hang 0.2.11 (moq#1767) re-adds Catalog.Consumer, a thin wrapper over @moq/json's snapshot+delta Consumer pre-wired with RootSchema. Switching to it also picks up catalog deltas, which a one-shot frame read would miss.

No new dependency is needed: 0.2.11 declares @moq/json as a dependency, so it's pulled transitively.

Verification

Ran the real smoke harness locally against the published @moq/hang@0.2.11 (no patching/shims) with a moq-relay + rust ffmpeg publisher:

rust -> js-native-node   PASS
rust -> js-native-bun    PASS
rust -> rust             PASS
smoke: all checks passed

Notes for reviewers

• Requires @moq/hang >= 0.2.11 on npm (now live). The next scheduled smoke run will pick it up.
• The first commit in this branch was an interim manual frame-parse fix that worked against 0.2.10; the second commit replaces it with the supported Catalog.Consumer API now that 0.2.11 is out.

🤖 Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 72ca3b15-e4e8-45cb-9034-f1a58c1abb2c

📥 Commits

Reviewing files that changed from the base of the PR and between 6fecbeb and 88faa42.

📒 Files selected for processing (1)

• clients/js-native/subscribe.ts

---

Walkthrough

In clients/js-native/subscribe.ts, the catalog discovery logic is refactored. The previous approach called Catalog.fetch(...) in a loop; the new approach creates a Catalog.Consumer from a bc.subscribe("catalog.json", ...) subscription and advances it with catalog.next() on each iteration until a root containing a video rendition track is found. Surrounding comments were updated to match the consumer-driven approach.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The PR title clearly and specifically describes the main change: using Catalog.Consumer API in the native JS smoke client to replace the deprecated Catalog.fetch.
Description check	✅ Passed	The PR description is comprehensive and directly related to the changeset, explaining the what, why, verification, and notes for the Catalog.Consumer API migration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch claude/epic-grothendieck-ffc90d

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}