gsd-mempalace-recall

**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 RECALL ``` 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. **DO NOT use `gsd-tools config get-value`** -- it hard-exits on missing keys. 1. Read `.planning/config.json` with the Read tool. 2. If the file does not exist: write the "unavailable" stub (Step 4) and **STOP**. 3. Parse the JSON. Proceed to Step 2 only if `config.mempalace && config.mempalace.enabled === true` **and** `config.mempalace.recall_on_plan !== false`. Otherwise display the disabled message and **STOP** (`recall_on_plan: false` turns plan-time recall off while leaving the rest of the capability enabled). **Disabled message:** ``` GSD > MEMPALACE RECALL MemPalace memory is disabled. To activate: node <runtime-home>/gsd-core/bin/gsd-tools.cjs config-set mempalace.enabled true Recall is opt-in; the loop proceeds normally without it. ``` This step is `onError: skip` at `plan:pre` -- recall never blocks planning. ## Step 2 -- Resolve wing, mode, and transport 1. **Wing.** Use `config.mempalace.wing` if non-empty; otherwise derive from `config.project_code`; otherwise fall back to the r...