chore!: rename to caia-cli — repo, distribution, and import package (3.0.0)

[Ali Bahaloo (alibahaloo)]

The command has always been caia. The repo, the uv/pip distribution name, and the import package still carried the long form. This aligns all three.

	Before	After
Repo	xavient/cisco-advisory-impact-agent	xavient/caia-cli (already renamed)
Distribution	cisco-advisory-impact-agent	caia-cli
Import package	cisco_advisory_impact_agent/	caia/
Command	caia	caia — unchanged
Product name	Cisco Advisory Impact Agent	unchanged

caia-cli names the artifact; "Cisco Advisory Impact Agent" remains the product name and is what the splash banner prints under the CAIA wordmark. Everything already user-facing — the command, CAIA_* environment variables, and the per-user config directory — was caia before this change and is untouched.

Breaking change

Existing installs cannot reach 3.0.0 through caia --update. GitHub redirects the old repo URL, so the git fetch succeeds, but uv then fails on a distribution name mismatch (caia-cli != cisco-advisory-impact-agent). The failure is loud and non-destructive: the current install keeps working. Users migrate with

uv tool uninstall cisco-advisory-impact-agent
uv tool install caia-cli --from git+https://github.com/xavient/caia-cli

Uninstall-first rather than --force, because two uv tools both providing a caia executable is the one messy state here, and because it sidesteps the Windows self-uninstall file lock. Saved credentials survive — the per-user config directory was already named caia and neither step touches it, so no re-running --config.

VERSION goes to 3.0.0: the documented install path breaks for existing installs, which is MAJOR under the repo's own semver rule.

Changes

• pyproject.toml — dist name, script target, packages, Homepage, Repository
• cisco_advisory_impact_agent/ -> caia/ — git mv, so all 13 modules record as renames and git blame survives
• caia/version.py — DIST_NAME, DEFAULT_REPO, UA, the three constants driving --version/--update/--uninstall
• tests/ — imports across 10 files, plus the two dist-name string assertions in test_version.py
• README.md and docs/index.html — install commands, all repo links, the releases-API fetch behind the version pill, and a migration note in both (the constitution's Documentation gate requires the two to mirror each other)
• tools/install-test.sh — REPO_URL, RELEASES_API, install command
• .specify/memory/constitution.md — 2.2.0 -> 2.2.1 (PATCH) for the install command in the Distribution constraint, with a Sync Impact Report entry. No principle or gate changes in substance.

Needed no changes: both workflows, CONTRIBUTING.md, .env.example, .gitignore, tools/release.py — all use <repo> placeholders, globs, or were already caia-based.

specs/ and brds/ are left as written. They are frozen spec-kit records that already carry an even earlier name (cisco-advisory-impact-analyzer) which was never retro-edited; rewriting them would falsify the record.

Verification

• 244 tests pass (python -m unittest discover -s tests)
• Clean-venv pip install . -> metadata resolves as caia-cli == 3.0.0, the caia entry point lands on PATH, and the documented python -m caia.cli fallback works
• Landing page renders — the migration callout reuses the existing .callout styling
• Pre-release window is safe: --version swallows the failed latest-check and just prints the version; --update reports "Could not determine the latest version" and exits 3 rather than crashing, until the 3.0.0 Release is published

After merge

Tag 3.0.0 (python tools/release.py) so the version check resolves, confirm GitHub Pages now serves at xavient.github.io/caia-cli, then send existing users the migration command above.

🤖 Generated with Claude Code