feat!: delete kix, quest.moq.dev, and quest runner

.github/dependabot.yml

@@ -9,12 +9,6 @@ updates:
     groups:
       bun:
         patterns: ["*"]
-    ignore:
-      # Bump by hand once @cloudflare/vitest-plugin's peer range includes the new major.
-      - dependency-name: vitest
-        update-types: ["version-update:semver-major"]
-      # The flake's opencode-client check pins the client to nixpkgs' opencode; bump both together.
-      - dependency-name: "@opencode/client"
   - package-ecosystem: github-actions
     directory: /
     schedule:

CONTRIBUTING.md

@@ -22,8 +22,8 @@ dependencies. `packageManager` in `package.json` names the same Bun for CI
 runners without Nix, and `nix flake check` fails when the two disagree. Without
 Nix, install the tools listed in `flake.nix` and run the same just recipes.
 
-`just test` runs vitest, the shell hook suites, the built CLI's lifecycle check,
-and the Worker tests. `just check` includes TypeScript, formatting, workflow,
+`just test` runs vitest, the shell hook suites, and the built CLI's lifecycle
+check. `just check` includes TypeScript, formatting, workflow,
 shell, and Nix checks in addition to quest validation.
 
 `nix build` builds the package; `nix run -- --help` runs it. `nix flake check`

SETUP.md

@@ -116,7 +116,7 @@ Settings → Actions → General → Workflow permissions to read; move reposito
 secrets, and organization secrets shared with the repository, into
 environments whose deployment branches are limited to protected branches; and
 keep write `permissions:` out of jobs that pull requests and pushes to other
-branches run. kix checks the same settings when a repository enrolls.
+branches run.
 Change settings and workflows only if the user agrees.
 
 Run `quest check`, then suggest next steps: restart the agent session so it

assets/AGENTS.md

@@ -115,10 +115,8 @@ Stop and report a PR that makes the same change; one that only touches the same
 `quest unblocked` ranks the ready quests, and `quest unblocked <path>` prints what blocks one.
 With `--unclaimed`, it skips quests someone holds and lists them on stderr.
 
-Work is taken when it has a live runner lock or an open change on the forge.
-kix.quest records each active job in its database and reassigns a job whose
-runner goes offline. Check those locks and open changes before
-starting. These states stay out of the quest file.
+Work is taken when it has an open change on the forge. Check open changes
+before starting. These states stay out of the quest file.
 
 On GitHub, a quest is claimed by an open PR whose head branch is the quest's
 branch, from the upstream repository or a fork, or by that branch upstream

assets/CONTEXT.md

@@ -96,7 +96,7 @@ Run the repository's checks locally while the PR is a draft; CI may run only on
 
 Before a PR is marked ready for review, and before each push to one that is, a model other than the one that changed it last reviews the committed branch locally, as `/quest-review` describes.
 
-The PR body's `## Models` section records its size as `Size: M` (its quest's, or for a skill's own PR, as a quest is sized) and one `Implementer: Codex, gpt-6.1-sol, high effort` line per implementing session, moved last whenever it pushes; kix records one that pushes to an open PR in its own comment.
+The PR body's `## Models` section records its size as `Size: M` (its quest's, or for a skill's own PR, as a quest is sized) and one `Implementer: Codex, gpt-6.1-sol, high effort` line per implementing session, moved last whenever it pushes.
 Read your model and effort rather than guess, writing `unknown` for any you cannot find: Claude Code knows its model and exports `CLAUDE_EFFORT`, and Codex records `model` and `effort` in the last `turn_context` of `~/.codex/sessions/*/*/*/rollout-*-$CODEX_THREAD_ID.jsonl`.
 
 GitHub gives secrets to workflows on branches pushed to the repository, as quest branches usually are, so keep pull request CI, which runs unreviewed code, read-only: a read-only `GITHUB_TOKEN`, and write credentials only in environments limited to protected branches.

assets/skills/review.md

@@ -22,7 +22,7 @@ If a `## Review` record that `/quest-merge` counts names the committed head, or
 If you judge the change too trivial to review, skip the review instead and record the skip and its reason in `## Review`.
 
 Otherwise, review the committed branch with `quest review --base <remote>/<base>`, which picks a reviewer other than the model that changed it last, and its effort, by the PR's size; `quest review --help` explains the round.
-It reads the latest implementing model, and on a branch that is not a quest's the size, from the PR body's `## Models` record and kix's sessions comment, so write that record before the first round; a quest branch's size is read from its quest.
+It reads the latest implementing model, and on a branch that is not a quest's the size, from the PR body's `## Models` record, so write that record before the first round; a quest branch's size is read from its quest.
 Pass `--exclude-model` or `--size` only for a PR whose body cannot hold the record.
 Where the repository's root instructions name other reviewers, pass them with `--harness`, `--model`, and `--effort`.
 Run it in the foreground; a round takes minutes.

assets/skills/start.md

@@ -9,7 +9,7 @@ The argument is the quest to work on.
 If you are unsure on the best course of action, ask the user for direction.
 
 Confirm you can write in your worktree; if you cannot, stop and report without claiming.
-Update your checkout and check the forge for a live runner lock and for an open PR already doing the quest's work, then claim the quest with `quest start <quest>`.
+Update your checkout and check the forge for an open PR already doing the quest's work, then claim the quest with `quest start <quest>`.
 If it refuses, the quest is blocked or someone else holds it: report what it printed and stop.
 If it warns that the quest's local branch already exists, the claim succeeded: resume that earlier attempt as the guide describes.
 If you cannot pursue a claim before pushing work, release it with `quest start --release <quest>` and remove your isolated worktree; once work is pushed, hand it back as the guide describes.