gsd-beads-recalllisted

**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 > BEADS RECALL ``` Then proceed to Step 1. ## Step 1 -- Config Gate Check whether the beads 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 exists, `config.beads` is present, and `config.beads.enabled` is explicitly the boolean `false`: display the disabled message and **STOP**. 3. Otherwise -- the file is missing, `config.beads` is absent, or `config.beads` is present with no `enabled` key -- fall through to the shipped default (`beads.enabled: true` in `capability.json`) and proceed to Step 2. **Disabled message:** ``` GSD > BEADS RECALL Beads recall is disabled (beads.enabled). Nothing was written; the loop proceeds normally. ``` This step is `onError: skip` at `plan:pre` -- a recall dispatch never fails a phase. ## Step 2 -- bd-availability gate `bd` usability is not checked here directly -- it is delegated to `sync.py beads-recall`, which locates the binary and runs one cheap read command as its first action (B6/D-08). If `bd` is absent, failing, or locked, `sync.py` prints the one required notice line, appends an entry to `.planning/STATE.md` under `### Blockers/Concerns