[WRONG BRANCH] fix(grok): preserve orphan model tables that have no replacement

[luvs01]

Motivation

• The orphan sweep removed OpenCodex-owned [model.<alias>] tables unconditionally which could delete the only table named by [models] default or fork_secondary_model, leaving dangling references when no replacement is emitted.
• The adoption logic must only remove orphans that map to a model id that will actually be re-emitted by the managed block, and must preserve retired/unknown/excluded model tables.

Description

• Restrict orphan removal to only those orphan tables whose model id appears in the set of model ids that will be emitted (honouring opts.excluded).
• Update src/grok/inject.ts to compute emittedModelIds and filter findOpencodexOrphans accordingly before calling removeOrphanTables.
• Strengthen tests in tests/grok-orphan-adoption.test.ts to assert that an orphan whose model is no longer in the catalog is preserved and to add a test that an orphan remains when its catalog model is explicitly excluded.
• Files changed: src/grok/inject.ts, tests/grok-orphan-adoption.test.ts.

Testing

• Ran the focused Grok regression suite with bun test tests/grok-orphan-adoption.test.ts, which passed all 19 tests in that file.
• Ran bun run typecheck, which completed successfully.
• Ran bun run privacy:scan, which completed successfully.
• Ran the broader bun run test during validation but that run encountered unrelated failures/timeouts in other subsystems; the targeted Grok tests listed above passed independently.

---

Codex Task

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 57 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 71ea25a8-b38d-47c5-b0bd-cbf797ee2922

📥 Commits

Reviewing files that changed from the base of the PR and between 121f1ad and 3adf80a.

📒 Files selected for processing (2)

• src/grok/inject.ts
• tests/grok-orphan-adoption.test.ts

---

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

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.