artgraph-rename

## Purpose The agent runs `artgraph rename` (or its `--split` / `--merge` variants) to safely rewrite a requirement ID across spec lists/headings, `@impl` tags, test `[ID]` tags, frontmatter `depends_on` / `derives_from`, and `.trace.lock`. The operation is destructive and writes directly to tracked files — always run `--dry-run` first. ## Preconditions - Working tree must be committed — `artgraph rename` writes directly to tracked files, and an uncommitted state makes the change irreversible. - Target IDs must be in a form artgraph re-scans: `REQ-001`, `auth/FR-2`, `doc:xxx`. Forms like `REQ-COMBINED` or `REQ-001a` are rejected. ## Steps ### 1. Prerequisite check See [install-check](../_shared/install-check.md) for the standard pre-flight check. If artgraph is not installed, stop and invoke the `artgraph-setup` Skill instead. > `<PM-exec>` is the project's package runner: `npx` (npm), `pnpm exec`, `bunx`, or `deno run -A npm:artgraph/cli`. Substitute the one detected by `_shared/package-manager.md` (or written in `.artgraph.json#packageManager`). ### 2. Confirm git is clean ```bash git status --porcelain ``` The output must be empty. If anything is listed, instruct the user to commit (or stash) before continuing — rename mutates tracked files in place and a dirty tree mixes manual edits with the rewrite. ### 3. Dry-run the rewrite Pick the command shape that matches the user's intent and add `--dry-run`: ```bash # rename <PM-exec> rename --from REQ-001 --to REQ-...