decision: Fork naming after org rename

[rubambiza]

Summary

Decide how the automation's fork should be named after the org rename, then wire the scripts accordingly.

Background

The fork used for the standing dashboard PR was not renamed and still resolves under its old name, so pushes to it currently work. Per-repo forks used by the fixers are derived from <fork-owner>/<repo-name>; with the repo-name remaps (e.g. cortex), the fixers will look for forks that may not exist yet.

Options

• (A) Keep the existing fork name. Lowest effort; the standing dashboard PR keeps working. Codify with an explicit override variable so the upstream/fork name mismatch is intentional and documented, not accidental.
• (B) Rename the fork to match the new org. Cleaner; lets fork derivation stay uniform. Requires a one-time repo rename and re-pointing existing branches.

Recommendation: (B) long-term; ship (A) with the explicit override if (B) is deferred.

Work

• Implement the chosen option.
• Audit that per-repo forks exist (or are auto-created) for the remapped core repos.

Acceptance

• Fork resolution is explicit in the scripts and matches the chosen option.
• Fixers can push to / open PRs against the correct forks for all core repos.

[rubambiza]

Part of epic #32.

[rubambiza]

Decision: Option B — canonical fork names, auto-create

We will pass canonical repo names to the fixer write paths and let ensure_fork create any missing clawgenti/<repo> fork on first run (it already does gh repo fork when the fork is absent). Fork names then follow the canonical scheme uniformly, with no permanent special-case in the code.

Why (current fork inventory):

• clawgenti/cortex, clawgenti/workload-harness — already exist under the new names.
• clawgenti/automation, clawgenti/agent-skills, clawgenti/operator — do not exist yet; ensure_fork will create them on first fixer run.
• clawgenti/kagenti — still the old name (does not redirect to a rossoctl-named fork). Under Option B it becomes an orphan but is harmless; the write path will target the canonical fork instead.

Rejected Option A (explicit MAIN_FORK_REPO override to codify the mismatch): avoids fork churn but leaves a permanent naming special-case; not worth it given ensure_fork already auto-creates.

Scope reminder for the implementation: also fixes the source_repo_name="${repo#"$ORG/"}" prefix-strip (breaks on a rossoctl/ prefix) and the fix_repo_dir clone-dir mapping, and requires a controlled live-run verification before rollout (dry-run alone is insufficient for a write path).