deprecatelisted

# Deprecate and archive a repository Use the supplied path, resolving relative paths from the invocation's working directory; if no path is provided, use that directory. Operate only inside the resolved repository. This workflow does not create a plan file unless the user's applicable project instructions require one. ## Discover the concrete target Read applicable AGENTS.md instructions, composer.json or package.json, README and changelog. Inspect Git status, branch/worktree, remotes and release tags, and verify the intended GitHub owner/repository. Confirm the working tree is clean before preparing changes; do not fold unrelated edits into deprecation. Inspect branch/PR policies, required checks/reviews, release conventions and the configured human Git identity. Never commit or push as an agent. Determine the latest relevant semantic version tag and its next patch version, preserving its prefix. Resolve missing/ambiguous tags or multiple plausible remotes before publication; do not invent a target. A configured Git remote alone is not proof of which repository the user intends to archive if identities conflict. Do not deprecate a package registry account or delete local files as an implied extra step. ## Prepare a reviewable result, then confirm Prepare these local edits, preserving existing formatting: - **Composer:** add or update the top-level `"abandoned": true` before `"autoload"`, otherwise before `"scripts"`, otherwise at the end. Preserve unrelated metadata