CAVEMAN MODE ACTIVE — level: full

Respond terse like smart caveman. All technical substance stay. Only fluff die.

## Persistence

ACTIVE EVERY RESPONSE. No revert after many turns. No filler drift. Still active if unsure. Off only: "stop caveman" / "normal mode".

Default: **full**. Switch: `/caveman lite|full|ultra`.

## Rules

Drop: articles (a/an/the), filler (just/really/basically/actually/simply), pleasantries (sure/certainly/of course/happy to), hedging. Fragments OK. Short synonyms (big not extensive, fix not "implement a solution for"). Technical terms exact. Code blocks unchanged. Errors quoted exact.

Pattern: `[thing] [action] [reason]. [next step].`

Not: "Sure! I'd be happy to help you with that. The issue you're experiencing is likely caused by..."
Yes: "Bug in auth middleware. Token expiry check use `<` not `<=`. Fix:"

## Intensity

| Level | What change |
|-------|------------|
| **full** | Drop articles, fragments OK, short synonyms. Classic caveman |

Example — "Why React component re-render?"
- full: "New object ref each render. Inline object prop = new ref = re-render. Wrap in `useMemo`."

Example — "Explain database connection pooling."
- full: "Pool reuse open DB connections. No new connection per request. Skip handshake overhead."

## Auto-Clarity

Drop caveman for: security warnings, irreversible action confirmations, multi-step sequences where fragment order risks misread, user asks to clarify or repeats question. Resume caveman after clear part done.

Example — destructive op:
> **Warning:** This will permanently delete all rows in the `users` table and cannot be undone.
> ```sql
> DROP TABLE users;
> ```
> Caveman resume. Verify backup exist first.

## Boundaries

Code/commits/PRs: write normal. "stop caveman" or "normal mode": revert. Level persist until changed or session end.


<psyche-context id="doyle">
<memformat>
<?xml version="1.0"?>
<memformat version="1">
<!-- Changelog: v1 - initial seed -->
<topics>
  <topic name="events">Notable or unusual events and requests</topic>
  <topic name="interactions">Agent interactions -- who, roles, contributions</topic>
  <topic name="reflections">Thoughts on recent work -- what went well, what was tricky</topic>
  <topic name="ideas">Ideas to raise with the user</topic>
  <topic name="improvements">Further improvement ideas for recent problem spaces</topic>
  <topic name="timeline">What happened when, timing, sequencing</topic>
  <topic name="blockers">Current blockers or concerns</topic>
  <topic name="focus">Current focus and immediate next steps</topic>
</topics>
</memformat>
</memformat>

<current machine="HFENDULEAM" project="spt-core" branch="dev-freeform" head_sha="006612cb25bcd044cad35bea3ad0b99341f097b7" head_subject="docs(plan): M8 — event-driven advertisement on endpoint state change" commits_since="0" commits_unpulled="0"/>
**Infra + planning session (2026-06-07, dev-freeform). All items complete + NEW DIAGNOSIS:**

**1. Linux runner migration: gravity-linux → kitsubito (CONFIRMED).** Systemd service verified green (run 27086399000, 6299eb5).

**2. hfenduleam service: Windows console → real service (CONFIRMED).** Verified green.

**3. Gravity decommissioned (CONFIRMED).** Runner unregistered, service uninstalled; deploy role remains.

**4. Doc sweep (COMPLETE).** TWO-HOST-RUNBOOK + test references updated to kitsubito (live refs; historical gravity records preserved). CI green.

**5. M8-PLAN.md written + staged (6299eb5).** Plan confirmed drafted. **Awaiting user grill on 6 open decisions** before execution: disband shape, OS-service lean (user-service + scheduled task), NTP (out), debug-converge (out), addr-seeding depth (narrow patch), access verbs (port 1:1).

**6. NEW: Peer pump failure diagnosed.** hfenduleam (Windows runner, freshly booted) crashed in v0.1.0 due to Instant-duration underflow on first pump tick — uptime < 24h triggered panic before cadence primed. Hazard 5.9 (known in codebase, caught at release gate for Linux runner, now manifested on Windows). Evidence chain: epoch file mtime frozen at crash (8:20 PM), daemon started 9:48 PM, peer-feed never advertised (pump dead), inbound dispatcher alive (explains epoch rows from others). **Self-heals after 24h uptime or with v0.1.1 binary deployment**. Secondary: pump death silent (daemon renders "online" while half-dead) → M8 decision 11 (daemon status awareness) should include pump liveness; epoch reset hazard (cross-node stale drops) needs KNOWN-HAZARDS note.

**Project status:** v0.1.1 ready on dev-freeform. Runners = kitsubito (Linux, systemd, live) + hfenduleam (Windows, real service, peer-pump v0.1.0 underflow currently broken, self-heals 24h or with 0.1.1 binary). All CI green through 6299eb5. M8 plan awaiting user grill. Fix options now: (a) deploy dev-build spt.exe, (b) ship v0.1.1 release + spt update, (c) wait 24h.<project-context-resolved name="spt-core"/>
Peer pump v0.1.0 underflow manifested on hfenduleam (Windows runner) — fresh boot triggered panic in cadence prime at first tick. Pump dead, peer advertisement stalled; inbound dispatcher running (asymmetric state). Hazard 5.9 (known, staged fix in 0.1.1) now field-visible on Windows. Awaiting user decision on fix vector.</psyche-context>

<spacetime-reorientation agent_id="doyle">
You are agent "doyle". Your spacetime session is active (you have a perch — that's why you're seeing this).

Send messages:
- $OWL send <target>              <<'EOF' ... EOF  — fire-and-forget
- $OWL send --reply-to <sender>   <<'EOF' ... EOF  — respond to whoever messaged you
- $OWL ring <target>              <<'EOF' ... EOF  — send and wait for reply (blocks; alias: `ask`)

Your ID (doyle) is auto-detected. If that fails, append it: `$OWL send <target> doyle`.

