issue

# issue: GitHub issues as resolution memory Persist problem-solving state in GitHub issues so a later session (or a fresh context) can re-read an issue cold and continue. Each issue records the problem, a self-contained Pickup Directive, the working hypothesis, attempts, and the final resolution. ## Prerequisites - `gh` CLI authenticated (`gh auth status`). - Inside a GitHub repo (a remote with issues enabled). If not, stop and tell the user. ## Natural-language routing Interpret intent and route: | User says | Action | |-----------|--------| | "track this in an issue", "log this problem", "open an issue for this" | **create** | | "update the issue", "note progress on #N", "I found the cause" | **update** | | "resume issue #N", "what was I doing on #N", "pick up where I left off" | **resume** | | "list my memory issues", "what issues am I tracking" | **list** | Default when ambiguous and a number is present → **resume #N**; otherwise → **create**. ## create 1. Draft the issue body from `references/issue-template.md` (Problem / Pickup Directive / Hypothesis / Attempts / Resolution). Fill Problem + Pickup Directive + initial Hypothesis from the current context; leave Attempts/Resolution as stubs. 2. **Confirm with the user before opening** (opening an issue is outward-facing). Show the drafted title + body. 3. Create with the memory label so `resume`/`list` can filter: ```bash gh issue create --title "<concise title>" --label claude-memory --body "<rendered templ...