Skip to content

quest: plan landing follow-ups from the 2026-11-02 complete session - #398

Merged
moq-bot[bot] merged 1 commit into
mainfrom
quest-plan/landing-follow-ups
Nov 3, 2026
Merged

moq-bot[bot] merged 1 commit into
mainfrom
quest-plan/landing-follow-ups

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Summary

Plans the follow-ups from the 2026-11-02 /quest-complete session, which landed moq-dev/quest#338, #342 and #395 and reviewed kixelated/nixos#19.

Decisions

Decided 2026-11-02 (user, /quest-plan):

  • pushed-head-ci scope: ✅ watcher only · watcher and gate · gate only. Then, shown that moq's watcher-pushed heads already get runs: ✅ delete it · keep an [XS] watcher guard
  • Stale labels: ✅ fold into merge-driver-upkeep and the cutover · a new XS pin-bump quest · clear them once
  • Runner hardening items: ✅ watch-mode cleanup, ✅ runner-group workflow limits, ✅ approval for all fork PRs; milestone ✅ m0 · m1
  • Boundary test: ✅ CI on Linux · a manual recipe; milestone ✅ m0 · m1

Review

  • Reviewer: Codex (quest review), gpt-6.1-sol, medium effort
  • Head: 7cbacdb, round 1
  • Findings: none

just check and quest check pass.

🤖 Generated with Claude Code

(Written by Claude Opus 5.5)

Delete pushed-head-ci (the watcher's fixer pushes already get pull_request
runs on moq, and the gate is retiring), fold the stale quest:merge holds
into the pin bump and the cutover, and add runner hardening and a CI
boundary test for the opencode sandbox.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kixelated
kixelated enabled auto-merge (squash) November 3, 2026 00:48
@moq-bot
moq-bot Bot merged commit 3f852ed into main Nov 3, 2026
5 of 6 checks passed
@moq-bot
moq-bot Bot deleted the quest-plan/landing-follow-ups branch November 3, 2026 00:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant