From 9deec70ddfe2b25a1ca23f5cb8339da348901869 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Mon, 2 Nov 2026 22:21:18 -0800 Subject: [PATCH 1/8] chore(quest): claim quest/m0/quest-worktree-hooks.md Quest-Claim: 3dfc555d6fffccc4 From 31169be635233c29f48df264a3ba842a93519077 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Mon, 2 Nov 2026 22:26:29 -0800 Subject: [PATCH 2/8] chore(quest): record why moq can't adopt quest's worktree hooks yet The hooks leave T3 Code's checkouts alone, but they run with the PATH Claude Code started with, which has no `quest` here, so every isolated subagent and `--worktree` would fail. Record the findings and what the quest waits on, and ignore the main checkout's `.worktrees/`, where quest's checkouts already land. Co-Authored-By: Claude Opus 5.5 --- .gitignore | 4 ++++ quest/m0/quest-worktree-hooks.md | 34 ++++++++++++++++++++++++++++++++ 2 files changed, 38 insertions(+) diff --git a/.gitignore b/.gitignore index b4aa4e2515c..b3ef8e75a69 100644 --- a/.gitignore +++ b/.gitignore @@ -13,6 +13,10 @@ /.claude/cache/ /.claude/tmp/ /.claude/worktrees/ +# quest's own checkouts (`quest worktree create`, /quest-spawn, and its Claude +# Code worktree hooks) live under the main checkout's .worktrees/, for the same +# reason. +/.worktrees/ # Per-checkout scratch output, such as benchmark logs and agent notes. /.tmp/ diff --git a/quest/m0/quest-worktree-hooks.md b/quest/m0/quest-worktree-hooks.md index 59c519d7eb8..31a09d37f9b 100644 --- a/quest/m0/quest-worktree-hooks.md +++ b/quest/m0/quest-worktree-hooks.md @@ -18,3 +18,37 @@ moq never adopted them after moq-dev/quest#350. isolated delegate checkouts (create, hand off, and clean up one of each with the hooks on). If they conflict, stop and report rather than adopting. - Then add them with `quest init` and document the behavior in AGENTS.md. + +Findings, 2026-11-02 ([moq-dev/moq#7674](https://github.com/moq-dev/moq/pull/7674)): + +- The hook itself leaves T3 Code's checkouts alone. T3 makes its own + (`~/worktrees/moq/t3-*` on `t3/*` branches) rather than going through + Claude's `WorktreeCreate`. `SubagentStart`/`SubagentStop` act only on a + registered checkout named `agent-`, and `WorktreeRemove` refuses a + path quest doesn't own. A scratch run against a T3-style linked worktree + confirmed each case. +- They still conflict today: hooks run with the `PATH` Claude Code started + with, not the direnv dev shell, and T3 Code's `PATH` has no `quest`. With the + hooks on, every isolated subagent, `--worktree`, and `EnterWorktree` fails + with `quest: not found`. moq-dev/quest's own adoption, + [moq-dev/quest#423](https://github.com/moq-dev/quest/pull/423), waits on the + same install. +- Without + [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425) in moq's pin, + `--worktree '#123'` starts at `origin/HEAD` instead of the PR head, and + workflow agents' checkouts are never released. +- Once both clear, run `quest init`, document the behavior and the `quest` + install in AGENTS.md, and do the live T3 check above, plus a native + `isolation: "worktree"` subagent inside a T3 session. + +## Waiting + +- Maintainer: install a reviewed `quest` on the `PATH` Claude Code and T3 Code + start with on every host that runs agents here, for example + `nix profile add github:moq-dev/quest` (`~/.nix-profile/bin` is already on + T3 Code's `PATH`). Check from a shell outside the dev shell: + `echo '{}' | quest worktree hook` prints `expected a Claude Code hook's JSON + input`, not `command not found`. +- moq-dev/quest: land + [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425), then bump + moq's `quest` flake input past it. From 49e805f1d9cd3891bc952f06d6f4287575e7f692 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 3 Nov 2026 09:45:14 -0800 Subject: [PATCH 3/8] feat(claude): run quest's worktree hooks through the flake's pinned quest Claude Code runs hooks with the PATH it started with, not the dev shell, so a bare `quest worktree hook` fails here. Run the quest moq pins with `nix run "${CLAUDE_PROJECT_DIR}#quest" -- worktree hook` instead, and note in AGENTS.md how to keep the hooks across `quest init`, which refuses a command other than its literal one. Co-Authored-By: Claude Opus 5.5 --- .claude/settings.json | 40 ++++++++++++++++++++++++++++++++++++++++ AGENTS.md | 1 + 2 files changed, 41 insertions(+) diff --git a/.claude/settings.json b/.claude/settings.json index 6575a2bc3fe..2d105c725d5 100644 --- a/.claude/settings.json +++ b/.claude/settings.json @@ -10,6 +10,46 @@ } ] } + ], + "WorktreeCreate": [ + { + "hooks": [ + { + "type": "command", + "command": "nix run \"${CLAUDE_PROJECT_DIR}#quest\" -- worktree hook" + } + ] + } + ], + "WorktreeRemove": [ + { + "hooks": [ + { + "type": "command", + "command": "nix run \"${CLAUDE_PROJECT_DIR}#quest\" -- worktree hook" + } + ] + } + ], + "SubagentStart": [ + { + "hooks": [ + { + "type": "command", + "command": "nix run \"${CLAUDE_PROJECT_DIR}#quest\" -- worktree hook" + } + ] + } + ], + "SubagentStop": [ + { + "hooks": [ + { + "type": "command", + "command": "nix run \"${CLAUDE_PROJECT_DIR}#quest\" -- worktree hook" + } + ] + } ] }, "permissions": { diff --git a/AGENTS.md b/AGENTS.md index 26a26952d5b..37e66aec2db 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -102,6 +102,7 @@ These diff the branch against its base and only run the affected packages. Quests: before starting work, run `quest guide` and follow it. The `quest` binary comes from the moq-dev/quest flake input and serves the quest skills; change them upstream and bump the input. +Claude Code's worktree hooks run that pinned `quest` through `nix run`, because hooks don't see the dev shell; `quest init` refuses them, so drop them for its run and restore `.claude/settings.json` afterwards. # Cross-Package Sync From ae281b59f7743aa41f3a33b66f3d064495802954 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 3 Nov 2026 09:46:51 -0800 Subject: [PATCH 4/8] chore(quest): rewrite the worktree-hooks quest to what remains Record the maintainer's nix-or-submodule decision, the measured hook latency, and what still waits on moq-dev/quest. Co-Authored-By: Claude Opus 5.5 --- quest/m0/README.md | 2 +- quest/m0/quest-worktree-hooks.md | 80 ++++++++++++++------------------ 2 files changed, 37 insertions(+), 45 deletions(-) diff --git a/quest/m0/README.md b/quest/m0/README.md index 55bddeb5c1f..c6d02a4c7d7 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -38,5 +38,5 @@ since cutting segments from first-frame pts waits on nothing in m1. - [Backport the relay and auth hardening to release](/quest/m0/backport-release-hardening.md) - `release`'s relay refuses dot-segment paths, serves its HTTP routes with main's response hardening, and withdraws advertisements a peer starves of send credit; its auth client refuses redirects - [Release's MKV importer bounds what it buffers](/quest/m0/backport-mkv-buffer.md) - on `release`, an MKV input that declares a huge element and trickles its bytes no longer grows the importer's memory without limit - [HLS export on a declared grid](/quest/m0/hls-media-grid.md) - the catalog's `hls` field and record tracks go away, and the export numbers segments on `media.join.interval` from media tracks -- [Agents use quest's worktree hooks](/quest/m0/quest-worktree-hooks.md) - adopt `quest worktree hook` once it's shown to coexist with T3 Code's worktrees +- [quest init keeps moq's nix-wrapped worktree hooks](/quest/m0/quest-worktree-hooks.md) - pin bumps keep the hooks that run moq's pinned `quest`, and PR and workflow worktrees behave under them - [HLS lists contributions](/quest/m0/hls-contributions.md) - an HLS master lists each catalog contribution's renditions, and a contribution's media is subscribed only while players fetch it diff --git a/quest/m0/quest-worktree-hooks.md b/quest/m0/quest-worktree-hooks.md index 31a09d37f9b..1ccad4f37a9 100644 --- a/quest/m0/quest-worktree-hooks.md +++ b/quest/m0/quest-worktree-hooks.md @@ -1,54 +1,46 @@ -# [S] Agents use quest's worktree hooks +# [XS] quest init keeps moq's nix-wrapped worktree hooks ## Goal -moq's `.claude/settings.json` carries the `WorktreeCreate`, `WorktreeRemove`, -`SubagentStart` and `SubagentStop` hooks that `quest init` installs (running -`quest worktree hook`), so agent worktrees are created and cleaned up the way -quest expects, without breaking T3 Code's own worktree management. +moq's Claude Code worktree hooks run the `quest` moq pins, and they survive +quest pin bumps: `quest init` leaves them alone instead of refusing them, and +`--worktree '#123'` and workflow agents behave under them as without them. ## Plan -Planned 2026-11-02 (maintainer, /quest-unblock), from -[moq-dev/moq#7644](https://github.com/moq-dev/moq/pull/7644): the quest pin bump -left the hooks out because they change how agent worktrees are made here, and -moq never adopted them after moq-dev/quest#350. - -- First confirm the hooks coexist with T3 Code's worktree threads and its - isolated delegate checkouts (create, hand off, and clean up one of each with - the hooks on). If they conflict, stop and report rather than adopting. -- Then add them with `quest init` and document the behavior in AGENTS.md. - -Findings, 2026-11-02 ([moq-dev/moq#7674](https://github.com/moq-dev/moq/pull/7674)): - -- The hook itself leaves T3 Code's checkouts alone. T3 makes its own - (`~/worktrees/moq/t3-*` on `t3/*` branches) rather than going through - Claude's `WorktreeCreate`. `SubagentStart`/`SubagentStop` act only on a - registered checkout named `agent-`, and `WorktreeRemove` refuses a - path quest doesn't own. A scratch run against a T3-style linked worktree - confirmed each case. -- They still conflict today: hooks run with the `PATH` Claude Code started - with, not the direnv dev shell, and T3 Code's `PATH` has no `quest`. With the - hooks on, every isolated subagent, `--worktree`, and `EnterWorktree` fails - with `quest: not found`. moq-dev/quest's own adoption, - [moq-dev/quest#423](https://github.com/moq-dev/quest/pull/423), waits on the - same install. -- Without - [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425) in moq's pin, - `--worktree '#123'` starts at `origin/HEAD` instead of the PR head, and - workflow agents' checkouts are never released. -- Once both clear, run `quest init`, document the behavior and the `quest` - install in AGENTS.md, and do the live T3 check above, plus a native - `isolation: "worktree"` subagent inside a T3 session. +Decided 2026-11-03 (maintainer, on +[moq-dev/moq#7674](https://github.com/moq-dev/moq/pull/7674)): ✅ the hooks +reach `quest` through nix (or a submodule) long-term, so they run moq's pin. +A host-wide `quest` on `PATH` is acceptable only as a temporary bridge. +Rejected: relying on an installed `quest`, `direnv exec`, adopting the bare +`quest worktree hook` now, and dropping the quest. + +[moq-dev/moq#7674](https://github.com/moq-dev/moq/pull/7674) installed the four +hooks as `nix run "${CLAUDE_PROJECT_DIR}#quest" -- worktree hook`. That command +takes 0.1–0.5 s warm and 1.5–3 s with a cold nix cache, and builds a new pin in +about 6 s. The PR checked live that it coexists with T3 Code's worktree threads +and isolated delegates. What remains: + +- `quest init` matches only the literal `quest worktree hook`, so it refuses a + wrapped `WorktreeCreate`/`WorktreeRemove` command (exit 1, nothing written) + and would add duplicate subagent hooks. Until quest recognizes a wrapped + command, a pin bump drops the four entries for its `quest init` run and + restores `.claude/settings.json` afterwards, as AGENTS.md says. Once a + quest release recognizes them, bump the pin, check that `quest init` is a + no-op here, and drop that AGENTS.md sentence. +- Bump moq's `quest` input past + [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425), so + `--worktree '#123'` starts at the PR head instead of `origin/HEAD` and + workflow agents' checkouts get released. ## Waiting -- Maintainer: install a reviewed `quest` on the `PATH` Claude Code and T3 Code - start with on every host that runs agents here, for example - `nix profile add github:moq-dev/quest` (`~/.nix-profile/bin` is already on - T3 Code's `PATH`). Check from a shell outside the dev shell: - `echo '{}' | quest worktree hook` prints `expected a Claude Code hook's JSON - input`, not `command not found`. +- Maintainer: ask moq-dev/quest to let `quest init` and `quest uninstall` + recognize a hook command that wraps `quest worktree hook` in a launcher, such + as `nix run #quest -- worktree hook`. Options: (a) recognize any + command hook whose arguments end in `worktree hook` (recommended: no config, + and `quest init` stays idempotent); (b) a configured hook command `quest init` + writes and matches; (c) don't ask, and keep the drop-and-restore step on + every pin bump. - moq-dev/quest: land - [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425), then bump - moq's `quest` flake input past it. + [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425). From 4940d8637a7bd66b1d51ec62c5387e1092bb1ef1 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 3 Nov 2026 10:58:40 -0800 Subject: [PATCH 5/8] chore(quest): plan the quest pin bump past moq-dev/quest#425 moq-dev/quest#425 merged, so the bump is ready work, not a wait. Co-Authored-By: Claude Opus 5.5 --- quest/m0/quest-worktree-hooks.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/quest/m0/quest-worktree-hooks.md b/quest/m0/quest-worktree-hooks.md index 1ccad4f37a9..1949d9ad67e 100644 --- a/quest/m0/quest-worktree-hooks.md +++ b/quest/m0/quest-worktree-hooks.md @@ -29,9 +29,11 @@ and isolated delegates. What remains: quest release recognizes them, bump the pin, check that `quest init` is a no-op here, and drop that AGENTS.md sentence. - Bump moq's `quest` input past - [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425), so - `--worktree '#123'` starts at the PR head instead of `origin/HEAD` and - workflow agents' checkouts get released. + [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425) (merged + 2026-11-03 as `53f78b9`), so `--worktree '#123'` starts at the PR head + instead of `origin/HEAD` and workflow agents' checkouts get released. + Refresh the skill stubs with the AGENTS.md drop-and-restore step, then + check both routes live. ## Waiting @@ -42,5 +44,3 @@ and isolated delegates. What remains: and `quest init` stays idempotent); (b) a configured hook command `quest init` writes and matches; (c) don't ask, and keep the drop-and-restore step on every pin bump. -- moq-dev/quest: land - [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425). From 90af3fe94c8949504f9ed9a99bcdb514bfc54894 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 3 Nov 2026 11:41:02 -0800 Subject: [PATCH 6/8] chore(nix): bump quest past moq-dev/quest#425 With the PR-head and workflow-agent fixes from moq-dev/quest#425, the worktree hooks start `--worktree '#N'` at the PR head and release workflow agents' checkouts. Refresh the skill stubs with `quest init`. Co-Authored-By: Claude Opus 5.5 --- .claude/skills/quest-merge/SKILL.md | 2 +- flake.lock | 14 +++++++------- flake.nix | 2 +- 3 files changed, 9 insertions(+), 9 deletions(-) diff --git a/.claude/skills/quest-merge/SKILL.md b/.claude/skills/quest-merge/SKILL.md index c03a0d84973..156d4aba306 100644 --- a/.claude/skills/quest-merge/SKILL.md +++ b/.claude/skills/quest-merge/SKILL.md @@ -1,6 +1,6 @@ --- name: quest-merge -description: Queue a reviewed PR to land, or send it to /quest-iterate. +description: Queue a PR to land, running /quest-iterate first when it needs work. --- Run `quest skill merge` and follow its output. diff --git a/flake.lock b/flake.lock index b5e2c97c919..b086087c5a3 100644 --- a/flake.lock +++ b/flake.lock @@ -77,28 +77,28 @@ "quest-pinned": "quest-pinned" }, "locked": { - "lastModified": 1793656089, - "narHash": "sha256-QsOBS3Md96SVAwwGsmWWmZLJQcWymHPdDdyy2UvqKFg=", + "lastModified": 1793732323, + "narHash": "sha256-rmhEvaqsKShdBJ+8WbXmDj9HkHIr5GEMfs2lDTxTnD4=", "owner": "moq-dev", "repo": "quest", - "rev": "5e66075d5acc397e400094ea4f53f7db45e351ce", + "rev": "36d0429cce0d540ad90f6c1a006a9ca1659b0696", "type": "github" }, "original": { "owner": "moq-dev", "repo": "quest", - "rev": "5e66075d5acc397e400094ea4f53f7db45e351ce", + "rev": "36d0429cce0d540ad90f6c1a006a9ca1659b0696", "type": "github" } }, "quest-pinned": { "flake": false, "locked": { - "lastModified": 1793505952, - "narHash": "sha256-jDq0fsxzLGIu6FsFfIsnUgvb23Pb+Rja4KZwIxGa34I=", + "lastModified": 1793721754, + "narHash": "sha256-pPsXWcv0LdYqW5bRYx7Av6urjcRTC3bGRWh8BGwO0Ug=", "owner": "moq-dev", "repo": "quest", - "rev": "7a191e6197c691f477b4c55edba34cc425c3e77c", + "rev": "2aa60a2d6676147314e725b0410882128eacea49", "type": "github" }, "original": { diff --git a/flake.nix b/flake.nix index 616ca64a9ff..09c3ccfd3dd 100644 --- a/flake.nix +++ b/flake.nix @@ -32,7 +32,7 @@ # The quest CLI, which also serves the quest guide and skills the stubs in # .claude/skills call. Bump the rev to upgrade them. quest = { - url = "github:moq-dev/quest/5e66075d5acc397e400094ea4f53f7db45e351ce"; + url = "github:moq-dev/quest/36d0429cce0d540ad90f6c1a006a9ca1659b0696"; inputs.nixpkgs.follows = "nixpkgs"; inputs.flake-utils.follows = "flake-utils"; }; From f26e953f66fdc326a1e4d704af876b7f38730f52 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 3 Nov 2026 11:41:22 -0800 Subject: [PATCH 7/8] chore(quest): narrow the worktree-hooks quest to quest init The pin bump past moq-dev/quest#425 is done; what remains is quest init recognizing the nix-wrapped hooks. Co-Authored-By: Claude Opus 5.5 --- quest/m0/README.md | 2 +- quest/m0/quest-worktree-hooks.md | 23 ++++++++++------------- 2 files changed, 11 insertions(+), 14 deletions(-) diff --git a/quest/m0/README.md b/quest/m0/README.md index c6d02a4c7d7..25a135c7f0d 100644 --- a/quest/m0/README.md +++ b/quest/m0/README.md @@ -38,5 +38,5 @@ since cutting segments from first-frame pts waits on nothing in m1. - [Backport the relay and auth hardening to release](/quest/m0/backport-release-hardening.md) - `release`'s relay refuses dot-segment paths, serves its HTTP routes with main's response hardening, and withdraws advertisements a peer starves of send credit; its auth client refuses redirects - [Release's MKV importer bounds what it buffers](/quest/m0/backport-mkv-buffer.md) - on `release`, an MKV input that declares a huge element and trickles its bytes no longer grows the importer's memory without limit - [HLS export on a declared grid](/quest/m0/hls-media-grid.md) - the catalog's `hls` field and record tracks go away, and the export numbers segments on `media.join.interval` from media tracks -- [quest init keeps moq's nix-wrapped worktree hooks](/quest/m0/quest-worktree-hooks.md) - pin bumps keep the hooks that run moq's pinned `quest`, and PR and workflow worktrees behave under them +- [quest init keeps moq's nix-wrapped worktree hooks](/quest/m0/quest-worktree-hooks.md) - quest pin bumps keep the hooks that run moq's pinned `quest` - [HLS lists contributions](/quest/m0/hls-contributions.md) - an HLS master lists each catalog contribution's renditions, and a contribution's media is subscribed only while players fetch it diff --git a/quest/m0/quest-worktree-hooks.md b/quest/m0/quest-worktree-hooks.md index 1949d9ad67e..7c493b316f7 100644 --- a/quest/m0/quest-worktree-hooks.md +++ b/quest/m0/quest-worktree-hooks.md @@ -2,9 +2,9 @@ ## Goal -moq's Claude Code worktree hooks run the `quest` moq pins, and they survive -quest pin bumps: `quest init` leaves them alone instead of refusing them, and -`--worktree '#123'` and workflow agents behave under them as without them. +moq's Claude Code worktree hooks, which run the `quest` moq pins through nix, +survive quest pin bumps: `quest init` leaves them alone instead of refusing +them. ## Plan @@ -18,22 +18,19 @@ Rejected: relying on an installed `quest`, `direnv exec`, adopting the bare [moq-dev/moq#7674](https://github.com/moq-dev/moq/pull/7674) installed the four hooks as `nix run "${CLAUDE_PROJECT_DIR}#quest" -- worktree hook`. That command takes 0.1–0.5 s warm and 1.5–3 s with a cold nix cache, and builds a new pin in -about 6 s. The PR checked live that it coexists with T3 Code's worktree threads -and isolated delegates. What remains: +about 6 s. It also bumped the pin past +[moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425), so +`--worktree '#123'` starts at the PR head and workflow agents' checkouts get +released, and checked live that the hooks coexist with T3 Code's worktree +threads and isolated delegates. What remains: - `quest init` matches only the literal `quest worktree hook`, so it refuses a wrapped `WorktreeCreate`/`WorktreeRemove` command (exit 1, nothing written) and would add duplicate subagent hooks. Until quest recognizes a wrapped command, a pin bump drops the four entries for its `quest init` run and - restores `.claude/settings.json` afterwards, as AGENTS.md says. Once a - quest release recognizes them, bump the pin, check that `quest init` is a + restores `.claude/settings.json` afterwards, as AGENTS.md says. Once + quest recognizes them, bump the pin, check that `quest init` is a no-op here, and drop that AGENTS.md sentence. -- Bump moq's `quest` input past - [moq-dev/quest#425](https://github.com/moq-dev/quest/pull/425) (merged - 2026-11-03 as `53f78b9`), so `--worktree '#123'` starts at the PR head - instead of `origin/HEAD` and workflow agents' checkouts get released. - Refresh the skill stubs with the AGENTS.md drop-and-restore step, then - check both routes live. ## Waiting From d41d0bca660bef5e728b34c5654e4b0a252dfe38 Mon Sep 17 00:00:00 2001 From: Luke Curley Date: Tue, 3 Nov 2026 11:43:51 -0800 Subject: [PATCH 8/8] chore(quest): wait on moq-dev/quest matching wrapped worktree hooks Record the maintainer's pick: quest init treats any command hook whose arguments end in `worktree hook` as its own. Co-Authored-By: Claude Opus 5.5 --- quest/m0/quest-worktree-hooks.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/quest/m0/quest-worktree-hooks.md b/quest/m0/quest-worktree-hooks.md index 7c493b316f7..50c2c67fd0b 100644 --- a/quest/m0/quest-worktree-hooks.md +++ b/quest/m0/quest-worktree-hooks.md @@ -15,6 +15,12 @@ A host-wide `quest` on `PATH` is acceptable only as a temporary bridge. Rejected: relying on an installed `quest`, `direnv exec`, adopting the bare `quest worktree hook` now, and dropping the quest. +Decided 2026-11-03 (maintainer, on +[moq-dev/moq#7674](https://github.com/moq-dev/moq/pull/7674)): ✅ ask +moq-dev/quest to have `quest init` treat any command hook whose arguments end +in `worktree hook` as its own. Rejected: a configured hook command, and not +asking. + [moq-dev/moq#7674](https://github.com/moq-dev/moq/pull/7674) installed the four hooks as `nix run "${CLAUDE_PROJECT_DIR}#quest" -- worktree hook`. That command takes 0.1–0.5 s warm and 1.5–3 s with a cold nix cache, and builds a new pin in @@ -34,10 +40,7 @@ threads and isolated delegates. What remains: ## Waiting -- Maintainer: ask moq-dev/quest to let `quest init` and `quest uninstall` - recognize a hook command that wraps `quest worktree hook` in a launcher, such - as `nix run #quest -- worktree hook`. Options: (a) recognize any - command hook whose arguments end in `worktree hook` (recommended: no config, - and `quest init` stays idempotent); (b) a configured hook command `quest init` - writes and matches; (c) don't ask, and keep the drop-and-restore step on - every pin bump. +- moq-dev/quest: land `quest init` and `quest uninstall` treating a command + hook whose arguments end in `worktree hook` as Quest's own (being planned + there as of 2026-11-03). Check: with this repository's hooks in place, the + pinned `quest init` exits 0 and leaves `.claude/settings.json` unchanged.