feat(stokowski): make glean own the follow-up contract

[ruby-automation]

Problem

EXT-68 finished its pipeline with two failures:

• The approved follow-ups were never created. Glean described them as prose findings with no ids, while improvement.md required Approve follow-ups: G1, G3. The improvement agent never saw the approval comment (fixed in feat(orchestrator): blocked transitions, report follow-ups, gate comments in prompts bougyman/stokowski#14). With a short, partly blank prompt, it made an unrequested code change instead.
• EXT-68 was marked Done while PR feat: support filter-only batch issue unassignment #286 was unmerged. merge reported blocked, but nothing acted on it.

Changes

• glean.md: glean does all the thinking.
  • Every proposed follow-up goes in the report's follow_ups list. Each item has id (G1, G2, … with no gaps), title, the complete Markdown issue body, priority, and optional existing labels.
  • Stokowski renders the list for review and saves it to .stokowski/follow-ups.json.
  • Glean's first next step tells the reviewer to approve with a comment containing Approve and the ids, for example Approve G1, G2. The comment holds only ids; all issue data comes from follow_ups.
• improvement.md: a mechanical stage.
  • One approval rule: the latest comment in the prompt's Recent Activity that contains Approve approves every G<number> after that word.
  • It copies each approved item from .stokowski/follow-ups.json with lc issue create --yes --no-take --team EXT --project "Linear CLI", and records what it created in .stokowski/follow-ups-created.json so a rerun can't duplicate issues.
  • With no approval, its headline is "No approved follow ups found". Every proposed follow-up it did not create is listed as Not created, with a note on filing it by hand with lc i create.
  • It then checks the PR and reports blocked unless mergeStateStatus is CLEAN. Spike and exploration workflows, which have no blocked transition, skip the PR check.
• merge.md: report blocked whenever the PR was not merged, instead of posting to Linear. The blank {{ issue.* }} variables are fixed here and in glean.md.
• feature and bug-fix workflows: improvement and merge declare blocked: merge-review. This new gate's approve runs merge, and its rework reruns improvement.

Deploy order

This depends on bougyman/stokowski#14. On the current pin, blocked is ignored and .stokowski/follow-ups.json is never written. Merge #14 first, then bump vendor/stokowski on this branch.

Verification

• The workflow loads, and validate_config reports no errors on the Support Ruby's short subcommand aliases (lc i dev CRY-37, etc.) #14 branch.
• The improvement prompt rendered from the EXT-68 comment history shows Approve follow-ups: G1, G3 under Recent Activity, and lists both complete and blocked transitions.
• The pre-commit gate passed: 24 root tests, 577 app tests, Credo clean.

🤖 Generated with Claude Code