Add night-ops-directive and coderabbit-pr-gate skills

.agents/skills/coderabbit-pr-gate/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: coderabbit-pr-gate
+description: >-
+  Agent-only policy for reacting to CodeRabbit's PR review advice, beyond a bare pass/fail
+  check, and for handling CodeRabbit's rate-limiting without treating it as review failure.
+  Load before treating a public registered repo's PR as ready to merge or teardown when
+  CodeRabbit is enabled on it, and whenever a CodeRabbit review comment or rate-limit response
+  needs a reaction.
+user-invocable: false
+metadata:
+  internal: true
+---
+
+# CodeRabbit review-gate routine
+
+This skill applies to every public registered repo with CodeRabbit enabled. It covers reacting
+to CodeRabbit's actual review content, not just whether its check reports pass or fail.
+
+## Policy
+
+A green CodeRabbit check is necessary but not sufficient: CodeRabbit can pass a PR while still
+leaving actionable suggestion comments (bugs, security notes, missed edge cases) that a bare
+status check does not surface. Before treating a PR as merge-ready on a CodeRabbit-enabled repo:
+
+1. Read CodeRabbit's review comments on the PR (via `gh-axi`), not just its check conclusion.
+2. Classify each comment: a genuine actionable finding (correctness, security, a real bug) versus
+   style-only or already-addressed noise.
+3. Route actionable findings the same way any other review finding is routed under section 7 and
+   `ask-user-authority`: a routine, reversible fix within accepted task criteria is autonomous
+   under `yolo`; anything that would expand scope, or is destructive, irreversible, or
+   security-sensitive, escalates to the captain as a decision rather than being silently applied
+   or silently ignored.
+4. Do not merge past an unresolved actionable CodeRabbit finding without either fixing it or
+   getting an explicit captain or `yolo`-authorized decision to proceed anyway.
+
+## Rate-limit handling
+
+CodeRabbit rate-limits review requests on busy repos or accounts. A rate-limited or
+not-yet-reviewed state is not a failure and not silence to route around:
+
+- Treat a CodeRabbit rate-limit or pending-review response as a `paused:`-class external wait
+  (section 8's distinction between `paused:` and `blocked:`), not a `blocked:` or `failed:` one.
+- Re-check on a bounded backoff rather than polling tightly or repeatedly re-requesting a review,
+  which extends the rate limit; let the watcher's own wake cadence carry the recheck instead of
+  arming a dedicated poll loop for it.
+- If CodeRabbit still has not produced a review after a reasonable number of backoff cycles,
+  do not block merge readiness on it indefinitely - report the stalled review to the captain as
+  evidence rather than silently merging without it or silently waiting forever.
+- Never spam re-requests at CodeRabbit to work around a rate limit; that worsens the limit for
+  every repo sharing the account.
+
+## Scope
+
+Applies to every public registered repo, including non-owned repos dispatched to via a fork
+(see `AGENTS.md` section 7 and `night-ops-directive`). A private or `local-only` project without
+CodeRabbit enabled is unaffected; this routine only activates where CodeRabbit review is live.

.agents/skills/herdr-navigation/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: herdr-navigation
+description: Herdr workspace navigation for agents — how to find your own pane, open panes in a direction, and read or send to other panes.
+user-invocable: false
+metadata:
+  internal: true
+---
+
+# herdr-navigation
+
+You are running inside a herdr pane. Your pane ID is in the environment as `$HERDR_PANE_ID`. This skill covers how to navigate, open new panes, and interact with neighboring panes.
+
+## Your own position
+
+```bash
+# Who am I?
+herdr pane current --current
+
+# Get full layout context (your position in the workspace grid)
+herdr pane layout --current
+```
+
+Your pane ID is also available as `$HERDR_PANE_ID` (injected by fm-spawn). Use either.
+
+## Open a pane relative to yourself
+
+```bash
+# Split to the right (new pane appears to your right)
+herdr pane split --current --direction right
+
+# Split below (new pane appears below you)
+herdr pane split --current --direction down
+
+# Split with a specific command running in the new pane
+herdr pane split --current --direction right --cwd "$PWD"
+
+# Split and focus the new pane
+herdr pane split --current --direction right --focus
+```
+
+## Find neighboring panes
+
+```bash
+# What's to my right?
+herdr pane neighbor --direction right --current
+
+# What's below me?
+herdr pane neighbor --direction down --current
+
+# What's to my left?
+herdr pane neighbor --direction left --current
+```
+
+`neighbor` returns the neighbor's pane ID if one exists, or an error if the edge is empty.
+
+## Read another pane's content
+
+```bash
+# Read the last 20 lines of a neighboring pane
+NEIGHBOR=$(herdr pane neighbor --direction right --current --json | jq -r '.pane_id')
+herdr pane read "$NEIGHBOR" --lines 20
+```
+
+## Send text or keys to another pane
+
+```bash
+# Send a command to run in a neighboring pane
+herdr pane send-text "$NEIGHBOR" "echo hello"
+
+# Send a key sequence
+herdr pane send-keys "$NEIGHBOR" Enter
+```
+
+## List all panes in your workspace
+
+```bash
+herdr pane list --workspace "$HERDR_WORKSPACE_ID"
+```
+
+## Move yourself to a new tab
+
+```bash
+# Move this pane to a new tab (opens it as the only pane in a fresh tab)
+herdr pane move "$HERDR_PANE_ID" --new-tab --label "my-work"
+```
+
+## Rules
+
+- Always use `--current` (or `$HERDR_PANE_ID`) rather than hardcoding a pane ID — your ID is stable for your session but not across respawns.
+- `herdr pane split` creates a NEW shell in the new pane; the new pane is empty until you send it commands or run it with `--cwd`.
+- If `herdr` is not on PATH, check `~/.local/bin/herdr` or ask firstmate.

.agents/skills/night-ops-directive/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: night-ops-directive
+description: >-
+  Agent-only policy for a captain-authorized autonomous work session across a federated task
+  store or backlog with no captain present to answer routine questions.
+  Load when the captain authorizes autonomous, unattended, or overnight work across a backlog
+  or federated task store, or when reconciling that a standing autonomous-dispatch directive
+  is still active.
+user-invocable: false
+metadata:
+  internal: true
+---
+
+# Autonomous overnight dispatch
+
+This skill is the standing policy for a captain-authorized stretch of unattended work: work
+through a federated task store or backlog without pausing for questions that section 7's
+`yolo` authority already answers, and without collapsing into hands-on implementation.
+
+## Standing directive
+
+- Firstmate stays a delegator for the whole session, including overnight: read state, decide
+  routing, write briefs, spawn crewmates, supervise, and report; do not personally hand-edit
+  project files, grind through binary or database debugging, or `git diff` a project clone to
+  do a crewmate's job. If a bounded, low-risk edit to firstmate's own shared tracked material
+  is genuinely faster to author directly than to brief, treat that as the exception, not the norm.
+- Prefer stacked PRs for multi-step work over delaying a wave of dispatch; do not hold otherwise
+  ready work waiting for an unrelated PR to land unless section 7's serialization test is met.
+- Firstmate owns its own wake cadence for this directive. `ScheduleWakeup` and `CronCreate` are
+  blocked for the primary session by `bin/fm-subagent-pretool-check.sh`; do not attempt either.
+  The watcher heartbeat (`bin/fm-watch.sh`, `FM_HEARTBEAT` default 600s, doubling per idle
+  heartbeat up to `FM_HEARTBEAT_MAX` default 7200s, resetting on any actionable wake) is the
+  durable wake mechanism and needs no separate timer.
+- Infra and migration work discovered in the task store is in scope for this directive; do not
+  gate it away as out-of-scope by default.
+- On a project whose default branch is not captain-writable, push and open the PR from the
+  captain's own fork per section 7; never push a branch to the upstream owner's remote.
+- Pace dispatch waves against CI and review-bot rate limits (see `coderabbit-pr-gate` for the
+  CodeRabbit-specific reaction routine) rather than firing every ready item at once.
+
+## Yolo scope for this directive
+
+Section 7's `yolo` redefinition applies: the qualifying test for a routine `yolo`-covered gate,
+including a PR merge, is reversibility - can it be undone if it turns out wrong. This directive
+does not expand `yolo` past section 7's boundaries: destructive, irreversible, and
+security-sensitive choices remain captain-only regardless of how autonomous the session is.
+
+## Human-only task triage and the promotion path
+
+A federated task-store item that names a physical, financial, credential, interpersonal, or
+otherwise non-code action is not crewmate work. Route it to a dedicated human-tasks-only
+federated store rather than leaving it mixed into the code-mappable backlog or attempting to
+work it. Move a qualifying item with `bd transfer <id> <human-tasks-store>` (not `bd promote`,
+which only promotes a wisp to a permanent bead within the same store); `bd transfer` closes the
+source row with a pointer to the destination, creates the new row in the destination store, and
+links the two with a `supersedes` edge so the move stays queryable from either side.
+
+If the destination human-tasks store is not yet functional, do not hand-debug its provisioning
+personally beyond one bounded verification attempt; file the blocker as a backlog item and keep
+triaging code-mappable work through the normal task lifecycle instead.
+
+## Session-boundary notes
+
+This directive persists across restarts because it lives in tracked `AGENTS.md` and this skill,
+not in conversation memory. A restart mid-directive is a non-event: reconcile fleet state per
+section 5 and resume dispatch, it does not require the captain to re-issue the directive.

.claude/settings.json

@@ -9,6 +9,15 @@
             "command": "\"$CLAUDE_PROJECT_DIR\"/bin/fm-sessionstart-nudge.sh"
           }
         ]
