inugram

Use when rebasing the inugram stgit patchset onto newer upstream Telegram and resolving the conflicts it produces. Trigger whenever `pnpm run rebase latest`/`<ref>` reports merge conflicts, when worktree files show `<<<<<<< current` / `>>>>>>> patched` markers, or the user says "rebase the patchset", "fix the rebase conflict", "continue the rebase". Covers the per-conflict loop (identify patch → cross-reference its `patches/*.patch` → resolve → `git add -f` → `stg refresh` → `stg push -a`), reading `current` (new upstream) vs `patched` (the fork's recorded delta), the recurring conflict shapes and their fixes, dispatching a subagent for big multi-file refactors, and logging questionable resolutions to `TODO.md`. NOT for creating or editing a single patch (that's covered by `CLAUDE.md`), and NOT for ordinary git merge conflicts unrelated to the stgit stack.

Analyze Java/Android heap dumps (.hprof, converted Eclipse MAT .ec.hprof) to find likely memory leak roots. Use when asked to inspect hprof/heapdump/memory dump/OOM artifacts, interpret Eclipse MAT leak suspects/top consumers/histograms, trace retained objects to GC roots, compare heap evidence with source lifecycle cleanup, or propose memory leak fixes without blindly patching downstream retained objects.

Use when syncing, actualizing, auditing, or adding inugram translations — the per-locale `src/res/values-<iso>/strings_inu.xml` files against the base `src/res/values/strings_inu.xml`. Trigger on requests to "update translations", "sync translations", "find missing strings", "translate to X", or to add a new locale.