syntaur 0.1.13 → 0.2.0

package/examples/playbooks/keep-records-updated.md

@@ -23,7 +23,7 @@ tags:
 
 ## When starting work:
 - Add a progress entry noting you've begun and what your approach is
-- If a plan.md exists, update its task checkboxes as you complete steps
+- If any plan files exist (plan.md, plan-v2.md, ...), update their task checkboxes as you complete steps
 
 ## When stopping or handing off:
 - Write a final progress entry summarizing current state

package/examples/playbooks/read-before-plan.md

@@ -1,8 +1,8 @@
 ---
 name: "Read Before You Plan"
 slug: read-before-plan
-description: "Agents must read all mission context files before creating or modifying a plan"
-when_to_use: "Before creating or modifying plan.md"
+description: "Agents must read all project context files before creating or modifying a plan"
+when_to_use: "Before creating or modifying any plan file (plan.md, plan-v2.md, ...)"
 created: "2026-04-02T00:00:00Z"
 updated: "2026-04-02T00:00:00Z"
 tags:
@@ -12,10 +12,10 @@ tags:
 
 # Read Before You Plan
 
-Before creating or modifying plan.md, read these files in order:
+Before creating or modifying any plan file (plan.md, plan-v2.md, ...), read these files in order:
 
-1. `manifest.md` -- understand the mission structure
-2. `mission.md` -- understand the goal and scope
+1. `manifest.md` -- understand the project structure
+2. `project.md` -- understand the goal and scope
 3. `agent.md` -- understand conventions and constraints
 4. `claude.md` (if exists) -- Claude-specific instructions
 5. `assignment.md` -- understand your specific task, acceptance criteria, and dependencies

package/examples/{sample-mission → sample-project}/_index-assignments.md

@@ -1,5 +1,5 @@
 ---
-mission: build-auth-system
+project: build-auth-system
 generated: "2026-03-18T14:30:00Z"
 total: 3
 by_status:

package/examples/{sample-mission → sample-project}/_index-decisions.md

@@ -1,5 +1,5 @@
 ---
-mission: build-auth-system
+project: build-auth-system
 generated: "2026-03-18T14:30:00Z"
 ---
 

package/examples/{sample-mission → sample-project}/_index-plans.md

@@ -1,5 +1,5 @@
 ---
-mission: build-auth-system
+project: build-auth-system
 generated: "2026-03-18T14:30:00Z"
 ---
 

package/examples/{sample-mission → sample-project}/_status.md

@@ -1,5 +1,5 @@
 ---
-mission: build-auth-system
+project: build-auth-system
 generated: "2026-03-18T14:30:00Z"
 status: active
 progress:
@@ -13,10 +13,10 @@ progress:
 needsAttention:
   blockedCount: 0
   failedCount: 0
-  unansweredQuestions: 1
+  openQuestions: 1
 ---
 
-# Mission Status: Build Authentication System
+# Project Status: Build Authentication System
 
 **Status:** active
 **Progress:** 1/3 assignments complete

package/examples/{sample-mission → sample-project}/assignments/design-auth-schema/assignment.md

@@ -32,6 +32,10 @@ Design the PostgreSQL database schema for the authentication system. This includ
 - [x] All tables have appropriate indexes for query patterns
 - [x] Migration scripts are idempotent and backward-compatible
 
+## Todos
+
+- [x] Execute [plan](./plan.md)
+
 ## Context
 
 This is the foundational data layer for the auth system. The schema must support the JWT middleware (implement-jwt-middleware) and be testable (write-auth-tests). See [Auth Requirements](../../resources/auth-requirements.md) for functional specs.
@@ -55,7 +59,6 @@ Started schema design. Reviewed auth requirements document. Planning three table
 
 ## Links
 
-- [Plan](./plan.md)
 - [Scratchpad](./scratchpad.md)
 - [Handoff](./handoff.md)
 - [Decision Record](./decision-record.md)

package/examples/{sample-mission → sample-project}/assignments/implement-jwt-middleware/assignment.md

