**Step 9's last full-pass plan governs this step:** run the native pass only on `DISPATCH: adversarial-native` and the outside voice only on `DISPATCH: outside-voice`. Without the native line (light depth at runtime 0; above 0 the plan lists it beside the batched specialist), print `ADVERSARIAL: skipped (review plan)`; with neither line, take decision 3 of Finish the adversarial phase. On `DISPATCH: targeted`, also run the targeted reader (`gstack-review-dispatch render --role targeted --classes --base --diff-base `, the merge base on every pass, never RANGE_BASE) like the voices; `verify --targeted-out` feeds the receipt's `--review-targeted`. Under a token cap, reserve the planned voices as one batch (`gstack-ship-budget check --next dispatch:`) and add `--reservation ` to the `--start adversarial-review` call below. {{ADVERSARIAL_STEP}} {{LEARNINGS_LOG}} {{GBRAIN_SAVE_RESULTS}} ### Refresh learnings for the headline feature on this branch Step 8 used broad release terms. Before VERSION/CHANGELOG, search for versioning or changelog pitfalls tied to this branch's headline feature. Use ONE noun naming the skill, module, feature or changed binary. The keyword must be alphanumeric or hyphen only; simplify other characters. For example, use `token-or-search`, not `feat: token-or search`. ```bash { _LE=$(~/.claude/skills/gstack/bin/gstack-learnings-search --query "" --limit 5 2>&1 >&3 3>&-); _LR=$?; } 3>&1 [ "$_LR" = 0 ] || { _LE=${_LE%%$'\n'*}; echo "LEARNINGS: unavailable (${_LE:-exit $_LR})"; } ``` Name an applicable learning and its effect on the version bump or CHANGELOG in one sentence. If none applies, continue without a reference.