Update AGENTS.md

Refresh the AGENTS.md that scopes the user's current working directory so its claims match the code today. Claude Code 2.1.277+ reads this file when no project CLAUDE.md is on the path; other agents read it directly.

Scope rules

• Target file: the closest AGENTS.md to cwd walking upward. Prefer the app/package-level file when cwd is inside one; only touch the monorepo root AGENTS.md when cwd is at the root (or no package-level file exists).
• Legacy CLAUDE.md. If no AGENTS.md exists in scope but a project CLAUDE.md, .claude/CLAUDE.md, or CLAUDE.local.md does, stop. Claude Code reads that file and ignores AGENTS.md while it remains. Ask the user to rename it to AGENTS.md, then continue this skill against the renamed file. Do not edit the CLAUDE.md in place.
• Shadowing. If the target AGENTS.md has a project CLAUDE.md in the same directory or any parent, flag it before editing. Claude Code will not load the AGENTS.md until that file is migrated.
• Never invent an AGENTS.md. If none exists in scope and there is no legacy CLAUDE.md to migrate, stop and tell the user.
• Never touch ~/.claude/CLAUDE.md (global user instructions) or other packages' instruction files — single-package scope only.
• ## Task-specific plan / scratch sections: prune, don't preserve. Entries for work that already landed are cruft — remove them (see the task-cruft sweep in step 5). Keep only entries for tasks still in flight; when you can't tell, keep and flag in the summary.

Detect progressive-disclosure structure

Before doing anything else, check whether the target AGENTS.md is a thin index that defers deep content to a context/ (or similar) directory of sibling .md files. Signals: