JAR-13 Define agw rename and compatibility strategy

[jarrodwatts]

Summary

• add a dedicated rename and compatibility strategy doc covering repo, package, binary, MCP alias, and state-path rules
• align README, product, PRD, and user-flow docs around the current @abstract-foundation/agw-mcp package versus the canonical agw target
• clarify the decision log by marking the original repo naming ADR as superseded by the new rename strategy ADR

Validation

• Pending full local validation gate

Refs JAR-13

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agw-mcp-app	Ready	Preview	Mar 12, 2026 3:19am

[cursor]

PR Summary

Low Risk
Documentation-only changes establishing a rename/compatibility plan; no runtime behavior, APIs, or security-sensitive code paths are modified.

Overview
Adds a dedicated rename + compatibility strategy doc (meta/rename-compatibility-strategy.md) defining how the project will converge on agw while keeping @abstract-foundation/agw-mcp/agw-mcp working during a migration window (including binary, MCP alias, and state-dir rules).

Updates top-level and product docs (README, PRD, product brief, user flows, app README) to consistently describe the current install commands vs the future agw canonical identity, and records this direction in the ADR log by introducing ADR-020 and marking ADR-001 as superseded.

^{Written by Cursor Bugbot for commit 2c2c5cd. This will update automatically on new commits. Configure here.}