chore: Retire kagenti->rossoctl clone remap

[rubambiza]

Summary

Retires the transitional kagenti->rossoctl clone-dir remap now that the
stale-named clones have been removed from the scanner host.

Background

The link-health scanner iterates local clones by globbing $REPOS_DIR/*/,
which expands alphabetically. A stale kagenti clone (a copy of
rossoctl/rossoctl, weeks out of date) sorted ahead of the fresh rossoctl
clone. Both canonicalize to rossoctl via PROFILE_REMAP, and the
order-dependent dedup kept the first one it saw — the stale copy. The scanner
therefore read outdated files and re-filed broken-link issues that had already
been fixed on main.

The stale duplicate clones have since been removed from the host, so each core
repo now has a single, canonically named clone.

Change

• Empty PROFILE_REMAP in config/org.env (data-only). With no mis-named
  clone dirs remaining, canonical_repo_for_dir() falls through to identity.
• Refresh the org.sh comments to describe the generic, data-driven mechanism
  rather than asserting an active kagenti bridge.

canonical_repo_for_dir() and its data-driven design are intentionally kept so
a future org whose clone dirs are mis-named can re-enable the remap via
PROFILE_REMAP. No control-flow change; the allowlist filter and duplicate
dedup are untouched.

Testing

• tests/test-core-repos.sh, tests/test-org-profile.sh,
  tests/test-lib-modules.sh, tests/test-lib-inventory.sh — pass.
• Loading the shipped config/org.env confirms REMAP is empty and
  canonical_repo_for_dir returns identity for kagenti, rossoctl, cortex.

Fixes #37

Assisted-By: Claude Code

[clawgenti]

Straightforward doc-and-data retirement — empties PROFILE_REMAP and refreshes comments to describe the generic mechanism without the now-gone kagenti bridge. All checks pass. Ready for human review.

---

Reviewed by clawgenti using the github-pr-review skill