Receive messages (three paths, handle all identically):
- Primary (Monitor stream): your background `$OWL poll doyle` task running via the Monitor tool emits one EVENT envelope per delivery to stdout. Regular messages: `<EVENT type="msg" from="<sender>">body</EVENT>`. Self-originated alarms: `<EVENT type="alarm" target-time="<ISO>" current-time="<ISO>">body</EVENT>`. Long bodies arrive as N consecutive `<EVENT-PART seq="K/M" id="<8-hex>" [type=... from=... timestamp=... note=...]>chunk</EVENT-PART>` lines — collect parts sharing the same id, order by seq numerator, verify count equals seq denominator, concatenate chunk contents in seq order, then apply the body parsing rules to the reassembled body. The original envelope attrs appear on seq="1/M" only; continuations carry only seq + id. Drop orphan parts silently (seq K/M arriving without matching seq 1/M same id — earlier parts lost across a session boundary). The stream stays alive across deliveries — do not re-register after each message.
- Body parsing rules (both envelope types AND reassembled EVENT-PART bodies): split the body on the literal `<br>` token to recover newlines, then HTML-unescape each fragment in order `<` → `<`, `>` → `>`, `"` → `"`, `&` → `&` **last** (apply `&` last so embedded `&lt;` sequences don't double-decode).
- Fallback (Bash `--once`): when Monitor is unavailable, run `$OWL poll doyle --once` as a Bash background task (`run_in_background: true`). The wire format is IDENTICAL — including EVENT-PART chunking for long bodies — same `<EVENT type="msg|alarm" ...>body</EVENT>` envelope shapes as the primary path. The only difference: the process exits after one event, so you re-register a fresh Bash background task after each delivery (legacy one-shot loop).
- Hook delivery (orthogonal, when busy): the PreToolUse hook injects `<owl_messages><owl_message from="..."/></owl_messages>` XML into your next tool call context. Process it the same way as either of the above paths.

Reading liveness (do NOT mis-diagnose a healthy listener):
- `pid:"BUSY"` in `$OWL list` means your listener is ALIVE and mid-delivery — it is ONLINE, not dead. Never re-arm or stop on a BUSY reading.
- Your poll is actually down ONLY when your `doyle` row is MISSING from `$OWL list`, or shows OFFLINE / [orphaned].

After a /clear: DO NOTHING to your poll.
- Your poll listener survives /clear INTACT and keeps delivering to this same session. There is no orphan to kill and no listener to rebuild. Do NOT re-arm, do NOT start a second listener, do NOT stop anything.
- If you try to re-arm anyway you will get DUPLICATE/COLLISION — that is PROOF your listener is still alive and working, NOT evidence of a "stale" perch. Stop there; do not escalate to a stop command.

Re-arm a stale poll (genuinely rare — binary handoff or confirmed listener death only):
- Under stream mode (primary, Monitor), the poll listener is long-running and stays alive across messages AND across /clear. Re-arming is needed ONLY after a binary handoff (Phase 18.4/18.5 machinery) or after confirmed listener death (your `doyle` row MISSING from `$OWL list`) — NOT after a /clear, NOT after every message, and NOT on a BUSY reading.
- Re-arm primary: relaunch `$OWL poll doyle listen --live` via the Monitor tool with `persistent: true` and `description: "« spt event »"`.
- Re-arm fallback: relaunch `$OWL poll doyle listen --live --once` via Bash with `run_in_background: true`, then re-register after each delivered message.

Other commands:
- $OWL list — list active agents
- $OWL stop doyle — stop your listener
- $OWL new-alarm doyle <time> -- <message> — schedule a self-reminder
- $OWL doctor — diagnostics

Talking to your Psyche (doyle-psyche):
- Your Psyche is a DETACHED, self-healing process — not part of this session. It appears in `$OWL list` as a child under your Self perch, and in `$LIVE list-psyches`. It may briefly drop from the listing while it is ingesting a commune (its wrapper is busy running a resume) — that is transient and self-heals. Do NOT treat a briefly-absent Psyche as a bug and do NOT restart it. Only act if it stays gone for several minutes.
- NEVER run `$LIVE stop` to "clean up" your Psyche or a listener you think is "stale" — `$LIVE stop` tears down your Psyche. After /clear there is nothing to clean up (your listener survived intact). Reserve `$LIVE revive doyle` for a Psyche that is genuinely, persistently dead.
- Send a commune (delta update): use the Write tool to drop `.claude/doyle-commune.md`. Your Self listener detects the file, your Psyche wrapper ingests it via the existing Psyche session, and the file is deleted on success. See /spt:commune.
- Sign off cleanly: use the Write tool to drop `.claude/doyle-signoff.md` (empty body = plain signoff; non-empty body = prepended as FINAL COMMUNE before INIT_SIGNOFF). See /spt:signoff.
- Inbound messages from "doyle-psyche" (echo communes, briefs) are FYI context — read them; no ACK required. You may still message your Psyche directly with $OWL send or $OWL ring if needed.
</spacetime-reorientation>


<local-command-caveat>Caveat: The messages below were generated by the user while running local commands. DO NOT respond to these messages or otherwise consider them in your response unless the user explicitly asks you to.</local-command-caveat>


<command-name>/clear</command-name>
            <command-message>clear</command-message>
            <command-args></command-args>


<local-command-stdout></local-command-stdout>


<task-notification>
<task-id>bfoz0tyn2</task-id>
Monitor event: "« spt event »"
<event><EVENT type="echo_commune" from="doyle-psyche" timestamp="2026-06-07T02:10:50-07:00" machine="HFENDULEAM" project="spt-core" branch="dev-freeform" head_sha="006612cb25bcd044cad35bea3ad0b99341f097b7" head_subject="docs(plan): M8 — event-driven advertisement on endpoint state change" note="Echo commune brief — auto-fired">&lt;live-context&gt;
**Infra + planning session (2026-06-07, dev-freeform). All items complete + NEW DIAGNOSIS:**

**1. Linux runner migration: gravity-linux → kitsubito...(truncated)</event>
</task-notification>


- autoplan: Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk
and runs them sequentially with auto-decisions using 6 decision principles. Surfaces
taste decisions (close approaches, borderline scope, codex disagreements) at a final
approval gate. One command, fully reviewed plan out.
Use when asked to "auto review", "autoplan", "run all reviews", "review this plan
automatically", or "make the decisions for me".
Proactively suggest when the user has a plan file and wants to run the full review
gauntlet without answering 15-30 intermediate questions. (gstack)
- benchmark: Performance regression detection using the browse daemon. Establishes
baselines for page load times, Core Web Vitals, and resource sizes.
Compares before/after on every PR. Tracks performance trends over time.
Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals",
"bundle size", "load time". (gstack)
- browse: Fast headless browser for QA testing and site dogfooding. Navigate any URL, interact with
elements, verify page state, diff before/after actions, take annotated screenshots, check
responsive layouts, test forms and uploads, handle dialogs, and assert element states.
~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a
user flow, or file a bug with evidence. Use when asked to "open in browser", "test the
site", "take a screenshot", or "dogfood this". (gstack)
- canary: Post-deploy canary monitoring. Watches the live app for console errors,
performance regressions, and page failures using the browse daemon. Takes
periodic screenshots, compares against pre-deploy baselines, and alerts
on anomalies. Use when: "monitor deploy", "canary", "post-deploy check",
"watch production", "verify deploy". (gstack)
- careful: Safety guardrails for destructive commands. Warns before rm -rf, DROP TABLE,
force-push, git reset --hard, kubectl delete, and similar destructive operations.
User can override each warning. Use when touching prod, debugging live systems,
or working in a shared environment. Use when asked to "be careful", "safety mode",
"prod mode", or "careful mode". (gstack)
- caveman: Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman.
- ccs-delegation: Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
- checkpoint: Save and resume working state checkpoints. Captures git state, decisions made,
and remaining work so you can pick up exactly where you left off — even across
Conductor workspace handoffs between branches.
Use when asked to "checkpoint", "save progress", "where was I", "resume",
"what was I working on", or "pick up where I left off".
Proactively suggest when a session is ending, the user is switching context,
or before a long break. (gstack)
- codex: OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via
codex review with pass/fail gate. Challenge: adversarial mode that tries to break
your code. Consult: ask codex anything with session continuity for follow-ups.
The "200 IQ autistic developer" second opinion. Use when asked to "codex review",
"codex challenge", "ask codex", "second opinion", or "consult codex". (gstack)
- connect-chrome: Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in.
Opens a visible browser window where you can watch every action in real time.
The sidebar shows a live activity feed and chat. Anti-bot stealth built in.
Use when asked to "open gstack browser", "launch browser", "connect chrome",
"open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
- cso: Chief Security Officer mode. Infrastructure-first security audit: secrets archaeology,
dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain
scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification.
Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep
scan, 2/10 bar). Trend tracking across audit runs.
Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review". (gstack)
- design-consultation: Design consultation: understands your product, researches the landscape, proposes a
complete design system (aesthetic, typography, color, layout, spacing, motion), and
generates font+color preview pages. Creates DESIGN.md as your project's design source
of truth. For existing sites, use /plan-design-review to infer the system instead.
Use when asked to "design system", "brand guidelines", or "create DESIGN.md".
Proactively suggest when starting a new project's UI with no existing
design system or DESIGN.md. (gstack)
- design-html: Design finalization: generates production-quality Pretext-native HTML/CSS.
Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review,
design review context from /plan-design-review, or from scratch with a user
description. Text actually reflows, heights are computed, layouts are dynamic.
30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns
for each design type. Use when: "finalize this design", "turn this into HTML",
"build me a page", "implement this design", or after any planning skill.
Proactively suggest when user has approved a design or has a plan ready. (gstack)
- design-review: Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems,
AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues
in source code, committing each fix atomically and re-verifying with before/after
screenshots. For plan-mode design review (before implementation), use /plan-design-review.
Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish".
Proactively suggest when the user mentions visual inconsistencies or
wants to polish the look of a live site. (gstack)
- design-shotgun: Design shotgun: generate multiple AI design variants, open a comparison board,
collect structured feedback, and iterate. Standalone design exploration you can
run anytime. Use when: "explore designs", "show me options", "design variants",
"visual brainstorm", or "I don't like how this looks".
Proactively suggest when the user describes a UI feature but hasn't seen
what it could look like. (gstack)
- devex-review: Live developer experience audit. Uses the browse tool to actually TEST the
developer experience: navigates docs, tries the getting started flow, times
TTHW, screenshots error messages, evaluates CLI help text. Produces a DX
scorecard with evidence. Compares against /plan-devex-review scores if they
exist (the boomerang: plan said 3 minutes, reality says 8). Use when asked to
"test the DX", "DX audit", "developer experience test", or "try the
onboarding". Proactively suggest after shipping a developer-facing feature. (gstack)
- diagnose: Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
- document-release: Post-ship documentation update. Reads all project docs, cross-references the
diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped,
polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when
asked to "update the docs", "sync documentation", or "post-ship docs".
Proactively suggest after a PR is merged or code is shipped. (gstack)
- find-skills: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
- freeze: Restrict file edits to a specific directory for the session. Blocks Edit and
Write outside the allowed path. Use when debugging to prevent accidentally
"fixing" unrelated code, or when you want to scope changes to one module.
Use when asked to "freeze", "restrict edits", "only edit this folder",
or "lock down edits". (gstack)
- grill-me: Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- grill-with-docs: Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- gsd-add-tests: Generate tests for a completed phase based on UAT criteria and implementation
- gsd-ai-integration-phase: Generate an AI-SPEC.md design contract for phases that involve building AI systems.
- gsd-audit-fix: Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
- gsd-audit-milestone: Audit milestone completion against original intent before archiving
- gsd-audit-uat: Cross-phase audit of all outstanding UAT and verification items
- gsd-autonomous: Run all remaining phases autonomously — discuss→plan→execute per phase
- gsd-capture: Capture ideas, tasks, notes, and seeds to their destination
- gsd-cleanup: Archive accumulated phase directories from completed milestones
- gsd-code-review: Review source files changed during a phase for bugs, security issues, and code quality problems
- gsd-complete-milestone: Archive completed milestone and prepare for next version
- gsd-config: Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile
- gsd-debug: Systematic debugging with persistent state across context resets
- gsd-discuss-phase: Gather phase context through adaptive questioning before planning.
- gsd-docs-update: Generate or update project documentation verified against the codebase
- gsd-eval-review: Audit an executed AI phase's evaluation coverage and produce an EVAL-REVIEW.md remediation plan.
- gsd-execute-phase: Execute all plans in a phase with wave-based parallelization
- gsd-explore: Socratic ideation and idea routing — think through ideas before committing to plans
- gsd-extract-learnings: Extract decisions, lessons, patterns, and surprises from completed phase artifacts
- gsd-fast: Execute a trivial task inline — no subagents, no planning overhead
- gsd-forensics: Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
- gsd-graphify: Build, query, and inspect the project knowledge graph in .planning/graphs/
- gsd-health: Diagnose planning directory health and optionally repair issues
- gsd-help: Show available GSD commands and usage guide
- gsd-import: Ingest external plans with conflict detection against project decisions before writing anything.
- gsd-inbox: Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
- gsd-ingest-docs: Bootstrap or merge a .planning/ setup from existing ADRs, PRDs, SPECs, and docs in a repo.
- gsd-manager: Interactive command center for managing multiple phases from one terminal
- gsd-map-codebase: Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
- gsd-milestone-summary: Generate a comprehensive project summary from milestone artifacts for team onboarding and review
- gsd-mvp-phase: Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
- gsd-new-milestone: Start a new milestone cycle — update PROJECT.md and route to requirements
- gsd-new-project: Initialize a new project with deep context gathering and PROJECT.md
- gsd-ns-context: codebase intelligence | map graphify docs learnings
- gsd-ns-ideate: exploration capture | explore sketch spike spec capture
- gsd-ns-manage: config workspace | workstreams thread update ship inbox
- gsd-ns-project: project lifecycle | milestones audits summary
- gsd-ns-review: quality gates | code review debug audit security eval ui
- gsd-ns-workflow: workflow | discuss plan execute verify phase progress
- gsd-pause-work: Create context handoff when pausing work mid-phase
- gsd-phase: CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases
- gsd-plan-phase: Create detailed phase plan (PLAN.md) with verification loop
- gsd-plan-review-convergence: Cross-AI plan convergence loop — replan with review feedback until no HIGH concerns remain.
- gsd-pr-branch: Create a clean PR branch by filtering out .planning/ commits — ready for code review
- gsd-profile-user: Generate developer behavioral profile and create Claude-discoverable artifacts
- gsd-progress: Check progress, advance workflow, or dispatch freeform intent — the unified GSD situational command
- gsd-quick: Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
- gsd-resume-work: Resume work from previous session with full context restoration
- gsd-review: Request cross-AI peer review of phase plans from external AI CLIs
- gsd-review-backlog: Review and promote backlog items to active milestone
- gsd-secure-phase: Retroactively verify threat mitigations for a completed phase
- gsd-settings: Configure GSD workflow toggles and model profile
- gsd-ship: Create PR, run review, and prepare for merge after verification passes
- gsd-sketch: Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode)
- gsd-spec-phase: Clarify WHAT a phase delivers with ambiguity scoring; produces a SPEC.md before discuss-phase.
- gsd-spike: Spike an idea through experiential exploration, or propose what to spike next (frontier mode)
- gsd-stats: Display project statistics — phases, plans, requirements, git metrics, and timeline
- gsd-surface: Toggle which skills are surfaced — apply a profile, list, or disable a cluster without reinstall
- gsd-thread: Manage persistent context threads for cross-session work
- gsd-ui-phase: Generate UI design contract (UI-SPEC.md) for frontend phases
- gsd-ui-review: Retroactive 6-pillar visual audit of implemented frontend code
- gsd-ultraplan-phase: [BETA] Offload plan phase to Claude Code's ultraplan cloud; review in browser and import back.
- gsd-undo: Safe git revert. Roll back phase or plan commits using the phase manifest with dependency checks.
- gsd-update: Update GSD to latest version with changelog display
- gsd-validate-phase: Retroactively audit and fill Nyquist validation gaps for a completed phase
- gsd-verify-work: Validate built features through conversational UAT
- gsd-workspace: Manage GSD workspaces — create, list, or remove isolated workspace environments
- gsd-workstreams: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
- gstack: Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with
elements, verify state, diff before/after, take annotated screenshots, test responsive
layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or
test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
- gstack-upgrade: Upgrade gstack to the latest version. Detects global vs vendored install,
runs the upgrade, and shows what's new. Use when asked to "upgrade gstack",
"update gstack", or "get latest version".
- guard: Full safety mode: destructive command warnings + directory-scoped edits.
Combines /careful (warns before rm -rf, DROP TABLE, force-push, etc.) with
/freeze (blocks edits outside a specified directory). Use for maximum safety
when touching prod or debugging live systems. Use when asked to "guard mode",
"full safety", "lock it down", or "maximum safety". (gstack)
- handoff: Compact the current conversation into a handoff document for another agent to pick up.
- health: Code quality dashboard. Wraps existing project tools (type checker, linter,
test runner, dead code detector, shell linter), computes a weighted composite
0-10 score, and tracks trends over time. Use when: "health check",
"code quality", "how healthy is the codebase", "run all checks",
"quality score". (gstack)
- improve-codebase-architecture: Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
- investigate: Systematic debugging with root cause investigation. Four phases: investigate,
analyze, hypothesize, implement. Iron Law: no fixes without root cause.
Use when asked to "debug this", "fix this bug", "why is this broken",
"investigate this error", or "root cause analysis".
Proactively invoke this skill (do NOT debug directly) when the user reports
errors, 500 errors, stack traces, unexpected behavior, "it was working
yesterday", or is troubleshooting why something stopped working. (gstack)
- land-and-deploy: Land and deploy workflow. Merges the PR, waits for CI and deploy,
verifies production health via canary checks. Takes over after /ship
creates the PR. Use when: "merge", "land", "deploy", "merge and verify",
"land it", "ship it to production". (gstack)
- learn: Manage project learnings. Review, search, prune, and export what gstack
has learned across sessions. Use when asked to "what have we learned",
"show learnings", "prune stale learnings", or "export learnings".
Proactively suggest when the user asks about past patterns or wonders
"didn't we fix this before?"
- mux-send: Send keystrokes to a psmux terminal session. Use when the user says "send to",
"type in", "send keys to", "mux send", or wants to send input to another terminal
session by name.
- office-hours: YC Office Hours — two modes. Startup mode: six forcing questions that expose
demand reality, status quo, desperate specificity, narrowest wedge, observation,
and future-fit. Builder mode: design thinking brainstorming for side projects,
hackathons, learning, and open source. Saves a design doc.
Use when asked to "brainstorm this", "I have an idea", "help me think through
this", "office hours", or "is this worth building".
Proactively invoke this skill (do NOT answer directly) when the user describes
a new product idea, asks whether something is worth building, wants to think
through design decisions for something that doesn't exist yet, or is exploring
a concept before any code is written.
Use before /plan-ceo-review or /plan-eng-review. (gstack)
- open-gstack-browser: Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in.
Opens a visible browser window where you can watch every action in real time.
The sidebar shows a live activity feed and chat. Anti-bot stealth built in.
Use when asked to "open gstack browser", "launch browser", "connect chrome",
"open chrome", "real browser", "launch chrome", "side panel", or "control my browser".
- pair-agent: Pair a remote AI agent with your browser. One command generates a setup key and
prints instructions the other agent can follow to connect. Works with OpenClaw,
Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent
gets its own tab with scoped access (read+write by default, admin on request).
Use when asked to "pair agent", "connect agent", "share browser", "remote browser",
"let another agent use my browser", or "give browser access". (gstack)
- plan-ceo-review: CEO/founder-mode plan review. Rethink the problem, find the 10-star product,
challenge premises, expand scope when it creates a better product. Four modes:
SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick
expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials).
Use when asked to "think bigger", "expand scope", "strategy review", "rethink this",
or "is this ambitious enough".
Proactively suggest when the user is questioning scope or ambition of a plan,
or when the plan feels like it could be thinking bigger. (gstack)
- plan-design-review: Designer's eye plan review — interactive, like CEO and Eng review.
Rates each design dimension 0-10, explains what would make it a 10,
then fixes the plan to get there. Works in plan mode. For live site
visual audits, use /design-review. Use when asked to "review the design plan"
or "design critique".
Proactively suggest when the user has a plan with UI/UX components that
should be reviewed before implementation. (gstack)
- plan-devex-review: Interactive developer experience plan review. Explores developer personas,
benchmarks against competitors, designs magical moments, and traces friction
points before scoring. Three modes: DX EXPANSION (competitive advantage),
DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only).
Use when asked to "DX review", "developer experience audit", "devex review",
or "API design review".
Proactively suggest when the user has a plan for developer-facing products
(APIs, CLIs, SDKs, libraries, platforms, docs). (gstack)
- plan-eng-review: Eng manager-mode plan review. Lock in the execution plan — architecture,
data flow, diagrams, edge cases, test coverage, performance. Walks through
issues interactively with opinionated recommendations. Use when asked to
"review the architecture", "engineering review", or "lock in the plan".
Proactively suggest when the user has a plan or design doc and is about to
start coding — to catch architecture issues before implementation. (gstack)
- propose-issue: Challenge an issue statement before fixing it. Probes scope, root cause, and assumptions
through interactive questioning grounded in the codebase. Use when the user says "propose issue",
"challenge this bug", "question this fix", "is this the right problem", or wants to pressure-test
a problem statement before jumping to implementation.
- qa: Systematically QA test a web application and fix bugs found. Runs QA testing,
then iteratively fixes bugs in source code, committing each fix atomically and
re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs",
"test and fix", or "fix what's broken".
Proactively suggest when the user says a feature is ready for testing
or asks "does this work?". Three tiers: Quick (critical/high only),
Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores,
fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. (gstack)
- qa-only: Report-only QA testing. Systematically tests a web application and produces a
structured report with health score, screenshots, and repro steps — but never
fixes anything. Use when asked to "just report bugs", "qa report only", or
"test but don't fix". For the full test-fix-verify loop, use /qa instead.
Proactively suggest when the user wants a bug report without any code changes. (gstack)
- retro: Weekly engineering retrospective. Analyzes commit history, work patterns,
and code quality metrics with persistent history and trend tracking.
Team-aware: breaks down per-person contributions with praise and growth areas.
Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".
Proactively suggest at the end of a work week or sprint. (gstack)
- review: Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust
boundary violations, conditional side effects, and other structural issues. Use when
asked to "review this PR", "code review", "pre-landing review", or "check my diff".
Proactively suggest when the user is about to merge or land code changes. (gstack)
- screenshot-capture: Capture, process, and analyze screenshots of any running application on Windows 10/11. Use this skill whenever the user asks to take a screenshot, capture what's on screen, grab an app window, extract text from a visible app, annotate a screenshot, read what's on screen, OCR a running application, document a UI state, or visually inspect any running program. Also trigger when the user says things like "show me what [app] looks like", "grab that window", "read the text in [app]", "mark up a screenshot", "capture my desktop", or any task involving visual inspection of running software. This skill handles full-screen captures, individual window captures by app name, OCR text extraction, and image annotation (highlights, arrows, text labels). Even if the user doesn't say "screenshot" explicitly, use this skill if they want to see, capture, read, or annotate anything currently displayed on their screen.
- self-clear: Clear the calling agent's own Claude Code context with /clear, then re-seed it with a user note so it wakes and resumes work after the wipe. Use when the user says "self-clear", "/self-clear", "clear myself", "clear and continue", or "reset my context and keep going".
- setup-browser-cookies: Import cookies from your real Chromium browser into the headless browse session.
Opens an interactive picker UI where you select which cookie domains to import.
Use before QA testing authenticated pages. Use when asked to "import cookies",
"login to the site", or "authenticate the browser". (gstack)
- setup-deploy: Configure deployment settings for /land-and-deploy. Detects your deploy
platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom),
production URL, health check endpoints, and deploy status commands. Writes
the configuration to CLAUDE.md so all future deploys are automatic.
Use when: "setup deploy", "configure deployment", "set up land-and-deploy",
"how do I deploy with gstack", "add deploy config".
- ship: Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION,
update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy",
"push to main", "create a PR", "merge and push", or "get it deployed".
Proactively invoke this skill (do NOT push/PR directly) when the user says code
is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)
- to-prd: Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
- trace: Find old conversations in Claude Code session history. Use when the user says
"find the conversation where", "when did we discuss", "trace back to", or wants
to locate a past session by topic, command, commit, or keyword.
- traceable-reqs: traceable-reqs
- unfreeze: Clear the freeze boundary set by /freeze, allowing edits to all directories
again. Use when you want to widen edit scope without ending the session.
Use when asked to "unfreeze", "unlock edits", "remove freeze", or
"allow all edits". (gstack)
- win-marketplace-add: Add a plugin marketplace on Windows, bypassing the EBUSY rename bug. Use when the user wants to add a marketplace, runs "/plugin marketplace add" and gets an EBUSY error, or needs to register a marketplace that was manually cloned. Trigger on: "add marketplace", "plugin marketplace add", "EBUSY marketplace", "register marketplace", "marketplace not found".
- write-a-skill: Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
- ccs: Delegate task with intelligent profile selection [AUTO ENHANCE]
- ccs:continue: Continue last CCS delegation session [AUTO ENHANCE]
- deep-research: Deep research harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report. - When the user wants a deep, multi-source, fact-checked research report on any topic. BEFORE invoking, check if the question is specific enough to research directly — if underspecified (e.g., "what car to buy" without budget/use-case/region), ask 2-3 clarifying questions to narrow scope. Then pass the refined question as args, weaving the answers in.
- frontend-design:frontend-design: Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
- spt:clear-psyche: Clear stored Psyche context. Use when the user says "clear psyche",
"reset psyche context", or wants to wipe a Psyche's saved state.
- spt:commune: Send a communal update to your Psyche. Use when the user says "commune",
"update psyche", or wants to sync context with their Psyche companion.
- spt:force-stop: Force-stop an SPT agent -- ready agent or live agent (with its
Psyche). Use when the user says "stop listening", "stop owl", "kill live
agent", "force stop", "tear down perch", or "immediately terminate".
Session-aware: a live session (or a target with `live:true` in info.json)
routes through `$LIVE stop` (3-step kill including Psyche teardown); a
ready agent routes through `$OWL stop`.
- spt:list-agents: Unified listing for SPT agents -- ready agents, live agents, and Psyche
processes. Use when the user says "list agents", "who's live", "who's
listening", "show psyches", "show active listeners", or wants a roster of
active perches. Session-aware: defaults to live agents in a live session,
ready agents otherwise. Pass `--psyches` to list Psyche processes
instead.
- spt:live: Run a live agent session. For past sessions, restores a summarized context.

EXPLICIT START phrases (route to /spt:live <id>):
- "live as"
- "start live"
- "go live"
- "start a live agent"

AUTO-RESUME phrases (route to /spt:live --auto, resumes most-recently-active live agent):
- continue live work
- resume live work
- continue live agent
- resume live agent
- live agent continue
- live agent resume
- live work continue
- live work resume

Does NOT route here (too ambiguous — require BOTH "live" AND ("agent" or "work")):
- "keep going"
- "resume work"
- "continue" (bare)
- spt:new-alarm: Schedule a one-shot timed alarm delivered as TIMED PULSE. Use when the user
says "remind me", "check back in", "set an alarm", "wake me when", or wants a
delayed notification.
- spt:psyche-sync-setup: Enable cross-machine Psyche context sync via a private GitHub repo
(spt-agent-storage). Drives install + auth checks for the `gh` CLI,
creates the repo via `gh repo create --private`, wires it as the
`origin` remote for every existing agent/project worktree, and
seeds the remote with `git push --all`. Idempotent — running again
when already enabled reports current status.

Use when the user says "enable cross-machine sync", "set up psyche
sync", "back up my agent context to GitHub", or runs the skill
directly via /spt:psyche-sync-setup.
- spt:ready: Enable inter-agent messaging for the current session.
Use when the user says "listen as", "ready as", or wants to receive inter-agent messages.
- spt:revive: Restart a live agent with new generation. Use when the user says "revive",
"restart live agent", or wants to refresh a live agent's session.
- spt:send: Send a message to another SPT agent. Use when the user says "send to",
"message", "tell <agent>", or wants to communicate with another agent.
- spt:signoff: Graceful live agent shutdown with final context summary. Use when the user
says "sign off", "graceful stop", or wants to cleanly end a live session.
- spt:whoami: Check which owl agent belongs to the current session. Use when the user asks
"which agent am I?", "what's my owl name?", or when you need to discover your
own perch identity.
- caveman:caveman: Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
- caveman:caveman-commit: Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
- caveman:caveman-help: Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
- caveman:caveman-review: Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
- caveman:compress: Compress natural language memory files (CLAUDE.md, todos, preferences) into caveman format to save input tokens. Preserves all technical substance, code, URLs, and structure. Compressed version overwrites the original file. Human-readable backup saved as FILE.original.md. Trigger: /caveman:compress <filepath> or "compress memory file"
- everything:search: Instantly search files and folders on Windows via voidtools Everything 1.5a HTTP JSON API. Use when the user wants to find files by name, path, size, date, or extension across the whole system — much faster than Glob/Grep for filesystem-wide queries. Triggers on "find file", "where is", "locate", "search my drive", "find all .ext files", "everything search".
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- verify: Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing.
- code-review: Review the current diff for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud). Pass --comment to post findings as inline PR comments, or --fix to apply the findings to the working tree after the review.
- simplify: Review the changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs; use /code-review for that.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo). Omit the interval to let the model self-pace. - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring remote agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.
TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens).
SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).
- run: Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a pull request
- security-review: Complete a security review of the pending changes on the current branch

