Skip to content

docs(quest): plan the local harness and inbox answer flow - #147

Merged
kixelated merged 2 commits into
mainfrom
quest/plan-inbox-harness
Oct 19, 2026
Merged

kixelated merged 2 commits into
mainfrom
quest/plan-inbox-harness

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Summary

This plans three of the follow-ups from the decision inbox PR (#144) as two quests:

  • [M] quest/m0/kix/harness.md: one checked-in command that serves the real Worker locally, using Miniflare with local D1 and R2, mocked GitHub, a local sign-in and seeded inbox state, so agents can check UI changes in a browser. wrangler dev hangs in the agent sandbox today. The seed and mock are meant to become the base for the kix epic's stubbed end-to-end test. It ranks first in the kix epic.
  • [XS] quest/m0/kix/answer-flow.md: after an answer, move to the next active decision with an "Answer recorded" notice, and give the refused-action page a neutral title. It ranks after the co-maintainer inbox.

Both quests require quest/m0/kix/prompts.md, which #144 deletes. Whichever of the two PRs merges second must drop that Required entry.

Planning decisions

Inbox polish: after an answer, go to the next decision, and use a neutral refusal title. How should these be planned?

  • ✅ One [XS] quest (Recommended)
  • Two quests
  • Stay on the item and plan only the title fix

Agent UI testing: how should agents run the inbox in a browser?

  • ✅ A seeded local harness (Recommended)
  • Fix wrangler dev in the sandbox
  • Both

Rank: where do the new quests go?

  • ✅ The harness at the top of the kix epic, and polish after the co-maintainer inbox (Recommended)
  • Polish first
  • Both at the end

Checks

quest check, just check and just test pass.

🤖 Generated with Claude Code

(Written by Claude Opus 5.5)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T15:26:57.707928Z accb703 PR opened
🔒 Security Review ✅ Completed 2026-10-19T15:27:10.252979Z accb703 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@kixelated

Copy link
Copy Markdown
Collaborator Author

Merge summary:

(Written by Claude Opus 5.5)

@kixelated
kixelated merged commit e77b03a into main Oct 19, 2026
5 checks passed
kixelated added a commit that referenced this pull request Oct 19, 2026
Brings in raw output retention (#142) and the harness and answer-flow
plans (#147). The inbox migration becomes 0009_inbox.sql after
0008_output.sql. The shared maintainerOf() fixture adopts main's
stricter GitHub mock, where only the signed-in user holds the maintain
role. harness.md and answer-flow.md drop this deleted quest from
Required, and activity.md drops both deleted quests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kixelated
kixelated deleted the quest/plan-inbox-harness branch October 21, 2026 21:05
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