chore: replace the stale csaf packaging keyword with psirt

[Ali Bahaloo (alibahaloo)]

One-line metadata fix. pyproject.toml still advertised csaf as a keyword, but the tool no longer fetches or parses CSAF — that capability went with caia/cisco.py in 4.0.0.

-keywords = ["cisco", "security", "advisory", "firewall", "csaf", "vulnerability"]
+keywords = ["cisco", "security", "advisory", "firewall", "psirt", "vulnerability"]

psirt is what the tool actually queries, and what someone looking for a tool like this would search for.

How it was missed

The residue sweep for spec 007 (FR-032) grepped for the AI provider's name, agentic, ai-driven, ai-assisted, and the old product name. It never looked for csaf — the data format the retired mode consumed, rather than the mode itself. Worth noting as a gap in how that check was framed: removing a capability leaves traces under the names of the things it touched, not only under its own name.

Confirmed this is the only live occurrence:

$ grep -rniE '\bcsaf\b' --exclude-dir={.git,.venv,specs,brds,build} .
pyproject.toml:12:  keywords = [... "csaf" ...]
.specify/memory/constitution.md:32,35:  (Sync Impact Report — amendment history)

The two constitution hits are inside the v3.0.0 Sync Impact Report, which has to name what it removed. Those stay.

Verification

• 246 tests pass
• pyproject.toml still parses and metadata resolves: caia-cli, description and keywords as expected

Not included

VERSION stays at 4.0.0. Packaging keywords don't warrant a release of their own, so this rides along with whatever ships next — the constitution's release gate only requires that the tag match VERSION when a tag is pushed, and none is.

Separately, the GitHub repo topics carry the same stale csaf term (cisco, csaf, firewall, python, vulnerability-management-cybersecurity). That's a repository setting rather than code, so it isn't in this PR — worth swapping csaf for psirt there too, alongside the repo description update.

🤖 Generated with Claude Code