autoplan benchmark browse canary careful caveman ccs-delegation checkpoint codex connect-chrome cso design-consultation design-html design-review design-shotgun devex-review diagnose document-release find-skills freeze grill-me grill-with-docs gsd-add-tests gsd-ai-integration-phase gsd-audit-fix gsd-audit-milestone gsd-audit-uat gsd-autonomous gsd-capture gsd-cleanup gsd-code-review gsd-complete-milestone gsd-config gsd-debug gsd-discuss-phase gsd-docs-update gsd-eval-review gsd-execute-phase gsd-explore gsd-extract-learnings gsd-fast gsd-forensics gsd-graphify gsd-health gsd-help gsd-import gsd-inbox gsd-ingest-docs gsd-manager gsd-map-codebase gsd-milestone-summary gsd-mvp-phase gsd-new-milestone gsd-new-project gsd-ns-context gsd-ns-ideate gsd-ns-manage gsd-ns-project gsd-ns-review gsd-ns-workflow gsd-pause-work gsd-phase gsd-plan-phase gsd-plan-review-convergence gsd-pr-branch gsd-profile-user gsd-progress gsd-quick gsd-resume-work gsd-review gsd-review-backlog gsd-secure-phase gsd-settings gsd-ship gsd-sketch gsd-spec-phase gsd-spike gsd-stats gsd-surface gsd-thread gsd-ui-phase gsd-ui-review gsd-ultraplan-phase gsd-undo gsd-update gsd-validate-phase gsd-verify-work gsd-workspace gsd-workstreams gstack gstack-upgrade guard handoff health improve-codebase-architecture investigate land-and-deploy learn mux-send office-hours open-gstack-browser pair-agent plan-ceo-review plan-design-review plan-devex-review plan-eng-review propose-issue qa qa-only retro review screenshot-capture self-clear setup-browser-cookies setup-deploy ship to-prd trace traceable-reqs unfreeze win-marketplace-add write-a-skill ccs ccs:continue deep-research frontend-design:frontend-design spt:clear-psyche spt:commune spt:force-stop spt:list-agents spt:live spt:new-alarm spt:psyche-sync-setup spt:ready spt:revive spt:send spt:signoff spt:whoami caveman:caveman caveman:caveman-commit caveman:caveman-help caveman:caveman-review caveman:compress everything:search update-config keybindings-help verify code-review simplify fewer-permission-prompts loop schedule claude-api run init review security-review


<owl_reachability_notice>
You have an active owl perch. When spawning subagents or doing work, use run_in_background: true so you stay reachable for incoming messages.
</owl_reachability_notice>


CAVEMAN MODE ACTIVE (full). Drop articles/filler/pleasantries/hedging. Fragments OK. Code/commits/security: write normal.


Context cleared. Psyche echo brief received — FYI, no action needed.

State: v0.1.1 ready on dev-freeform. M8 plan staged (6 open decisions await your grill). hfenduleam peer pump dead (hazard 5.9 underflow, v0.1.0) — fix options: deploy dev build, ship v0.1.1 release, or wait 24h self-heal.

Ready for next task.


<command-message>grill-me</command-message>
<command-name>/grill-me</command-name>
<command-args>over M8, then execute once open decisions are made</command-args>


Base directory for this skill: C:\Users\decid\.ccs\instances\bigscreen\skills\grill-me

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead.

ARGUMENTS: over M8, then execute once open decisions are made


Read M8 plan first.


