[AAASM-2718] 🔧 (agent-assembly): Use canonical lowercase org ID ai-agent-assembly

[Chisanan232]

Description

Mechanical rename of the GitHub org ID from the mixed-case AI-agent-assembly to the canonical lowercase ai-agent-assembly across the agent-assembly monorepo. The repository itself has already moved to the lowercase location (https://github.com/ai-agent-assembly/agent-assembly); this PR aligns every in-repo reference (URLs, module paths, image labels, docs) with the canonical casing. No behaviour change.

Precedent: go-sdk PR #48 (facc3af) applied the same rename for the go-sdk repo.

Touched categories (one commit each):

• 🔧 (ci): .github/workflows/* (ci, dev-verify, docker, integration-tests)
• 🔧 (config): root + aa-ebpf-programs Cargo.toml repository/homepage metadata, Dockerfiles, docker/*, openapi/v1.yaml, sonar-project.properties, release scripts, integration-test fixtures (go.mod/main.go go-sdk module path, pyproject.toml comment), aa-api OpenAPI contact URL
• 📝 (docs): README.md, docs/**, CHANGELOG.md, CONTRIBUTING.md, SECURITY.md, verification reports, quickstart.cast

No active Cargo git = dependency URLs reference the org (the only such URLs are in comments / docs / verification reports), so Cargo.lock is unchanged and no lock regen was required.

Type of Change

• 🔧 Configuration / CI change
• 📝 Documentation update

Breaking Changes

• No

GitHub org names are case-insensitive for routing, so existing AI-agent-assembly URLs continue to redirect. The Go fixture module path is updated consistently across require/replace/import and the -replace= flag, matching the lowercased go-sdk module.

Related Issues

• Related Jira ticket: AAASM-2718 (Epic AAASM-2715)
• Closes AAASM-2718

Testing

• No tests required (string rename, no behaviour change)
• Verified git grep 'AI-agent-assembly' returns 0 matches; 407 lowercase ai-agent-assembly refs remain.
• cargo metadata --format-version 1 resolves cleanly; Cargo.lock unchanged.
• cargo fmt --all --check clean.
• mdbook build (in docs/) succeeds.

Checklist

• Code follows project style guidelines (cargo fmt)
• Self-review of the diff completed
• Documentation updated if behaviour changed
• All CI checks passing
• Commits are small and follow the Gitmoji convention

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[Chisanan232]

Review — Claude Code

CI: ✅ Fixed and green. The only real failure was Compatibility matrix update check (→ CI Success): the rename touched root Cargo.toml [workspace.package] repository/homepage URLs, and .ci/check-compatibility-matrix.sh requires docs/src/compatibility.md to change whenever a version-carrying file changes. Added commit 20bbeb9 📝 — an HTML-comment note in compatibility.md recording that this is URL-casing metadata only, no version change (same mechanism precedent rows AAASM-2526 / 1602 / 2357 use). Compatibility matrix update check now passes; all other completed jobs are green and the heavy jobs (Test / e2e / Integration / eBPF) are re-running with identical content to the previously-green run. No remaining real failures.

Scope vs AAASM-2718 (lowercase org ID across agent-assembly monorepo): ✅ Complete — git grep 'AI-agent-assembly' → 0 (407 lowercase refs). 89 files across CI workflows, manifests, Dockerfiles, OpenAPI/sonar/scripts, docs, and verification reports. No active Cargo git = dependency URL referenced the org (only comments/ADR docs did), so Cargo.lock is unchanged and no dep regen was needed. cargo metadata resolves cleanly; cargo fmt --check clean; mdbook build succeeds.

One deliberate consistency choice worth noting: the Go fixture (probe_go/go.mod + the -replace= flag in e2e_sdk_runtime_lifecycle.rs) was lowercased too. This is safe because that fixture resolves via a local -replace to a checkout — not a published go-sdk tag — so it sidesteps the Go module-path ordering gate that blocks the examples repo (Epic AAASM-2715). Internally consistent and builds clean.

Verdict: ✅ Ready for Pioneer approval + merge once the heavy jobs finish (expected green). The only red was the compat-matrix gate, now resolved.

[Chisanan232]

Review update — Claude Code (second CI fix)

A second real failure surfaced after the heavy jobs ran: Build language image — go failed with:

go install github.com/ai-agent-assembly/go-sdk/...@latest
  go: ...go-sdk@v0.0.1-alpha.3: parsing go.mod:
  module declares its path as: github.com/AI-agent-assembly/go-sdk
          but was required as: github.com/ai-agent-assembly/go-sdk

Root cause: the same Go module-path ordering gate that affects the examples repo — but here it hit docker/Dockerfile.go-1.{24,25,26}-alpine. Those images run go install … @latest / go list -m … @latest, which resolve to the published go-sdk tag (v0.0.1-alpha.3), whose go.mod still declares module github.com/AI-agent-assembly/go-sdk. The initial rename lowercased these module-path strings; Go's case-sensitive path check then rejected the published tag. (The -replace-based test fixture was fine — it resolves to local master, which carries the lowercase rename.)

Fix (commit 444e917): reverted just the 6 Go module-path references (2 per Dockerfile) back to mixed-case AI-agent-assembly, with an inline NOTE explaining why. Web-URL references (LABEL org.opencontainers.image.source) stay lowercase — GitHub resolves org names case-insensitively, so those are unaffected.

Consequence for scope: git grep 'AI-agent-assembly' in this repo is now intentionally non-zero — exactly these 6 Dockerfile lines remain mixed-case as a documented exception, gated on go-sdk publishing a lowercase-module-path release tag (same owner action as AAASM-2729 / Epic AAASM-2715). Once that tag exists, the follow-up lowercases these 6 lines and bumps @latest→ the new tag in one commit.

Status: the go-image build re-runs against the published mixed-case tag and resolves. No remaining real failures; the only other reds anywhere in this batch are the GHA org billing block (owner action).