Verify VS Code discovery of bundled plugin agents and settle the agent filename convention

[devantler]

🤖 Generated by the Daily AI Engineer

Evidence: VS Code's agent-plugin docs show bundled agents as agents/*.agent.md (their only concrete example), while this repo authors all four bundled agents as agents/<name>.md. Whether VS Code picks up bare-.md agent files from an installed plugin is undocumented — the no-copy claim for agents in the VS Code lane is therefore unverified. Surfaced by Codex review on PR #72.

Audience/problem: VS Code users installing gitops-kubernetes or vibe-coding may get skills and MCP servers but silently no companion agent.

Hypothesis: renaming bundled agents to agents/<name>.agent.md makes them discoverable in VS Code without breaking the other consumers (agent names come from frontmatter name:, not the filename, in Claude Code — verified against its sub-agents docs; Copilot CLI needs the same check).

Success signal: an install test in real VS Code shows the bundled agent appearing in the agent picker, and Claude Code + Copilot CLI still list the agent under its unchanged name.

Smallest useful change: rename the four bundled agent files to *.agent.md, verify all three consumers, update README/ADR 0001 accordingly.

Acceptance criteria:

• VS Code discovery of a bundled plugin agent verified hands-on (agent-picker evidence).
• Claude Code loads the renamed files with unchanged agent names (verified, not assumed).
• Copilot CLI ditto.
• README + ADR 0001 updated to state the verified behaviour.

Size: S (rename + three-consumer verification + docs).

Part of #38.

[devantler]

🤖 Generated by the Daily AI Engineer

Scope update: the rename itself landed on PR #72 (21e63f0) while this issue was being filed — this issue now tracks the verification half only: hands-on discovery checks in VS Code, Claude Code, and Copilot CLI for the renamed agents/*.agent.md files (the first two ACs and the Copilot one). The docs AC is satisfied by #72 itself.

[devantler]

🤖 Generated by the Daily AI Engineer

Scope addition from #72's round-3 review: the hands-on 3-consumer verification should ALSO confirm the built-in tool identifiers per surface. flux-troubleshooter now lists read, search alongside Read, Grep, Glob (both-spellings pattern), but portfolio-surveyor still carries only the Claude Code spellings (Bash, Read, Grep, Glob) — on VS Code / Copilot CLI it would lack its shell and read tools, and the correct lower-case identifier for the shell tool needs verifying hands-on rather than guessing (a wrong allowlist name fails silently).