Repo cleanup: retire the served C0 probe and stale upstream-finding content - #132
Merged
Conversation
…m (component-model#690) - upstream-issue-stale-async-drop.md predated the tracker (scaffold commit), was referenced nowhere, and duplicated CM-1 — its unique filing notes (#578/#646 removal history, the leave-cancel-read/write-alone caveat) now live in the CM-1 entry. - CM-2 (dead canon_backpressure_set in definitions.py) was fixed upstream independently by 1c42aeb02 (WebAssembly/component-model#690); status flipped to RESOLVED so #15 doesn't drive a dead filing. Runtime annotations describing the pinned submodule stay until the pin bumps. - CM-1/CM-3/CM-5 re-verified still present at upstream main (2026-08-14).
…ered The probe (2026-08-08) settled whether Deno substitutes for Node on WebRTC — both node-datachannel/polyfill and pure-TS werift loopbacks green — and the verdicts are recorded in docs/consumers.md's capability table and the milestones C0 row. No gate runs it; the living WebRTC coverage is `just test-webrtc` (ports/webrtc suite, node-datachannel under Deno). Same pattern as the exams/iroh-endpoint retirement: history via `git log -- tools/probes/webrtc-deno`. Provenance comments in ports/webrtc and the consumers.md evidence section now point at history; milestones.md and smoke-c0/REPORT.md stay as point-in-time records. Note the werift fallback leg keeps no in-tree executable twin — its verdict stands as dated evidence only.
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
2 participants
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.
Cleanup pass over outdated / low-value content. Three separable items, one commit per concern:
1. Findings tracker: orphan CM-1 draft folded in
upstream-issue-stale-async-drop.mddated from the scaffold commit, was referenced nowhere, and duplicated the tracker's CM-1 entry (the declared single source of truth). Its unique filing notes (#578/#646 removal history; the leave-{stream,future}.cancel-*caveat) moved into CM-1; the file is deleted.2. Findings tracker: CM-2 is RESOLVED upstream — no filing needed
Upstream removed
canon_backpressure_setthemselves: WebAssembly/component-model#690 (1c42aeb02), verified absent atmain2026-08-14. Status flipped so #15 doesn't drive a dead filing; the now-moot draft-PR text is trimmed (git history keeps it). Runtime annotations describing the pinned submodule (73b7ad5, where the dead code still exists) stay until the next pin bump, per the tracker's own checklist.While re-verifying: CM-1, CM-3, CM-5 are all still present at upstream
main(2026-08-14) — those drafts remain live.3. Retire
tools/probes/webrtc-deno/The C0 capability probe answered its question 2026-08-08 (Deno substitutes for Node on WebRTC: node-datachannel + werift loopbacks both green); the verdicts are recorded in docs/consumers.md and the milestones C0 row, and no gate runs it. Living coverage is
just test-webrtc. Same retire-with-history-pointer pattern as exams/iroh-endpoint (−685 lines, mostly its lockfile). Provenance comments inports/webrtcand the consumers.md evidence section now point at history; milestones.md and smoke-c0/REPORT.md stay untouched as point-in-time records. Caveat noted in the commit: the werift fallback leg keeps no in-tree executable twin — dated evidence only.Deliberately kept
upstream-issue-sync-streams-schedule-overfit.md+.patch) — filing still pending (File the upstream findings (IROH-1; component-model tracker) #15 open; CM-4: sync-streams.wast:145 overfits wasmtime's scheduler — upstream test-defect filing kit #43 closed with the kit READY).tools/smoke-c0/REPORT.md+repro_stream_pump.ts— C0 exit artifacts, task-wired.Gates
just test-webrtc— 10/10 pass (only code touched is comment-only in ports/webrtc; markdown otherwise).Sidenote for the operator: issue #15's body still lists IROH-1 as needing a consumer filing, but the tracker marks it RESOLVED-BY-HOST (no filing needed) — the issue body may be worth a trim when convenient.