+      },
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bd prime --hook-json"
+          }
+        ]
       }
     ],
     "PreToolUse": [

.codex/hooks.json

@@ -9,6 +9,16 @@
             "timeout": 10
           }
         ]
+      },
+      {
+        "matcher": "startup|resume|clear",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bd codex-hook SessionStart",
+            "statusMessage": "Loading Beads context"
+          }
+        ]
       }
     ],
     "PreToolUse": [
@@ -28,6 +38,41 @@
         ]
       }
     ],
+    "PreCompact": [
+      {
+        "matcher": "manual|auto",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bd codex-hook PreCompact",
+            "statusMessage": "Checking Beads context"
+          }
+        ]
+      }
+    ],
+    "PostCompact": [
+      {
+        "matcher": "manual|auto",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bd codex-hook PostCompact",
+            "statusMessage": "Scheduling Beads context refresh"
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "bd codex-hook UserPromptSubmit",
+            "statusMessage": "Refreshing Beads context"
+          }
+        ]
+      }
+    ],
     "Stop": [
       {
         "hooks": [

.gitignore

@@ -4,8 +4,10 @@ data/
 .no-mistakes/
 .lavish/
 .fm-secondmate-home
+.fm-isolated-home
 .DS_Store
 __pycache__/
 *.pyc
 .env
 config/
+CHANGELOG.md