fix: Restore search-based automation broken by org rename

[rubambiza]

Summary

After the org rename (kagenti → rossoctl), three code paths that rely on GitHub search (which does not follow org renames) silently break, while git/gh api calls keep working via redirect. This issue covers restoring the broken behavior. Scoped to a functional fix only — no cleanup (per Scope Discipline in CLAUDE.md).

Bugs to fix

1. scripts/pr-review-impact.sh — get_repos(): emits kagenti/* repo names. The reviewed-by search (q=repo:kagenti/... reviewed-by:clawgenti type:pr) returns HTTP 422 on the renamed repos, so the script writes reviewed: 0 and the impact metrics freeze. Fix: emit rossoctl/* with name remaps (kagenti→rossoctl, kagenti-extensions→cortex; automation, agent-skills unchanged).

2. scripts/extract-broken-links.sh (~line 87): link classification uses test("github\\.com/kagenti"). Links now under github.com/rossoctl get classified external, so genuinely-internal broken links stop getting fix-PRs. Fix: match both orgs — test("github\\.com/(kagenti|rossoctl)") — so surviving (still-redirecting) old links stay internal. Drop the kagenti alternative only after a docs sweep confirms none remain.

3. scripts/link-health-scanner.sh (~line 343): gh search issues "org:kagenti in:title ..." returns empty post-rename, zeroing the dashboard's per-repo issue counts. Fix: org:kagenti → org:rossoctl.

Acceptance

• Dry-run each of the three scripts; pr-review-impact reports nonzero reviewed when reviews exist, a rossoctl link classifies as internal, and the issue search returns results.
• tests/test-pr-review-impact.sh and tests/test-extract-broken-links.sh pass; fixtures updated for the new org prefix / regex.

[rubambiza]

Part of epic #32.