@@ -36,6 +36,10 @@ Implement Express.js middleware that validates JWT access tokens on protected ro
 - [ ] Token revocation endpoint (logout)
 - [ ] Role-based route guards (admin vs user)
 
+## Todos
+
+- [ ] Execute [plan](./plan.md)
+
 ## Context
 
 Depends on the database schema from [design-auth-schema](../design-auth-schema/assignment.md). The schema is complete — see the [handoff notes](../design-auth-schema/handoff.md) for integration details. Key table: `sessions` with `jti` column for token validation. See [Auth Requirements](../../resources/auth-requirements.md) for full specs.
@@ -59,7 +63,6 @@ Started implementation. Set up RS256 key pair loading from environment variables
 
 ## Links
 
-- [Plan](./plan.md)
 - [Scratchpad](./scratchpad.md)
 - [Handoff](./handoff.md)
 - [Decision Record](./decision-record.md)

package/examples/{sample-mission → sample-project}/assignments/write-auth-tests/assignment.md

@@ -34,6 +34,10 @@ Write comprehensive unit and integration tests for the authentication system, co
 - [ ] Edge case tests: expired tokens, revoked sessions, refresh token reuse detection
 - [ ] Coverage report showing 80%+ line coverage
 
+## Todos
+
+- [ ] Execute [plan](./plan.md)
+
 ## Context
 
 This assignment depends on [implement-jwt-middleware](../implement-jwt-middleware/assignment.md) being completed. Tests will cover both the schema layer (from design-auth-schema) and the middleware/endpoint layer (from implement-jwt-middleware). Use Jest as the test framework with `supertest` for HTTP integration tests.
@@ -48,7 +52,6 @@ No progress yet.
 
 ## Links
 
-- [Plan](./plan.md)
 - [Scratchpad](./scratchpad.md)
 - [Handoff](./handoff.md)
 - [Decision Record](./decision-record.md)

package/examples/{sample-mission → sample-project}/manifest.md

@@ -1,13 +1,13 @@
 ---
 version: "1.0"
-mission: build-auth-system
+project: build-auth-system
 generated: "2026-03-18T14:30:00Z"
 ---
 
-# Mission: build-auth-system
+# Project: build-auth-system
 
 ## Overview
-- [Mission Overview](./mission.md)
+- [Project Overview](./project.md)
 
 ## Indexes
 - [Assignments](./_index-assignments.md)

package/examples/{sample-mission → sample-project}/memories/_index.md

@@ -1,5 +1,5 @@
 ---
-mission: build-auth-system
+project: build-auth-system
 generated: "2026-03-18T14:30:00Z"
 total: 1
 ---
@@ -8,4 +8,4 @@ total: 1
 
 | Name | Source | Scope | Source Assignment | Updated |
 |------|--------|-------|------------------|---------|
-| [postgres-connection-pooling](./postgres-connection-pooling.md) | claude-2 | mission | design-auth-schema | 2026-03-17T09:00:00Z |
+| [postgres-connection-pooling](./postgres-connection-pooling.md) | claude-2 | project | design-auth-schema | 2026-03-17T09:00:00Z |

package/examples/{sample-mission → sample-project}/memories/postgres-connection-pooling.md

@@ -6,7 +6,7 @@ sourceAssignment: design-auth-schema
 relatedAssignments:
   - design-auth-schema
   - implement-jwt-middleware
-scope: mission
+scope: project
 created: "2026-03-17T09:00:00Z"
 updated: "2026-03-17T09:00:00Z"
 tags:

package/examples/{sample-mission → sample-project}/resources/_index.md

@@ -1,5 +1,5 @@
 ---
