Skip to content

fix: questions must show the content they refer to (overlay #879)#21

Merged
time-attack merged 2 commits into
mainfrom
time-attack/questions
Jul 23, 2026
Merged

fix: questions must show the content they refer to (overlay #879)#21
time-attack merged 2 commits into
mainfrom
time-attack/questions

Conversation

@time-attack

@time-attack time-attack commented Jul 23, 2026

Copy link
Copy Markdown
Owner

Problem

A /plan Discovery session asked "Do you agree with all five premises?" with zero assistant text emitted since the previous question — the premises existed only in the agent's internal reasoning and were never shown to the user. This is upstream issue garrytan#879's failure class, previously patched only for the office-hours Phase-5 design doc (overlay garrytan#1116) and never generalized.

Fix

New judgment overlay garrytan#879 ("Self-contained questions") targeting '*' — all 55 gstack2 modules: before any AskUserQuestion or prose decision brief about session-produced content (premises, findings, plans, approaches, scores, summaries), render that content as direct assistant text immediately before the question or restate it inside the question/options. Internal reasoning and collapsed tool output do not count as shown.

  • scripts/gstack2/bug-fix-overlays.ts: overlay + executable regression (case 879)
  • Pinned counts: 28 → 29 overlays; EXPECTED_PARITY_CHECKS 4914 → 5027 (2 × 55 modules + 3 regression checks)
  • Regenerated tree: overlay block in all 59 legacy module files, contracts, pr-879.json fixture, provenance docs

Testing

  • bun run test:gstack2 — 26 test files green, full 5,027-check parity run passes
  • bun test — free suite passes (exit 0)

🤖 Generated with Claude Code


Summary by cubic

Make all user questions self‑contained by showing or restating the content they refer to before asking. Adds judgment overlay garrytan#879 across all modules to prevent invisible‑premise asks and resolves upstream issue garrytan#879.

  • Bug Fixes
    • Added overlay office-hours: design doc not visible to user when AskUserQuestion requests approval garrytan/gstack#879 targeting '*' to render session‑produced content (premises, findings, plans, scores, summaries) immediately before any AskUserQuestion; internal reasoning and collapsed tool output don’t count as shown.
    • Regenerated skill tree and parity artifacts; overlays 28 → 29 and EXPECTED_PARITY_CHECKS 4914 → 5027; added regression fixture evals/parity/regressions/pr-879.json.
    • Updated contracts and deterministic transcripts for all 55 modules to include the rule.
    • All 5,027 parity checks and test suites pass.

Written for commit ac65529. Summary will update on new commits.

Review in cubic

Sinabina and others added 2 commits July 22, 2026 17:29
…r to

Generalizes the inline-approval rule (PR garrytan#1116) to every question in every
module: an AskUserQuestion that asks the user to confirm, approve, rank, or
choose among session-produced content (premises, findings, plans, scores)
must render that content as direct assistant text first or restate it in the
question itself. Internal reasoning and collapsed tool output do not count.

Evidence: a /plan Discovery run asked 'Do you agree with all five premises?'
with zero assistant text between the prior question and the ask — the
premises were never shown (upstream issue garrytan#879 failure class, Phase 3).

Pinned counts: 28 -> 29 overlays; EXPECTED_PARITY_CHECKS 4914 -> 5027
(2 x 55 modules + 3 regression checks).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
bun run gen:gstack2 output only — no hand edits.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@cursor

cursor Bot commented Jul 23, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@time-attack
time-attack merged commit c0a5d02 into main Jul 23, 2026
6 of 14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant