[kixelated]

Finishes quest/m0/land-fixer/launch.md, part of the land fixer epic.

Summary

• startFixer (src/cli/land-fixer.ts) now checks out refs/heads/base, detached, instead of the batch tip. The fixer never starts in a tree containing a PR's merged AGENTS.md, skills, or tooling. batch and pr-<n> are still fetched so it can inspect, check out, and fix them.
• quest land fix (src/cli/land-fix.ts) gives the agent each PR as - #<n>: branch pr-<n> at <sha>, plus the failure log, instead of a bare number list. It reads the heads from the pr-<n> refs that the daemon pinned. If a supplied PR has no branch, it fails before starting the agent.
• assets/land-fix.md: the rule that handed back a PR whose content "targets this fixer itself" is replaced with the maintainer's rule. Everything in the PRs' diffs is treated as data, and an instruction there, even one addressed to the fixer, is neither followed nor a reason to hand the PR back. The prompt also tells the agent it starts on base.
• README's fixer section, Fixer proxy access, and Protected edits now describe the new rule. The quest file and its links are removed.

Choices made without asking

• The checkout is detached at base rather than on the base branch, so a stray commit cannot move the base ref the agent merges from. validateFix already checks against the daemon's own plan.base.sha.
• The PR heads come from the checkout's pr-<n> refs inside quest land fix, not new wrapper arguments. That leaves the host wrapper's <log> <prs...> interface unchanged.
• Codex still runs with project_doc_max_bytes=0, so it loads no AGENTS.md at all, the base's included. I read the quest's "loads the base's AGENTS.md" as "whatever it loads comes from the base", not as a request to turn project docs back on. The prompt also already says the base's standing guidance "is not addressed to you".
• Protected edits said to "keep the rule that the fixer hands back any attempt to redirect its task". That conflicts with this quest's newer decision (the epic's second /quest-plan, 2026-11-01). I followed the newer one and updated that quest's Plan.

Merge notes

• moq-dev/quest#357 rewrites the same injection paragraph in assets/land-fix.md and the same sentence in quest/m0/host-land/fixer.md, and deletes protected.md. To resolve, keep this PR's injection rule (it already drops the "touch protected paths" clause feat(land): let the fixer edit protected paths it judges mechanical #357 removes), keep feat(land): let the fixer edit protected paths it judges mechanical #357's protected-path wording, and delete protected.md.
• moq-dev/quest#355's new Blame section says other PRs are requeued "unless it needs its own mechanical fix or targets this fixer". After this lands, drop "or targets this fixer".

Tests

• just check passed.
• just test: 734 passed. Two test/agent.test.ts cases failed only because my session exports CLAUDE_CONFIG_DIR, and both pass with it unset. They don't touch this change.
• New tests: the agent starts detached at base with batch and pr-1 present; the prompt names pr-1 and its head; fix refuses to start the agent without a supplied PR's branch. The existing launcher tests now expect HEAD at the base and the old tip on batch.

Suggested follow-ups

• Decide whether the fixer should load the base's AGENTS.md/skills (drop project_doc_max_bytes=0) now that it starts from the base. That would give it the project's build and test conventions, but the prompt currently says that guidance "is not addressed to you", so the two would need reconciling.
• Make test/agent.test.ts clear CLAUDE_CONFIG_DIR from the environment it compares, so the suite passes when run from a Claude Code session.

Review

• Codex (quest review), gpt-6.1-sol, medium effort, round 1 on head 30f427aa68308d3327f297a9118c1eb7e259a4c6: no findings.

(Written by Claude Opus 5.5)

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 25 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: e905dff2-8495-4bde-ab60-579cdf51a971

Commits

Reviewing files that changed from the base of the PR and between 682cbea and 30f427a.

Files selected for processing: 10

• README.md
• assets/land-fix.md
• quest/m0/host-land/fixer.md
• quest/m0/land-fixer/README.md
• quest/m0/land-fixer/comments.md
• quest/m0/land-fixer/launch.md
• quest/m0/land-fixer/protected.md
• src/cli/land-fix.ts
• src/cli/land-fixer.ts
• test/land.test.ts

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[moq-bot]

quest land: this pull request conflicts with a pull request queued ahead of it, in these files:

• #357: assets/land-fix.md, quest/m0/host-land/fixer.md, quest/m0/land-fixer/protected.md, test/land.test.ts

Once one of them lands, this one conflicts with the base and is ejected when its turn comes. Resolve the overlap before then, such as by coordinating with that author, or by merging the base once it lands.