Docs: update org profile README for the Rossoctl rename

[Ibrahim2595]

Summary

Updates the org profile (profile/README.md, shown at github.com/rossoctl) for the Kagenti → Rossoctl rename.

• Rebrand Kagenti → Rossoctl (title, prose, links, rossoctl.io, Slack)
• Repositories → add a Core section listing the four core repos: rossoctl, operator, cortex, examples
• Remove archived repos from the list (verified archived: true via API): ecosystem-guide, adk, adk-starter, agentic-control-plane, plugins-adapter
• Repoint remaining links to github.com/rossoctl/*

Scope

Only profile/README.md (the org landing page). The repo's root README.md ("Kagenti Marketing Site") is website content owned by the separate website workstream — intentionally left untouched.

Note

Two links depend on external services being set up: rossoctl.io (org owns the domain ✅) and the Slack redirect ibm.biz/rossoctl-slack (needs to exist, or point it at the real invite).

[mrsabath]

Approving — a clean rebrand of the org profile page. All 7 linked repos exist (rossoctl, operator, cortex, examples, capture-the-flag, workload-harness, .github), the Core section is accurate, the archived-repo removals check out, and scoping out the website root README is the right call. Docs: title, signed-off.

Confirm before merge (suggestion)

• The page publicly links “Learn more at rossoctl.dev”. Please confirm that domain actually resolves before this lands on the org landing page — I couldn't verify it. Worth double-checking against the domain the project actually owns: the rename domain plan (kagenti#2008) tracks rosso.dev (two s), so if rossoctl.dev isn't registered this would be a dead “Learn more” link and the intended domain may be rosso.dev. Your PR body already lists the domain as an external-setup dependency — just make sure it's live at merge.

Nits

• The Slack link text says “Rossoctl Slack” but the URL is still https://ibm.biz/kagenti-slack. Fine as an interim (the redirect works), but it's a visible text/target mismatch on a public page — worth creating ibm.biz/rossoctl-slack and repointing when convenient.
• The PR body is slightly stale vs. the diff (body mentions rossoctl.io + rossoctl-slack; the README actually uses rossoctl.dev + kagenti-slack). The commit message matches the diff — purely cosmetic, flagging so the description doesn't mislead a later reader.

Areas reviewed: docs (org profile README), link/repo correctness, external-dependency flags, commit conventions.
CI status: DCO passing (only check).