-mission: build-auth-system
+project: build-auth-system
 generated: "2026-03-18T14:30:00Z"
 total: 1
 ---

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "syntaur",
-  "version": "0.1.13",
-  "description": "Mission workflow CLI with dashboard, Claude Code plugin, and Codex plugin",
+  "version": "0.2.0",
+  "description": "Project workflow CLI with dashboard, Claude Code plugin, and Codex plugin",
   "homepage": "https://github.com/prong-horn/syntaur#readme",
   "repository": {
     "type": "git",
@@ -40,7 +40,9 @@
     "typecheck": "tsc --noEmit",
     "test": "vitest run",
     "test:watch": "vitest",
-    "prepublishOnly": "npm run build && npm ci --prefix dashboard && npm run build --prefix dashboard"
+    "prepublishOnly": "npm run build && npm ci --prefix dashboard && npm run build --prefix dashboard",
+    "try": "node scripts/try.mjs",
+    "untry": "npm unlink -g syntaur && npm install -g syntaur@latest && echo '\\n✓ global syntaur restored to latest published version'"
   },
   "engines": {
     "node": ">=20.0.0"

package/platforms/README.md

@@ -16,16 +16,16 @@ format expected by the target framework.
 
 ```bash
 # Generate Cursor adapter files in the current directory
-syntaur setup-adapter cursor --mission <mission-slug> --assignment <assignment-slug>
+syntaur setup-adapter cursor --project <project-slug> --assignment <assignment-slug>
 
 # Generate Codex adapter files
-syntaur setup-adapter codex --mission <mission-slug> --assignment <assignment-slug>
+syntaur setup-adapter codex --project <project-slug> --assignment <assignment-slug>
 
 # Generate OpenCode adapter files
-syntaur setup-adapter opencode --mission <mission-slug> --assignment <assignment-slug>
+syntaur setup-adapter opencode --project <project-slug> --assignment <assignment-slug>
 
 # Overwrite existing files
-syntaur setup-adapter cursor --mission my-mission --assignment my-task --force
+syntaur setup-adapter cursor --project my-project --assignment my-task --force
 ```
 
 ## What Gets Generated
@@ -35,8 +35,8 @@ All adapters embed equivalent protocol knowledge:
 - **Write boundary rules** (which files the agent can and cannot modify)
 - **Assignment lifecycle states** and valid transitions
 - **CLI commands** for state transitions (`syntaur start`, `syntaur complete`, etc.)
-- **Reading order** for mission and assignment files
-- **Current assignment context** (mission slug, assignment slug, paths)
+- **Reading order** for project and assignment files
+- **Current assignment context** (project slug, assignment slug, paths)
 
 ## Contributing a New Adapter
 
@@ -46,7 +46,7 @@ To add support for a new framework:
    reference file showing the format. This is documentation, not a runtime asset.
 
 2. **Create a TypeScript renderer** in `src/templates/<framework>.ts`:
-   - Define a params interface with `missionSlug`, `assignmentSlug`, `missionDir`, `assignmentDir`
+   - Define a params interface with `projectSlug`, `assignmentSlug`, `projectDir`, `assignmentDir`
    - Export a render function returning the file content as a string
    - Embed protocol knowledge directly in the template literal (do not read files at runtime)
 

package/platforms/claude-code/README.md

@@ -4,7 +4,7 @@ Syntaur plugin for Claude Code. Installed automatically during `syntaur setup`.
 
 ## What's included
 
-- **Skills:** grab-assignment, plan-assignment, complete-assignment, create-mission, create-assignment, syntaur-protocol
+- **Skills:** grab-assignment, plan-assignment, complete-assignment, create-project, create-assignment, syntaur-protocol
 - **Agents:** syntaur-protocol (background)
 - **Hooks:** write boundary enforcement (PreToolUse)
 - **Commands:** track-session

package/platforms/claude-code/agents/syntaur-expert.md

@@ -6,7 +6,7 @@ model: opus
 maxTurns: 20
 ---
 
-You are the authoritative expert on the Syntaur platform — the markdown-based, filesystem-hosted protocol for multi-agent mission coordination. You know every detail of the protocol spec, CLI, plugin, dashboard, adapters, and file formats.
+You are the authoritative expert on the Syntaur platform — the markdown-based, filesystem-hosted protocol for multi-agent project coordination. You know every detail of the protocol spec, CLI, plugin, dashboard, adapters, and file formats.
 
 When answering questions, read the actual source files rather than relying solely on this prompt. The codebase is your ground truth.
 
@@ -42,20 +42,20 @@ Syntaur is a **markdown-based, filesystem-hosted protocol** that coordinates wor
 ~/.syntaur/
   config.md                          # Global config (optional)
   syntaur.db                         # SQLite database for agent sessions
-  missions/
-    <mission-slug>/
+  projects/
+    <project-slug>/
       manifest.md                    # Derived: root navigation
-      mission.md                     # Human-authored: goal, context, success criteria
+      project.md                     # Human-authored: goal, context, success criteria
       agent.md                       # Human-authored: universal agent instructions
       claude.md                      # Human-authored: Claude Code-specific instructions
       _index-assignments.md          # Derived: assignment summary table
       _index-plans.md                # Derived: plan status summary
       _index-decisions.md            # Derived: decision record summary
-      _status.md                     # Derived: mission status rollup
+      _status.md                     # Derived: project status rollup
       assignments/
         <assignment-slug>/
-          assignment.md              # Agent-writable: source of truth for state
-          plan.md                    # Agent-writable: implementation plan
+          assignment.md              # Agent-writable: source of truth for state (includes ## Todos)
+          plan*.md                   # Agent-writable: versioned implementation plans (0+, optional)
           scratchpad.md              # Agent-writable: working notes
           handoff.md                 # Agent-writable: append-only handoff log
           decision-record.md         # Agent-writable: append-only decision log
@@ -72,13 +72,13 @@ Syntaur is a **markdown-based, filesystem-hosted protocol** that coordinates wor
 ## File Ownership Model
 
 ### Human-Authored (READ-ONLY for agents)
-- `mission.md` — mission overview, goal, context, success criteria
+- `project.md` — project overview, goal, context, success criteria
 - `agent.md` — universal agent instructions
 - `claude.md` — Claude Code-specific instructions
 
 ### Agent-Writable (single-writer per assignment)
-- `assignment.md` — source of truth for assignment state
-- `plan.md` — implementation plan
+- `assignment.md` — source of truth for assignment state (includes `## Todos` checklist)
+- `plan*.md` — versioned implementation plans (optional, one per `## Todos` entry: `plan.md`, `plan-v2.md`, ...)
 - `scratchpad.md` — unstructured working notes
 - `handoff.md` — append-only handoff log
 - `decision-record.md` — append-only decision log
@@ -128,8 +128,8 @@ Only the assigned agent may write to its own assignment folder.
 - `pending` + unmet dependencies = structural wait (automatic, no action needed)
 - `blocked` = runtime obstacle requiring human intervention (must set `blockedReason`)
 
-### Mission Status Rollup (computed, first-match-wins)
-1. `archived: true` in mission.md → `archived`
+### Project Status Rollup (computed, first-match-wins)
+1. `archived: true` in project.md → `archived`
 2. ALL assignments `completed` → `completed`
 3. ANY `in_progress` or `review` → `active`
 4. ANY `failed` → `failed`
@@ -151,31 +151,31 @@ Only the assigned agent may write to its own assignment folder.
 | `syntaur setup-adapter <framework>` | Generate adapter files for cursor, codex, or opencode |
 | `syntaur uninstall [--all]` | Remove plugins and optionally `~/.syntaur` data |
 
-### Mission & Assignment Creation
+### Project & Assignment Creation
 | Command | Description |
 |---------|-------------|
-| `syntaur create-mission <title> [--slug S] [--dir D]` | Create new mission with full scaffolding |
-| `syntaur create-assignment <title> --mission M [--priority P] [--depends-on D] [--slug S]` | Create assignment in a mission |
+| `syntaur create-project <title> [--slug S] [--dir D]` | Create new project with full scaffolding |
+| `syntaur create-assignment <title> --project M [--priority P] [--depends-on D] [--slug S]` | Create assignment in a project |
 | `syntaur create-assignment <title> --one-off` | Create standalone one-off assignment |
 
 ### State Transitions
 | Command | Description |
 |---------|-------------|
-| `syntaur assign <slug> --agent <name> --mission <mission>` | Set assignee |
-| `syntaur start <slug> --mission <mission>` | pending → in_progress |
-| `syntaur review <slug> --mission <mission>` | in_progress → review |
-| `syntaur complete <slug> --mission <mission>` | in_progress/review → completed |
-| `syntaur block <slug> --mission <mission> --reason <text>` | → blocked |
-| `syntaur unblock <slug> --mission <mission>` | blocked → in_progress |
-| `syntaur fail <slug> --mission <mission>` | → failed |
-| `syntaur reopen <slug> --mission <mission>` | completed/failed → in_progress |
+| `syntaur assign <slug> --agent <name> --project <project>` | Set assignee |
+| `syntaur start <slug> --project <project>` | pending → in_progress |
+| `syntaur review <slug> --project <project>` | in_progress → review |
+| `syntaur complete <slug> --project <project>` | in_progress/review → completed |
+| `syntaur block <slug> --project <project> --reason <text>` | → blocked |
+| `syntaur unblock <slug> --project <project>` | blocked → in_progress |
+| `syntaur fail <slug> --project <project>` | → failed |
+| `syntaur reopen <slug> --project <project>` | completed/failed → in_progress |
 
 ### Session Tracking
 | Command | Description |
 |---------|-------------|
-| `syntaur track-session --mission M --assignment A --agent N` | Register agent session |
+| `syntaur track-session --project M --assignment A --agent N` | Register agent session |
 
-All commands support `--dir <path>` to override the default `~/.syntaur/missions/` directory.
+All commands support `--dir <path>` to override the default `~/.syntaur/projects/` directory.
 
 ---
 
@@ -192,7 +192,7 @@ plugin/
   skills/
     syntaur-protocol/SKILL.md    # Core protocol rules (background)
     grab-assignment/SKILL.md     # Claim a pending assignment
-    create-mission/SKILL.md      # Create new mission
+    create-project/SKILL.md      # Create new project
     create-assignment/SKILL.md   # Create new assignment
     plan-assignment/SKILL.md     # Write implementation plan
     complete-assignment/SKILL.md # Handoff and complete
@@ -212,17 +212,17 @@ plugin/
 | Skill | Trigger | Purpose |
 |-------|---------|---------|
 | `/syntaur-protocol` | Background — auto-loaded when working with Syntaur files | Core write boundary rules and protocol knowledge |
-| `/grab-assignment` | User says "grab assignment" or starts work on a mission | Discover pending assignments, claim one, create context.json |
-| `/create-mission` | User wants to create a new mission | Run CLI scaffolding, guide through editing mission files |
-| `/create-assignment` | User wants to add an assignment to a mission | Create assignment with all supporting files |
-| `/plan-assignment` | User wants to plan current assignment | Explore workspace, write detailed plan.md |
+| `/grab-assignment` | User says "grab assignment" or starts work on a project | Discover pending assignments, claim one, create context.json |
+| `/create-project` | User wants to create a new project | Run CLI scaffolding, guide through editing project files |
+| `/create-assignment` | User wants to add an assignment to a project | Create assignment with all supporting files |
+| `/plan-assignment` | User wants to plan current assignment | Explore workspace, write the next `plan-v<N>.md`, append a linked todo to `## Todos` (supersede prior plan todo) |
 | `/complete-assignment` | User is done with assignment work | Verify criteria, write handoff, transition state, close session |
 
 ### Hooks
 
 | Hook | Event | Behavior |
 |------|-------|----------|
-| PostToolUse: ExitPlanMode | User exits plan mode | Prompts to update plan.md with the plan just created |
+| PostToolUse: ExitPlanMode | User exits plan mode | Prompts to write the plan to the next unused `plan-v<N>.md` (or `plan.md` if none exists) and append a linked todo in the `## Todos` section of `assignment.md` |
 | SessionEnd | Claude Code session exits | Runs session-cleanup.sh to mark session as stopped |
 | PreToolUse: enforce-boundaries | Edit/Write/MultiEdit | Validates target path is within assignment boundaries |
 
@@ -240,27 +240,27 @@ syntaur                    # Dashboard is the default command
 ```
 
 ### Features
-- **Overview page:** Mission stats, quick actions, attention items
-- **Mission detail:** Assignment listing, resources, memories, status
+- **Overview page:** Project stats, quick actions, attention items
+- **Project detail:** Assignment listing, resources, memories, status
 - **Assignment detail:** Full assignment view with all fields, criteria checklist
 - **Kanban board:** Drag assignments between status columns
 - **Agent sessions:** Track active/completed/stopped agent sessions
 - **Server tracking:** Discover running dev servers via tmux session scanning
 - **Real-time updates:** WebSocket pushes file changes to the browser
-- **Markdown editing:** Edit mission.md, assignment.md, plan.md, scratchpad.md in-browser
+- **Markdown editing:** Edit project.md, assignment.md, plan files, scratchpad.md in-browser
 - **Attention queue:** Highlights blocked, failed, and review-pending items
 
 ### API Endpoints
 - `GET /api/overview` — Dashboard summary stats
-- `GET /api/missions` — List all missions
-- `GET /api/missions/:slug` — Mission detail with assignments
-- `GET /api/missions/:slug/assignments/:aslug` — Assignment detail
-- `GET /api/assignments` — All assignments across missions
+- `GET /api/projects` — List all projects
+- `GET /api/projects/:slug` — Project detail with assignments
+- `GET /api/projects/:slug/assignments/:aslug` — Assignment detail
+- `GET /api/assignments` — All assignments across projects
 - `GET /api/attention` — Items needing attention
 - `GET /api/agent-sessions` — Agent session list
-- `POST /api/missions` — Create mission
-- `POST /api/missions/:slug/assignments` — Create assignment
-- `PATCH /api/missions/:slug/assignments/:aslug` — Update assignment
+- `POST /api/projects` — Create project
+- `POST /api/projects/:slug/assignments` — Create assignment
+- `PATCH /api/projects/:slug/assignments/:aslug` — Update assignment
 - WebSocket at `/ws` for real-time file change notifications
 
 ### Architecture
@@ -276,9 +276,9 @@ syntaur                    # Dashboard is the default command
 Syntaur supports Cursor, Codex, and OpenCode via generated adapter files.
 
 ```bash
-syntaur setup-adapter cursor --mission <slug> --assignment <slug>
-syntaur setup-adapter codex --mission <slug> --assignment <slug>
-syntaur setup-adapter opencode --mission <slug> --assignment <slug>
+syntaur setup-adapter cursor --project <slug> --assignment <slug>
+syntaur setup-adapter codex --project <slug> --assignment <slug>
+syntaur setup-adapter opencode --project <slug> --assignment <slug>
 ```
 
 | Framework | Generated Files | Discovery |
@@ -297,17 +297,17 @@ Adapters embed protocol knowledge (write boundaries, lifecycle states, CLI comma
 
 **assignment.md:** id, slug, title, status, priority, created, updated, assignee, externalIds, dependsOn, blockedReason, workspace (repository, worktreePath, branch, parentBranch), tags
 
-**plan.md:** assignment, status (draft/approved/in_progress/completed), created, updated
+**plan files (plan.md, plan-v2.md, ...):** assignment, status (draft/approved/in_progress/completed), created, updated — zero or more per assignment, each linked from a todo in `assignment.md`'s `## Todos` section
 
 **handoff.md:** assignment, updated, handoffCount
 
 **decision-record.md:** assignment, updated, decisionCount
 
-**mission.md:** id, slug, title, archived, archivedAt, archivedReason, created, updated, externalIds, tags
+**project.md:** id, slug, title, archived, archivedAt, archivedReason, created, updated, externalIds, tags
 
-**manifest.md:** version, mission, generated
+**manifest.md:** version, project, generated
 
-**_status.md:** mission, generated, status, progress (total/completed/in_progress/blocked/pending/review/failed), needsAttention (blockedCount/failedCount/unansweredQuestions)
+**_status.md:** project, generated, status, progress (total/completed/in_progress/blocked/pending/review/failed), needsAttention (blockedCount/failedCount/unansweredQuestions)
 
 ### Conventions
 - **Timestamps:** RFC 3339 / ISO 8601 with UTC: `2026-03-18T14:30:00Z`
@@ -324,12 +324,12 @@ Adapters embed protocol knowledge (write boundaries, lifecycle states, CLI comma
 # 1. Run guided setup
 npx syntaur@latest setup
 
-# 2. Create your first mission
-syntaur create-mission "My First Mission"
+# 2. Create your first project
+syntaur create-project "My First Project"
 
 # 3. Create assignments
-syntaur create-assignment "Design the schema" --mission my-first-mission --priority high
-syntaur create-assignment "Implement the API" --mission my-first-mission --depends-on design-the-schema
+syntaur create-assignment "Design the schema" --project my-first-project --priority high
+syntaur create-assignment "Implement the API" --project my-first-project --depends-on design-the-schema
 
 # 4. Start the dashboard
 syntaur dashboard
@@ -338,7 +338,7 @@ syntaur dashboard
 ### Agent Workflow
 ```bash
 # In Claude Code, use skills:
-/grab-assignment my-first-mission       # Claim a pending assignment
+/grab-assignment my-first-project       # Claim a pending assignment
 /plan-assignment                         # Write implementation plan
 # ... do the work ...
 /complete-assignment                     # Handoff and complete
@@ -351,10 +351,10 @@ syntaur dashboard
 Created by `/grab-assignment` in the current working directory. Contains:
 ```json
 {
-  "missionSlug": "my-first-mission",
+  "projectSlug": "my-first-project",
   "assignmentSlug": "design-the-schema",
-  "missionDir": "/Users/you/.syntaur/missions/my-first-mission",
-  "assignmentDir": "/Users/you/.syntaur/missions/my-first-mission/assignments/design-the-schema",
+  "projectDir": "/Users/you/.syntaur/projects/my-first-project",
+  "assignmentDir": "/Users/you/.syntaur/projects/my-first-project/assignments/design-the-schema",
   "workspaceRoot": "/Users/you/projects/my-app",
   "title": "Design the schema",
   "branch": "feature/design-the-schema",
@@ -370,7 +370,7 @@ Read by `/plan-assignment`, `/complete-assignment`, and the write boundary hook
 ## Common Questions
 
 **Q: How do I see what assignments are available?**
-A: Use `/grab-assignment <mission-slug>` — it lists pending assignments. Or check the dashboard, or read `_index-assignments.md`.
+A: Use `/grab-assignment <project-slug>` — it lists pending assignments. Or check the dashboard, or read `_index-assignments.md`.
 
 **Q: Can two agents work on the same assignment?**
 A: No. Single-writer guarantee — one agent per assignment folder. Use separate assignments for parallel work.

package/platforms/claude-code/commands/doctor-syntaur/doctor-syntaur.md

@@ -0,0 +1,112 @@
+---
+name: doctor-syntaur
+description: Diagnose and help recover from common Syntaur bad states
+arguments:
+  - name: args
+    description: "Optional flags: --verbose, --only <check-id>"
+    required: false
+---
+
+# /doctor-syntaur
+
+Run `syntaur doctor` and help the user interpret the results, remediating issues where appropriate. Respect Syntaur write boundaries throughout.
+
+## Usage
+
+- `/doctor-syntaur` — run all checks
+- `/doctor-syntaur --verbose` — include passing checks in the summary
+- `/doctor-syntaur --only <check-id>` — re-run one check after remediation (e.g. `--only assignment.workspace-missing`)
+
+## Instructions
+
+When the user runs this command:
+
+### Step 1: Parse arguments
+
+From the argument string, extract optional flags:
+
+- `--verbose` — pass through to the CLI and include passing checks in the summary
+- `--only <check-id>` — pass through to the CLI to restrict to a single check
+
+### Step 2: Run the CLI and capture output + exit code
+
+Exit code 1 is expected (means issues were found). Do NOT let a non-zero exit fail the turn. Use a pattern like:
+
+```bash
+output=$(syntaur doctor --json [--only <check-id>] 2>&1); exit_code=$?
+```
+
+Then parse `$output` as JSON. If the JSON fails to parse, surface the raw output — that means the CLI itself broke.
+
+### Step 3: Handle exit codes and severity
+
+- **Exit 2** — Syntaur isn't initialized. Tell the user to run `syntaur init` and stop.
+- **Exit 1** (one or more errors) — continue to step 4; report both errors and warnings.
+- **Exit 0 and `summary.warn === 0`** — everything passed. Say so in one line (e.g. "All checks passed — no issues found.") and stop.
+- **Exit 0 and `summary.warn > 0`** — no errors but warnings exist. Continue to step 4; report the warnings. The CLI only exits 1 on errors, so warn-only runs still need to be surfaced to the user.
+
+### Step 4: Summarize results
+
+Group the `checks` array from the JSON by `category`. For each category:
+
+- Show errors first, then warnings.
+- Skip passes unless `--verbose` was passed.
+- Always include the `check.id` so the user can reference a specific issue in follow-up.
+
+Format each issue like:
+
+```
+[category] check.id — title
+  detail line
+  affected: path (truncate long lists)
+  fix: remediation.suggestion
+```
+
+### Step 5: Establish your write boundary (before offering any edit)
+
+Doctor reports issues from anywhere under `~/.syntaur/`. You are NOT allowed to edit most of those files. Before offering any remediation edit, compute your current write boundary:
+
+1. Read `.syntaur/context.json` in the current working directory (the same `cwd` you ran the CLI from).
+2. If the file does not exist, or exists but has no assignment fields (`projectSlug`, `assignmentSlug`, `projectDir`, `assignmentDir`):
+   - You have NO assignment context.
+   - Your only permitted edit target is the literal file `<cwd>/.syntaur/context.json` itself.
+   - For every other issue, show the `suggestion` text verbatim and do NOT offer to edit.
+3. If the file has assignment fields, record these paths:
+   - `assignmentDir` — your per-assignment write zone.
+   - `workspaceRoot` — your code write zone (may be absent).
+   - `<cwd>/.syntaur/context.json` — always editable.
+
+### Step 6: Offer remediation (issue by issue)
+
+For each error or warning, determine what kind of offer is appropriate.
+
+**First, use `remediation.kind`:**
+
+- **`auto-safe`** — offer to run `syntaur doctor --fix --only <id>`. Ask the user to confirm before running. (v1 has no auto-safe remediations yet — this is a placeholder for future versions.)
+- **`auto-destructive`** — never auto-run. Describe the impact and wait for the user.
+- **`manual`** — apply the path check below before offering an edit.
+
+**For `manual` remediations, compare each path in `affected[]` against your boundary from Step 5:**
+
+1. Let `allowed = [assignmentDir, workspaceRoot, <cwd>/.syntaur/context.json]` (dropping any undefined entries).
+2. A path is within boundary if and only if it equals `<cwd>/.syntaur/context.json` OR it is a strict path-prefix descendant of `assignmentDir` or `workspaceRoot`. Use path-segment comparison, not substring matching.
+3. If **every** path in `affected[]` is within boundary, you may offer to make the edit. Show a diff first; wait for confirmation; then write.
+4. If **any** path in `affected[]` is outside your boundary, do NOT offer to edit. Show the `suggestion` text verbatim and tell the user they or another tool must apply it.
+
+**Hard stop list — never write to these regardless of what doctor reports:**
+
+- `project.md`, `agent.md`, `claude.md`, `manifest.md`, `_status.md`
+- Any file starting with `_index-` or ending in `_index.md`
+- Any file in a project's `resources/` or `memories/` directory
+- Any file inside a different assignment's folder (i.e. `projects/<m>/assignments/<other>/...` where `<other> !== assignmentSlug`)
+
+### Step 7: Suggest a follow-up
+
+After proposing fixes, suggest the user re-run `/doctor-syntaur --only <check-id>` (or the whole command) to verify that issues resolved.
+
+## Guardrails
+
+- Always invoke `syntaur doctor --json`. Do not re-derive checks from the filesystem yourself.
+- Never pass `--fix` without explicit user confirmation.
+- Always show each issue's `check.id` so the user can reference it.
+- If the CLI output isn't valid JSON, show the raw output and stop — something is wrong with the install.