docs: retire removed repository from governance records

[seonghobae]

Outcome

Retire the removed vooster-v2-mvp repository from two durable internal governance/context records while preserving the already-merged curated organization profile.

Reconciliation

This branch originally re-expanded profile/README.md into a long repository/fork catalog. That public-profile delta duplicates and conflicts with merged #1676, whose product-first profile explicitly defines itself as a curated entry point rather than an exhaustive catalog. The profile has therefore been restored byte-for-byte to current protected main on exact branch commit 7fdf2445dd05a3800f8db028a296dc5a25193ebf.

The surviving unique changes are internal truth repairs only:

• docs/CWL-MASTER-CONTEXT.md removes vooster-v2-mvp from the active fork list and records that it no longer exists in the organization;
• PR_GOVERNANCE_AUDIT.md removes the same deleted repository from the public-fork governance inventory.

These two changes subsume the useful scope of competing #1679. #1679 can be closed without merge because this branch preserves both unique stale-reference corrections while avoiding the public-profile regression.

Scope

No public profile expansion, product/runtime source, repository metadata/settings, license, dependency, workflow, security control, release, or governance rule is changed. The effective protected-main-relative scope is the two internal stale-reference corrections above.

Integration boundary

Only exact-head checks/reviews after 7fdf2445dd05a3800f8db028a296dc5a25193ebf are admissible. Merge through ordinary protected governance after fresh checks, review/thread requirements, base ancestry and mergeability are satisfied. No predecessor evidence, self-approval, force-push or routine administrator bypass is requested.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: a157e234-e05b-4afc-809c-4f9236e4a6f8

---

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.}

[devin-ai-integration]

Devin Review found 3 potential issues.

[seonghobae]

Merged main@f2f91b80 into this head as 9d3bd60e (parents e1205d12 + f2f91b80), no conflicts and no change to this PR's own content — so its next noema-review/strix runs are created after .github#1939 and execute the round-robin sidecar instead of the NVIDIA-only one behind the earlier 502 / provider-unavailable failures (a re-run would have kept the old workflow_sha). Verified before pushing: the merged tree is byte-identical to one an independent gate run passed (2896 passed / 1 skipped, coverage 100%, interrogate 100%) and contains no conflict markers. opencode-review and the CodeQL shards remain gated by .github#1929 and will not turn green from this.

[seonghobae]

Outcome of the re-based head's first noema-review run (33993637015, created 21:38Z on the post-#1939 round-robin sidecar; no trace artifact because it predates #1943/#1944/#1945): failed — Noema gateway transport failed: HTTPError: HTTP Error 502: Bad Gateway; caller attempts=1, duration=542.2s, phase=response_error, served_model=deepseek-ai/deeps. duration 542.2 s, preflight ready 1/12, slow-hop estimate 0.99 (routes that waited out the full timeout). Same structural class as before the re-base, now on the wider pool; nothing in this PR's diff is implicated and no push is made. The next push to this branch would produce a run with the per-route trace artifact.