feat(coss)!: retire standalone public-site surface

[jason931225]

Summary

• finalize the already-landed removal of the shipped coss-rn standalone public-site surface
• remove the orphaned npm workspace and canonically prune its unreachable lock graph
• record accepted ADR-0026 as the newest decision and reconcile older COSS references without changing MaintenanceField parity authority
• add fail-closed workspace topology, symlink, stale-lock, mutation, and canonical-lock CI gates

Release boundary

This is intentionally a breaking pre-1.0 minor change. The commit carries:

• feat(coss)!
• BREAKING CHANGE: for removal without an in-repository replacement
• Release-As: 0.2.0

The existing release PR #484 must update from the incorrect 0.1.66 patch to exactly 0.2.0 before it may merge.

Verification

• canonical lockfile check under Node 24.16.0 / npm 11.13.0
• package-lock.json: 1,417 -> 797 entries; 620 removals, zero additions, zero COSS/React Native/Metro entries
• npm ci --dry-run --ignore-scripts --no-audit --no-fund
• root workspace gate and 5 mutation tests, including symlink and stale lock package/link failures
• ADR gate plus 29 ADR tests; ADR-0026 is newest and reciprocal amendment graph is valid
• foundation gate: 100 checks
• web/Android/iOS i18n and mobile parity gate
• actionlint and git diff --check

Review

Independent code review: APPROVE. Independent verifier: PASS; live CI remains the final merge gate.

[coderabbitai]

Warning

Review limit reached

@jason931225, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 7552a838-c6b3-45b2-ac45-3b2758051a2e

📥 Commits

Reviewing files that changed from the base of the PR and between 5fd4993 and 68ec6c2.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (12)

• .github/workflows/ci.yml
• .omc/plans/oyatie-console-plan.md
• .omc/research/oyatie/frontend-map.md
• docs/CI-GATES.md
• docs/decisions/ADR-0023-oyatie-console-authority.md
• docs/decisions/ADR-0026-retire-coss-rn-public-site-surface.md
• docs/decisions/README.md
• docs/parity-checklist.md
• package.json
• scripts/check-i18n.mjs
• scripts/check-root-workspaces.mjs
• scripts/check-root-workspaces.test.mjs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/coss-retirement-release-boundary

---

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

[jason931225]

The standalone iOS Simulator workflow was cancelled on this COSS-only release-boundary PR to release scarce macOS capacity for the dedicated iOS remediation PR #486. The base workflow is the known pre-existing #434 failure and this PR does not modify .github/workflows/ios-ui-tests.yml or ios/**; merge remains gated on this PR’s affected CI, Security, Android, web, contract, and governance checks. PR #486 must provide the replacement live Simulator evidence before the 0.2.0 release PR merges.