📖 Rename Kagenti → Rossoctl across agent-examples

[Ibrahim2595]

Content sweep renaming the project Kagenti → Rossoctl in this repo (agent-examples → examples). All 253 case-insensitive kagenti references updated; grep is clean.

Changes:

• Brand / prose / comments: Kagenti → Rossoctl
• Go module: github.com/kagenti/mcp-mitm → github.com/rossoctl/mcp-mitm
• Images: ghcr.io/kagenti/agent-examples/* → ghcr.io/rossoctl/examples/*
• Cross-repo links: kagenti/kagenti → rossoctl/rossoctl, kagenti-extensions → rossoctl/rossocortex, agent-examples → examples, workload-harness → rossoctl/workload-harness
• CODEOWNERS: @kagenti/* → @rossoctl/*
• CI reusable-workflow refs: kagenti/.github → rossoctl/.github
• Env vars: KAGENTI_* → ROSSOCTL_*
• Sample runtime-contract values (this repo ships samples, not live contracts): labels kagenti.io/* → rossoctl.io/*, namespace kagenti-system → rossoctl-system, SPIFFE kagenti.{local,example.com} → rossoctl.{local,example.com}, Keycloak realm/client kagenti → rossoctl

Verification: ruff check + format clean, go build/vet clean, pytest 80 passed. Docker image builds unaffected (image names derive from ${{ github.repository }}).

Related to #1972

Assisted-By: Claude Opus 4.8 noreply@anthropic.com

Summary

Related issue(s)

(Optional) Testing Instructions

Fixes #

[esnible]

Converted to "DRAFT" because it is important that this not merge until we have support in other repos.

For example, a2a/a2a_currency_converter/deployment/k8s.yaml refers to K8s labels that are not yet understood by the Rossoctl-operator.

@cwiklik I could not find an issue for label renaming. Is there one? Is the plan to have a period where both the old and new labels are supported?

[mrsabath]

Summary

Approving — this is the cleanest of the four #1972 rename PRs. The content rename is faithful: no residual kagenti references added, ghcr.io/rossoctl/examples/* applied consistently, and images derive from ${{ github.repository }} so builds are unaffected by the repo rename. pytest/ruff/go build all green.

Notably, this PR does not carry the go.sum lockfile defect flagged in kagenti-extensions#678 and kagenti-operator#485: the only Go change here is the self-module rename (module github.com/kagenti/mcp-mitm → github.com/rossoctl/mcp-mitm in mcp/github_tool/go.mod), which has no checksum implications, and there's no consumed kagenti/* dependency to break. No go.sum was touched, correctly.

Non-blocking

• Trivy code-scanning reports "2 new high alerts" — pre-existing CVEs, re-flagged, not introduced here. The two are jwt-go CVE-2020-26160 and jsonparser CVE-2026-32285 on mcp/github_tool/go.mod, but that file's diff is only the module line rename — no dependency was added or changed. GitHub's code-scanning diff view treats the touched file's findings as "new". The actual filesystem scan job (trivy-scan) passes. Same mass-rename artifact as CodeQL on rossoctl/rossoctl#2230.
• Follow-up (out of scope for a rename): Trivy also surfaces a broader set of real, pre-existing highs across the uv.lock files — the MCP Python SDK (mcp 1.12/1.26/1.27 → fixed in 1.27.2 / 1.28.1: CVE-2026-52869, -52870, -59950) and the two Go deps above. Worth a dedicated dependency-bump PR, but not something this rename should take on.

Nit

• Title uses a 📖 emoji prefix; the org title Ruleset expects an allowed word prefix (e.g. Docs: or Refactor:). Length (49) is fine. Consider Docs: Rename Kagenti → Rossoctl across agent-examples.

Areas reviewed: Go module, Python/uv.lock deps, images, K8s samples, security scanners (both Trivy jobs traced), commit conventions.
Commits: 1, signed-off ✅ (DCO green).
CI status: Trivy code-scanning failing (pre-existing CVEs re-flagged); trivy-scan, CodeQL, lint, test, test-startup, hadolint, dependency-review all passing.