feat(cli)!: inspect a relay with moq ls and moq fetch

.claude/hooks/submodule.sh

@@ -0,0 +1,20 @@
+#!/usr/bin/env bash
+# The shared skills in .claude/skills are symlinks into the .claude/shared
+# submodule. git leaves that unpopulated in a new worktree, and a dangling
+# symlink is silently skipped. A checkout on the wrong commit stays stale too.
+
+set -eu
+
+# Require an explicit project dir so we never touch a stray checkout.
+[ -n "${CLAUDE_PROJECT_DIR:-}" ] || exit 0
+cd "$CLAUDE_PROJECT_DIR" || exit 0
+
+# '-' is uninitialized. '+' is populated at a commit other than the gitlink.
+# A matching checkout has no prefix.
+case "$(git submodule status .claude/shared 2>/dev/null)" in
+    -* | +*) ;;
+    *) exit 0 ;;
+esac
+
+echo "submodule hook: updating .claude/shared to the pinned skills." >&2
+git submodule update --init .claude/shared >&2

.claude/settings.json

@@ -4,6 +4,10 @@
 		"SessionStart": [
 			{
 				"hooks": [
+					{
+						"type": "command",
+						"command": "${CLAUDE_PROJECT_DIR}/.claude/hooks/submodule.sh"
+					},
 					{
 						"type": "command",
 						"command": "${CLAUDE_PROJECT_DIR}/.claude/hooks/direnv.sh"

.claude/skills/bump

@@ -0,0 +1 @@
+../shared/bump

.claude/skills/clean

@@ -0,0 +1 @@
+../shared/clean

.claude/skills/close

@@ -0,0 +1 @@
+../shared/close

.claude/skills/grill

@@ -0,0 +1 @@
+../shared/grill

.claude/skills/merge

@@ -0,0 +1 @@
+../shared/merge

.claude/skills/peer-review

@@ -0,0 +1 @@
+../shared/peer-review

.claude/skills/plan-quests/SKILL.md

@@ -26,14 +26,15 @@ When the work changes what a user sees (a wire, an API, a flag, a dashboard), as
 When the frontier disagrees with a settled quest/plan, challenge the user and resolve the conflict.
 
 Begin the interview by scoping the goal: the observable outcome, why it matters, and its important boundaries and non-goals.
-Do not move on to implementation decisions until the goal is settled.
+Restate the goal in one sentence and get it confirmed before moving on to implementation decisions.
 If the goal contains independently completable outcomes, split them before planning.
 Map the implementation plan as a design tree: every material decision branches into the decisions that hang off it.
 
 The session is done when the frontier is empty.
 The result may be one quest or multiple quests and questlines, split based on what can be completed independently.
 Prefix each quest title with `[XS]`, `[S]`, `[M]`, `[L]`, or `[XL]`, including implementation, verification, and landing work.
 Once complete, create, update, or delete the relevant quests and questlines.
+Record each settled decision and its reason in the quest's Plan, so later sessions don't ask it again.
 New work joins the milestone matching its priority, at its rank; a questline groups only quests that ship together, and its README holds the work no child owns (the end-to-end test, the docs page).
 
 When done, commit and create a draft PR following `CONTRIBUTING.md`.

.claude/skills/recommended

@@ -0,0 +1 @@
+../shared/recommended

.claude/skills/spawn-merge

@@ -0,0 +1 @@
+../shared/spawn-merge

.claude/skills/spawn-quests/SKILL.md

@@ -10,18 +10,23 @@ If you are unsure of the best course of action, ask the user for clarification b
 
 The scope consists of all ready quests that are not claimed.
 Use the argument (if provided) to filter to specific quests/questlines.
+Main's tree lags its lines: a child finished on its line branch, or on `dev`, still looks ready from `main`.
+Judge readiness from each line branch's own quest directory, and treat a quest deleted on `dev` as done.
 Inspect any blocked quests, and determine if they can be unblocked.
 A line whose `Quests` list has emptied is a ready quest too: finishing it marks the line's PR ready.
 
-One at a time, for each each quest, interactively prompt the user if we should /start-quest, /plan-quests, skip, or delete.
-Include a short summary and your recommendation.
+Recommend an action for each quest: /start-quest, /plan-quests, skip, or delete.
+Start the quests you'd start with no open question right away.
+Interactively prompt the user about the rest, a few per prompt, each with a short summary and your recommendation.
 
 Spawn a background sub-agent for each /start-quest.
 Create a fresh worktree on the base `quest branch` prints, creating that line branch first if it is missing.
 Agents share no writable files: each keeps its scratch files in its own worktree's `.scratch/`, and anything you hand every agent goes in its prompt, not a shared file.
+Each agent blocks on its own checks and reports back only when done or blocked.
 Limit the concurrency to at most N agents in parallel, where N is half the number of physical CPU cores.
+Other sessions share this machine: hold new agents while the load average exceeds the core count.
 
-Monitor the sub-agents and report their final status, but do not monitor their PRs.
+Report each sub-agent's final status, staying silent on interim notifications, but do not monitor their PRs.
 Prompt the user if they want to /plan-quests for any suggested follow-ups.
 
 Run /plan-quests for any selected quests in the foreground.

.claude/skills/takeover

@@ -0,0 +1 @@
+../shared/takeover

.config/nextest.toml

@@ -24,6 +24,18 @@ retries = 0
 # workload once, and the large origin fan-outs take ~20s each for no signal.
 default-filter = "not kind(bench)"
 
+# Every io_uring ring is charged to the user's `RLIMIT_MEMLOCK` (8 MiB by
+# default), a budget shared with every other process that user runs, and
+# desktop apps built on libuv already spend most of it. A worker's ring is
+# ~84 KiB, so a parallel run of tests holding a few workers each exhausts it
+# and fails with `ENOMEM`. Four at a time stays near 1 MiB.
+[[profile.default.overrides]]
+filter = "package(moq-uring) | binary_id(moq-relay::runtime_uring) | (binary_id(moq-relay::embed) & test(/uring/))"
+test-group = "io-uring"
+
+[test-groups]
+io-uring = { max-threads = 4 }
+
 # CI has noisier neighbours and cold caches, so give a test longer before
 # calling it wedged.
 [profile.ci]

.github/workflows/nightly.yml

@@ -77,6 +77,15 @@ jobs:
           nix develop --command bun install --frozen-lockfile
           nix develop --command bun js/net/bench/broadcasts.ts
 
+      # Runs each moq-net Criterion routine once, so a bench that panics (an
+      # unparsable version, a shape that deadlocks) fails here instead of on the
+      # next manual run. Timing is not compared; nextest never runs a
+      # `harness = false` target. `fuzz` enables the announce bench, which the
+      # `'*'` glob otherwise refuses.
+      - name: moq-net benchmark smoke
+        if: ${{ !cancelled() }}
+        run: nix develop --command cargo bench --locked -p moq-net --features fuzz --bench '*' -- --test
+
       - name: Audit
         if: ${{ !cancelled() }}
         run: nix develop --command just rs audit
@@ -224,7 +233,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        target: [lite, ietf, varint, path, pattern]
+        target: [lite, announce, ietf, varint, path, pattern]
     steps:
       - name: Free disk space
         uses: jlumbroso/free-disk-space@54081f138730dfa15788a46383842cd2f914a1be # main

.gitmodules

@@ -0,0 +1,3 @@
+[submodule ".claude/shared"]
+	path = .claude/shared
+	url = https://github.com/kixelated/skills

.remarkignore

@@ -15,3 +15,10 @@ doc/draft/
 
 # Quests use a constrained Markdown dialect checked by the quest validator.
 quest/
+
+# Skills are symlinks into the kixelated/skills submodule, which formats its
+# own files; remark would follow them (and .agents, Codex's link to the same
+# directory) and rewrite the pinned checkout.
+.claude/shared/
+.claude/skills/
+.agents/