docs(planning): T1.6 scoping correction — @blockcast/mmt-transport second package

[kkroo]

Corrects the T1.6 scoping doc, which found only the ssm-transport collision and missed a second existing transport package: @blockcast/mmt-transport (libmmt/packages/transport) — a high-level mode manager (WT↔multicast↔AMT promotion, ABR, FEC).

Key point: mmt-transport/src/transport-manager.ts has no new WebTransport/serverCertificateHashes/.ready — it orchestrates modes, doesn't own the connect dance. So a new @blockcast/moq-transport is still correct (the factory is a missing primitive, not a dup), with a clean 3-layer story (moq-transport ← mmt-transport ← ssm-transport).

Mirrors the recommendation posted on BLO-8646. Follow-up to the scoping docs merged in #8.

🤖 Generated with Claude Code

[blockcast-ci-packages]

Ally — Consolidated PR Review

Lenses: pr-review-toolkit (code, tests, comments, errors, types) + gstack/review + gstack/codex.

Looks good. Docs-only planning correction (single file, +31/-0, no code). The code/test/error/type and SQL/trust-boundary/side-effect lenses have no surface to act on here; the substantive review is factual accuracy of the added "CORRECTION (2026-06-01)" section, which I verified independently against the live repos:

• @blockcast/mmt-transport is the real package name of libmmt/packages/transport — confirmed (package.json#name).
• libmmt/packages/transport/src/transport-manager.ts contains none of new WebTransport / serverCertificateHashes / .ready — confirmed (grep over the file returns zero matches). The PR's load-bearing argument ("new factory is a missing primitive, not a dup of mmt-transport") holds.
• mmt-transport's index.ts header still self-labels @blockcast/transport — confirmed.
• Table row 1 (@blockcast/transport → packages/ssm-transport) — confirmed; that package lives in pim-multicast-gateway (code search).

Critical Issues (0)

None.

Important Issues (0)

None.

Suggestions (1)

• [comments] .planning/m4-scoping/T1.6-transport-factory.md (added comparison table) — The two dirs cited (libmmt/packages/transport, packages/ssm-transport) live in different repos (Blockcast/libmmt and Blockcast/pim-multicast-gateway), not in moq-rs where this planning doc resides. The "(VERIFIED against HEAD)" note doesn't say which repo's HEAD. A one-word repo qualifier per row would let a future reader landing in moq-rs find the sources without guessing.

Strengths

• The 3-layer framing (moq-transport ← mmt-transport ← ssm-transport) is clear and correctly distinguishes a low-level connect primitive from a mode manager — the distinction is borne out by the actual transport-manager.ts contents.
• Correctly scopes the @blockcast/transport→ssm-transport rename as a separate, out-of-T1.6 ticket rather than smuggling a migration into this pass.

Recommended Action

1. No blockers — safe to merge.
2. Consider the repo-qualifier suggestion opportunistically.

Codex adversarial lens: skipped for this docs-only diff (no code surface; running it on a 31-line markdown add is low-value). Factual claims were instead verified directly against the referenced repos, above.

[blockcast-ci-packages]

Addressed, thanks. I pushed a follow-up commit adding explicit repo qualifiers to the correction table and clarifying verification scope as "each repo HEAD":\n\n- Added column with and \n- Updated wording from "VERIFIED against HEAD" to "VERIFIED against each repo HEAD"\n\nCommit: 270cf21

[blockcast-ci-packages]

Addressed, thanks. I pushed a follow-up commit adding explicit repo qualifiers to the correction table and clarifying verification scope as "each repo HEAD".

• Added a Repo column with Blockcast/pim-multicast-gateway and Blockcast/libmmt
• Updated wording from "VERIFIED against HEAD" to "VERIFIED against each repo HEAD"

Commit: 270cf21