Coordinate ward-mcp -> agent-guard-mcp rename after agent-guard settles #19

Open
opened 2026-07-14 08:32:19 +00:00 by coilyco-ops · 0 comments
Member

Decision

Go, from coilysiren/inbox#210.

Rename ward-mcp to agent-guard-mcp after the agent-guard naming sweep is settled. This is separate from cli-guard#200, which already captures cli-guard to agent-guard and importer updates.

Scope

  • Rename the ward-mcp repository and public prose to agent-guard-mcp.
  • Retag images/charts only after the new agent-guard name is settled.
  • Preserve MCP tool contracts and deployment behavior.

Dependencies

Non-goals

  • Do not change the MCP runtime contract.
  • Do not rename the Ward product.
  • Do not bundle this with Ward kernel refactors.

Parent: coilysiren/inbox#210.

## Decision Go, from coilysiren/inbox#210. Rename ward-mcp to agent-guard-mcp after the agent-guard naming sweep is settled. This is separate from cli-guard#200, which already captures cli-guard to agent-guard and importer updates. ## Scope - Rename the ward-mcp repository and public prose to agent-guard-mcp. - Retag images/charts only after the new agent-guard name is settled. - Preserve MCP tool contracts and deployment behavior. ## Dependencies - coilyco-flight-deck/cli-guard#200 should land or be actively coordinated first. ## Non-goals - Do not change the MCP runtime contract. - Do not rename the Ward product. - Do not bundle this with Ward kernel refactors. Parent: coilysiren/inbox#210.
Sign in to join this conversation.
No description provided.