gsd-mempalace-capture

**STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by the command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.** ## Step 0 -- Banner **Before ANY tool calls**, display this banner: ``` GSD > MEMPALACE CAPTURE ``` Then proceed to Step 1. ## Step 1 -- Config Gate Check whether the MemPalace capability is enabled by reading `.planning/config.json` directly with the Read tool. 1. Read `.planning/config.json` with the Read tool. 2. If the file does not exist, or `config.mempalace` is absent, or `config.mempalace.enabled !== true`, or `config.mempalace.capture_artifacts === false`: display the disabled message and **STOP**. 3. Otherwise proceed to Step 2. **Disabled message:** ``` GSD > MEMPALACE CAPTURE MemPalace capture is disabled (mempalace.enabled / mempalace.capture_artifacts). Nothing was filed; the loop proceeds normally. ``` This step is `onError: skip` at `discuss:post` / `plan:post` / `verify:post` -- capture never fails a phase. ## Step 2 -- Resolve target 1. **Artifact.** Take the artifact from `$ARGUMENTS`. If absent, infer from the loop point: `discuss:post` → `CONTEXT.md`, `plan:post` → `PLAN.md`, `verify:post` → `SUMMARY.md`. 2. **Room.** Map artifact → room: - `CONTEXT.md` → `decisions` - `PLAN.md` → `planning` - `SUMMARY.md` → `milestones` (Confirmed problem→fix pairs go to `problems` — see the `capture-problems` fragment used at `execute:w...