Repository navigation
docs(quest): plan follow-ups from the 2026-10-21 merge wave - #179
Conversation
Six new quests (kix epic branches, inbox accuracy, job recovery; upstream claims, wait gaps, guard in CI) and real-device and live-read checks in operator setup. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6083b12853
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `cloudflare/src/github/state.ts` maps branches back to quests, and | ||
| `questHref` in `cloudflare/src/board/model.ts` builds board links. Git |
There was a problem hiding this comment.
The directory form is intentional for questHref: the board route resolves /board/quest/m0/foo to quest/m0/foo/README.md, while /board/quest/m0/foo/README resolves to neither an existing .md file nor an epic README. Applying the new branch rule to this function would therefore turn epic links into 404s; restrict the /README mapping to branch creation and branch-to-quest association.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Declining: /README page URLs do not 404. The board route (cloudflare/src/index.tsx:315) resolves pages through findDoc in cloudflare/src/board/model.ts, which tries ${page}.md first, so quest/m0/foo/README resolves to quest/m0/foo/README.md; its doc comment lists quest/m0/epic/README as a supported form. questHref is in scope because its comment defines a page as "its path without .md, like its branch name", so it should follow the same rule as the branch.
(Written by Claude Opus 5.5)
| - **Unknown merge state.** GitHub reports `mergeStateStatus` `UNKNOWN` while it | ||
| computes mergeability. Treat it as not yet known: keep the item's previous | ||
| state and do not mark it unread until a definite state arrives. |
There was a problem hiding this comment.
When a pull request's first observation has mergeStateStatus: UNKNOWN, there is no previous item state to retain, and the newly opened PR itself is still something the maintainer must act on. Suppressing unread state until mergeability becomes definite can hide the PR indefinitely because GitHub need not send another event when that background computation finishes; limit this rule to transient UNKNOWN updates of an already-recorded PR while still surfacing new PRs.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Agreed, fixed in f11e84b: the UNKNOWN rule now applies only to an already-recorded PR, and a newly seen PR still surfaces as unread, since GitHub may send no further event when mergeability is computed.
(Written by Claude Opus 5.5)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Merge summary:
(Written by Claude Opus 5.5) |
Plans the follow-ups that merge agents reported while landing 20 PRs on 2026-10-21. Each was checked against the quest tree on
main, and items an existing quest already covers were folded in there.Changes
quest/m0/kix/epic-branches.md[S]: kix starts epics onquest/<path>/README(#169).quest/m0/kix/inbox-accuracy.md[M]:UNKNOWNmerge state (#163);quest/m0/kix/recovery.md[M]:quest/m0/helpers/claims.md[S]: claims ignore merged-PR heads, readiness comes from the upstream tree, and the head repository comes from the push URL (#164, #167).quest/m0/helpers/wait-gaps.md[S]:quest waitmissed events (#127, #172).quest/m0/helpers/ci-guard.md[XS]: the landed-quest guard runs in CI (#169).operator-setup.md:quest worktree remove(#127) went to the agent working onquest/m0/worktree.md, rather than being edited under it.Dropped (each is recorded in its PR thread):
checks:passed.testEnvcleanup, and the title-from-read test.quest rm.--autoalready merges them at once.Already covered:
local-gate.md, which is in flight.headless-agents.md, also in flight.quest unblockedcolours are part of the theme epic's size colours.Out of scope: switching CI in moq-dev/moq and moq.pro to ready PRs only needs
/quest-planin those repositories.Done directly at the user's request, outside this PR:
quest/m0/worktree.mdandquest/m0/local-gate.mdlook claimed.Decision paper trail
Round 1: scope
Goal: turn the merge wave's follow-ups into quests, keeping real defects and gaps and dropping minor ones whose PR threads keep the record.
Triage:
Kix ranks:
Round 2: details (user: "whatever you recommend")
Activity retention:
Blocked fork branch:
Leftover branches that stop counting as claims:
Stale claims (asked during the spawn):
just checkandjust testpass.(Written by Claude Opus 5.5)
🤖 Generated with Claude Code