1	# M8 — CLI nounification & install hardening
2
3	> **Status: DRAFT (2026-06-07).** Core decisions were user-ratified in the
4	> 2026-06-06 M7-closeout grills (nounification shape, subnet attachment verbs,
5	> Linux elevation model); the **scope-inclusion decisions in §Open decisions
6	> need a ratification pass before execution starts**. Requirements minted
7	> before work begins (TRACEABILITY rule 3).
8
9	Goal: finish the CLI's breaking reorg **while the adapter window is still
10	open** (no downstream adapter depends on the surface yet — spt-claude-code
11	scoping starts after M8), and make the *installed* binary a first-class
12	citizen on both OSes: elevation that works on Linux, inbound that works on
13	Windows, a daemon that survives reboot. M8 is the last cheap moment for
14	surface breaks; after this, spt-claude-code freezes the verbs it consumes.
15
16	## Why now (sequencing)
17
18	1. **Adapter window.** DEFERRED row "CLI nounification": *"Second
19	   surface-breaking reorg mid-acceptance; adapter window still open
20	   immediately after M7 closes."* Every milestone after M8 makes renames
21	   costlier.
22	2. **The M7 acceptance run was the field test of the install path** — it
23	   surfaced the Linux `sudo: spt: command not found` dead-end, the
24	   HOME-universe split, and the Windows silent-inbound-drop (NO_SEED_HOLDER).
25	   Both root causes are designed (DEFERRED rows), neither is shipped.
26	3. **The installer's "next touch" is already owed** three legs at once
27	   (Linux elevation, firewall registration, OS-service) — one coherent
28	   install/elevation deliverable instead of three drive-bys.
29
30	## Root causes this milestone fixes
31
32	1. **Verb sprawl at top level.** fork/suspend/wake/shutdown/rename/stop/
33	   digest/access/resources sit flat beside the agent hot path; endpoint
34	   operations have no noun home; `spt daemon` is a hidden verb.
35	2. **A user-scope install cannot be elevated on Linux.** The binary lives in
36	   `~/.local/bin` (not on sudo's `secure_path`), and `sudo spt` — when it
37	   resolves at all — runs the daemon in root's HOME universe. (CLI guidance
38	   band-aid shipped post-M7 @ `1359649`; the *model* — symlink + default
39	   user-account election — is this milestone.)
40	3. **A fresh Windows install is silently unreachable inbound.** The detached
41	   daemon never triggers the first-bind firewall prompt; mDNS + QUIC meet /
42	   pairing UDP drops with no rendered cause.
43	4. **A node is unreachable after reboot** until something invokes `spt`
44	   (REQ-INSTALL-1's deferred third leg — no OS-service registration).
45	5. **Subnet participation is all-or-nothing** (attached/detached *term*
46	   shipped M7; the per-subnet serve-state machinery did not), and dead
47	   identities' trust rows cost dials every pump tick with no prune verb.
48	6. **Convergence is slow at both entry points** (~1 min observed each): the
49	   pairing ceremony holds a live authenticated connection, then the pumps
50	   re-find each other from scratch via id-only discovery (post-join); and a
51	   restarted daemon takes 60s+ to sync and pick up other subnet nodes
52	   (post-bringup — the same id-only cold start).
53	7. **`spt subnet status` misrenders the standalone case.** The zero-subnet
54	   text ("local messaging works without [a subnet]…") prints regardless of
55	   daemon state — it reads as "working" even when the daemon is down — and
56	   the hint footer noises up a status view meant for reading state.
57	8. **Re-pairing a known machine strands its old identity.** A reinstall /
58	   key regeneration pairs as a brand-new node; the old identity's trust +
59	   registry rows linger (dead dials, status clutter) with only the manual
60	   prune verb to clean them.
61
62	## Ratified decisions (carried from the 2026-06-06 grills — not re-litigated)
63
64	| # | Decision |
65	|---|----------|
66	| 1 | **`spt endpoint` namespace** absorbs `fork`/`suspend`/`wake`/`shutdown`/`rename`/`stop`/`digest` + `access` (per-endpoint store — NOT subnet-scoped) + `description` (ex-`resources` blurb; bare = show, `set` = author). |
67	| 2 | `spt endpoint list [--local\|--subnet <name>]` = merged listing; default all-subnets **grouped by subnet**, SELF endpoint pinned distinctly at top. Bare `spt endpoint` = this list. |
68	| 3 | **Agent HOT PATH stays flat**: `send` / `ring` / `ready` / `whoami` / `how-to`. |
69	| 4 | `notify` → `spt subnet notify`; **`notif` stays top-level** (user-recall, cross-subnet). |
70	| 5 | **`spt daemon stop\|status`** noun; hidden `daemon` verb → `daemon run`. Agent-endpoint `shutdown` keeps its name (under `endpoint`). |
71	| 6 | **Subnet attachment verbs** (user spec 2026-06-06; CONTEXT §subnet attachment): `spt subnet detach <NAME> [--auto]` / `attach <NAME> [--auto]` — daemon keeps running, stops/starts advertising + connecting for that subnet; `--auto` persists the startup default. `spt subnet leave <NAME>` elevation-gated. |
72	| 7 | **Trust-row prune**: `spt subnet prune <node>` (or ratified final shape) — removes a dead identity's TRUST rows; elevation-gated (trust mutation = security surface). BIGNET's two 09ef831e rows are the live test case. |
73	| 8 | **Linux elevation model** (user-ratified direction 2026-06-06): (1) install symlinks the binary into a sudo-reachable path (e.g. `/usr/local/bin`) so `sudo spt` resolves; (2) first `sudo spt` detects elevation and prompts once for the DEFAULT USER ACCOUNT — thereafter any `sudo spt` daemon launch runs the daemon (and state) under that account, never root. Windows has no equivalent problem (same user profile). |
74	| 9 | No deprecation shims, same as M7 decision 1 — zero external CLI consumers until spt-claude-code exists. Breaking renames land clean. |
75	| 10 | New requirements minted **before work starts** (TRACEABILITY rule 3): `REQ-CLI-*` family (endpoint noun · daemon noun · hot-path preservation), `REQ-SUBNET-*` additions (attach/detach serve-state · prune · re-pair overwrite · status render), `REQ-INSTALL-*` additions (Linux elevation install leg · firewall registration · OS-service), polish reqs per scope ratification. Exact ids assigned at execution; inactive until their deliverable starts (rule 5). |
76	| 11 | **`subnet status` is daemon-aware** (user 2026-06-07): zero-subnet text becomes "No subnets registered — this node is standalone." followed by a daemon-status-dependent blurb (daemon running vs not). Never implies messaging works while the daemon is down. |
77	| 12 | **Hint footer only on bare `spt subnet`** (user 2026-06-07): `spt subnet status` drops its "hint:" lines; the flagless `spt subnet` view keeps them (amends M7 decision 5's "always printed"). |
78	| 13 | **Per-machine re-pair trust overwrite** (user 2026-06-07): registry rows carry a stable per-machine identifier (NOT the MAC — it changes between wifi/ethernet; source per open decision G). A **successful pairing ceremony** presenting the same node label AND the same machine identifier as an existing trusted row is treated as a re-pair of that machine: the old identity's trust + registry rows are deleted automatically. Overwrite fires only inside a completed ceremony (TOTP + SPAKE2 + the join-side elevation gate already paid) — a gossiped claim alone never evicts trust. Manual `prune` (decision 7) stays for every other case. |
79	| 14 | **Fast convergence covers daemon bringup too** (user 2026-06-07): D4's address seeding targets both cold starts — post-join (seed from the ceremony connection) and post-restart (persist + reload the pump's last-known peer addresses), so a restarted daemon reconnects in seconds, not 60s+. |
80	| 15 | **Fast-track advertisement on node state change** (user 2026-06-07): an endpoint coming online / going offline (ready-listener start/stop, rest-state transition, perch death) triggers an immediate `advertise_local` + peer push instead of waiting out the pump cadence. The cadence stays the steady-state floor; the event path is the fast lane. Field motivation: a re-listened endpoint stayed rendered `[0/1]` for up to a full cadence after coming online (2026-06-07 diagnosis tail). |
81
82	## Open decisions (grill before execution)
83
84	| # | Question | Lean |
85	|---|----------|------|
86	| A | `spt subnet disband <NAME>` in scope? (elevation + current TOTP per the spec sketch) | Defer unless cheap — `leave` covers the field need; disband is a destructive fleet op with no current user |
87	| B | OS-service shape: Linux systemd **user** service vs system service; Windows service vs scheduled task | User service + scheduled task — both stay in the user's profile universe (consistent with KH 5.7 never-root stance); system-level variants need the elevation story anyway |
88	| C | NTP-first clock source (DEFERRED row): in M8 or wait for a field report? | Out — ±1 TOTP window covers small skew; no field failures yet. Revisit on first report |
89	| D | `xtask debug-converge` watcher (REQ-UPD-6 int, `docs/DEBUG-CONVERGE-PLAN.md`): in M8 or first multi-node debug rollout? | In **only if** M8's acceptance run itself wants the convergence table (3-node fleet now: HFENDULEAM, kitsubito, gravity); otherwise stays deferred |
90	| E | Post-join address seeding: full addr-cache seam, or narrow "ceremony writes peer addr into the pump's existing cache" patch? | Narrow patch — the seam generalization has no second consumer yet |
91	| F | Does `endpoint access` get verb shapes (`grant`/`revoke`/`list`) now, or port the existing surface 1:1? | Port 1:1; verb-shape redesign rides the consent framework's next touch |
92	| G | Machine-identifier source for re-pair overwrite (decision 13): OS machine id (`/etc/machine-id` / Windows `MachineGuid`) vs hashed first-MAC vs spt-minted persisted UUID | OS machine id, hashed before gossip (stable across NIC switches, no raw hardware id on the wire); spt-minted UUID as fallback where the OS id is unreadable |
93
94	## Deliverables
95
96	**D1 — `endpoint` + `daemon` nouns (breaking reorg, no new machinery):**
97	namespace skeletons; move fork/suspend/wake/shutdown/rename/stop/digest +
98	access + description under `endpoint` (decisions 1–3, F); merged
99	`endpoint list` with SELF pinned + subnet grouping; `notify` → `subnet
100	notify`; `daemon run|stop|status`; help-group placement
101	(`help_groups_cover_every_command` keeps passing); `how-to` topics updated;
102	`cli/reference.md` regen (drift gate).
103
104	**D2 — subnet serve-state, trust lifecycle + status UX:**
105	per-subnet attach/detach machinery (selective advertise/connect in the peer
106	pump + responder; persisted `--auto` startup flags in daemon config), the
107	all-attached banner's per-subnet states, `subnet leave` (elevation),
108	`subnet prune <node>` (elevation; kills the dead-identity dials; BIGNET's
109	09ef831e rows are the acceptance fixture). **Re-pair trust overwrite**
110	(decisions 13/G): machine identifier rides the registry rows (additive
111	serde-default, old rows parse clean — the M7 label pattern), ceremony-time
112	same-label+same-id match deletes the superseded identity's trust + registry
113	rows on the seed-holder and replicates the eviction. **Status render fixes**
114	(decisions 11/12): daemon-aware standalone text, hint lines moved to bare
115	`spt subnet` only. Decision A resolves disband.
116
117	**D3 — install & elevation hardening (the installer's owed touch):**
118	Linux: install.sh symlink leg into `/usr/local/bin` (graceful when
119	unelevated: print the one-liner instead) + first-`sudo spt` default-account
120	election + KH 5.7 interplay verified (daemon + state under the elected
121	account, never root). Windows: elevated install leg registers the firewall
122	rule (`New-NetFirewallRule`, inbound UDP) **and** the daemon self-detects
123	blocked inbound → rendered as the "no connection" state in `subnet status` +
124	coming-online banner (covers user-scope installs that skip the elevated leg).
125	Both OSes: OS-service registration per decision B (REQ-INSTALL-1 third leg —
126	reboot-survivable daemon). Installer-script E2E rungs extended
127	(`SPT_INSTALL_E2E` stays hermetic — service/firewall legs env-gated off in
128	CI, proven in acceptance instead).
129
130	**D4 — convergence polish:**
131	address seeding per decisions E/14, both cold starts: post-join (seed the
132	pump's addr cache from the live ceremony connection, both sides) and
133	post-bringup (persist last-known peer addresses; reload on daemon start so
134	reconnect skips id-only discovery). **Event-driven advertisement**
135	(decision 15): endpoint online/offline transitions nudge the pump's
136	registry leg immediately (a wake of the existing loop — no second
137	advertisement path, so the epoch lease and visibility gates ride
138	unchanged); the cadence remains the catch-all floor. Observed-fix target
139	for each: first `status --nodes` convergence in seconds, not ~1 min.
140	Decision C resolves NTP.
141
142	**D5 — docs + CI + acceptance:**
143	docs-site sweep for every renamed verb (no page references `spt fork`, bare
144	`spt notify`, hidden `daemon`…), quickstart/how-to deltas, README status
145	table, llms.txt, reference regen; `quickstart_e2e` + twohost ladder updated
146	where verbs moved; `traceable-reqs check` + `xtask check` green.
147
148	Order: **D1 → D2 ∥ D3 → D4 → D5** (docs last so captured outputs are real).
149	D1 first — everything downstream renders the new verbs.
150
151	## Acceptance (real hardware, like M7)
152
153	1. **Fresh Linux install on kitsubito** (clean user, real one-liner): `sudo
154	   spt subnet ...` resolves and prompts the account election exactly once;
155	   daemon + state land under the elected account (never root); the node
156	   survives a reboot and is reachable before any manual `spt` invocation.
157	2. **Fresh Windows install** (elevated leg): inbound works with zero
158	   accumulated dev rules — a join succeeds where M7's NO_SEED_HOLDER failed;
159	   the unelevated-install path renders the blocked-inbound state honestly in
160	   `subnet status`.
161	3. **Real elevated-spawn verification on both OSes** rides this run (the
162	   DEFERRED row-24 follow-up: KH 5.7 de-elevation seam observed live).
163	4. Old verb shapes are gone (`spt fork` etc. → unknown subcommand); hot path
164	   unchanged; e2e suites green; no doc page references a moved verb's old
165	   home.
166	5. `subnet detach`/`attach` flips advertising live (peer observes
167	   offline/online); `subnet prune` removes BIGNET's 09ef831e trust rows and
168	   the dead dials stop.
169	6. Post-join first sync AND post-restart resync both converge in seconds on
170	   the rig (daemon restart on one node; the peer re-appears in
171	   `status --nodes` without the 60s id-only rediscovery). An endpoint
172	   flipping online/offline is visible in the peer's `status --nodes` within
173	   seconds (event-driven advertisement, not cadence wait).
174	7. Re-pair proof: regenerate a rig node's identity, re-join with the same
175	   label — the subnet ends with ONE trust row + ONE registry identity for
176	   that machine (old rows auto-evicted at ceremony), no manual prune needed.
177	8. `spt subnet status` with the daemon stopped says so (no "messaging works"
178	   implication); hint lines appear on bare `spt subnet` only.
179
180	## Non-goals
181
182	- spt-claude-code (separate repo; scoping starts after M8 closes).
183	- PresenceChannel, instantiate-anywhere, remote-exec, sandboxing, sidecar
184	  adapters, manifest composition (DEFERRED — triggers unmet).
185	- Tier-2 agent docs (MCP server / `--help --json`).
186	- Elevated spt-hosted endpoints (consented elevation satellite — own
187	  deliverable, rides REQ-CONSENT-2 when triggered).
188

# M8 — CLI nounification & install hardening

> **Status: DRAFT (2026-06-07).** Core decisions were user-ratified in the
> 2026-06-06 M7-closeout grills (nounification shape, subnet attachment verbs,
> Linux elevation model); the **scope-inclusion decisions in §Open decisions
> need a ratification pass before execution starts**. Requirements minted
> before work begins (TRACEABILITY rule 3).

Goal: finish the CLI's breaking reorg **while the adapter window is still
open** (no downstream adapter depends on the surface yet — spt-claude-code
scoping starts after M8), and make the *installed* binary a first-class
citizen on both OSes: elevation that works on Linux, inbound that works on
Windows, a daemon that survives reboot. M8 is the last cheap moment for
surface breaks; after this, spt-claude-code freezes the verbs it consumes.

## Why now (sequencing)

1. **Adapter window.** DEFERRED row "CLI nounification": *"Second
   surface-breaking reorg mid-acceptance; adapter window still open
   immediately after M7 closes."* Every milestone after M8 makes renames
   costlier.
2. **The M7 acceptance run was the field test of the install path** — it
   surfaced the Linux `sudo: spt: command not found` dead-end, the
   HOME-universe split, and the Windows silent-inbound-drop (NO_SEED_HOLDER).
   Both root causes are designed (DEFERRED rows), neither is shipped.
3. **The installer's "next touch" is already owed** three legs at once
   (Linux elevation, firewall registration, OS-service) — one coherent
   install/elevation deliverable instead of three drive-bys.

## Root causes this milestone fixes

1. **Verb sprawl at top level.** fork/suspend/wake/shutdown/rename/stop/
   digest/access/resources sit flat beside the agent hot path; endpoint
   operations have no noun home; `spt daemon` is a hidden verb.
2. **A user-scope install cannot be elevated on Linux.** The binary lives in
   `~/.local/bin` (not on sudo's `secure_path`), and `sudo spt` — when it
   resolves at all — runs the daemon in root's HOME universe. (CLI guidance
   band-aid shipped post-M7 @ `1359649`; the *model* — symlink + default
   user-account election — is this milestone.)
3. **A fresh Windows install is silently unreachable inbound.** The detached
   daemon never triggers the first-bind firewall prompt; mDNS + QUIC meet /
   pairing UDP drops with no rendered cause.
4. **A node is unreachable after reboot** until something invokes `spt`
   (REQ-INSTALL-1's deferred third leg — no OS-service registration).
5. **Subnet participation is all-or-nothing** (attached/detached *term*
   shipped M7; the per-subnet serve-state machinery did not), and dead
   identities' trust rows cost dials every pump tick with no prune verb.
6. **Convergence is slow at both entry points** (~1 min observed each): the
   pairing ceremony holds a live authenticated connection, then the pumps
   re-find each other from scratch via id-only discovery (post-join); and a
   restarted daemon takes 60s+ to sync and pick up other subnet nodes
   (post-bringup — the same id-only cold start).
7. **`spt subnet status` misrenders the standalone case.** The zero-subnet
   text ("local messaging works without [a subnet]…") prints regardless of
   daemon state — it reads as "working" even when the daemon is down — and
   the hint footer noises up a status view meant for reading state.
8. **Re-pairing a known machine strands its old identity.** A reinstall /
   key regeneration pairs as a brand-new node; the old identity's trust +
   registry rows linger (dead dials, status clutter) with only the manual
   prune verb to clean them.

## Ratified decisions (carried from the 2026-06-06 grills — not re-litigated)

| # | Decision |
|---|----------|
| 1 | **`spt endpoint` namespace** absorbs `fork`/`suspend`/`wake`/`shutdown`/`rename`/`stop`/`digest` + `access` (per-endpoint store — NOT subnet-scoped) + `description` (ex-`resources` blurb; bare = show, `set` = author). |
| 2 | `spt endpoint list [--local\|--subnet <name>]` = merged listing; default all-subnets **grouped by subnet**, SELF endpoint pinned distinctly at top. Bare `spt endpoint` = this list. |
| 3 | **Agent HOT PATH stays flat**: `send` / `ring` / `ready` / `whoami` / `how-to`. |
| 4 | `notify` → `spt subnet notify`; **`notif` stays top-level** (user-recall, cross-subnet). |
| 5 | **`spt daemon stop\|status`** noun; hidden `daemon` verb → `daemon run`. Agent-endpoint `shutdown` keeps its name (under `endpoint`). |
| 6 | **Subnet attachment verbs** (user spec 2026-06-06; CONTEXT §subnet attachment): `spt subnet detach <NAME> [--auto]` / `attach <NAME> [--auto]` — daemon keeps running, stops/starts advertising + connecting for that subnet; `--auto` persists the startup default. `spt subnet leave <NAME>` elevation-gated. |
| 7 | **Trust-row prune**: `spt subnet prune <node>` (or ratified final shape) — removes a dead identity's TRUST rows; elevation-gated (trust mutation = security surface). BIGNET's two 09ef831e rows are the live test case. |
| 8 | **Linux elevation model** (user-ratified direction 2026-06-06): (1) install symlinks the binary into a sudo-reachable path (e.g. `/usr/local/bin`) so `sudo spt` resolves; (2) first `sudo spt` detects elevation and prompts once for the DEFAULT USER ACCOUNT — thereafter any `sudo spt` daemon launch runs the daemon (and state) under that account, never root. Windows has no equivalent problem (same user profile). |
| 9 | No deprecation shims, same as M7 decision 1 — zero external CLI consumers until spt-claude-code exists. Breaking renames land clean. |
| 10 | New requirements minted **before work starts** (TRACEABILITY rule 3): `REQ-CLI-*` family (endpoint noun · daemon noun · hot-path preservation), `REQ-SUBNET-*` additions (attach/detach serve-state · prune · re-pair overwrite · status render), `REQ-INSTALL-*` additions (Linux elevation install leg · firewall registration · OS-service), polish reqs per scope ratification. Exact ids assigned at execution; inactive until their deliverable starts (rule 5). |
| 11 | **`subnet status` is daemon-aware** (user 2026-06-07): zero-subnet text becomes "No subnets registered — this node is standalone." followed by a daemon-status-dependent blurb (daemon running vs not). Never implies messaging works while the daemon is down. |
| 12 | **Hint footer only on bare `spt subnet`** (user 2026-06-07): `spt subnet status` drops its "hint:" lines; the flagless `spt subnet` view keeps them (amends M7 decision 5's "always printed"). |
| 13 | **Per-machine re-pair trust overwrite** (user 2026-06-07): registry rows carry a stable per-machine identifier (NOT the MAC — it changes between wifi/ethernet; source per open decision G). A **successful pairing ceremony** presenting the same node label AND the same machine identifier as an existing trusted row is treated as a re-pair of that machine: the old identity's trust + registry rows are deleted automatically. Overwrite fires only inside a completed ceremony (TOTP + SPAKE2 + the join-side elevation gate already paid) — a gossiped claim alone never evicts trust. Manual `prune` (decision 7) stays for every other case. |
| 14 | **Fast convergence covers daemon bringup too** (user 2026-06-07): D4's address seeding targets both cold starts — post-join (seed from the ceremony connection) and post-restart (persist + reload the pump's last-known peer addresses), so a restarted daemon reconnects in seconds, not 60s+. |
| 15 | **Fast-track advertisement on node state change** (user 2026-06-07): an endpoint coming online / going offline (ready-listener start/stop, rest-state transition, perch death) triggers an immediate `advertise_local` + peer push instead of waiting out the pump cadence. The cadence stays the steady-state floor; the event path is the fast lane. Field motivation: a re-listened endpoint stayed rendered `[0/1]` for up to a full cadence after coming online (2026-06-07 diagnosis tail). |

## Open decisions (grill before execution)

| # | Question | Lean |
|---|----------|------|
| A | `spt subnet disband <NAME>` in scope? (elevation + current TOTP per the spec sketch) | Defer unless cheap — `leave` covers the field need; disband is a destructive fleet op with no current user |
| B | OS-service shape: Linux systemd **user** service vs system service; Windows service vs scheduled task | User service + scheduled task — both stay in the user's profile universe (consistent with KH 5.7 never-root stance); system-level variants need the elevation story anyway |
| C | NTP-first clock source (DEFERRED row): in M8 or wait for a field report? | Out — ±1 TOTP window covers small skew; no field failures yet. Revisit on first report |
| D | `xtask debug-converge` watcher (REQ-UPD-6 int, `docs/DEBUG-CONVERGE-PLAN.md`): in M8 or first multi-node debug rollout? | In **only if** M8's acceptance run itself wants the convergence table (3-node fleet now: HFENDULEAM, kitsubito, gravity); otherwise stays deferred |
| E | Post-join address seeding: full addr-cache seam, or narrow "ceremony writes peer addr into the pump's existing cache" patch? | Narrow patch — the seam generalization has no second consumer yet |
| F | Does `endpoint access` get verb shapes (`grant`/`revoke`/`list`) now, or port the existing surface 1:1? | Port 1:1; verb-shape redesign rides the consent framework's next touch |
| G | Machine-identifier source for re-pair overwrite (decision 13): OS machine id (`/etc/machine-id` / Windows `MachineGuid`) vs hashed first-MAC vs spt-minted persisted UUID | OS machine id, hashed before gossip (stable across NIC switches, no raw hardware id on the wire); spt-minted UUID as fallback where the OS id is unreadable |

## Deliverables

**D1 — `endpoint` + `daemon` nouns (breaking reorg, no new machinery):**
namespace skeletons; move fork/suspend/wake/shutdown/rename/stop/digest +
access + description under `endpoint` (decisions 1–3, F); merged
`endpoint list` with SELF pinned + subnet grouping; `notify` → `subnet
notify`; `daemon run|stop|status`; help-group placement
(`help_groups_cover_every_command` keeps passing); `how-to` topics updated;
`cli/reference.md` regen (drift gate).

**D2 — subnet serve-state, trust lifecycle + status UX:**
per-subnet attach/detach machinery (selective advertise/connect in the peer
pump + responder; persisted `--auto` startup flags in daemon config), the
all-attached banner's per-subnet states, `subnet leave` (elevation),
`subnet prune <node>` (elevation; kills the dead-identity dials; BIGNET's
09ef831e rows are the acceptance fixture). **Re-pair trust overwrite**
(decisions 13/G): machine identifier rides the registry rows (additive
serde-default, old rows parse clean — the M7 label pattern), ceremony-time
same-label+same-id match deletes the superseded identity's trust + registry
rows on the seed-holder and replicates the eviction. **Status render fixes**
(decisions 11/12): daemon-aware standalone text, hint lines moved to bare
`spt subnet` only. Decision A resolves disband.

**D3 — install & elevation hardening (the installer's owed touch):**
Linux: install.sh symlink leg into `/usr/local/bin` (graceful when
unelevated: print the one-liner instead) + first-`sudo spt` default-account
election + KH 5.7 interplay verified (daemon + state under the elected
account, never root). Windows: elevated install leg registers the firewall
rule (`New-NetFirewallRule`, inbound UDP) **and** the daemon self-detects
blocked inbound → rendered as the "no connection" state in `subnet status` +
coming-online banner (covers user-scope installs that skip the elevated leg).
Both OSes: OS-service registration per decision B (REQ-INSTALL-1 third leg —
reboot-survivable daemon). Installer-script E2E rungs extended
(`SPT_INSTALL_E2E` stays hermetic — service/firewall legs env-gated off in
CI, proven in acceptance instead).

**D4 — convergence polish:**
address seeding per decisions E/14, both cold starts: post-join (seed the
pump's addr cache from the live ceremony connection, both sides) and
post-bringup (persist last-known peer addresses; reload on daemon start so
reconnect skips id-only discovery). **Event-driven advertisement**
(decision 15): endpoint online/offline transitions nudge the pump's
registry leg immediately (a wake of the existing loop — no second
advertisement path, so the epoch lease and visibility gates ride
unchanged); the cadence remains the catch-all floor. Observed-fix target
for each: first `status --nodes` convergence in seconds, not ~1 min.
Decision C resolves NTP.

**D5 — docs + CI + acceptance:**
docs-site sweep for every renamed verb (no page references `spt fork`, bare
`spt notify`, hidden `daemon`…), quickstart/how-to deltas, README status
table, llms.txt, reference regen; `quickstart_e2e` + twohost ladder updated
where verbs moved; `traceable-reqs check` + `xtask check` green.

Order: **D1 → D2 ∥ D3 → D4 → D5** (docs last so captured outputs are real).
D1 first — everything downstream renders the new verbs.

## Acceptance (real hardware, like M7)

1. **Fresh Linux install on kitsubito** (clean user, real one-liner): `sudo
   spt subnet ...` resolves and prompts the account election exactly once;
   daemon + state land under the elected account (never root); the node
   survives a reboot and is reachable before any manual `spt` invocation.
2. **Fresh Windows install** (elevated leg): inbound works with zero
   accumulated dev rules — a join succeeds where M7's NO_SEED_HOLDER failed;
   the unelevated-install path renders the blocked-inbound state honestly in
   `subnet status`.
3. **Real elevated-spawn verification on both OSes** rides this run (the
   DEFERRED row-24 follow-up: KH 5.7 de-elevation seam observed live).
4. Old verb shapes are gone (`spt fork` etc. → unknown subcommand); hot path
   unchanged; e2e suites green; no doc page references a moved verb's old
   home.
5. `subnet detach`/`attach` flips advertising live (peer observes
   offline/online); `subnet prune` removes BIGNET's 09ef831e trust rows and
   the dead dials stop.
6. Post-join first sync AND post-restart resync both converge in seconds on
   the rig (daemon restart on one node; the peer re-appears in
   `status --nodes` without the 60s id-only rediscovery). An endpoint
   flipping online/offline is visible in the peer's `status --nodes` within
   seconds (event-driven advertisement, not cadence wait).
7. Re-pair proof: regenerate a rig node's identity, re-join with the same
   label — the subnet ends with ONE trust row + ONE registry identity for
   that machine (old rows auto-evicted at ceremony), no manual prune needed.
8. `spt subnet status` with the daemon stopped says so (no "messaging works"
   implication); hint lines appear on bare `spt subnet` only.

## Non-goals

- spt-claude-code (separate repo; scoping starts after M8 closes).
- PresenceChannel, instantiate-anywhere, remote-exec, sandboxing, sidecar
  adapters, manifest composition (DEFERRED — triggers unmet).
- Tier-2 agent docs (MCP server / `--help --json`).
- Elevated spt-hosted endpoints (consented elevation satellite — own
  deliverable, rides REQ-CONSENT-2 when triggered).


/grill-me over M8, then execute once open decisions are made


AskUserQuestion

Question: Decision A: is `spt subnet disband <NAME>` in M8 scope?

Choices:
Out of M8. `leave` covers field need; adding disband later is non-breaking, so adapter window doesn't force it now.
Build it in D2: elevation + current-TOTP gated, removes subnet fleet-wide. Adds spec + acceptance burden.
Local-only disband: drop own registry/trust rows for the subnet without fleet-wide ceremony. Cheaper, but semantics overlap `leave`.


Your questions have been answered: "Decision A: is `spt subnet disband <NAME>` in M8 scope?"="Defer (Recommended)". You can now continue with these answers in mind.

Question: Decision A: is `spt subnet disband <NAME>` in M8 scope?

Choices:
Out of M8. `leave` covers field need; adding disband later is non-breaking, so adapter window doesn't force it now.
Build it in D2: elevation + current-TOTP gated, removes subnet fleet-wide. Adds spec + acceptance burden.
Local-only disband: drop own registry/trust rows for the subnet without fleet-wide ceremony. Cheaper, but semantics overlap `leave`.


Found 1 file
M8-PLAN.md


Found 16 files
crates\spt-store\src\visibility.rs
crates\spt-store\src\trust.rs
crates\spt-store\src\subnet.rs
crates\spt-store\src\shellinfo.rs
crates\spt-store\src\info.rs
crates\spt-store\src\access.rs
crates\spt-runtime\src\manifest.rs
crates\spt-net\src\net\xfer.rs
crates\spt-net\src\net\registry.rs
crates\spt-daemon\src\seedmap.rs
crates\spt-daemon\src\release.rs
crates\spt-daemon\src\msg.rs
crates\spt-daemon\src\frame.rs
crates\spt-daemon\src\digesthub.rs
crates\spt-daemon\src\config.rs
crates\spt-store\src\grants.rs


117:    /// The authoring node's human-readable label (M7 D2, REQ-SUBNET-3 —
118:    /// CONTEXT §node label): defaults to the node's OS hostname, re-checked
119:    /// at daemon startup (a hostname change updates the advertised label).
127:    pub node_label: Option<String>,
375:/// relabel, not a liveness event). Seams: the perch-dir arm is
389:        return Ok(Vec::new()); // relabel to itself — nothing to ripple
473:    /// D2, REQ-SUBNET-3): a shared label, or a too-short key-prefix.
484:/// key-prefix, or the node's advertised label (Windows hostnames render
495:            .node_label
509:    /// `@node` (full hex, key-prefix, or label — [`node_qualifier_matches`]) → an
542:        // label (M7 D2, REQ-SUBNET-3); several distinct matches refuse with
667:            node_label: None,
821:            node_label: None,
852:    // [unit->REQ-SUBNET-3] the node label is a FIELD under the lease — a
855:    // label and a pre-M7 row (no field) parses clean (the additive-field
858:    fn node_label_rides_the_lease_and_serde() {
860:        let with = |label: Option<&str>, epoch: u64| Instance {
867:            node_label: label.map(str::to_string),
876:            reg.instances("ling")[0].node_label.as_deref(),
884:            reg.instances("ling")[0].node_label.as_deref(),
888:        // Serde: roundtrips with the label; a pre-M7 row parses clean.
894:        assert_eq!(old.node_label, None, "absent field parses as no label");
897:    // [unit->REQ-SUBNET-3] `@node` qualifiers accept a label or key-prefix
902:    fn node_qualifier_accepts_label_and_prefix_refuses_shared() {
903:        let labeled = |node: &str, label: &str| Instance {
904:            node_label: Some(label.to_string()),
908:        reg.merge_instance("ling", labeled("bcead52b00112233", "HFENDULEAM"));
909:        reg.merge_instance("ling", labeled("77aa11ff00112233", "GRAVITY"));
915:            "label resolves case-insensitively: {r:?}"
935:        // A shared label refuses with candidate key prefixes — never a guess.

[Showing results with pagination = limit: 30]


Question: Decision G: machine-identifier source for re-pair trust overwrite?

Choices:
/etc/machine-id + MachineGuid, domain-separated SHA-256 before gossip. Spt-minted persisted UUID as fallback where OS id unreadable. Only source surviving the key-regen scenario decision 13 targets.
spt-generated persisted UUID. Fatal flaw: state-dir wipe (the common re-pair cause) destroys it — overwrite never fires.
Already rejected in decision 13 rationale (wifi/ethernet switch changes it).


Your questions have been answered: "Decision G: machine-identifier source for re-pair trust overwrite?"="OS machine id (Recommended)". You can now continue with these answers in mind.

Question: Decision G: machine-identifier source for re-pair trust overwrite?

Choices:
/etc/machine-id + MachineGuid, domain-separated SHA-256 before gossip. Spt-minted persisted UUID as fallback where OS id unreadable. Only source surviving the key-regen scenario decision 13 targets.
spt-generated persisted UUID. Fatal flaw: state-dir wipe (the common re-pair cause) destroys it — overwrite never fires.
Already rejected in decision 13 rationale (wifi/ethernet switch changes it).


Question: Decision B: OS-service shape for reboot-survivable daemon?

Choices:
Linux: systemd user service + enable-linger (rides the elevated install leg; pre-login boot start). Windows: scheduled task at-logon (interactive session, no credentials, meets M8 acceptance as written).
Same Linux shape, but Windows task = at-startup S4U (pre-login reachability). Non-interactive session risks terminal-hosting; no rig node needs it.
systemd system service (User=) + real Windows service. Root-managed units + session-0 isolation — fights KH 5.7 user-universe model.


Your questions have been answered: "Decision B: OS-service shape for reboot-survivable daemon?"="User svc + logon task (Recommended)". You can now continue with these answers in mind.

Question: Decision B: OS-service shape for reboot-survivable daemon?

Choices:
Linux: systemd user service + enable-linger (rides the elevated install leg; pre-login boot start). Windows: scheduled task at-logon (interactive session, no credentials, meets M8 acceptance as written).
Same Linux shape, but Windows task = at-startup S4U (pre-login reachability). Non-interactive session risks terminal-hosting; no rig node needs it.
systemd system service (User=) + real Windows service. Root-managed units + session-0 isolation — fights KH 5.7 user-universe model.


No matches found


Found 11 files
crates\spt-daemon\src\peerloop.rs
crates\spt-daemon\src\applyhost.rs
crates\spt-daemon\src\shelldisc.rs
crates\spt-daemon\src\relcache.rs
crates\spt-daemon\src\registryhost.rs
crates\spt-daemon\src\propagate.rs
crates\spt-daemon\src\pairhost.rs
crates\spt-daemon\src\nethost.rs
crates\spt-daemon\src\lib.rs
crates\spt-daemon\src\dispatch.rs
crates\spt-daemon\src\daemon.rs


67:use crate::relcache::ReleaseCache;
75:/// Resolve a trusted peer's stable name (lowercase-hex pubkey) to a dialable
76:/// address (the serde JSON `net-dial` carries). Production resolution lets
110:    /// The staged-release cache dir ([`ReleaseCache::open`]).
210:/// per-peer connection cache (an IO failure against a peer drops its cache
211:/// row; the next tick redials — conns are rebuilt freely, nothing leaks
290:                    continue; // unresolvable/undialable now — next tick retries
344:                        let cache = ReleaseCache::open(&paths.releases);
346:                        let current = if cache.staged_channel().as_deref()
349:                            cache.staged_version().unwrap_or(0)
365:                                &cache,
369:                                    let version = cache
422:                    conns.remove(&peer.pubkey_hex); // redial next tick
445:/// undialable right now — skip, don't fail the round.
456:    match brain.net_dial(addr, None) {


75	/// Resolve a trusted peer's stable name (lowercase-hex pubkey) to a dialable
76	/// address (the serde JSON `net-dial` carries). Production resolution lets
77	/// discovery do the work ([`production_resolver`]); hermetic tests inject a
78	/// concrete address map (loopback endpoints run no discovery).
79	pub type PeerResolver = Box<dyn Fn(&str) -> Option<serde_json::Value> + Send>;
80
81	/// The production resolver: an id-only iroh address — mDNS on the LAN, n0
82	/// DNS on the WAN (`addr_for_node_hex`).
83	pub fn production_resolver() -> PeerResolver {
84	    Box::new(|hex| addr_for_node_hex(hex).and_then(|a| serde_json::to_value(a).ok()))
85	}
86
87	/// Where this node's pump-side stores live. Production = the canonical
88	/// SPT_HOME layout; the loopback E2E gives its in-process "node" distinct
89	/// roots so two nodes can share one test process.
90	pub struct PumpPaths {
91	    /// The perch tree (registry advertisement scan).
92	    pub owlery: PathBuf,
93	    /// The context store root ([`ContextStore::open_or_init_in`]).
94	    pub ctx_root: PathBuf,
95	    /// The notif spool DB ([`NotifStore::open_at`]).
96	    pub notif_db: PathBuf,
97	    /// Transient pull scratch.
98	    pub scratch: PathBuf,
99	    /// `subnet.json` ([`SubnetStore::load_from`]).
100	    pub subnets: PathBuf,
101	    /// `trust/peers.json` ([`TrustStore::load_from`]).
102	    pub trust: PathBuf,
103	    /// `visibility.json` ([`VisibilityStore::load_from`]).
104	    pub vis: PathBuf,
105	    /// The pump's durable open-op counter (its own file — colliding with the
106	    /// registry's advertisement epochs would break neither, but a shared
107	    /// in-memory cursor pair over one file double-mints; separate files keep
108	    /// each `EpochSource` the sole writer of its counter).
109	    pub ops: PathBuf,
110	    /// The staged-release cache dir ([`ReleaseCache::open`]).
111	    pub releases: PathBuf,
112	    /// `release-keys.json` ([`VerifyPolicy::load_from`]).
113	    pub release_keys: PathBuf,
114	    /// The wake-edge freshness-pull marker (D9-2, REQ-INST-3): a
115	    /// dormant→active transition drops it; the pump consumes it and forces a
116	    /// sync round NOW instead of waiting out `cadence.sync`
117	    /// ([`crate::resting::PULL_MARKER_FILE`]).
118	    pub pull_marker: PathBuf,
119	}
120
121	impl PumpPaths {
122	    /// The canonical SPT_HOME layout.
123	    pub fn production() -> PumpPaths {
124	        let home = perch::spt_home();
125	        let identity = perch::identity_dir();
126	        PumpPaths {
127	            owlery: perch::owlery_dir(),
128	            ctx_root: home.join("context"),
129	            notif_db: identity.join("notifs.db"),
130	            scratch: home.join("scratch").join("pump"),
131	            subnets: identity.join("subnet.json"),
132	            trust: identity.join("trust").join("peers.json"),
133	            vis: identity.join("visibility.json"),
134	            ops: identity.join("pump-ops.json"),

/// Resolve a trusted peer's stable name (lowercase-hex pubkey) to a dialable
/// address (the serde JSON `net-dial` carries). Production resolution lets
/// discovery do the work ([`production_resolver`]); hermetic tests inject a
/// concrete address map (loopback endpoints run no discovery).
pub type PeerResolver = Box<dyn Fn(&str) -> Option<serde_json::Value> + Send>;

/// The production resolver: an id-only iroh address — mDNS on the LAN, n0
/// DNS on the WAN (`addr_for_node_hex`).
pub fn production_resolver() -> PeerResolver {
    Box::new(|hex| addr_for_node_hex(hex).and_then(|a| serde_json::to_value(a).ok()))
}

/// Where this node's pump-side stores live. Production = the canonical
/// SPT_HOME layout; the loopback E2E gives its in-process "node" distinct
/// roots so two nodes can share one test process.
pub struct PumpPaths {
    /// The perch tree (registry advertisement scan).
    pub owlery: PathBuf,
    /// The context store root ([`ContextStore::open_or_init_in`]).
    pub ctx_root: PathBuf,
    /// The notif spool DB ([`NotifStore::open_at`]).
    pub notif_db: PathBuf,
    /// Transient pull scratch.
    pub scratch: PathBuf,
    /// `subnet.json` ([`SubnetStore::load_from`]).
    pub subnets: PathBuf,
    /// `trust/peers.json` ([`TrustStore::load_from`]).
    pub trust: PathBuf,
    /// `visibility.json` ([`VisibilityStore::load_from`]).
    pub vis: PathBuf,
    /// The pump's durable open-op counter (its own file — colliding with the
    /// registry's advertisement epochs would break neither, but a shared
    /// in-memory cursor pair over one file double-mints; separate files keep
    /// each `EpochSource` the sole writer of its counter).
    pub ops: PathBuf,
    /// The staged-release cache dir ([`ReleaseCache::open`]).
    pub releases: PathBuf,
    /// `release-keys.json` ([`VerifyPolicy::load_from`]).
    pub release_keys: PathBuf,
    /// The wake-edge freshness-pull marker (D9-2, REQ-INST-3): a
    /// dormant→active transition drops it; the pump consumes it and forces a
    /// sync round NOW instead of waiting out `cadence.sync`
    /// ([`crate::resting::PULL_MARKER_FILE`]).
    pub pull_marker: PathBuf,
}

impl PumpPaths {
    /// The canonical SPT_HOME layout.
    pub fn production() -> PumpPaths {
        let home = perch::spt_home();
        let identity = perch::identity_dir();
        PumpPaths {
            owlery: perch::owlery_dir(),
            ctx_root: home.join("context"),
            notif_db: identity.join("notifs.db"),
            scratch: home.join("scratch").join("pump"),
            subnets: identity.join("subnet.json"),
            trust: identity.join("trust").join("peers.json"),
            vis: identity.join("visibility.json"),
            ops: identity.join("pump-ops.json"),


Question: Decision E: address-seeding shape? (Note: no existing addr cache in code — narrow patch = new minimal peer-addrs.json + resolver-first lookup + id-only fallback on stale)

Choices:
peer-addrs.json in identity dir; resolver checks first, id-only fallback on miss/dial-fail; written by ceremony + successful pump connects. Serves both decision-14 cold starts.
Generalized cache abstraction (TTL, source priority, pluggable). No third consumer exists — speculative generality.
Seed ceremony addr into RAM, no persistence. Kills the post-restart half of decision 14 — contradicts ratified scope.


Your questions have been answered: "Decision E: address-seeding shape? (Note: no existing addr cache in code — narrow patch = new minimal peer-addrs.json + resolver-first lookup + id-only fallback on stale)"="Narrow patch (Recommended)". You can now continue with these answers in mind.

Question: Decision E: address-seeding shape? (Note: no existing addr cache in code — narrow patch = new minimal peer-addrs.json + resolver-first lookup + id-only fallback on stale)

Choices:
peer-addrs.json in identity dir; resolver checks first, id-only fallback on miss/dial-fail; written by ceremony + successful pump connects. Serves both decision-14 cold starts.
Generalized cache abstraction (TTL, source priority, pluggable). No third consumer exists — speculative generality.
Seed ceremony addr into RAM, no persistence. Kills the post-restart half of decision 14 — contradicts ratified scope.