From dc301aae91ec6182cba5724847d9cc4f2903985d Mon Sep 17 00:00:00 2001
From: jefbinomed <jean.francois.garreau@gmail.com>
Date: Tue, 14 Jul 2026 15:04:13 +0200
Subject: [PATCH 1/7] =?UTF-8?q?=F0=9F=90=9B=20fix(docs):=20base=20VitePres?=
 =?UTF-8?q?s=20/talk-control/=20pour=20GitHub=20Pages?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le site est servi en project page (talkcontrol.github.io/talk-control/)
mais base valait '/' : tous les assets étaient référencés à la racine du
domaine et 404aient — page publiée sans style ni JS. Vérifié en local :
6 références préfixées, 0 à la racine après build.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 docs-sources/.vitepress/config.js | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs-sources/.vitepress/config.js b/docs-sources/.vitepress/config.js
index b7a3b3f0..d26a7b98 100644
--- a/docs-sources/.vitepress/config.js
+++ b/docs-sources/.vitepress/config.js
@@ -1,7 +1,9 @@
 export default {
     title: 'TalkControl',
     description: 'TalkControl documentation',
-    base: '/',
+    // Le site est servi en project page GitHub Pages (…github.io/talk-control/) —
+    // sans ce base, les assets sont référencés à la racine du domaine et 404ent.
+    base: '/talk-control/',
     ignoreDeadLinks: 'localhostLinks',
     themeConfig: {
         nav: [

From 0e677b816c42b53a14c3e78bd6846e1054180181 Mon Sep 17 00:00:00 2001
From: jefbinomed <jean.francois.garreau@gmail.com>
Date: Fri, 7 Aug 2026 16:17:03 +0200
Subject: [PATCH 2/7] =?UTF-8?q?=F0=9F=94=A7=20chore(tooling):=20int=C3=A9g?=
 =?UTF-8?q?rer=20OpenSpec=20pour=20le=20workflow=20spec-driven?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- openspec init — structure openspec/specs/ + openspec/changes/
- config.yaml avec contexte TalkControl (stack, conventions, règles)
- 9 skills + 9 commands /opsx:* dans .claude/ pour Claude Code
- .gitignore : exceptionner .claude/commands/ et .claude/skills/openspec-*/

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
---
 .claude/commands/opsx/apply.md                | 158 +++++
 .claude/commands/opsx/archive.md              | 162 +++++
 .claude/commands/opsx/continue.md             | 122 ++++
 .claude/commands/opsx/explore.md              | 182 ++++++
 .claude/commands/opsx/new.md                  |  80 +++
 .claude/commands/opsx/onboard.md              | 570 +++++++++++++++++
 .claude/commands/opsx/propose.md              | 117 ++++
 .claude/commands/opsx/sync.md                 | 150 +++++
 .claude/commands/opsx/verify.md               | 171 ++++++
 .claude/skills/openspec-apply-change/SKILL.md | 162 +++++
 .../skills/openspec-archive-change/SKILL.md   | 119 ++++
 .../skills/openspec-continue-change/SKILL.md  | 126 ++++
 .claude/skills/openspec-explore/SKILL.md      | 300 +++++++++
 .claude/skills/openspec-new-change/SKILL.md   |  85 +++
 .claude/skills/openspec-onboard/SKILL.md      | 574 ++++++++++++++++++
 .claude/skills/openspec-propose/SKILL.md      | 121 ++++
 .claude/skills/openspec-sync-specs/SKILL.md   | 154 +++++
 .../skills/openspec-verify-change/SKILL.md    | 175 ++++++
 .gitignore                                    |  12 +
 openspec/config.yaml                          |  43 ++
 20 files changed, 3583 insertions(+)
 create mode 100644 .claude/commands/opsx/apply.md
 create mode 100644 .claude/commands/opsx/archive.md
 create mode 100644 .claude/commands/opsx/continue.md
 create mode 100644 .claude/commands/opsx/explore.md
 create mode 100644 .claude/commands/opsx/new.md
 create mode 100644 .claude/commands/opsx/onboard.md
 create mode 100644 .claude/commands/opsx/propose.md
 create mode 100644 .claude/commands/opsx/sync.md
 create mode 100644 .claude/commands/opsx/verify.md
 create mode 100644 .claude/skills/openspec-apply-change/SKILL.md
 create mode 100644 .claude/skills/openspec-archive-change/SKILL.md
 create mode 100644 .claude/skills/openspec-continue-change/SKILL.md
 create mode 100644 .claude/skills/openspec-explore/SKILL.md
 create mode 100644 .claude/skills/openspec-new-change/SKILL.md
 create mode 100644 .claude/skills/openspec-onboard/SKILL.md
 create mode 100644 .claude/skills/openspec-propose/SKILL.md
 create mode 100644 .claude/skills/openspec-sync-specs/SKILL.md
 create mode 100644 .claude/skills/openspec-verify-change/SKILL.md
 create mode 100644 openspec/config.yaml

diff --git a/.claude/commands/opsx/apply.md b/.claude/commands/opsx/apply.md
new file mode 100644
index 00000000..bb7f5188
--- /dev/null
+++ b/.claude/commands/opsx/apply.md
@@ -0,0 +1,158 @@
+---
+name: 'OPSX: Apply'
+description: Implement tasks from an OpenSpec change (Experimental)
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
+
+Implement tasks from an OpenSpec change.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name (e.g., `/opsx:apply add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+    If a name is provided, use it. Otherwise:
+    - Infer from conversation context if the user mentioned a change
+    - Auto-select if only one active change exists
+    - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+    Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to understand:
+    - `schemaName`: The workflow being used (e.g., "spec-driven")
+    - `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints
+    - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+    ```bash
+    openspec instructions apply --change "<name>" --json
+    ```
+
+    This returns:
+    - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema)
+    - Progress (total, complete, remaining)
+    - Task list with status
+    - Dynamic instruction based on current state
+
+    **Handle states:**
+    - If `state: "blocked"` (missing artifacts): show message, suggest using `/opsx:continue`
+    - If `state: "all_done"`: congratulate, suggest archive
+    - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+    Read every file path listed under `contextFiles` from the apply instructions output.
+    The files depend on the schema being used:
+    - **spec-driven**: proposal, specs, design, tasks
+    - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+    Display:
+    - Schema being used
+    - Progress: "N/M tasks complete"
+    - Remaining tasks overview
+    - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+    For each pending task:
+    - Show which task is being worked on
+    - Make the code changes required
+    - Keep changes minimal and focused
+    - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+    - Continue to next task
+
+    **Pause if:**
+    - Task is unclear → ask for clarification
+    - Implementation reveals a design issue → suggest updating artifacts
+    - Error or blocker encountered → report and wait for guidance
+    - User interrupts
+
+7. **On completion or pause, show status**
+
+    Display:
+    - Tasks completed this session
+    - Overall progress: "N/M tasks complete"
+    - If all done: suggest archive
+    - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! You can archive this change with `/opsx:archive`.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
diff --git a/.claude/commands/opsx/archive.md b/.claude/commands/opsx/archive.md
new file mode 100644
index 00000000..aa0b8f3e
--- /dev/null
+++ b/.claude/commands/opsx/archive.md
@@ -0,0 +1,162 @@
+---
+name: 'OPSX: Archive'
+description: Archive a completed change in the experimental workflow
+category: Workflow
+tags: [workflow, archive, experimental]
+---
+
+Archive a completed change in the experimental workflow.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name after `/opsx:archive` (e.g., `/opsx:archive add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+    Show only active changes (not already archived).
+    Include the schema used for each change if available.
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+    Run `openspec status --change "<name>" --json` to check artifact completion.
+
+    Parse the JSON to understand:
+    - `schemaName`: The workflow being used
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context
+    - `artifacts`: List of artifacts with their status (`done` or other)
+
+    **If any artifacts are not `done`:**
+    - Display warning listing incomplete artifacts
+    - Prompt user for confirmation to continue
+    - Proceed if user confirms
+
+3. **Check task completion status**
+
+    Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+    Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+    **If incomplete tasks found:**
+    - Display warning showing count of incomplete tasks
+    - Prompt user for confirmation to continue
+    - Proceed if user confirms
+
+    **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+    Use `artifactPaths.specs.existingOutputPaths` from status JSON to check for delta specs. If none exist, proceed without sync prompt.
+
+    **If delta specs exist:**
+    - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+    - Determine what changes would be applied (adds, modifications, removals, renames)
+    - Show a combined summary before prompting
+
+    **Prompt options:**
+    - If changes needed: "Sync now (recommended)", "Archive without syncing"
+    - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+    If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+    Create an `archive` directory under `planningHome.changesDir` if it doesn't exist:
+
+    ```bash
+    mkdir -p "<planningHome.changesDir>/archive"
+    ```
+
+    Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+    **Check if target already exists:**
+    - If yes: Fail with error, suggest renaming existing archive or using different date
+    - If no: Move `changeRoot` to the archive directory
+
+    ```bash
+    mv "<changeRoot>" "<planningHome.changesDir>/archive/YYYY-MM-DD-<name>"
+    ```
+
+6. **Display summary**
+
+    Show archive completion summary including:
+    - Change name
+    - Schema that was used
+    - Archive location
+    - Spec sync status (synced / sync skipped / no delta specs)
+    - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** the archive path derived from `planningHome.changesDir`/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success (No Delta Specs)**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** the archive path derived from `planningHome.changesDir`/YYYY-MM-DD-<name>/
+**Specs:** No delta specs
+
+All artifacts complete. All tasks complete.
+```
+
+**Output On Success With Warnings**
+
+```
+## Archive Complete (with warnings)
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** the archive path derived from `planningHome.changesDir`/YYYY-MM-DD-<name>/
+**Specs:** Sync skipped (user chose to skip)
+
+**Warnings:**
+- Archived with 2 incomplete artifacts
+- Archived with 3 incomplete tasks
+- Delta spec sync was skipped (user chose to skip)
+
+Review the archive if this was not intentional.
+```
+
+**Output On Error (Archive Exists)**
+
+```
+## Archive Failed
+
+**Change:** <change-name>
+**Target:** the archive path derived from `planningHome.changesDir`/YYYY-MM-DD-<name>/
+
+Target archive directory already exists.
+
+**Options:**
+1. Rename the existing archive
+2. Delete the existing archive if it's a duplicate
+3. Wait until a different date to archive
+```
+
+**Guardrails**
+
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- Don't block archive on warnings - just inform and confirm
+- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use the Skill tool to invoke `openspec-sync-specs` (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting
diff --git a/.claude/commands/opsx/continue.md b/.claude/commands/opsx/continue.md
new file mode 100644
index 00000000..6898b5d5
--- /dev/null
+++ b/.claude/commands/opsx/continue.md
@@ -0,0 +1,122 @@
+---
+name: 'OPSX: Continue'
+description: Continue working on a change - create the next artifact (Experimental)
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
+
+Continue working on a change by creating the next artifact.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name after `/opsx:continue` (e.g., `/opsx:continue add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
+
+    Present the top 3-4 most recently modified changes as options, showing:
+    - Change name
+    - Schema (from `schema` field if present, otherwise "spec-driven")
+    - Status (e.g., "0/5 tasks", "complete", "no tasks")
+    - How recently it was modified (from `lastModified` field)
+
+    Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check current status**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to understand current state. The response includes:
+    - `schemaName`: The workflow schema being used (e.g., "spec-driven")
+    - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked")
+    - `isComplete`: Boolean indicating if all artifacts are complete
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.
+
+3. **Act based on status**:
+
+    ***
+
+    **If all artifacts are complete (`isComplete: true`)**:
+    - Congratulate the user
+    - Show final status including the schema used
+    - Suggest: "All artifacts created! You can now implement this change with `/opsx:apply` or archive it with `/opsx:archive`."
+    - STOP
+
+    ***
+
+    **If artifacts are ready to create** (status shows artifacts with `status: "ready"`):
+    - Pick the FIRST artifact with `status: "ready"` from the status output
+    - Get its instructions:
+        ```bash
+        openspec instructions <artifact-id> --change "<name>" --json
+        ```
+    - Parse the JSON. The key fields are:
+        - `context`: Project background (constraints for you - do NOT include in output)
+        - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+        - `template`: The structure to use for your output file
+        - `instruction`: Schema-specific guidance
+        - `resolvedOutputPath`: Resolved path or pattern to write the artifact
+        - `dependencies`: Completed artifacts to read for context
+    - **Create the artifact file**:
+        - Read any completed dependency files for context
+        - Use `template` as the structure - fill in its sections
+        - Apply `context` and `rules` as constraints when writing - but do NOT copy them into the file
+        - Write to the `resolvedOutputPath` specified in instructions. If it is a glob pattern, choose the concrete file path using the schema instruction and the change's context
+    - Show what was created and what's now unlocked
+    - STOP after creating ONE artifact
+
+    ***
+
+    **If no artifacts are ready (all blocked)**:
+    - This shouldn't happen with a valid schema
+    - Show status and suggest checking for issues
+
+4. **After creating an artifact, show progress**
+    ```bash
+    openspec status --change "<name>"
+    ```
+
+**Output**
+
+After each invocation, show:
+
+- Which artifact was created
+- Schema workflow being used
+- Current progress (N/M complete)
+- What artifacts are now unlocked
+- Prompt: "Run `/opsx:continue` to create the next artifact"
+
+**Artifact Creation Guidelines**
+
+The artifact types and their purpose depend on the schema. Use the `instruction` field from the instructions output to understand what to create.
+
+Common artifact patterns:
+
+**spec-driven schema** (proposal → specs → design → tasks):
+
+- **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.
+    - The Capabilities section is critical - each capability listed will need a spec file.
+- **specs/<capability>/spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).
+- **design.md**: Document technical decisions, architecture, and implementation approach.
+- **tasks.md**: Break down implementation into checkboxed tasks.
+
+For other schemas, follow the `instruction` field from the CLI output.
+
+**Guardrails**
+
+- Create ONE artifact per invocation
+- Always read dependency artifacts before creating a new one
+- Never skip artifacts or create out of order
+- If context is unclear, ask the user before creating
+- Verify the artifact file exists after writing before marking progress
+- Use the schema's artifact sequence, don't assume specific artifact names
+- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
+    - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+    - These guide what you write, but should never appear in the output
diff --git a/.claude/commands/opsx/explore.md b/.claude/commands/opsx/explore.md
new file mode 100644
index 00000000..be3d77fe
--- /dev/null
+++ b/.claude/commands/opsx/explore.md
@@ -0,0 +1,182 @@
+---
+name: 'OPSX: Explore'
+description: 'Enter explore mode - think through ideas, investigate problems, clarify requirements'
+category: Workflow
+tags: [workflow, explore, experimental, thinking]
+---
+
+Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
+
+**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.
+
+**This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: The argument after `/opsx:explore` is whatever the user wants to think about. Could be:
+
+- A vague idea: "real-time collaboration"
+- A specific problem: "the auth system is getting unwieldy"
+- A change name: "add-dark-mode" (to explore in context of that change)
+- A comparison: "postgres vs sqlite for this"
+- Nothing (just enter explore mode)
+
+---
+
+## The Stance
+
+- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
+- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
+- **Visual** - Use ASCII diagrams liberally when they'd help clarify thinking
+- **Adaptive** - Follow interesting threads, pivot when new information emerges
+- **Patient** - Don't rush to conclusions, let the shape of the problem emerge
+- **Grounded** - Explore the actual codebase when relevant, don't just theorize
+
+---
+
+## What You Might Do
+
+Depending on what the user brings, you might:
+
+**Explore the problem space**
+
+- Ask clarifying questions that emerge from what they said
+- Challenge assumptions
+- Reframe the problem
+- Find analogies
+
+**Investigate the codebase**
+
+- Map existing architecture relevant to the discussion
+- Find integration points
+- Identify patterns already in use
+- Surface hidden complexity
+
+**Compare options**
+
+- Brainstorm multiple approaches
+- Build comparison tables
+- Sketch tradeoffs
+- Recommend a path (if asked)
+
+**Visualize**
+
+```
+┌─────────────────────────────────────────┐
+│     Use ASCII diagrams liberally        │
+├─────────────────────────────────────────┤
+│                                         │
+│      ┌────────┐         ┌────────┐      │
+│      │ State  │────────▶│ State  │      │
+│      │   A    │         │   B    │      │
+│      └────────┘         └────────┘      │
+│                                         │
+│   System diagrams, state machines,      │
+│   data flows, architecture sketches,    │
+│   dependency graphs, comparison tables  │
+│                                         │
+└─────────────────────────────────────────┘
+```
+
+**Surface risks and unknowns**
+
+- Identify what could go wrong
+- Find gaps in understanding
+- Suggest spikes or investigations
+
+---
+
+## OpenSpec Awareness
+
+You have full context of the OpenSpec system. Use it naturally, don't force it.
+
+### Check for context
+
+At the start, quickly check what exists:
+
+```bash
+openspec list --json
+```
+
+This tells you:
+
+- If there are active changes
+- Their names, schemas, and status
+- What the user might be working on
+
+If the user mentioned a specific change name, read its artifacts for context.
+
+### When no change exists
+
+Think freely. When insights crystallize, you might offer:
+
+- "This feels solid enough to start a change. Want me to create a proposal?"
+- Or keep exploring - no pressure to formalize
+
+### When a change exists
+
+If the user mentions a change or you detect one is relevant:
+
+1. **Resolve and read existing artifacts for context**
+    - Run `openspec status --change "<name>" --json`.
+    - Use `changeRoot`, `artifactPaths`, and `actionContext` from the status JSON.
+    - Read existing files from `artifactPaths.<artifact>.existingOutputPaths`.
+
+2. **Reference them naturally in conversation**
+    - "Your design mentions using Redis, but we just realized SQLite fits better..."
+    - "The proposal scopes this to premium users, but we're now thinking everyone..."
+
+3. **Offer to capture when decisions are made**
+
+    | Insight Type               | Where to Capture             |
+    | -------------------------- | ---------------------------- |
+    | New requirement discovered | `specs/<capability>/spec.md` |
+    | Requirement changed        | `specs/<capability>/spec.md` |
+    | Design decision made       | `design.md`                  |
+    | Scope changed              | `proposal.md`                |
+    | New work identified        | `tasks.md`                   |
+    | Assumption invalidated     | Relevant artifact            |
+
+    Example offers:
+    - "That's a design decision. Capture it in design.md?"
+    - "This is a new requirement. Add it to specs?"
+    - "This changes scope. Update the proposal?"
+
+4. **The user decides** - Offer and move on. Don't pressure. Don't auto-capture.
+
+---
+
+## What You Don't Have To Do
+
+- Follow a script
+- Ask the same questions every time
+- Produce a specific artifact
+- Reach a conclusion
+- Stay on topic if a tangent is valuable
+- Be brief (this is thinking time)
+
+---
+
+## Ending Discovery
+
+There's no required ending. Discovery might:
+
+- **Flow into a proposal**: "Ready to start? I can create a change proposal."
+- **Result in artifact updates**: "Updated design.md with these decisions"
+- **Just provide clarity**: User has what they need, moves on
+- **Continue later**: "We can pick this up anytime"
+
+When things crystallize, you might offer a summary - but it's optional. Sometimes the thinking IS the value.
+
+---
+
+## Guardrails
+
+- **Don't implement** - Never write code or implement features. Creating OpenSpec artifacts is fine, writing application code is not.
+- **Don't fake understanding** - If something is unclear, dig deeper
+- **Don't rush** - Discovery is thinking time, not task time
+- **Don't force structure** - Let patterns emerge naturally
+- **Don't auto-capture** - Offer to save insights, don't just do it
+- **Do visualize** - A good diagram is worth many paragraphs
+- **Do explore the codebase** - Ground discussions in reality
+- **Do question assumptions** - Including the user's and your own
diff --git a/.claude/commands/opsx/new.md b/.claude/commands/opsx/new.md
new file mode 100644
index 00000000..e4185470
--- /dev/null
+++ b/.claude/commands/opsx/new.md
@@ -0,0 +1,80 @@
+---
+name: 'OPSX: New'
+description: Start a new change using the experimental artifact workflow (OPSX)
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
+
+Start a new change using the experimental artifact-driven approach.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: The argument after `/opsx:new` is the change name (kebab-case), OR a description of what the user wants to build.
+
+**Steps**
+
+1. **If no input provided, ask what they want to build**
+
+    Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+    > "What change do you want to work on? Describe what you want to build or fix."
+
+    From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+    **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Determine the workflow schema**
+
+    Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.
+
+    **Use a different schema only if the user mentions:**
+    - A specific schema name → use `--schema <name>`
+    - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose
+
+    **Otherwise**: Omit `--schema` to use the default.
+
+3. **Create the change directory**
+
+    ```bash
+    openspec new change "<name>"
+    ```
+
+    Add `--schema <name>` only if the user requested a specific workflow.
+    This creates a scaffolded change in the planning home resolved by the CLI.
+
+4. **Show the artifact status**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Use the returned `planningHome`, `changeRoot`, `artifactPaths`, and `nextSteps` instead of assuming repo-local paths.
+
+5. **Get instructions for the first artifact**
+   The first artifact depends on the schema. Check the status output to find the first artifact with status "ready".
+
+    ```bash
+    openspec instructions <first-artifact-id> --change "<name>"
+    ```
+
+    This outputs the template and context for creating the first artifact.
+
+6. **STOP and wait for user direction**
+
+**Output**
+
+After completing the steps, summarize:
+
+- Change name and location
+- Schema/workflow being used and its artifact sequence
+- Current status (0/N artifacts complete)
+- The template for the first artifact
+- Prompt: "Ready to create the first artifact? Run `/opsx:continue` or just describe what this change is about and I'll draft it."
+
+**Guardrails**
+
+- Do NOT create any artifacts yet - just show the instructions
+- Do NOT advance beyond showing the first artifact template
+- If the name is invalid (not kebab-case), ask for a valid name
+- If a change with that name already exists, suggest using `/opsx:continue` instead
+- Pass --schema if using a non-default workflow
diff --git a/.claude/commands/opsx/onboard.md b/.claude/commands/opsx/onboard.md
new file mode 100644
index 00000000..5d891a58
--- /dev/null
+++ b/.claude/commands/opsx/onboard.md
@@ -0,0 +1,570 @@
+---
+name: 'OPSX: Onboard'
+description: Guided onboarding - walk through a complete OpenSpec workflow cycle with narration
+category: Workflow
+tags: [workflow, onboarding, tutorial, learning]
+---
+
+Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+---
+
+## Preflight
+
+Before starting, check if the OpenSpec CLI is installed:
+
+```bash
+# Unix/macOS
+openspec --version 2>&1 || echo "CLI_NOT_INSTALLED"
+# Windows (PowerShell)
+# if (Get-Command openspec -ErrorAction SilentlyContinue) { openspec --version } else { echo "CLI_NOT_INSTALLED" }
+```
+
+**If CLI not installed:**
+
+> OpenSpec CLI is not installed. Install it first, then come back to `/opsx:onboard`.
+
+Stop here if not installed.
+
+---
+
+## Phase 1: Welcome
+
+Display:
+
+```
+## Welcome to OpenSpec!
+
+I'll walk you through a complete change cycle—from idea to implementation—using a real task in your codebase. Along the way, you'll learn the workflow by doing it.
+
+**What we'll do:**
+1. Pick a small, real task in your codebase
+2. Explore the problem briefly
+3. Create a change (the container for our work)
+4. Build the artifacts: proposal → specs → design → tasks
+5. Implement the tasks
+6. Archive the completed change
+
+**Time:** ~15-20 minutes
+
+Let's start by finding something to work on.
+```
+
+---
+
+## Phase 2: Task Selection
+
+### Codebase Analysis
+
+Scan the codebase for small improvement opportunities. Look for:
+
+1. **TODO/FIXME comments** - Search for `TODO`, `FIXME`, `HACK`, `XXX` in code files
+2. **Missing error handling** - `catch` blocks that swallow errors, risky operations without try-catch
+3. **Functions without tests** - Cross-reference `src/` with test directories
+4. **Type issues** - `any` types in TypeScript files (`: any`, `as any`)
+5. **Debug artifacts** - `console.log`, `console.debug`, `debugger` statements in non-debug code
+6. **Missing validation** - User input handlers without validation
+
+Also check recent git activity:
+
+```bash
+# Unix/macOS
+git log --oneline -10 2>/dev/null || echo "No git history"
+# Windows (PowerShell)
+# git log --oneline -10 2>$null; if ($LASTEXITCODE -ne 0) { echo "No git history" }
+```
+
+### Present Suggestions
+
+From your analysis, present 3-4 specific suggestions:
+
+```
+## Task Suggestions
+
+Based on scanning your codebase, here are some good starter tasks:
+
+**1. [Most promising task]**
+   Location: `src/path/to/file.ts:42`
+   Scope: ~1-2 files, ~20-30 lines
+   Why it's good: [brief reason]
+
+**2. [Second task]**
+   Location: `src/another/file.ts`
+   Scope: ~1 file, ~15 lines
+   Why it's good: [brief reason]
+
+**3. [Third task]**
+   Location: [location]
+   Scope: [estimate]
+   Why it's good: [brief reason]
+
+**4. Something else?**
+   Tell me what you'd like to work on.
+
+Which task interests you? (Pick a number or describe your own)
+```
+
+**If nothing found:** Fall back to asking what the user wants to build:
+
+> I didn't find obvious quick wins in your codebase. What's something small you've been meaning to add or fix?
+
+### Scope Guardrail
+
+If the user picks or describes something too large (major feature, multi-day work):
+
+```
+That's a valuable task, but it's probably larger than ideal for your first OpenSpec run-through.
+
+For learning the workflow, smaller is better—it lets you see the full cycle without getting stuck in implementation details.
+
+**Options:**
+1. **Slice it smaller** - What's the smallest useful piece of [their task]? Maybe just [specific slice]?
+2. **Pick something else** - One of the other suggestions, or a different small task?
+3. **Do it anyway** - If you really want to tackle this, we can. Just know it'll take longer.
+
+What would you prefer?
+```
+
+Let the user override if they insist—this is a soft guardrail.
+
+---
+
+## Phase 3: Explore Demo
+
+Once a task is selected, briefly demonstrate explore mode:
+
+```
+Before we create a change, let me quickly show you **explore mode**—it's how you think through problems before committing to a direction.
+```
+
+Spend 1-2 minutes investigating the relevant code:
+
+- Read the file(s) involved
+- Draw a quick ASCII diagram if it helps
+- Note any considerations
+
+```
+## Quick Exploration
+
+[Your brief analysis—what you found, any considerations]
+
+┌─────────────────────────────────────────┐
+│   [Optional: ASCII diagram if helpful]  │
+└─────────────────────────────────────────┘
+
+Explore mode (`/opsx:explore`) is for this kind of thinking—investigating before implementing. You can use it anytime you need to think through a problem.
+
+Now let's create a change to hold our work.
+```
+
+**PAUSE** - Wait for user acknowledgment before proceeding.
+
+---
+
+## Phase 4: Create the Change
+
+**EXPLAIN:**
+
+```
+## Creating a Change
+
+A "change" in OpenSpec is a container for all the thinking and planning around a piece of work. It lives at the `changeRoot` reported by `openspec status --change "<name>" --json` and holds your artifacts—proposal, specs, design, tasks.
+
+Let me create one for our task.
+```
+
+**DO:** Create the change with a derived kebab-case name:
+
+```bash
+openspec new change "<derived-name>"
+```
+
+**SHOW:**
+
+```
+Created: <changeRoot from status JSON>
+
+The folder structure:
+```
+
+<changeRoot>/
+├── proposal.md ← Why we're doing this (empty, we'll fill it)
+├── design.md ← How we'll build it (empty)
+├── specs/ ← Detailed requirements (empty)
+└── tasks.md ← Implementation checklist (empty)
+
+```
+
+Now let's fill in the first artifact—the proposal.
+```
+
+---
+
+## Phase 5: Proposal
+
+**EXPLAIN:**
+
+```
+## The Proposal
+
+The proposal captures **why** we're making this change and **what** it involves at a high level. It's the "elevator pitch" for the work.
+
+I'll draft one based on our task.
+```
+
+**DO:** Draft the proposal content (don't save yet):
+
+```
+Here's a draft proposal:
+
+---
+
+## Why
+
+[1-2 sentences explaining the problem/opportunity]
+
+## What Changes
+
+[Bullet points of what will be different]
+
+## Capabilities
+
+### New Capabilities
+- `<capability-name>`: [brief description]
+
+### Modified Capabilities
+<!-- If modifying existing behavior -->
+
+## Impact
+
+- `src/path/to/file.ts`: [what changes]
+- [other files if applicable]
+
+---
+
+Does this capture the intent? I can adjust before we save it.
+```
+
+**PAUSE** - Wait for user approval/feedback.
+
+After approval, save the proposal:
+
+```bash
+openspec instructions proposal --change "<name>" --json
+```
+
+Then write the content to the `resolvedOutputPath` from `openspec instructions proposal --change "<name>" --json`.
+
+```
+Proposal saved. This is your "why" document—you can always come back and refine it as understanding evolves.
+
+Next up: specs.
+```
+
+---
+
+## Phase 6: Specs
+
+**EXPLAIN:**
+
+```
+## Specs
+
+Specs define **what** we're building in precise, testable terms. They use a requirement/scenario format that makes expected behavior crystal clear.
+
+For a small task like this, we might only need one spec file.
+```
+
+**DO:** Resolve where the spec file should be created:
+
+```bash
+openspec instructions specs --change "<name>" --json
+# Use resolvedOutputPath from the JSON. If it is a glob, choose the concrete file path using the schema instruction and the change's context.
+```
+
+Draft the spec content:
+
+```
+Here's the spec:
+
+---
+
+## ADDED Requirements
+
+### Requirement: <Name>
+
+<Description of what the system should do>
+
+#### Scenario: <Scenario name>
+
+- **WHEN** <trigger condition>
+- **THEN** <expected outcome>
+- **AND** <additional outcome if needed>
+
+---
+
+This format—WHEN/THEN/AND—makes requirements testable. You can literally read them as test cases.
+```
+
+Save to the concrete file path chosen from `resolvedOutputPath`.
+
+---
+
+## Phase 7: Design
+
+**EXPLAIN:**
+
+```
+## Design
+
+The design captures **how** we'll build it—technical decisions, tradeoffs, approach.
+
+For small changes, this might be brief. That's fine—not every change needs deep design discussion.
+```
+
+**DO:** Draft design.md:
+
+```
+Here's the design:
+
+---
+
+## Context
+
+[Brief context about the current state]
+
+## Goals / Non-Goals
+
+**Goals:**
+- [What we're trying to achieve]
+
+**Non-Goals:**
+- [What's explicitly out of scope]
+
+## Decisions
+
+### Decision 1: [Key decision]
+
+[Explanation of approach and rationale]
+
+---
+
+For a small task, this captures the key decisions without over-engineering.
+```
+
+Save to the `resolvedOutputPath` from `openspec instructions design --change "<name>" --json`.
+
+---
+
+## Phase 8: Tasks
+
+**EXPLAIN:**
+
+```
+## Tasks
+
+Finally, we break the work into implementation tasks—checkboxes that drive the apply phase.
+
+These should be small, clear, and in logical order.
+```
+
+**DO:** Generate tasks based on specs and design:
+
+```
+Here are the implementation tasks:
+
+---
+
+## 1. [Category or file]
+
+- [ ] 1.1 [Specific task]
+- [ ] 1.2 [Specific task]
+
+## 2. Verify
+
+- [ ] 2.1 [Verification step]
+
+---
+
+Each checkbox becomes a unit of work in the apply phase. Ready to implement?
+```
+
+**PAUSE** - Wait for user to confirm they're ready to implement.
+
+Save to the `resolvedOutputPath` from `openspec instructions tasks --change "<name>" --json`.
+
+---
+
+## Phase 9: Apply (Implementation)
+
+**EXPLAIN:**
+
+```
+## Implementation
+
+Now we implement each task, checking them off as we go. I'll announce each one and occasionally note how the specs/design informed the approach.
+```
+
+**DO:** For each task:
+
+1. Announce: "Working on task N: [description]"
+2. Implement the change in the codebase
+3. Reference specs/design naturally: "The spec says X, so I'm doing Y"
+4. Mark complete in tasks.md: `- [ ]` → `- [x]`
+5. Brief status: "✓ Task N complete"
+
+Keep narration light—don't over-explain every line of code.
+
+After all tasks:
+
+```
+## Implementation Complete
+
+All tasks done:
+- [x] Task 1
+- [x] Task 2
+- [x] ...
+
+The change is implemented! One more step—let's archive it.
+```
+
+---
+
+## Phase 10: Archive
+
+**EXPLAIN:**
+
+```
+## Archiving
+
+When a change is complete, we archive it. The archive path is derived from `planningHome.changesDir` and the date.
+
+Archived changes become your project's decision history—you can always find them later to understand why something was built a certain way.
+```
+
+**DO:**
+
+```bash
+openspec archive "<name>"
+```
+
+**SHOW:**
+
+```
+Archived to: `<planningHome.changesDir>/archive/YYYY-MM-DD-<name>/`
+
+The change is now part of your project's history. The code is in your codebase, the decision record is preserved.
+```
+
+---
+
+## Phase 11: Recap & Next Steps
+
+```
+## Congratulations!
+
+You just completed a full OpenSpec cycle:
+
+1. **Explore** - Thought through the problem
+2. **New** - Created a change container
+3. **Proposal** - Captured WHY
+4. **Specs** - Defined WHAT in detail
+5. **Design** - Decided HOW
+6. **Tasks** - Broke it into steps
+7. **Apply** - Implemented the work
+8. **Archive** - Preserved the record
+
+This same rhythm works for any size change—a small fix or a major feature.
+
+---
+
+## Command Reference
+
+**Core workflow:**
+
+ | Command           | What it does                               |
+ |-------------------|--------------------------------------------|
+ | `/opsx:propose` | Create a change and generate all artifacts |
+ | `/opsx:explore` | Think through problems before/during work  |
+ | `/opsx:apply`   | Implement tasks from a change              |
+ | `/opsx:archive` | Archive a completed change                 |
+
+**Additional commands:**
+
+ | Command            | What it does                                             |
+ |--------------------|----------------------------------------------------------|
+ | `/opsx:new`      | Start a new change, step through artifacts one at a time |
+ | `/opsx:continue` | Continue working on an existing change                   |
+ | `/opsx:ff`       | Fast-forward: create all artifacts at once               |
+ | `/opsx:verify`   | Verify implementation matches artifacts                  |
+
+---
+
+## What's Next?
+
+Try `/opsx:propose` on something you actually want to build. You've got the rhythm now!
+```
+
+---
+
+## Graceful Exit Handling
+
+### User wants to stop mid-way
+
+If the user says they need to stop, want to pause, or seem disengaged:
+
+```
+No problem! Your change is saved at the `changeRoot` reported by `openspec status --change "<name>" --json`.
+
+To pick up where we left off later:
+- `/opsx:continue <name>` - Resume artifact creation
+- `/opsx:apply <name>` - Jump to implementation (if tasks exist)
+
+The work won't be lost. Come back whenever you're ready.
+```
+
+Exit gracefully without pressure.
+
+### User just wants command reference
+
+If the user says they just want to see the commands or skip the tutorial:
+
+```
+## OpenSpec Quick Reference
+
+**Core workflow:**
+
+ | Command                  | What it does                               |
+ |--------------------------|--------------------------------------------|
+ | `/opsx:propose <name>` | Create a change and generate all artifacts |
+ | `/opsx:explore`        | Think through problems (no code changes)   |
+ | `/opsx:apply <name>`   | Implement tasks                            |
+ | `/opsx:archive <name>` | Archive when done                          |
+
+**Additional commands:**
+
+ | Command                   | What it does                        |
+ |---------------------------|-------------------------------------|
+ | `/opsx:new <name>`      | Start a new change, step by step    |
+ | `/opsx:continue <name>` | Continue an existing change         |
+ | `/opsx:ff <name>`       | Fast-forward: all artifacts at once |
+ | `/opsx:verify <name>`   | Verify implementation               |
+
+Try `/opsx:propose` to start your first change.
+```
+
+Exit gracefully.
+
+---
+
+## Guardrails
+
+- **Follow the EXPLAIN → DO → SHOW → PAUSE pattern** at key transitions (after explore, after proposal draft, after tasks, after archive)
+- **Keep narration light** during implementation—teach without lecturing
+- **Don't skip phases** even if the change is small—the goal is teaching the workflow
+- **Pause for acknowledgment** at marked points, but don't over-pause
+- **Handle exits gracefully**—never pressure the user to continue
+- **Use real codebase tasks**—don't simulate or use fake examples
+- **Adjust scope gently**—guide toward smaller tasks but respect user choice
diff --git a/.claude/commands/opsx/propose.md b/.claude/commands/opsx/propose.md
new file mode 100644
index 00000000..22f52395
--- /dev/null
+++ b/.claude/commands/opsx/propose.md
@@ -0,0 +1,117 @@
+---
+name: 'OPSX: Propose'
+description: Propose a new change - create it and generate all artifacts in one step
+category: Workflow
+tags: [workflow, artifacts, experimental]
+---
+
+Propose a new change - create the change and generate all artifacts in one step.
+
+I'll create a change with artifacts:
+
+- proposal.md (what & why)
+- design.md (how)
+- tasks.md (implementation steps)
+
+When ready to implement, run /opsx:apply
+
+---
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: The argument after `/opsx:propose` is the change name (kebab-case), OR a description of what the user wants to build.
+
+**Steps**
+
+1. **If no input provided, ask what they want to build**
+
+    Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+    > "What change do you want to work on? Describe what you want to build or fix."
+
+    From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+    **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Create the change directory**
+
+    ```bash
+    openspec new change "<name>"
+    ```
+
+    This creates a scaffolded change in the planning home resolved by the CLI with `.openspec.yaml`.
+
+3. **Get the artifact build order**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to get:
+    - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)
+    - `artifacts`: list of all artifacts with their status and dependencies
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.
+
+4. **Create artifacts in sequence until apply-ready**
+
+    Use the **TodoWrite tool** to track progress through the artifacts.
+
+    Loop through artifacts in dependency order (artifacts with no pending dependencies first):
+
+    a. **For each artifact that is `ready` (dependencies satisfied)**:
+    - Get instructions:
+        ```bash
+        openspec instructions <artifact-id> --change "<name>" --json
+        ```
+    - The instructions JSON includes:
+        - `context`: Project background (constraints for you - do NOT include in output)
+        - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+        - `template`: The structure to use for your output file
+        - `instruction`: Schema-specific guidance for this artifact type
+        - `resolvedOutputPath`: Resolved path or pattern to write the artifact
+        - `dependencies`: Completed artifacts to read for context
+    - Read any completed dependency files for context
+    - Create the artifact file using `template` as the structure and write it to `resolvedOutputPath`
+    - Apply `context` and `rules` as constraints - but do NOT copy them into the file
+    - Show brief progress: "Created <artifact-id>"
+
+    b. **Continue until all `applyRequires` artifacts are complete**
+    - After creating each artifact, re-run `openspec status --change "<name>" --json`
+    - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
+    - Stop when all `applyRequires` artifacts are done
+
+    c. **If an artifact requires user input** (unclear context):
+    - Use **AskUserQuestion tool** to clarify
+    - Then continue with creation
+
+5. **Show final status**
+    ```bash
+    openspec status --change "<name>"
+    ```
+
+**Output**
+
+After completing all artifacts, summarize:
+
+- Change name and location
+- List of artifacts created with brief descriptions
+- What's ready: "All artifacts created! Ready for implementation."
+- Prompt: "Run `/opsx:apply` to start implementing."
+
+**Artifact Creation Guidelines**
+
+- Follow the `instruction` field from `openspec instructions` for each artifact type
+- The schema defines what each artifact should contain - follow it
+- Read dependency artifacts for context before creating new ones
+- Use `template` as the structure for your output file - fill in its sections
+- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
+    - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+    - These guide what you write, but should never appear in the output
+
+**Guardrails**
+
+- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)
+- Always read dependency artifacts before creating a new one
+- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
+- If a change with that name already exists, ask if user wants to continue it or create a new one
+- Verify each artifact file exists after writing before proceeding to next
diff --git a/.claude/commands/opsx/sync.md b/.claude/commands/opsx/sync.md
new file mode 100644
index 00000000..afffaf35
--- /dev/null
+++ b/.claude/commands/opsx/sync.md
@@ -0,0 +1,150 @@
+---
+name: 'OPSX: Sync'
+description: Sync delta specs from a change to main specs
+category: Workflow
+tags: [workflow, specs, experimental]
+---
+
+Sync delta specs from a change to main specs.
+
+This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name after `/opsx:sync` (e.g., `/opsx:sync add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+    Show changes that have delta specs (under `specs/` directory).
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Resolve change context**
+
+    Run:
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+3. **Find delta specs**
+
+    Use `artifactPaths.specs.existingOutputPaths` from the status JSON as the list of delta spec files.
+
+    Each delta spec file contains sections like:
+    - `## ADDED Requirements` - New requirements to add
+    - `## MODIFIED Requirements` - Changes to existing requirements
+    - `## REMOVED Requirements` - Requirements to remove
+    - `## RENAMED Requirements` - Requirements to rename (FROM:/TO: format)
+
+    If no delta specs found, inform user and stop.
+
+4. **For each delta spec, apply changes to main specs**
+
+    For each repo-local capability delta spec path returned by the CLI:
+
+    a. **Read the delta spec** to understand the intended changes
+
+    b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet)
+
+    c. **Apply changes intelligently**:
+
+    **ADDED Requirements:**
+    - If requirement doesn't exist in main spec → add it
+    - If requirement already exists → update it to match (treat as implicit MODIFIED)
+
+    **MODIFIED Requirements:**
+    - Find the requirement in main spec
+    - Apply the changes - this can be:
+        - Adding new scenarios (don't need to copy existing ones)
+        - Modifying existing scenarios
+        - Changing the requirement description
+    - Preserve scenarios/content not mentioned in the delta
+
+    **REMOVED Requirements:**
+    - Remove the entire requirement block from main spec
+
+    **RENAMED Requirements:**
+    - Find the FROM requirement, rename to TO
+
+    d. **Create new main spec** if capability doesn't exist yet:
+    - Create `openspec/specs/<capability>/spec.md`
+    - Add Purpose section (can be brief, mark as TBD)
+    - Add Requirements section with the ADDED requirements
+
+5. **Show summary**
+
+    After applying all changes, summarize:
+    - Which capabilities were updated
+    - What changes were made (requirements added/modified/removed/renamed)
+
+**Delta Spec Format Reference**
+
+```markdown
+## ADDED Requirements
+
+### Requirement: New Feature
+
+The system SHALL do something new.
+
+#### Scenario: Basic case
+
+- **WHEN** user does X
+- **THEN** system does Y
+
+## MODIFIED Requirements
+
+### Requirement: Existing Feature
+
+#### Scenario: New scenario to add
+
+- **WHEN** user does A
+- **THEN** system does B
+
+## REMOVED Requirements
+
+### Requirement: Deprecated Feature
+
+## RENAMED Requirements
+
+- FROM: `### Requirement: Old Name`
+- TO: `### Requirement: New Name`
+```
+
+**Key Principle: Intelligent Merging**
+
+Unlike programmatic merging, you can apply **partial updates**:
+
+- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
+- The delta represents _intent_, not a wholesale replacement
+- Use your judgment to merge changes sensibly
+
+**Output On Success**
+
+```
+## Specs Synced: <change-name>
+
+Updated main specs:
+
+**<capability-1>**:
+- Added requirement: "New Feature"
+- Modified requirement: "Existing Feature" (added 1 scenario)
+
+**<capability-2>**:
+- Created new spec file
+- Added requirement: "Another Feature"
+
+Main specs are now updated. The change remains active - archive when implementation is complete.
+```
+
+**Guardrails**
+
+- Read both delta and main specs before making changes
+- Preserve existing content not mentioned in delta
+- If something is unclear, ask for clarification
+- Show what you're changing as you go
+- The operation should be idempotent - running twice should give same result
diff --git a/.claude/commands/opsx/verify.md b/.claude/commands/opsx/verify.md
new file mode 100644
index 00000000..d8923d42
--- /dev/null
+++ b/.claude/commands/opsx/verify.md
@@ -0,0 +1,171 @@
+---
+name: 'OPSX: Verify'
+description: Verify implementation matches change artifacts before archiving
+category: Workflow
+tags: [workflow, verify, experimental]
+---
+
+Verify that an implementation matches the change artifacts (specs, tasks, design).
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name after `/opsx:verify` (e.g., `/opsx:verify add-auth`). If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+    Show changes that have implementation tasks (tasks artifact exists).
+    Include the schema used for each change if available.
+    Mark changes with incomplete tasks as "(In Progress)".
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check status to understand the schema**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to understand:
+    - `schemaName`: The workflow being used (e.g., "spec-driven")
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context
+    - Which artifacts exist for this change
+
+3. **Get planning context and load artifacts**
+
+    ```bash
+    openspec instructions apply --change "<name>" --json
+    ```
+
+    This returns the change directory and `contextFiles` (artifact ID -> array of concrete file paths). Read all available artifacts from `contextFiles`.
+
+4. **Initialize verification report structure**
+
+    Create a report structure with three dimensions:
+    - **Completeness**: Track tasks and spec coverage
+    - **Correctness**: Track requirement implementation and scenario coverage
+    - **Coherence**: Track design adherence and pattern consistency
+
+    Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
+
+5. **Verify Completeness**
+
+    **Task Completion**:
+    - If `contextFiles.tasks` exists, read every file path in it
+    - Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)
+    - Count complete vs total tasks
+    - If incomplete tasks exist:
+        - Add CRITICAL issue for each incomplete task
+        - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
+
+    **Spec Coverage**:
+    - If delta specs exist in `contextFiles.specs`:
+        - Extract all requirements (marked with "### Requirement:")
+        - For each requirement:
+            - Search codebase for keywords related to the requirement
+            - Assess if implementation likely exists
+        - If requirements appear unimplemented:
+            - Add CRITICAL issue: "Requirement not found: <requirement name>"
+            - Recommendation: "Implement requirement X: <description>"
+
+6. **Verify Correctness**
+
+    **Requirement Implementation Mapping**:
+    - For each requirement from delta specs:
+        - Search codebase for implementation evidence
+        - If found, note file paths and line ranges
+        - Assess if implementation matches requirement intent
+        - If divergence detected:
+            - Add WARNING: "Implementation may diverge from spec: <details>"
+            - Recommendation: "Review <file>:<lines> against requirement X"
+
+    **Scenario Coverage**:
+    - For each scenario in delta specs (marked with "#### Scenario:"):
+        - Check if conditions are handled in code
+        - Check if tests exist covering the scenario
+        - If scenario appears uncovered:
+            - Add WARNING: "Scenario not covered: <scenario name>"
+            - Recommendation: "Add test or implementation for scenario: <description>"
+
+7. **Verify Coherence**
+
+    **Design Adherence**:
+    - If `contextFiles.design` exists:
+        - Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
+        - Verify implementation follows those decisions
+        - If contradiction detected:
+            - Add WARNING: "Design decision not followed: <decision>"
+            - Recommendation: "Update implementation or revise design.md to match reality"
+    - If no design.md: Skip design adherence check, note "No design.md to verify against"
+
+    **Code Pattern Consistency**:
+    - Review new code for consistency with project patterns
+    - Check file naming, directory structure, coding style
+    - If significant deviations found:
+        - Add SUGGESTION: "Code pattern deviation: <details>"
+        - Recommendation: "Consider following project pattern: <example>"
+
+8. **Generate Verification Report**
+
+    **Summary Scorecard**:
+
+    ```
+    ## Verification Report: <change-name>
+
+    ### Summary
+    | Dimension    | Status           |
+    |--------------|------------------|
+    | Completeness | X/Y tasks, N reqs|
+    | Correctness  | M/N reqs covered |
+    | Coherence    | Followed/Issues  |
+    ```
+
+    **Issues by Priority**:
+
+    1. **CRITICAL** (Must fix before archive):
+        - Incomplete tasks
+        - Missing requirement implementations
+        - Each with specific, actionable recommendation
+
+    2. **WARNING** (Should fix):
+        - Spec/design divergences
+        - Missing scenario coverage
+        - Each with specific recommendation
+
+    3. **SUGGESTION** (Nice to fix):
+        - Pattern inconsistencies
+        - Minor improvements
+        - Each with specific recommendation
+
+    **Final Assessment**:
+    - If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
+    - If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
+    - If all clear: "All checks passed. Ready for archive."
+
+**Verification Heuristics**
+
+- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)
+- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
+- **Coherence**: Look for glaring inconsistencies, don't nitpick style
+- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
+- **Actionability**: Every issue must have a specific recommendation with file/line references where applicable
+
+**Graceful Degradation**
+
+- If only tasks.md exists: verify task completion only, skip spec/design checks
+- If tasks + specs exist: verify completeness and correctness, skip design
+- If full artifacts: verify all three dimensions
+- Always note which checks were skipped and why
+
+**Output Format**
+
+Use clear markdown with:
+
+- Table for summary scorecard
+- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
+- Code references in format: `file.ts:123`
+- Specific, actionable recommendations
+- No vague suggestions like "consider reviewing"
diff --git a/.claude/skills/openspec-apply-change/SKILL.md b/.claude/skills/openspec-apply-change/SKILL.md
new file mode 100644
index 00000000..285233b0
--- /dev/null
+++ b/.claude/skills/openspec-apply-change/SKILL.md
@@ -0,0 +1,162 @@
+---
+name: openspec-apply-change
+description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Implement tasks from an OpenSpec change.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+    If a name is provided, use it. Otherwise:
+    - Infer from conversation context if the user mentioned a change
+    - Auto-select if only one active change exists
+    - If ambiguous, run `openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+    Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to understand:
+    - `schemaName`: The workflow being used (e.g., "spec-driven")
+    - `planningHome`, `changeRoot`, and `actionContext`: planning scope and edit constraints
+    - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+    ```bash
+    openspec instructions apply --change "<name>" --json
+    ```
+
+    This returns:
+    - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
+    - Progress (total, complete, remaining)
+    - Task list with status
+    - Dynamic instruction based on current state
+
+    **Handle states:**
+    - If `state: "blocked"` (missing artifacts): show message, suggest using openspec-continue-change
+    - If `state: "all_done"`: congratulate, suggest archive
+    - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+    Read every file path listed under `contextFiles` from the apply instructions output.
+    The files depend on the schema being used:
+    - **spec-driven**: proposal, specs, design, tasks
+    - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+    Display:
+    - Schema being used
+    - Progress: "N/M tasks complete"
+    - Remaining tasks overview
+    - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+    For each pending task:
+    - Show which task is being worked on
+    - Make the code changes required
+    - Keep changes minimal and focused
+    - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+    - Continue to next task
+
+    **Pause if:**
+    - Task is unclear → ask for clarification
+    - Implementation reveals a design issue → suggest updating artifacts
+    - Error or blocker encountered → report and wait for guidance
+    - User interrupts
+
+7. **On completion or pause, show status**
+
+    Display:
+    - Tasks completed this session
+    - Overall progress: "N/M tasks complete"
+    - If all done: suggest archive
+    - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! Ready to archive this change.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly
diff --git a/.claude/skills/openspec-archive-change/SKILL.md b/.claude/skills/openspec-archive-change/SKILL.md
new file mode 100644
index 00000000..59a073aa
--- /dev/null
+++ b/.claude/skills/openspec-archive-change/SKILL.md
@@ -0,0 +1,119 @@
+---
+name: openspec-archive-change
+description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Archive a completed change in the experimental workflow.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+    Show only active changes (not already archived).
+    Include the schema used for each change if available.
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+    Run `openspec status --change "<name>" --json` to check artifact completion.
+
+    Parse the JSON to understand:
+    - `schemaName`: The workflow being used
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context
+    - `artifacts`: List of artifacts with their status (`done` or other)
+
+    **If any artifacts are not `done`:**
+    - Display warning listing incomplete artifacts
+    - Use **AskUserQuestion tool** to confirm user wants to proceed
+    - Proceed if user confirms
+
+3. **Check task completion status**
+
+    Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+    Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+    **If incomplete tasks found:**
+    - Display warning showing count of incomplete tasks
+    - Use **AskUserQuestion tool** to confirm user wants to proceed
+    - Proceed if user confirms
+
+    **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+    Use `artifactPaths.specs.existingOutputPaths` from status JSON to check for delta specs. If none exist, proceed without sync prompt.
+
+    **If delta specs exist:**
+    - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+    - Determine what changes would be applied (adds, modifications, removals, renames)
+    - Show a combined summary before prompting
+
+    **Prompt options:**
+    - If changes needed: "Sync now (recommended)", "Archive without syncing"
+    - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+    If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+    Create an `archive` directory under `planningHome.changesDir` if it doesn't exist:
+
+    ```bash
+    mkdir -p "<planningHome.changesDir>/archive"
+    ```
+
+    Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+    **Check if target already exists:**
+    - If yes: Fail with error, suggest renaming existing archive or using different date
+    - If no: Move `changeRoot` to the archive directory
+
+    ```bash
+    mv "<changeRoot>" "<planningHome.changesDir>/archive/YYYY-MM-DD-<name>"
+    ```
+
+6. **Display summary**
+
+    Show archive completion summary including:
+    - Change name
+    - Schema that was used
+    - Archive location
+    - Whether specs were synced (if applicable)
+    - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** the archive path derived from `planningHome.changesDir`/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs (or "No delta specs" or "Sync skipped")
+
+All artifacts complete. All tasks complete.
+```
+
+**Guardrails**
+
+- Always prompt for change selection if not provided
+- Use artifact graph (openspec status --json) for completion checking
+- Don't block archive on warnings - just inform and confirm
+- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use openspec-sync-specs approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting
diff --git a/.claude/skills/openspec-continue-change/SKILL.md b/.claude/skills/openspec-continue-change/SKILL.md
new file mode 100644
index 00000000..54d0c9c9
--- /dev/null
+++ b/.claude/skills/openspec-continue-change/SKILL.md
@@ -0,0 +1,126 @@
+---
+name: openspec-continue-change
+description: Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Continue working on a change by creating the next artifact.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to work on.
+
+    Present the top 3-4 most recently modified changes as options, showing:
+    - Change name
+    - Schema (from `schema` field if present, otherwise "spec-driven")
+    - Status (e.g., "0/5 tasks", "complete", "no tasks")
+    - How recently it was modified (from `lastModified` field)
+
+    Mark the most recently modified change as "(Recommended)" since it's likely what the user wants to continue.
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check current status**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to understand current state. The response includes:
+    - `schemaName`: The workflow schema being used (e.g., "spec-driven")
+    - `artifacts`: Array of artifacts with their status ("done", "ready", "blocked")
+    - `isComplete`: Boolean indicating if all artifacts are complete
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.
+
+3. **Act based on status**:
+
+    ***
+
+    **If all artifacts are complete (`isComplete: true`)**:
+    - Congratulate the user
+    - Show final status including the schema used
+    - Suggest: "All artifacts created! You can now implement this change or archive it."
+    - STOP
+
+    ***
+
+    **If artifacts are ready to create** (status shows artifacts with `status: "ready"`):
+    - Pick the FIRST artifact with `status: "ready"` from the status output
+    - Get its instructions:
+        ```bash
+        openspec instructions <artifact-id> --change "<name>" --json
+        ```
+    - Parse the JSON. The key fields are:
+        - `context`: Project background (constraints for you - do NOT include in output)
+        - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+        - `template`: The structure to use for your output file
+        - `instruction`: Schema-specific guidance
+        - `resolvedOutputPath`: Resolved path or pattern to write the artifact
+        - `dependencies`: Completed artifacts to read for context
+    - **Create the artifact file**:
+        - Read any completed dependency files for context
+        - Use `template` as the structure - fill in its sections
+        - Apply `context` and `rules` as constraints when writing - but do NOT copy them into the file
+        - Write to the `resolvedOutputPath` specified in instructions. If it is a glob pattern, choose the concrete file path using the schema instruction and the change's context
+    - Show what was created and what's now unlocked
+    - STOP after creating ONE artifact
+
+    ***
+
+    **If no artifacts are ready (all blocked)**:
+    - This shouldn't happen with a valid schema
+    - Show status and suggest checking for issues
+
+4. **After creating an artifact, show progress**
+    ```bash
+    openspec status --change "<name>"
+    ```
+
+**Output**
+
+After each invocation, show:
+
+- Which artifact was created
+- Schema workflow being used
+- Current progress (N/M complete)
+- What artifacts are now unlocked
+- Prompt: "Want to continue? Just ask me to continue or tell me what to do next."
+
+**Artifact Creation Guidelines**
+
+The artifact types and their purpose depend on the schema. Use the `instruction` field from the instructions output to understand what to create.
+
+Common artifact patterns:
+
+**spec-driven schema** (proposal → specs → design → tasks):
+
+- **proposal.md**: Ask user about the change if not clear. Fill in Why, What Changes, Capabilities, Impact.
+    - The Capabilities section is critical - each capability listed will need a spec file.
+- **specs/<capability>/spec.md**: Create one spec per capability listed in the proposal's Capabilities section (use the capability name, not the change name).
+- **design.md**: Document technical decisions, architecture, and implementation approach.
+- **tasks.md**: Break down implementation into checkboxed tasks.
+
+For other schemas, follow the `instruction` field from the CLI output.
+
+**Guardrails**
+
+- Create ONE artifact per invocation
+- Always read dependency artifacts before creating a new one
+- Never skip artifacts or create out of order
+- If context is unclear, ask the user before creating
+- Verify the artifact file exists after writing before marking progress
+- Use the schema's artifact sequence, don't assume specific artifact names
+- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
+    - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+    - These guide what you write, but should never appear in the output
diff --git a/.claude/skills/openspec-explore/SKILL.md b/.claude/skills/openspec-explore/SKILL.md
new file mode 100644
index 00000000..e070d15e
--- /dev/null
+++ b/.claude/skills/openspec-explore/SKILL.md
@@ -0,0 +1,300 @@
+---
+name: openspec-explore
+description: Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Enter explore mode. Think deeply. Visualize freely. Follow the conversation wherever it goes.
+
+**IMPORTANT: Explore mode is for thinking, not implementing.** You may read files, search code, and investigate the codebase, but you must NEVER write code or implement features. If the user asks you to implement something, remind them to exit explore mode first and create a change proposal. You MAY create OpenSpec artifacts (proposals, designs, specs) if the user asks—that's capturing thinking, not implementing.
+
+**This is a stance, not a workflow.** There are no fixed steps, no required sequence, no mandatory outputs. You're a thinking partner helping the user explore.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+---
+
+## The Stance
+
+- **Curious, not prescriptive** - Ask questions that emerge naturally, don't follow a script
+- **Open threads, not interrogations** - Surface multiple interesting directions and let the user follow what resonates. Don't funnel them through a single path of questions.
+- **Visual** - Use ASCII diagrams liberally when they'd help clarify thinking
+- **Adaptive** - Follow interesting threads, pivot when new information emerges
+- **Patient** - Don't rush to conclusions, let the shape of the problem emerge
+- **Grounded** - Explore the actual codebase when relevant, don't just theorize
+
+---
+
+## What You Might Do
+
+Depending on what the user brings, you might:
+
+**Explore the problem space**
+
+- Ask clarifying questions that emerge from what they said
+- Challenge assumptions
+- Reframe the problem
+- Find analogies
+
+**Investigate the codebase**
+
+- Map existing architecture relevant to the discussion
+- Find integration points
+- Identify patterns already in use
+- Surface hidden complexity
+
+**Compare options**
+
+- Brainstorm multiple approaches
+- Build comparison tables
+- Sketch tradeoffs
+- Recommend a path (if asked)
+
+**Visualize**
+
+```
+┌─────────────────────────────────────────┐
+│     Use ASCII diagrams liberally        │
+├─────────────────────────────────────────┤
+│                                         │
+│      ┌────────┐         ┌────────┐      │
+│      │ State  │────────▶│ State  │      │
+│      │   A    │         │   B    │      │
+│      └────────┘         └────────┘      │
+│                                         │
+│   System diagrams, state machines,      │
+│   data flows, architecture sketches,    │
+│   dependency graphs, comparison tables  │
+│                                         │
+└─────────────────────────────────────────┘
+```
+
+**Surface risks and unknowns**
+
+- Identify what could go wrong
+- Find gaps in understanding
+- Suggest spikes or investigations
+
+---
+
+## OpenSpec Awareness
+
+You have full context of the OpenSpec system. Use it naturally, don't force it.
+
+### Check for context
+
+At the start, quickly check what exists:
+
+```bash
+openspec list --json
+```
+
+This tells you:
+
+- If there are active changes
+- Their names, schemas, and status
+- What the user might be working on
+
+### When no change exists
+
+Think freely. When insights crystallize, you might offer:
+
+- "This feels solid enough to start a change. Want me to create a proposal?"
+- Or keep exploring - no pressure to formalize
+
+### When a change exists
+
+If the user mentions a change or you detect one is relevant:
+
+1. **Resolve and read existing artifacts for context**
+    - Run `openspec status --change "<name>" --json`.
+    - Use `changeRoot`, `artifactPaths`, and `actionContext` from the status JSON.
+    - Read existing files from `artifactPaths.<artifact>.existingOutputPaths`.
+
+2. **Reference them naturally in conversation**
+    - "Your design mentions using Redis, but we just realized SQLite fits better..."
+    - "The proposal scopes this to premium users, but we're now thinking everyone..."
+
+3. **Offer to capture when decisions are made**
+
+    | Insight Type               | Where to Capture             |
+    | -------------------------- | ---------------------------- |
+    | New requirement discovered | `specs/<capability>/spec.md` |
+    | Requirement changed        | `specs/<capability>/spec.md` |
+    | Design decision made       | `design.md`                  |
+    | Scope changed              | `proposal.md`                |
+    | New work identified        | `tasks.md`                   |
+    | Assumption invalidated     | Relevant artifact            |
+
+    Example offers:
+    - "That's a design decision. Capture it in design.md?"
+    - "This is a new requirement. Add it to specs?"
+    - "This changes scope. Update the proposal?"
+
+4. **The user decides** - Offer and move on. Don't pressure. Don't auto-capture.
+
+---
+
+## What You Don't Have To Do
+
+- Follow a script
+- Ask the same questions every time
+- Produce a specific artifact
+- Reach a conclusion
+- Stay on topic if a tangent is valuable
+- Be brief (this is thinking time)
+
+---
+
+## Handling Different Entry Points
+
+**User brings a vague idea:**
+
+```
+User: I'm thinking about adding real-time collaboration
+
+You: Real-time collab is a big space. Let me think about this...
+
+      COLLABORATION SPECTRUM
+      ════════════════════════════════════════════
+
+      Awareness          Coordination         Sync
+          │                   │                 │
+          ▼                   ▼                 ▼
+      ┌────────┐         ┌────────┐        ┌────────┐
+      │Presence│         │Cursors │        │  CRDT  │
+      │  "3    │         │ Multi  │        │Conflict│
+      │online" │         │ select │        │  free  │
+      └────────┘         └────────┘        └────────┘
+          │                   │                 │
+       trivial            moderate           complex
+
+      Where's your head at?
+```
+
+**User brings a specific problem:**
+
+```
+User: The auth system is a mess
+
+You: [reads codebase]
+
+     ┌─────────────────────────────────────────────┐
+     │              CURRENT AUTH FLOW              │
+     └─────────────────────────────────────────────┘
+                        │
+          ┌─────────────┼─────────────┐
+          ▼             ▼             ▼
+     ┌─────────┐  ┌─────────┐  ┌─────────┐
+     │ Google  │  │  GitHub │  │  Email  │
+     │  OAuth  │  │  OAuth  │  │  Magic  │
+     └────┬────┘  └────┬────┘  └────┬────┘
+          │             │             │
+          └─────────────┼─────────────┘
+                        ▼
+                  ┌───────────┐
+                  │  Session  │
+                  └─────┬─────┘
+                        │
+                        ▼
+                  ┌───────────┐
+                  │   Perms   │
+                  └───────────┘
+
+     I see three tangles. Which one's burning?
+```
+
+**User is stuck mid-implementation:**
+
+```
+User: /opsx:explore add-auth-system
+      The OAuth integration is more complex than expected
+
+You: [reads change artifacts]
+
+     You're on task 4: "Implement OAuth flow"
+
+     Let me trace what's involved...
+
+     [draws diagram, explores options, suggests paths]
+
+     Want to update the design to reflect this?
+     Or add a spike task to investigate?
+```
+
+**User wants to compare options:**
+
+```
+User: Should we use Postgres or SQLite?
+
+You: Generic answer is boring. What's the context?
+
+User: A CLI tool that tracks local dev environments
+
+You: That changes everything.
+
+     ┌─────────────────────────────────────────────────┐
+     │          CLI TOOL DATA STORAGE                  │
+     └─────────────────────────────────────────────────┘
+
+     Key constraints:
+     • No daemon running
+     • Must work offline
+     • Single user
+
+                  SQLite          Postgres
+     Deployment   embedded ✓      needs server ✗
+     Offline      yes ✓           no ✗
+     Single file  yes ✓           no ✗
+
+     SQLite. Not even close.
+
+     Unless... is there a sync component?
+```
+
+---
+
+## Ending Discovery
+
+There's no required ending. Discovery might:
+
+- **Flow into a proposal**: "Ready to start? I can create a change proposal."
+- **Result in artifact updates**: "Updated design.md with these decisions"
+- **Just provide clarity**: User has what they need, moves on
+- **Continue later**: "We can pick this up anytime"
+
+When it feels like things are crystallizing, you might summarize:
+
+```
+## What We Figured Out
+
+**The problem**: [crystallized understanding]
+
+**The approach**: [if one emerged]
+
+**Open questions**: [if any remain]
+
+**Next steps** (if ready):
+- Create a change proposal
+- Keep exploring: just keep talking
+```
+
+But this summary is optional. Sometimes the thinking IS the value.
+
+---
+
+## Guardrails
+
+- **Don't implement** - Never write code or implement features. Creating OpenSpec artifacts is fine, writing application code is not.
+- **Don't fake understanding** - If something is unclear, dig deeper
+- **Don't rush** - Discovery is thinking time, not task time
+- **Don't force structure** - Let patterns emerge naturally
+- **Don't auto-capture** - Offer to save insights, don't just do it
+- **Do visualize** - A good diagram is worth many paragraphs
+- **Do explore the codebase** - Ground discussions in reality
+- **Do question assumptions** - Including the user's and your own
diff --git a/.claude/skills/openspec-new-change/SKILL.md b/.claude/skills/openspec-new-change/SKILL.md
new file mode 100644
index 00000000..c45937bc
--- /dev/null
+++ b/.claude/skills/openspec-new-change/SKILL.md
@@ -0,0 +1,85 @@
+---
+name: openspec-new-change
+description: Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Start a new change using the experimental artifact-driven approach.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
+
+**Steps**
+
+1. **If no clear input provided, ask what they want to build**
+
+    Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+    > "What change do you want to work on? Describe what you want to build or fix."
+
+    From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+    **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Determine the workflow schema**
+
+    Use the default schema (omit `--schema`) unless the user explicitly requests a different workflow.
+
+    **Use a different schema only if the user mentions:**
+    - A specific schema name → use `--schema <name>`
+    - "show workflows" or "what workflows" → run `openspec schemas --json` and let them choose
+
+    **Otherwise**: Omit `--schema` to use the default.
+
+3. **Create the change directory**
+
+    ```bash
+    openspec new change "<name>"
+    ```
+
+    Add `--schema <name>` only if the user requested a specific workflow.
+    This creates a scaffolded change in the planning home resolved by the CLI.
+
+4. **Show the artifact status**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Use the returned `planningHome`, `changeRoot`, `artifactPaths`, and `nextSteps` instead of assuming repo-local paths.
+
+5. **Get instructions for the first artifact**
+   The first artifact depends on the schema (e.g., `proposal` for spec-driven).
+   Check the status output to find the first artifact with status "ready".
+
+    ```bash
+    openspec instructions <first-artifact-id> --change "<name>"
+    ```
+
+    This outputs the template and context for creating the first artifact.
+
+6. **STOP and wait for user direction**
+
+**Output**
+
+After completing the steps, summarize:
+
+- Change name and location
+- Schema/workflow being used and its artifact sequence
+- Current status (0/N artifacts complete)
+- The template for the first artifact
+- Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."
+
+**Guardrails**
+
+- Do NOT create any artifacts yet - just show the instructions
+- Do NOT advance beyond showing the first artifact template
+- If the name is invalid (not kebab-case), ask for a valid name
+- If a change with that name already exists, suggest continuing that change instead
+- Pass --schema if using a non-default workflow
diff --git a/.claude/skills/openspec-onboard/SKILL.md b/.claude/skills/openspec-onboard/SKILL.md
new file mode 100644
index 00000000..269618b8
--- /dev/null
+++ b/.claude/skills/openspec-onboard/SKILL.md
@@ -0,0 +1,574 @@
+---
+name: openspec-onboard
+description: Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Guide the user through their first complete OpenSpec workflow cycle. This is a teaching experience—you'll do real work in their codebase while explaining each step.
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+---
+
+## Preflight
+
+Before starting, check if the OpenSpec CLI is installed:
+
+```bash
+# Unix/macOS
+openspec --version 2>&1 || echo "CLI_NOT_INSTALLED"
+# Windows (PowerShell)
+# if (Get-Command openspec -ErrorAction SilentlyContinue) { openspec --version } else { echo "CLI_NOT_INSTALLED" }
+```
+
+**If CLI not installed:**
+
+> OpenSpec CLI is not installed. Install it first, then come back to `/opsx:onboard`.
+
+Stop here if not installed.
+
+---
+
+## Phase 1: Welcome
+
+Display:
+
+```
+## Welcome to OpenSpec!
+
+I'll walk you through a complete change cycle—from idea to implementation—using a real task in your codebase. Along the way, you'll learn the workflow by doing it.
+
+**What we'll do:**
+1. Pick a small, real task in your codebase
+2. Explore the problem briefly
+3. Create a change (the container for our work)
+4. Build the artifacts: proposal → specs → design → tasks
+5. Implement the tasks
+6. Archive the completed change
+
+**Time:** ~15-20 minutes
+
+Let's start by finding something to work on.
+```
+
+---
+
+## Phase 2: Task Selection
+
+### Codebase Analysis
+
+Scan the codebase for small improvement opportunities. Look for:
+
+1. **TODO/FIXME comments** - Search for `TODO`, `FIXME`, `HACK`, `XXX` in code files
+2. **Missing error handling** - `catch` blocks that swallow errors, risky operations without try-catch
+3. **Functions without tests** - Cross-reference `src/` with test directories
+4. **Type issues** - `any` types in TypeScript files (`: any`, `as any`)
+5. **Debug artifacts** - `console.log`, `console.debug`, `debugger` statements in non-debug code
+6. **Missing validation** - User input handlers without validation
+
+Also check recent git activity:
+
+```bash
+# Unix/macOS
+git log --oneline -10 2>/dev/null || echo "No git history"
+# Windows (PowerShell)
+# git log --oneline -10 2>$null; if ($LASTEXITCODE -ne 0) { echo "No git history" }
+```
+
+### Present Suggestions
+
+From your analysis, present 3-4 specific suggestions:
+
+```
+## Task Suggestions
+
+Based on scanning your codebase, here are some good starter tasks:
+
+**1. [Most promising task]**
+   Location: `src/path/to/file.ts:42`
+   Scope: ~1-2 files, ~20-30 lines
+   Why it's good: [brief reason]
+
+**2. [Second task]**
+   Location: `src/another/file.ts`
+   Scope: ~1 file, ~15 lines
+   Why it's good: [brief reason]
+
+**3. [Third task]**
+   Location: [location]
+   Scope: [estimate]
+   Why it's good: [brief reason]
+
+**4. Something else?**
+   Tell me what you'd like to work on.
+
+Which task interests you? (Pick a number or describe your own)
+```
+
+**If nothing found:** Fall back to asking what the user wants to build:
+
+> I didn't find obvious quick wins in your codebase. What's something small you've been meaning to add or fix?
+
+### Scope Guardrail
+
+If the user picks or describes something too large (major feature, multi-day work):
+
+```
+That's a valuable task, but it's probably larger than ideal for your first OpenSpec run-through.
+
+For learning the workflow, smaller is better—it lets you see the full cycle without getting stuck in implementation details.
+
+**Options:**
+1. **Slice it smaller** - What's the smallest useful piece of [their task]? Maybe just [specific slice]?
+2. **Pick something else** - One of the other suggestions, or a different small task?
+3. **Do it anyway** - If you really want to tackle this, we can. Just know it'll take longer.
+
+What would you prefer?
+```
+
+Let the user override if they insist—this is a soft guardrail.
+
+---
+
+## Phase 3: Explore Demo
+
+Once a task is selected, briefly demonstrate explore mode:
+
+```
+Before we create a change, let me quickly show you **explore mode**—it's how you think through problems before committing to a direction.
+```
+
+Spend 1-2 minutes investigating the relevant code:
+
+- Read the file(s) involved
+- Draw a quick ASCII diagram if it helps
+- Note any considerations
+
+```
+## Quick Exploration
+
+[Your brief analysis—what you found, any considerations]
+
+┌─────────────────────────────────────────┐
+│   [Optional: ASCII diagram if helpful]  │
+└─────────────────────────────────────────┘
+
+Explore mode (`/opsx:explore`) is for this kind of thinking—investigating before implementing. You can use it anytime you need to think through a problem.
+
+Now let's create a change to hold our work.
+```
+
+**PAUSE** - Wait for user acknowledgment before proceeding.
+
+---
+
+## Phase 4: Create the Change
+
+**EXPLAIN:**
+
+```
+## Creating a Change
+
+A "change" in OpenSpec is a container for all the thinking and planning around a piece of work. It lives at the `changeRoot` reported by `openspec status --change "<name>" --json` and holds your artifacts—proposal, specs, design, tasks.
+
+Let me create one for our task.
+```
+
+**DO:** Create the change with a derived kebab-case name:
+
+```bash
+openspec new change "<derived-name>"
+```
+
+**SHOW:**
+
+```
+Created: <changeRoot from status JSON>
+
+The folder structure:
+```
+
+<changeRoot>/
+├── proposal.md ← Why we're doing this (empty, we'll fill it)
+├── design.md ← How we'll build it (empty)
+├── specs/ ← Detailed requirements (empty)
+└── tasks.md ← Implementation checklist (empty)
+
+```
+
+Now let's fill in the first artifact—the proposal.
+```
+
+---
+
+## Phase 5: Proposal
+
+**EXPLAIN:**
+
+```
+## The Proposal
+
+The proposal captures **why** we're making this change and **what** it involves at a high level. It's the "elevator pitch" for the work.
+
+I'll draft one based on our task.
+```
+
+**DO:** Draft the proposal content (don't save yet):
+
+```
+Here's a draft proposal:
+
+---
+
+## Why
+
+[1-2 sentences explaining the problem/opportunity]
+
+## What Changes
+
+[Bullet points of what will be different]
+
+## Capabilities
+
+### New Capabilities
+- `<capability-name>`: [brief description]
+
+### Modified Capabilities
+<!-- If modifying existing behavior -->
+
+## Impact
+
+- `src/path/to/file.ts`: [what changes]
+- [other files if applicable]
+
+---
+
+Does this capture the intent? I can adjust before we save it.
+```
+
+**PAUSE** - Wait for user approval/feedback.
+
+After approval, save the proposal:
+
+```bash
+openspec instructions proposal --change "<name>" --json
+```
+
+Then write the content to the `resolvedOutputPath` from `openspec instructions proposal --change "<name>" --json`.
+
+```
+Proposal saved. This is your "why" document—you can always come back and refine it as understanding evolves.
+
+Next up: specs.
+```
+
+---
+
+## Phase 6: Specs
+
+**EXPLAIN:**
+
+```
+## Specs
+
+Specs define **what** we're building in precise, testable terms. They use a requirement/scenario format that makes expected behavior crystal clear.
+
+For a small task like this, we might only need one spec file.
+```
+
+**DO:** Resolve where the spec file should be created:
+
+```bash
+openspec instructions specs --change "<name>" --json
+# Use resolvedOutputPath from the JSON. If it is a glob, choose the concrete file path using the schema instruction and the change's context.
+```
+
+Draft the spec content:
+
+```
+Here's the spec:
+
+---
+
+## ADDED Requirements
+
+### Requirement: <Name>
+
+<Description of what the system should do>
+
+#### Scenario: <Scenario name>
+
+- **WHEN** <trigger condition>
+- **THEN** <expected outcome>
+- **AND** <additional outcome if needed>
+
+---
+
+This format—WHEN/THEN/AND—makes requirements testable. You can literally read them as test cases.
+```
+
+Save to the concrete file path chosen from `resolvedOutputPath`.
+
+---
+
+## Phase 7: Design
+
+**EXPLAIN:**
+
+```
+## Design
+
+The design captures **how** we'll build it—technical decisions, tradeoffs, approach.
+
+For small changes, this might be brief. That's fine—not every change needs deep design discussion.
+```
+
+**DO:** Draft design.md:
+
+```
+Here's the design:
+
+---
+
+## Context
+
+[Brief context about the current state]
+
+## Goals / Non-Goals
+
+**Goals:**
+- [What we're trying to achieve]
+
+**Non-Goals:**
+- [What's explicitly out of scope]
+
+## Decisions
+
+### Decision 1: [Key decision]
+
+[Explanation of approach and rationale]
+
+---
+
+For a small task, this captures the key decisions without over-engineering.
+```
+
+Save to the `resolvedOutputPath` from `openspec instructions design --change "<name>" --json`.
+
+---
+
+## Phase 8: Tasks
+
+**EXPLAIN:**
+
+```
+## Tasks
+
+Finally, we break the work into implementation tasks—checkboxes that drive the apply phase.
+
+These should be small, clear, and in logical order.
+```
+
+**DO:** Generate tasks based on specs and design:
+
+```
+Here are the implementation tasks:
+
+---
+
+## 1. [Category or file]
+
+- [ ] 1.1 [Specific task]
+- [ ] 1.2 [Specific task]
+
+## 2. Verify
+
+- [ ] 2.1 [Verification step]
+
+---
+
+Each checkbox becomes a unit of work in the apply phase. Ready to implement?
+```
+
+**PAUSE** - Wait for user to confirm they're ready to implement.
+
+Save to the `resolvedOutputPath` from `openspec instructions tasks --change "<name>" --json`.
+
+---
+
+## Phase 9: Apply (Implementation)
+
+**EXPLAIN:**
+
+```
+## Implementation
+
+Now we implement each task, checking them off as we go. I'll announce each one and occasionally note how the specs/design informed the approach.
+```
+
+**DO:** For each task:
+
+1. Announce: "Working on task N: [description]"
+2. Implement the change in the codebase
+3. Reference specs/design naturally: "The spec says X, so I'm doing Y"
+4. Mark complete in tasks.md: `- [ ]` → `- [x]`
+5. Brief status: "✓ Task N complete"
+
+Keep narration light—don't over-explain every line of code.
+
+After all tasks:
+
+```
+## Implementation Complete
+
+All tasks done:
+- [x] Task 1
+- [x] Task 2
+- [x] ...
+
+The change is implemented! One more step—let's archive it.
+```
+
+---
+
+## Phase 10: Archive
+
+**EXPLAIN:**
+
+```
+## Archiving
+
+When a change is complete, we archive it. The archive path is derived from `planningHome.changesDir` and the date.
+
+Archived changes become your project's decision history—you can always find them later to understand why something was built a certain way.
+```
+
+**DO:**
+
+```bash
+openspec archive "<name>"
+```
+
+**SHOW:**
+
+```
+Archived to: `<planningHome.changesDir>/archive/YYYY-MM-DD-<name>/`
+
+The change is now part of your project's history. The code is in your codebase, the decision record is preserved.
+```
+
+---
+
+## Phase 11: Recap & Next Steps
+
+```
+## Congratulations!
+
+You just completed a full OpenSpec cycle:
+
+1. **Explore** - Thought through the problem
+2. **New** - Created a change container
+3. **Proposal** - Captured WHY
+4. **Specs** - Defined WHAT in detail
+5. **Design** - Decided HOW
+6. **Tasks** - Broke it into steps
+7. **Apply** - Implemented the work
+8. **Archive** - Preserved the record
+
+This same rhythm works for any size change—a small fix or a major feature.
+
+---
+
+## Command Reference
+
+**Core workflow:**
+
+ | Command           | What it does                               |
+ |-------------------|--------------------------------------------|
+ | `/opsx:propose` | Create a change and generate all artifacts |
+ | `/opsx:explore` | Think through problems before/during work  |
+ | `/opsx:apply`   | Implement tasks from a change              |
+ | `/opsx:archive` | Archive a completed change                 |
+
+**Additional commands:**
+
+ | Command            | What it does                                             |
+ |--------------------|----------------------------------------------------------|
+ | `/opsx:new`      | Start a new change, step through artifacts one at a time |
+ | `/opsx:continue` | Continue working on an existing change                   |
+ | `/opsx:ff`       | Fast-forward: create all artifacts at once               |
+ | `/opsx:verify`   | Verify implementation matches artifacts                  |
+
+---
+
+## What's Next?
+
+Try `/opsx:propose` on something you actually want to build. You've got the rhythm now!
+```
+
+---
+
+## Graceful Exit Handling
+
+### User wants to stop mid-way
+
+If the user says they need to stop, want to pause, or seem disengaged:
+
+```
+No problem! Your change is saved at the `changeRoot` reported by `openspec status --change "<name>" --json`.
+
+To pick up where we left off later:
+- `/opsx:continue <name>` - Resume artifact creation
+- `/opsx:apply <name>` - Jump to implementation (if tasks exist)
+
+The work won't be lost. Come back whenever you're ready.
+```
+
+Exit gracefully without pressure.
+
+### User just wants command reference
+
+If the user says they just want to see the commands or skip the tutorial:
+
+```
+## OpenSpec Quick Reference
+
+**Core workflow:**
+
+ | Command                  | What it does                               |
+ |--------------------------|--------------------------------------------|
+ | `/opsx:propose <name>` | Create a change and generate all artifacts |
+ | `/opsx:explore`        | Think through problems (no code changes)   |
+ | `/opsx:apply <name>`   | Implement tasks                            |
+ | `/opsx:archive <name>` | Archive when done                          |
+
+**Additional commands:**
+
+ | Command                   | What it does                        |
+ |---------------------------|-------------------------------------|
+ | `/opsx:new <name>`      | Start a new change, step by step    |
+ | `/opsx:continue <name>` | Continue an existing change         |
+ | `/opsx:ff <name>`       | Fast-forward: all artifacts at once |
+ | `/opsx:verify <name>`   | Verify implementation               |
+
+Try `/opsx:propose` to start your first change.
+```
+
+Exit gracefully.
+
+---
+
+## Guardrails
+
+- **Follow the EXPLAIN → DO → SHOW → PAUSE pattern** at key transitions (after explore, after proposal draft, after tasks, after archive)
+- **Keep narration light** during implementation—teach without lecturing
+- **Don't skip phases** even if the change is small—the goal is teaching the workflow
+- **Pause for acknowledgment** at marked points, but don't over-pause
+- **Handle exits gracefully**—never pressure the user to continue
+- **Use real codebase tasks**—don't simulate or use fake examples
+- **Adjust scope gently**—guide toward smaller tasks but respect user choice
diff --git a/.claude/skills/openspec-propose/SKILL.md b/.claude/skills/openspec-propose/SKILL.md
new file mode 100644
index 00000000..6d317601
--- /dev/null
+++ b/.claude/skills/openspec-propose/SKILL.md
@@ -0,0 +1,121 @@
+---
+name: openspec-propose
+description: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Propose a new change - create the change and generate all artifacts in one step.
+
+I'll create a change with artifacts:
+
+- proposal.md (what & why)
+- design.md (how)
+- tasks.md (implementation steps)
+
+When ready to implement, run /opsx:apply
+
+---
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
+
+**Steps**
+
+1. **If no clear input provided, ask what they want to build**
+
+    Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:
+
+    > "What change do you want to work on? Describe what you want to build or fix."
+
+    From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).
+
+    **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.
+
+2. **Create the change directory**
+
+    ```bash
+    openspec new change "<name>"
+    ```
+
+    This creates a scaffolded change in the planning home resolved by the CLI with `.openspec.yaml`.
+
+3. **Get the artifact build order**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to get:
+    - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)
+    - `artifacts`: list of all artifacts with their status and dependencies
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.
+
+4. **Create artifacts in sequence until apply-ready**
+
+    Use the **TodoWrite tool** to track progress through the artifacts.
+
+    Loop through artifacts in dependency order (artifacts with no pending dependencies first):
+
+    a. **For each artifact that is `ready` (dependencies satisfied)**:
+    - Get instructions:
+        ```bash
+        openspec instructions <artifact-id> --change "<name>" --json
+        ```
+    - The instructions JSON includes:
+        - `context`: Project background (constraints for you - do NOT include in output)
+        - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)
+        - `template`: The structure to use for your output file
+        - `instruction`: Schema-specific guidance for this artifact type
+        - `resolvedOutputPath`: Resolved path or pattern to write the artifact
+        - `dependencies`: Completed artifacts to read for context
+    - Read any completed dependency files for context
+    - Create the artifact file using `template` as the structure and write it to `resolvedOutputPath`
+    - Apply `context` and `rules` as constraints - but do NOT copy them into the file
+    - Show brief progress: "Created <artifact-id>"
+
+    b. **Continue until all `applyRequires` artifacts are complete**
+    - After creating each artifact, re-run `openspec status --change "<name>" --json`
+    - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array
+    - Stop when all `applyRequires` artifacts are done
+
+    c. **If an artifact requires user input** (unclear context):
+    - Use **AskUserQuestion tool** to clarify
+    - Then continue with creation
+
+5. **Show final status**
+    ```bash
+    openspec status --change "<name>"
+    ```
+
+**Output**
+
+After completing all artifacts, summarize:
+
+- Change name and location
+- List of artifacts created with brief descriptions
+- What's ready: "All artifacts created! Ready for implementation."
+- Prompt: "Run `/opsx:apply` or ask me to implement to start working on the tasks."
+
+**Artifact Creation Guidelines**
+
+- Follow the `instruction` field from `openspec instructions` for each artifact type
+- The schema defines what each artifact should contain - follow it
+- Read dependency artifacts for context before creating new ones
+- Use `template` as the structure for your output file - fill in its sections
+- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file
+    - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact
+    - These guide what you write, but should never appear in the output
+
+**Guardrails**
+
+- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)
+- Always read dependency artifacts before creating a new one
+- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
+- If a change with that name already exists, ask if user wants to continue it or create a new one
+- Verify each artifact file exists after writing before proceeding to next
diff --git a/.claude/skills/openspec-sync-specs/SKILL.md b/.claude/skills/openspec-sync-specs/SKILL.md
new file mode 100644
index 00000000..965bd63d
--- /dev/null
+++ b/.claude/skills/openspec-sync-specs/SKILL.md
@@ -0,0 +1,154 @@
+---
+name: openspec-sync-specs
+description: Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Sync delta specs from a change to main specs.
+
+This is an **agent-driven** operation - you will read delta specs and directly edit main specs to apply the changes. This allows intelligent merging (e.g., adding a scenario without copying the entire requirement).
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+    Show changes that have delta specs (under `specs/` directory).
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Resolve change context**
+
+    Run:
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+3. **Find delta specs**
+
+    Use `artifactPaths.specs.existingOutputPaths` from the status JSON as the list of delta spec files.
+
+    Each delta spec file contains sections like:
+    - `## ADDED Requirements` - New requirements to add
+    - `## MODIFIED Requirements` - Changes to existing requirements
+    - `## REMOVED Requirements` - Requirements to remove
+    - `## RENAMED Requirements` - Requirements to rename (FROM:/TO: format)
+
+    If no delta specs found, inform user and stop.
+
+4. **For each delta spec, apply changes to main specs**
+
+    For each repo-local capability delta spec path returned by the CLI:
+
+    a. **Read the delta spec** to understand the intended changes
+
+    b. **Read the main spec** at `openspec/specs/<capability>/spec.md` (may not exist yet)
+
+    c. **Apply changes intelligently**:
+
+    **ADDED Requirements:**
+    - If requirement doesn't exist in main spec → add it
+    - If requirement already exists → update it to match (treat as implicit MODIFIED)
+
+    **MODIFIED Requirements:**
+    - Find the requirement in main spec
+    - Apply the changes - this can be:
+        - Adding new scenarios (don't need to copy existing ones)
+        - Modifying existing scenarios
+        - Changing the requirement description
+    - Preserve scenarios/content not mentioned in the delta
+
+    **REMOVED Requirements:**
+    - Remove the entire requirement block from main spec
+
+    **RENAMED Requirements:**
+    - Find the FROM requirement, rename to TO
+
+    d. **Create new main spec** if capability doesn't exist yet:
+    - Create `openspec/specs/<capability>/spec.md`
+    - Add Purpose section (can be brief, mark as TBD)
+    - Add Requirements section with the ADDED requirements
+
+5. **Show summary**
+
+    After applying all changes, summarize:
+    - Which capabilities were updated
+    - What changes were made (requirements added/modified/removed/renamed)
+
+**Delta Spec Format Reference**
+
+```markdown
+## ADDED Requirements
+
+### Requirement: New Feature
+
+The system SHALL do something new.
+
+#### Scenario: Basic case
+
+- **WHEN** user does X
+- **THEN** system does Y
+
+## MODIFIED Requirements
+
+### Requirement: Existing Feature
+
+#### Scenario: New scenario to add
+
+- **WHEN** user does A
+- **THEN** system does B
+
+## REMOVED Requirements
+
+### Requirement: Deprecated Feature
+
+## RENAMED Requirements
+
+- FROM: `### Requirement: Old Name`
+- TO: `### Requirement: New Name`
+```
+
+**Key Principle: Intelligent Merging**
+
+Unlike programmatic merging, you can apply **partial updates**:
+
+- To add a scenario, just include that scenario under MODIFIED - don't copy existing scenarios
+- The delta represents _intent_, not a wholesale replacement
+- Use your judgment to merge changes sensibly
+
+**Output On Success**
+
+```
+## Specs Synced: <change-name>
+
+Updated main specs:
+
+**<capability-1>**:
+- Added requirement: "New Feature"
+- Modified requirement: "Existing Feature" (added 1 scenario)
+
+**<capability-2>**:
+- Created new spec file
+- Added requirement: "Another Feature"
+
+Main specs are now updated. The change remains active - archive when implementation is complete.
+```
+
+**Guardrails**
+
+- Read both delta and main specs before making changes
+- Preserve existing content not mentioned in delta
+- If something is unclear, ask for clarification
+- Show what you're changing as you go
+- The operation should be idempotent - running twice should give same result
diff --git a/.claude/skills/openspec-verify-change/SKILL.md b/.claude/skills/openspec-verify-change/SKILL.md
new file mode 100644
index 00000000..08a31065
--- /dev/null
+++ b/.claude/skills/openspec-verify-change/SKILL.md
@@ -0,0 +1,175 @@
+---
+name: openspec-verify-change
+description: Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+    author: openspec
+    version: '1.0'
+    generatedBy: '1.5.0'
+---
+
+Verify that an implementation matches the change artifacts (specs, tasks, design).
+
+**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+    Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+    Show changes that have implementation tasks (tasks artifact exists).
+    Include the schema used for each change if available.
+    Mark changes with incomplete tasks as "(In Progress)".
+
+    **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check status to understand the schema**
+
+    ```bash
+    openspec status --change "<name>" --json
+    ```
+
+    Parse the JSON to understand:
+    - `schemaName`: The workflow being used (e.g., "spec-driven")
+    - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context
+    - Which artifacts exist for this change
+
+3. **Get planning context and load artifacts**
+
+    ```bash
+    openspec instructions apply --change "<name>" --json
+    ```
+
+    This returns the change directory and `contextFiles` (artifact ID -> array of concrete file paths). Read all available artifacts from `contextFiles`.
+
+4. **Initialize verification report structure**
+
+    Create a report structure with three dimensions:
+    - **Completeness**: Track tasks and spec coverage
+    - **Correctness**: Track requirement implementation and scenario coverage
+    - **Coherence**: Track design adherence and pattern consistency
+
+    Each dimension can have CRITICAL, WARNING, or SUGGESTION issues.
+
+5. **Verify Completeness**
+
+    **Task Completion**:
+    - If `contextFiles.tasks` exists, read every file path in it
+    - Parse checkboxes: `- [ ]` (incomplete) vs `- [x]` (complete)
+    - Count complete vs total tasks
+    - If incomplete tasks exist:
+        - Add CRITICAL issue for each incomplete task
+        - Recommendation: "Complete task: <description>" or "Mark as done if already implemented"
+
+    **Spec Coverage**:
+    - If delta specs exist in `contextFiles.specs`:
+        - Extract all requirements (marked with "### Requirement:")
+        - For each requirement:
+            - Search codebase for keywords related to the requirement
+            - Assess if implementation likely exists
+        - If requirements appear unimplemented:
+            - Add CRITICAL issue: "Requirement not found: <requirement name>"
+            - Recommendation: "Implement requirement X: <description>"
+
+6. **Verify Correctness**
+
+    **Requirement Implementation Mapping**:
+    - For each requirement from delta specs:
+        - Search codebase for implementation evidence
+        - If found, note file paths and line ranges
+        - Assess if implementation matches requirement intent
+        - If divergence detected:
+            - Add WARNING: "Implementation may diverge from spec: <details>"
+            - Recommendation: "Review <file>:<lines> against requirement X"
+
+    **Scenario Coverage**:
+    - For each scenario in delta specs (marked with "#### Scenario:"):
+        - Check if conditions are handled in code
+        - Check if tests exist covering the scenario
+        - If scenario appears uncovered:
+            - Add WARNING: "Scenario not covered: <scenario name>"
+            - Recommendation: "Add test or implementation for scenario: <description>"
+
+7. **Verify Coherence**
+
+    **Design Adherence**:
+    - If `contextFiles.design` exists:
+        - Extract key decisions (look for sections like "Decision:", "Approach:", "Architecture:")
+        - Verify implementation follows those decisions
+        - If contradiction detected:
+            - Add WARNING: "Design decision not followed: <decision>"
+            - Recommendation: "Update implementation or revise design.md to match reality"
+    - If no design.md: Skip design adherence check, note "No design.md to verify against"
+
+    **Code Pattern Consistency**:
+    - Review new code for consistency with project patterns
+    - Check file naming, directory structure, coding style
+    - If significant deviations found:
+        - Add SUGGESTION: "Code pattern deviation: <details>"
+        - Recommendation: "Consider following project pattern: <example>"
+
+8. **Generate Verification Report**
+
+    **Summary Scorecard**:
+
+    ```
+    ## Verification Report: <change-name>
+
+    ### Summary
+    | Dimension    | Status           |
+    |--------------|------------------|
+    | Completeness | X/Y tasks, N reqs|
+    | Correctness  | M/N reqs covered |
+    | Coherence    | Followed/Issues  |
+    ```
+
+    **Issues by Priority**:
+
+    1. **CRITICAL** (Must fix before archive):
+        - Incomplete tasks
+        - Missing requirement implementations
+        - Each with specific, actionable recommendation
+
+    2. **WARNING** (Should fix):
+        - Spec/design divergences
+        - Missing scenario coverage
+        - Each with specific recommendation
+
+    3. **SUGGESTION** (Nice to fix):
+        - Pattern inconsistencies
+        - Minor improvements
+        - Each with specific recommendation
+
+    **Final Assessment**:
+    - If CRITICAL issues: "X critical issue(s) found. Fix before archiving."
+    - If only warnings: "No critical issues. Y warning(s) to consider. Ready for archive (with noted improvements)."
+    - If all clear: "All checks passed. Ready for archive."
+
+**Verification Heuristics**
+
+- **Completeness**: Focus on objective checklist items (checkboxes, requirements list)
+- **Correctness**: Use keyword search, file path analysis, reasonable inference - don't require perfect certainty
+- **Coherence**: Look for glaring inconsistencies, don't nitpick style
+- **False Positives**: When uncertain, prefer SUGGESTION over WARNING, WARNING over CRITICAL
+- **Actionability**: Every issue must have a specific recommendation with file/line references where applicable
+
+**Graceful Degradation**
+
+- If only tasks.md exists: verify task completion only, skip spec/design checks
+- If tasks + specs exist: verify completeness and correctness, skip design
+- If full artifacts: verify all three dimensions
+- Always note which checks were skipped and why
+
+**Output Format**
+
+Use clear markdown with:
+
+- Table for summary scorecard
+- Grouped lists for issues (CRITICAL/WARNING/SUGGESTION)
+- Code references in format: `file.ts:123`
+- Specific, actionable recommendations
+- No vague suggestions like "consider reviewing"
diff --git a/.gitignore b/.gitignore
index 0a0ae15a..4e4ce78b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -77,3 +77,15 @@ config/config.json
 .claude/*
 !.claude/settings.json
 !.claude/review-guidelines.md
+!.claude/commands/
+!.claude/commands/opsx/
+!.claude/skills/
+!.claude/skills/openspec-apply-change/
+!.claude/skills/openspec-archive-change/
+!.claude/skills/openspec-continue-change/
+!.claude/skills/openspec-explore/
+!.claude/skills/openspec-new-change/
+!.claude/skills/openspec-onboard/
+!.claude/skills/openspec-propose/
+!.claude/skills/openspec-sync-specs/
+!.claude/skills/openspec-verify-change/
diff --git a/openspec/config.yaml b/openspec/config.yaml
new file mode 100644
index 00000000..2a8f7729
--- /dev/null
+++ b/openspec/config.yaml
@@ -0,0 +1,43 @@
+schema: spec-driven
+
+context: |
+    Project: TalkControl — télécommande de présentations reveal.js
+    One presenter at a time (IMP-002).
+
+    Architecture (3 services):
+    - tc-server (port 3001): Express 5 + socket.io, patcher/proxy des présentations, moteur d'état
+    - controller + component (port 3000): Vite dev server, layouts (presenter, on-stage…), web components Lit
+    - showcase (port 3002): présentation reveal.js d'exemple (http-server)
+
+    Flux: controller ↔ serveur ↔ component via event-bus typé (TcEventMap, 21 événements).
+    Pairing par session socket.io: token UUID opaque `?s=`, rooms `session:<id>`.
+    Store serveur maison (~35 lignes, src/server/store/), union discriminée TcAction.
+    Plugins auto-découverts par import.meta.glob, activation pilotée par config/plugins.json.
+
+    Tech stack:
+    - Node 24, TypeScript strict, Vite 8 (Rolldown/oxc), Vitest 4, Playwright e2e
+    - Lit 3 (décorateurs LEGACY experimentalDecorators:true — ne pas migrer vers TC39)
+    - Express 5, socket.io 4, Bulma 1, VitePress 2-alpha + TypeDoc
+
+    Conventions:
+    - Commits Gitmoji en français (ex: ✨ feat(server): ajouter X)
+    - Branches: feat|fix|chore|test/<slug>
+    - KISS d'abord, SOLID, TDD quand approprié
+    - Ne pas renommer les variables/clés existantes sans nécessité fonctionnelle
+    - Coverage: ne jamais baisser les seuils (80/90/70/80)
+
+    Validation rapide: tsc --noEmit && npm run lint:check && NODE_ENV=test npm test
+    Validation complète (CI): ./scripts/verify.sh
+
+rules:
+    proposal:
+        - Toujours mentionner l'impact sur les 3 services (tc-server, controller, showcase)
+        - Indiquer si un nouvel événement TcEventMap est nécessaire
+        - Préciser si des tests e2e Playwright sont à ajouter ou modifier
+    tasks:
+        - Découper en tâches de max 2h
+        - Chaque tâche doit mentionner les fichiers concernés
+        - Les tâches de test précèdent les tâches d'implémentation (TDD)
+    design:
+        - Mentionner les décisions IMP-XXX existantes impactées
+        - Documenter dans docs/improvements/decisions.md si décision structurante

From 4800408da8d4b65d26a37a2f41ecd6c27549443b Mon Sep 17 00:00:00 2001
From: jefbinomed <jean.francois.garreau@gmail.com>
Date: Tue, 11 Aug 2026 14:34:06 +0200
Subject: [PATCH 3/7] =?UTF-8?q?=F0=9F=90=9B=20fix(touch-pointer):=20calcul?=
 =?UTF-8?q?er=20le=20zoom=20dans=20le=20rep=C3=A8re=20du=20frame=20(#41)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le zoom du plugin touch-pointer calculait sa translation à partir de
window.innerWidth/innerHeight alors qu'il applique le transform sur
#slideViewFrame. En vue presenter, le frame n'occupe que 3/5 de la
largeur : mesuré avant correctif, la slide était projetée en x=835..2339
pour une fenêtre de 1280, soit entièrement hors de l'écran.

- extraction de la géométrie dans touch-pointer/zoom.ts, testable sans
  layout (jsdom n'en calcule pas) : t = s · (centre − point), dans le
  repère du frame ;
- plafonnement de la translation à (s − 1) · taille / 2, pour que le
  frame agrandi recouvre toujours sa boîte — sans quoi un clic en coin
  décolle un bord et laisse apparaître du vide ;
- _toggleZoom reçoit désormais les pourcentages bruts et les convertit
  contre le rect du frame, plus contre la fenêtre ;
- overflow: hidden sur #slideViewSection en filet de sécurité.

Tests : 8 cas unitaires sur la fonction pure (dont une propriété de
recouvrement balayant toutes les positions de clic), 3 cas sur
_toggleZoom, et un e2e golden-path vérifié rouge sans le correctif.
---
 e2e/golden-path/14-plugins.spec.js            | 34 ++++++++
 .../web-components/slide-view/slide-view.ts   |  8 ++
 src/plugins/input/touch-pointer/index.ts      | 43 ++++++----
 src/plugins/input/touch-pointer/zoom.ts       | 53 ++++++++++++
 .../plugins/input/touch-pointer/index.spec.ts | 62 +++++++++----
 test/plugins/input/touch-pointer/zoom.spec.ts | 86 +++++++++++++++++++
 6 files changed, 252 insertions(+), 34 deletions(-)
 create mode 100644 src/plugins/input/touch-pointer/zoom.ts
 create mode 100644 test/plugins/input/touch-pointer/zoom.spec.ts

diff --git a/e2e/golden-path/14-plugins.spec.js b/e2e/golden-path/14-plugins.spec.js
index 80a47031..70c08bdd 100644
--- a/e2e/golden-path/14-plugins.spec.js
+++ b/e2e/golden-path/14-plugins.spec.js
@@ -13,4 +13,38 @@ test.describe('Golden-path 7 — Menu plugins', () => {
         // Le plugin manuel (non autoActivate) touchPointerInput doit être proposé.
         await expect(page.getByText('touchPointerInput', { exact: false })).toBeVisible();
     });
+
+    // Régression #41 : le zoom du touch pointer calculait sa translation dans le repère
+    // de la FENÊTRE alors qu'il transforme l'iframe, qui n'occupe que 3/5 de la largeur
+    // en vue presenter. Résultat mesuré avant correctif : frame projeté en x=835..2339
+    // pour une fenêtre de 1280 — slide entièrement hors écran.
+    test('le zoom du touch pointer garde la slide dans son cadre', async ({ page }) => {
+        await openView(page, 'presenter.html');
+
+        await page.getByText('Plugins', { exact: false }).click();
+        await page.getByText('touchPointerInput', { exact: false }).click();
+
+        const mask = page.locator('tc-touch-pointer-mask');
+        await expect(mask).toBeVisible();
+
+        // Clic près du coin haut-gauche : le cas le plus défavorable, celui qui
+        // projetait la slide le plus loin hors du cadre.
+        await mask.click({ position: { x: 30, y: 20 } });
+
+        await expect
+            .poll(async () =>
+                page.evaluate(() => {
+                    const slide = document.getElementById('currentSlide');
+                    const root = slide.shadowRoot;
+                    const frame = root.getElementById('slideViewFrame').getBoundingClientRect();
+                    const section = root.getElementById('slideViewSection').getBoundingClientRect();
+                    return {
+                        zoomed: root.getElementById('slideViewFrame').style.transform.includes('scale'),
+                        // Le frame agrandi doit recouvrir sa section, sans laisser de vide.
+                        covers: frame.left <= section.left && frame.top <= section.top && frame.right >= section.right && frame.bottom >= section.bottom
+                    };
+                })
+            )
+            .toEqual({ zoomed: true, covers: true });
+    });
 });
diff --git a/src/client/web-components/slide-view/slide-view.ts b/src/client/web-components/slide-view/slide-view.ts
index bf756b82..0b5e4cea 100644
--- a/src/client/web-components/slide-view/slide-view.ts
+++ b/src/client/web-components/slide-view/slide-view.ts
@@ -20,6 +20,14 @@ export class SlideViewComponent extends TcStyledElement {
             width: 100%;
             height: 100%;
         }
+        /* Filet de sécurité du zoom (#41) : le plugin touch-pointer applique un
+           transform scale() sur l'iframe. Sans clipping, une translation erronée
+           projette la slide par-dessus le reste de la vue presenter — voire hors
+           de l'écran. La géométrie est corrigée dans touch-pointer/zoom.ts ; ceci
+           garantit qu'aucune régression future ne puisse repeindre hors du cadre. */
+        section {
+            overflow: hidden;
+        }
         section.fullscreen {
             width: 100vw;
             height: 100vh;
diff --git a/src/plugins/input/touch-pointer/index.ts b/src/plugins/input/touch-pointer/index.ts
index a043019a..7a8ab25e 100644
--- a/src/plugins/input/touch-pointer/index.ts
+++ b/src/plugins/input/touch-pointer/index.ts
@@ -1,5 +1,6 @@
 import { Plugin } from '@plugins/plugin.js';
 import { logger } from '@services/logger';
+import { ZOOM_SCALE, computeZoomTransform } from './zoom';
 
 interface PointerState {
     x: string;
@@ -155,10 +156,10 @@ class TouchPointerInput extends Plugin {
         }
 
         if (messageData.type === 'pointerClick') {
-            this._toggleZoom(
-                this._convertPercentToCoordinates(messageData.payload.x ?? '0', window.innerWidth),
-                this._convertPercentToCoordinates(messageData.payload.y ?? '0', window.innerHeight)
-            );
+            // Les coordonnées arrivent en POURCENTAGE de la zone de masque : elles ne sont
+            // converties en pixels qu'à l'intérieur de _toggleZoom, dans le repère du frame
+            // (cf. zoom.ts). Les convertir ici contre la fenêtre était le bug #41.
+            this._toggleZoom(messageData.payload.x ?? '0', messageData.payload.y ?? '0');
         }
     }
 
@@ -192,7 +193,7 @@ class TouchPointerInput extends Plugin {
         }
     }
 
-    _toggleZoom(mouseX: number, mouseY: number): void {
+    _toggleZoom(xPercent: string, yPercent: string): void {
         const currentSlide = document.getElementById('currentSlide');
         if (!currentSlide || !currentSlide.shadowRoot) {
             return;
@@ -204,23 +205,29 @@ class TouchPointerInput extends Plugin {
         }
 
         if (this.zooming) {
-            element.style.transform = 'translate3D(0px, 0px, 0px)';
-            element.style.cursor = 'zoom-in';
-            this.zooming = !this.zooming;
+            this._resetZoom(element);
             return;
         }
 
-        const scaleValue = 2;
-        const windowCenterX = window.innerWidth / 2;
-        const windowCenterY = window.innerHeight / 2;
-        const targetX = Math.round((windowCenterX - mouseX) * scaleValue);
-        const targetY = Math.round((windowCenterY - mouseY) * scaleValue);
+        // getBoundingClientRect() plutôt que offsetWidth : on ne passe ici qu'en état
+        // dézoomé, donc le rect vaut la boîte de mise en page, et il tient compte d'un
+        // éventuel scale porté par un ancêtre.
+        const box = element.getBoundingClientRect();
+        const point = {
+            x: this._convertPercentToCoordinates(xPercent, box.width),
+            y: this._convertPercentToCoordinates(yPercent, box.height)
+        };
+        const translation = computeZoomTransform(box, point, ZOOM_SCALE);
 
-        if (!this.zooming) {
-            element.style.transform = `translateX(${targetX}px) translateY(${targetY}px) scale(${scaleValue})`;
-            element.style.cursor = 'zoom-out';
-            this.zooming = !this.zooming;
-        }
+        element.style.transform = `translateX(${Math.round(translation.x)}px) translateY(${Math.round(translation.y)}px) scale(${ZOOM_SCALE})`;
+        element.style.cursor = 'zoom-out';
+        this.zooming = true;
+    }
+
+    _resetZoom(element: HTMLElement): void {
+        element.style.transform = 'translate3D(0px, 0px, 0px)';
+        element.style.cursor = 'zoom-in';
+        this.zooming = false;
     }
 
     _convertPercentToCoordinates(percentValue: string, size: number): number {
diff --git a/src/plugins/input/touch-pointer/zoom.ts b/src/plugins/input/touch-pointer/zoom.ts
new file mode 100644
index 00000000..71a2a498
--- /dev/null
+++ b/src/plugins/input/touch-pointer/zoom.ts
@@ -0,0 +1,53 @@
+/**
+ * Géométrie du zoom du plugin touch-pointer, isolée du DOM pour être testable
+ * sans layout (jsdom n'en calcule pas).
+ *
+ * Le zoom applique `translate(t) scale(s)` sur `#slideViewFrame`, dont le
+ * `transform-origin` est le centre (valeur par défaut). Un point `p` exprimé
+ * dans le repère LOCAL du frame (origine = coin haut-gauche du frame) se
+ * retrouve donc en `c + s·(p − c) + t`, avec `c` le centre du frame.
+ *
+ * Pour amener le point cliqué au centre, on résout `c = c + s·(p − c) + t`,
+ * d'où `t = s·(c − p)`.
+ *
+ * ⚠️ Le repère est celui du FRAME, pas celui de la fenêtre : c'était la cause
+ * du bug #41. En vue presenter, le frame n'occupe que 3/5 de la largeur, et
+ * calculer `t` à partir de `window.innerWidth` projetait la slide entièrement
+ * hors de l'écran.
+ */
+
+export const ZOOM_SCALE = 2;
+
+export interface Size {
+    width: number;
+    height: number;
+}
+
+export interface Point {
+    x: number;
+    y: number;
+}
+
+function clamp(value: number, bound: number): number {
+    return Math.min(Math.max(value, -bound), bound);
+}
+
+/**
+ * Translation à appliquer pour centrer `point` dans un frame de taille `box`
+ * agrandi d'un facteur `scale`.
+ *
+ * Le résultat est plafonné pour que le frame agrandi recouvre toujours sa boîte
+ * d'origine : au-delà de `(scale − 1)·taille / 2`, un bord se décollerait du
+ * conteneur, laissant apparaître du vide (et débordant de l'autre côté).
+ *
+ * @param box - dimensions de mise en page du frame, en pixels
+ * @param point - point à centrer, dans le repère local du frame, en pixels
+ * @param scale - facteur d'agrandissement (1 = pas de zoom)
+ * @returns translation en pixels à appliquer avant le `scale`
+ */
+export function computeZoomTransform(box: Size, point: Point, scale: number): Point {
+    return {
+        x: clamp(scale * (box.width / 2 - point.x), ((scale - 1) * box.width) / 2),
+        y: clamp(scale * (box.height / 2 - point.y), ((scale - 1) * box.height) / 2)
+    };
+}
diff --git a/test/plugins/input/touch-pointer/index.spec.ts b/test/plugins/input/touch-pointer/index.spec.ts
index b25e337b..263913f9 100644
--- a/test/plugins/input/touch-pointer/index.spec.ts
+++ b/test/plugins/input/touch-pointer/index.spec.ts
@@ -272,18 +272,16 @@ describe('TouchPointerInput', function () {
             expect(setPointerColorSpy).toHaveBeenCalledWith('');
         });
 
-        it('should toggle the zoom with converted coordinates on "pointerClick"', function () {
-            // Given
+        it('should forward the raw percentages to the zoom on "pointerClick"', function () {
+            // Given la conversion en pixels se fait dans _toggleZoom, contre le repère du
+            // frame et non celui de la fenêtre (#41).
             const toggleZoomSpy = vi.spyOn(instance, '_toggleZoom');
-            vi.stubGlobal('innerWidth', 1000);
-            vi.stubGlobal('innerHeight', 500);
 
             // When
             instance._onMessageEvent(messageEvent({ type: 'x', data: { type: 'pointerClick', payload: { x: '50%', y: '20%' } } }));
 
             // Then
-            expect(toggleZoomSpy).toHaveBeenCalledWith(500, 100);
-            vi.unstubAllGlobals();
+            expect(toggleZoomSpy).toHaveBeenCalledWith('50%', '20%');
         });
 
         it('should default missing coordinates to "0" on "pointerClick"', function () {
@@ -294,7 +292,7 @@ describe('TouchPointerInput', function () {
             instance._onMessageEvent(messageEvent({ type: 'x', data: { type: 'pointerClick', payload: {} } }));
 
             // Then
-            expect(toggleZoomSpy).toHaveBeenCalledWith(0, 0);
+            expect(toggleZoomSpy).toHaveBeenCalledWith('0', '0');
         });
     });
 
@@ -387,8 +385,13 @@ describe('TouchPointerInput', function () {
     });
 
     describe('_toggleZoom()', function () {
+        /** jsdom ne calcule aucun layout : il faut simuler la boîte du frame. */
+        function giveFrameABox(frame: HTMLElement, width: number, height: number): void {
+            vi.spyOn(frame, 'getBoundingClientRect').mockReturnValue({ width, height } as DOMRect);
+        }
+
         it('should do nothing when there is no current slide', function () {
-            expect(() => instance._toggleZoom(1, 2)).not.toThrow();
+            expect(() => instance._toggleZoom('1%', '2%')).not.toThrow();
         });
 
         it('should do nothing when slideViewFrame is missing', function () {
@@ -399,32 +402,59 @@ describe('TouchPointerInput', function () {
             host.attachShadow({ mode: 'open' });
 
             // When / Then
-            expect(() => instance._toggleZoom(1, 2)).not.toThrow();
+            expect(() => instance._toggleZoom('1%', '2%')).not.toThrow();
         });
 
         it('should zoom in and flip the zooming flag when not zoomed', function () {
             // Given
             const { frame } = buildCurrentSlide();
-            vi.stubGlobal('innerWidth', 1000);
-            vi.stubGlobal('innerHeight', 500);
+            giveFrameABox(frame, 800, 600);
 
-            // When
-            instance._toggleZoom(400, 200);
+            // When un clic au centre du frame
+            instance._toggleZoom('50%', '50%');
 
-            // Then
+            // Then aucune translation nécessaire, seulement l'agrandissement
+            expect(frame.style.transform).toBe('translateX(0px) translateY(0px) scale(2)');
             expect(frame.style.cursor).toBe('zoom-out');
-            expect(frame.style.transform).toContain('translateX');
             expect(instance.zooming).toBe(true);
+        });
+
+        it('should compute the translation in the frame reference frame, not the window one', function () {
+            // Given une fenêtre bien plus large que le frame : c'est la configuration de
+            // la vue presenter, où le frame n'occupe que 3/5 de la largeur (#41).
+            const { frame } = buildCurrentSlide();
+            giveFrameABox(frame, 800, 600);
+            vi.stubGlobal('innerWidth', 4000);
+            vi.stubGlobal('innerHeight', 3000);
+
+            // When
+            instance._toggleZoom('25%', '25%');
+
+            // Then t = 2 * (400 - 200) = 400, plafonné à (2 - 1) * 800 / 2 = 400
+            //      t = 2 * (300 - 150) = 300, plafonné à (2 - 1) * 600 / 2 = 300
+            expect(frame.style.transform).toBe('translateX(400px) translateY(300px) scale(2)');
             vi.unstubAllGlobals();
         });
 
+        it('should never translate the frame off its own box, even on a corner click', function () {
+            // Given
+            const { frame } = buildCurrentSlide();
+            giveFrameABox(frame, 800, 600);
+
+            // When un clic dans le coin, qui demanderait 2 * 400 = 800 sans plafond
+            instance._toggleZoom('0%', '0%');
+
+            // Then plafonné au recouvrement : la slide reste visible (#41)
+            expect(frame.style.transform).toBe('translateX(400px) translateY(300px) scale(2)');
+        });
+
         it('should zoom out and flip the zooming flag when already zoomed', function () {
             // Given
             const { frame } = buildCurrentSlide();
             instance.zooming = true;
 
             // When
-            instance._toggleZoom(0, 0);
+            instance._toggleZoom('0%', '0%');
 
             // Then
             expect(frame.style.cursor).toBe('zoom-in');
diff --git a/test/plugins/input/touch-pointer/zoom.spec.ts b/test/plugins/input/touch-pointer/zoom.spec.ts
new file mode 100644
index 00000000..f27b9bd6
--- /dev/null
+++ b/test/plugins/input/touch-pointer/zoom.spec.ts
@@ -0,0 +1,86 @@
+import { ZOOM_SCALE, computeZoomTransform } from '@plugins/input/touch-pointer/zoom';
+
+describe('computeZoomTransform()', function () {
+    describe('centrage du point cliqué', function () {
+        it('should not translate at all when the click is dead center', function () {
+            // Given / When
+            const transform = computeZoomTransform({ width: 800, height: 600 }, { x: 400, y: 300 }, 2);
+
+            // Then
+            expect(transform).toEqual({ x: 0, y: 0 });
+        });
+
+        it('should translate towards the center, proportionally to the scale', function () {
+            // Given un clic en deçà du centre, assez proche pour rester sous le plafond
+            // de recouvrement (400 pour la largeur, 300 pour la hauteur à scale 2).
+            // When
+            const transform = computeZoomTransform({ width: 800, height: 600 }, { x: 300, y: 250 }, 2);
+
+            // Then t = s * (centre - point) : 2 * 100 et 2 * 50
+            expect(transform).toEqual({ x: 200, y: 100 });
+        });
+
+        it('should translate in the opposite direction for a click past the center', function () {
+            // Given / When
+            const transform = computeZoomTransform({ width: 800, height: 600 }, { x: 500, y: 350 }, 2);
+
+            // Then
+            expect(transform).toEqual({ x: -200, y: -100 });
+        });
+    });
+
+    describe('recouvrement du conteneur (clamp)', function () {
+        // Le frame agrandi doit TOUJOURS couvrir son conteneur : sinon il déborde d'un côté
+        // (bug #41, où la slide sortait entièrement de l'écran) et découvre du vide de l'autre.
+        it('should clamp the translation so a corner click keeps the frame covering its box', function () {
+            // Given un clic dans le coin haut-gauche, qui demanderait t = 2 * 400 = 800
+            // When
+            const transform = computeZoomTransform({ width: 800, height: 600 }, { x: 0, y: 0 }, 2);
+
+            // Then plafonné à (s - 1) * taille / 2
+            expect(transform).toEqual({ x: 400, y: 300 });
+        });
+
+        it('should clamp symmetrically for the opposite corner', function () {
+            // Given / When
+            const transform = computeZoomTransform({ width: 800, height: 600 }, { x: 800, y: 600 }, 2);
+
+            // Then
+            expect(transform).toEqual({ x: -400, y: -300 });
+        });
+
+        it('should keep the transformed frame within its own box for any click position', function () {
+            // Given
+            const box = { width: 752, height: 668 };
+            const scale = ZOOM_SCALE;
+
+            for (let ratio = 0; ratio <= 1; ratio += 0.05) {
+                // When
+                const point = { x: box.width * ratio, y: box.height * ratio };
+                const { x, y } = computeZoomTransform(box, point, scale);
+
+                // Then les bords du frame transformé encadrent bien [0, taille]
+                const left = (box.width / 2) * (1 - scale) + x;
+                const right = (box.width / 2) * (1 + scale) + x;
+                const top = (box.height / 2) * (1 - scale) + y;
+                const bottom = (box.height / 2) * (1 + scale) + y;
+
+                expect(left).toBeLessThanOrEqual(0);
+                expect(right).toBeGreaterThanOrEqual(box.width);
+                expect(top).toBeLessThanOrEqual(0);
+                expect(bottom).toBeGreaterThanOrEqual(box.height);
+            }
+        });
+    });
+
+    describe('cas dégénérés', function () {
+        it('should return a neutral transform for a zero-sized box', function () {
+            // jsdom ne calcule pas de layout : getBoundingClientRect() y renvoie des zéros.
+            expect(computeZoomTransform({ width: 0, height: 0 }, { x: 0, y: 0 }, 2)).toEqual({ x: 0, y: 0 });
+        });
+
+        it('should return a neutral transform when the scale is 1 (no zoom)', function () {
+            expect(computeZoomTransform({ width: 800, height: 600 }, { x: 0, y: 0 }, 1)).toEqual({ x: 0, y: 0 });
+        });
+    });
+});

From d423236510737e9402c72453d6cf0fa7b9a73d51 Mon Sep 17 00:00:00 2001
From: jefbinomed <jean.francois.garreau@gmail.com>
Date: Tue, 11 Aug 2026 14:38:45 +0200
Subject: [PATCH 4/7] =?UTF-8?q?=F0=9F=90=9B=20fix(plugins):=20rendre=20le?=
 =?UTF-8?q?=20cycle=20init/unload=20sym=C3=A9trique=20(#42)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le pointeur quittait bien le DOM à la désactivation — le symptôme décrit
dans l'issue est corrigé depuis le passage au shadow DOM — mais le reste
du teardown ne suivait pas. Mesuré sur l'app réelle, trois cycles
activer/désactiver faisaient grimper `callbacks` à 1, 2 puis 3 : chaque
événement du plugin repartait en autant d'exemplaires.

- Plugin.unload() (classe de base) purge les callbacks et repasse
  `initialized` à false ; les surcharges appellent super.unload() ;
- touch-pointer : clearInterval du timer de masquage, restauration des
  styles posés sur le frame (dimensions, transition, curseur) et remise
  à zéro du transform — désactiver en état zoomé laissait sinon la slide
  hors cadre, sans retour possible ;
- touch-pointer : le handler `message` était enregistré via une lambda
  inline, donc impossible à détacher — référence stabilisée ;
- keyboard et touch : même traitement. Ils n'étaient pas concernés tant
  que unload() était un no-op, mais la base remet désormais
  `initialized` à false : sans détacher, une réactivation doublerait
  leurs listeners.

Tests : contrat de la classe de base, 6 cas de teardown sur
touch-pointer, détachement des listeners sur keyboard et touch, et une
régression sur pluginService couvrant trois cycles complets.
---
 src/plugins/input/keyboard/index.ts           | 17 +++-
 src/plugins/input/touch-pointer/index.ts      | 39 +++++++-
 src/plugins/input/touch/index.ts              | 15 ++-
 src/plugins/plugin.ts                         | 15 ++-
 test/common/services/plugin.spec.ts           | 24 +++++
 test/plugins/input/keyboard/index.spec.ts     | 32 +++++++
 .../plugins/input/touch-pointer/index.spec.ts | 91 +++++++++++++++++++
 test/plugins/input/touch/index.spec.ts        | 19 ++++
 test/plugins/plugin.spec.ts                   | 47 ++++++++++
 9 files changed, 292 insertions(+), 7 deletions(-)
 create mode 100644 test/plugins/plugin.spec.ts

diff --git a/src/plugins/input/keyboard/index.ts b/src/plugins/input/keyboard/index.ts
index 574d46c6..5745724a 100644
--- a/src/plugins/input/keyboard/index.ts
+++ b/src/plugins/input/keyboard/index.ts
@@ -2,19 +2,32 @@ import { config } from '@services/config';
 import { Plugin } from '@plugins/plugin.js';
 
 class KeyboardInput extends Plugin {
+    // Références stables : sans elles, removeEventListener n'a aucune prise et
+    // `unload()` laisserait les listeners actifs derrière lui (#42).
+    private readonly onKeyUp = (event: KeyboardEvent): void => this._captureKeyboardEvent(event, true);
+    private readonly onKeyDown = (event: KeyboardEvent): void => this._captureKeyboardEvent(event);
+
     constructor() {
         super();
         this.type = 'inputEvent';
     }
 
     override init(): void {
-        addEventListener('keyup', e => this._captureKeyboardEvent(e, true), true);
+        addEventListener('keyup', this.onKeyUp, true);
         // keydown sans forward : ne sert qu'à stopPropagation sur les touches bloquées,
         // avant que la présentation embarquée ne les voie. Seul keyup déclenche la navigation.
-        addEventListener('keydown', this._captureKeyboardEvent.bind(this), true);
+        addEventListener('keydown', this.onKeyDown, true);
         this.initialized = true;
     }
 
+    override unload(): void {
+        // Le 3e argument doit reproduire le flag de capture utilisé à l'ajout,
+        // sinon le navigateur ne retrouve pas le listener.
+        removeEventListener('keyup', this.onKeyUp, true);
+        removeEventListener('keydown', this.onKeyDown, true);
+        super.unload();
+    }
+
     _captureKeyboardEvent(event: KeyboardEvent, forward = false): void {
         const keys = config.tcComponent.keysBlocked;
         const activeElementIsInput = document.activeElement?.tagName && /input|textarea/i.test(document.activeElement.tagName);
diff --git a/src/plugins/input/touch-pointer/index.ts b/src/plugins/input/touch-pointer/index.ts
index 7a8ab25e..a1b5d1b2 100644
--- a/src/plugins/input/touch-pointer/index.ts
+++ b/src/plugins/input/touch-pointer/index.ts
@@ -26,6 +26,9 @@ class TouchPointerInput extends Plugin {
     interval: ReturnType<typeof setInterval> | undefined;
     messageEventRegistered = false;
 
+    /** Référence stable, sans laquelle `removeEventListener` serait impossible. */
+    private readonly messageHandler = (message: MessageEvent): void => this._onMessageEvent(message);
+
     constructor() {
         super();
         this.type = 'touchPointerEvent';
@@ -37,7 +40,7 @@ class TouchPointerInput extends Plugin {
         this._addPointer();
 
         if (!this.messageEventRegistered) {
-            addEventListener('message', message => this._onMessageEvent(message));
+            addEventListener('message', this.messageHandler);
             this.messageEventRegistered = true;
         }
         this.initialized = true;
@@ -47,7 +50,39 @@ class TouchPointerInput extends Plugin {
         this._removeSettingsArea();
         this._removeMaskArea();
         this._removePointer();
-        this.initialized = false;
+        this._restoreFrame();
+
+        if (this.messageEventRegistered) {
+            removeEventListener('message', this.messageHandler);
+            this.messageEventRegistered = false;
+        }
+
+        clearInterval(this.interval);
+        this.interval = undefined;
+
+        super.unload();
+    }
+
+    /** Shadow root de la slide courante, ou `undefined` hors vue presenter/on-stage. */
+    _slideShadowRoot(): ShadowRoot | undefined {
+        return document.getElementById('currentSlide')?.shadowRoot ?? undefined;
+    }
+
+    /**
+     * Rend au frame l'apparence qu'il avait avant `_addPointer` : dimensions,
+     * transition, curseur de zoom et transform éventuel. Sans cela, désactiver
+     * le plugin en état zoomé laissait la slide hors cadre, sans retour possible (#42).
+     */
+    _restoreFrame(): void {
+        const frame = this._slideShadowRoot()?.getElementById('slideViewFrame');
+        if (frame) {
+            frame.style.width = '';
+            frame.style.height = '';
+            frame.style.transitionDuration = '';
+            frame.style.cursor = '';
+            frame.style.transform = '';
+        }
+        this.zooming = false;
     }
 
     _addPointer(): void {
diff --git a/src/plugins/input/touch/index.ts b/src/plugins/input/touch/index.ts
index bf408fb4..ec4c1293 100644
--- a/src/plugins/input/touch/index.ts
+++ b/src/plugins/input/touch/index.ts
@@ -9,6 +9,11 @@ interface TouchPosition {
 class TouchInput extends Plugin {
     touchPosition: { touchstart: TouchPosition; touchend: TouchPosition };
 
+    // Références stables : sans elles, removeEventListener n'a aucune prise et
+    // `unload()` laisserait les listeners actifs derrière lui (#42).
+    private readonly onTouchStart = (event: TouchEvent): void => this._captureTouchEvent(event);
+    private readonly onTouchEnd = (event: TouchEvent): void => this._captureTouchEvent(event, true);
+
     constructor() {
         super();
         this.type = 'inputEvent';
@@ -19,11 +24,17 @@ class TouchInput extends Plugin {
     }
 
     override init(): void {
-        addEventListener('touchstart', this._captureTouchEvent.bind(this), false);
-        addEventListener('touchend', e => this._captureTouchEvent(e, true), false);
+        addEventListener('touchstart', this.onTouchStart, false);
+        addEventListener('touchend', this.onTouchEnd, false);
         this.initialized = true;
     }
 
+    override unload(): void {
+        removeEventListener('touchstart', this.onTouchStart, false);
+        removeEventListener('touchend', this.onTouchEnd, false);
+        super.unload();
+    }
+
     _captureTouchEvent(event: TouchEvent, forward = false): void {
         if (!event.view) return;
         if (contextService.isPresentationIframe(event.view.location.href)) {
diff --git a/src/plugins/plugin.ts b/src/plugins/plugin.ts
index cf120117..0f2bd2ff 100644
--- a/src/plugins/plugin.ts
+++ b/src/plugins/plugin.ts
@@ -11,5 +11,18 @@ export class Plugin {
     }
 
     init(): void {}
-    unload(): void {}
+
+    /**
+     * Défait ce que `init()` a mis en place. Les surcharges doivent appeler
+     * `super.unload()` : la classe de base est responsable de l'état qu'elle
+     * possède, à savoir les callbacks et le drapeau `initialized`.
+     *
+     * Sans cette purge, `pluginService.activateOnComponent` empile un callback
+     * supplémentaire à chaque réactivation — le plugin réémet alors chacun de
+     * ses événements en autant d'exemplaires qu'il y a eu de cycles (#42).
+     */
+    unload(): void {
+        this.callbacks = [];
+        this.initialized = false;
+    }
 }
diff --git a/test/common/services/plugin.spec.ts b/test/common/services/plugin.spec.ts
index 67141651..c02c88da 100644
--- a/test/common/services/plugin.spec.ts
+++ b/test/common/services/plugin.spec.ts
@@ -1,6 +1,7 @@
 import { loadPluginModule } from '@plugins/plugin-loader';
 import { logger } from '@services/logger';
 import pluginService from '@services/plugin';
+import { Plugin } from '@plugins/plugin';
 
 vi.mock('@plugins/plugin-loader');
 
@@ -231,5 +232,28 @@ describe('Plugin service', function () {
             }
             expect(threw).toBe(false);
         });
+
+        // Régression #42 : c'est ici que la fuite se matérialisait. Mesuré sur l'app
+        // réelle avant correctif, le tableau `callbacks` du singleton grimpait à 1, 2,
+        // puis 3 sur trois cycles activer/désactiver, et chaque événement du plugin
+        // partait en autant d'exemplaires.
+        it('should not accumulate callbacks across activate/unload cycles', async function () {
+            // Given un vrai Plugin plutôt qu'un mock : le contrat testé est celui de la classe de base
+            const pluginName = 'pluginName';
+            const pluginInstance = new Plugin();
+            pluginInstance.type = 'type';
+            vi.mocked(loadPluginModule).mockResolvedValue({ instance: pluginInstance });
+            const host = { controllerComponentChannel: { broadcast: vi.fn() } };
+
+            // When trois cycles complets
+            for (let cycle = 0; cycle < 3; cycle++) {
+                await pluginService.activateOnComponent(pluginName, host as any);
+                pluginInstance.unload();
+            }
+            await pluginService.activateOnComponent(pluginName, host as any);
+
+            // Then un seul callback, celui du cycle courant
+            expect(pluginInstance.callbacks).toHaveLength(1);
+        });
     });
 });
diff --git a/test/plugins/input/keyboard/index.spec.ts b/test/plugins/input/keyboard/index.spec.ts
index e6a5a6c6..749b4406 100644
--- a/test/plugins/input/keyboard/index.spec.ts
+++ b/test/plugins/input/keyboard/index.spec.ts
@@ -37,6 +37,38 @@ describe('KeyboardInput', function () {
         });
     });
 
+    describe('unload()', function () {
+        // La classe de base remet `initialized` à false : sans détacher les listeners,
+        // une réactivation les enregistrerait une seconde fois (#42).
+        it('should detach both listeners with the same capture flag used to attach them', function () {
+            // Given
+            const removeEventListenerSpy = vi.spyOn(globalThis, 'removeEventListener');
+            instance.init();
+
+            // When
+            instance.unload();
+
+            // Then
+            expect(removeEventListenerSpy).toHaveBeenCalledWith('keyup', expect.any(Function), true);
+            expect(removeEventListenerSpy).toHaveBeenCalledWith('keydown', expect.any(Function), true);
+            expect(instance.initialized).toBe(false);
+        });
+
+        it('should stop forwarding key events once unloaded', function () {
+            // Given
+            instance.init();
+            const callback = vi.fn();
+            instance.onEvent(callback);
+
+            // When
+            instance.unload();
+            dispatchEvent(new KeyboardEvent('keyup', { code: 'ArrowRight', key: 'ArrowRight' }));
+
+            // Then
+            expect(callback).not.toHaveBeenCalled();
+        });
+    });
+
     describe('_captureKeyboardEvent()', function () {
         it('should ignore the event when the active element is an <input>', function () {
             // Given
diff --git a/test/plugins/input/touch-pointer/index.spec.ts b/test/plugins/input/touch-pointer/index.spec.ts
index 263913f9..199ec038 100644
--- a/test/plugins/input/touch-pointer/index.spec.ts
+++ b/test/plugins/input/touch-pointer/index.spec.ts
@@ -86,6 +86,97 @@ describe('TouchPointerInput', function () {
             expect(document.getElementById('placeholder2')?.innerHTML).toBe('');
             expect(instance.initialized).toBe(false);
         });
+
+        // Le teardown était incomplet (#42) : le pointeur partait bien du DOM, mais
+        // callbacks, timer, styles du frame et état de zoom survivaient à la désactivation.
+        it('should drop the accumulated callbacks on unload', function () {
+            // Given
+            instance.init();
+            instance.onEvent(() => {});
+
+            // When
+            instance.unload();
+
+            // Then
+            expect(instance.callbacks).toHaveLength(0);
+        });
+
+        it('should clear the pointer hide-timer on unload', function () {
+            // Given
+            vi.useFakeTimers();
+            const clearIntervalSpy = vi.spyOn(globalThis, 'clearInterval');
+            buildCurrentSlide();
+            instance.init();
+            instance._setPointer('1px', '1px');
+            const timer = instance.interval;
+            expect(timer).toBeDefined();
+
+            // When
+            instance.unload();
+
+            // Then
+            expect(clearIntervalSpy).toHaveBeenCalledWith(timer);
+            expect(instance.interval).toBeUndefined();
+            vi.useRealTimers();
+        });
+
+        it('should restore the frame styles it had applied on unload', function () {
+            // Given
+            const { frame } = buildCurrentSlide();
+            instance.init();
+            expect(frame.style.cursor).toBe('zoom-in');
+
+            // When
+            instance.unload();
+
+            // Then
+            expect(frame.style.cursor).toBe('');
+            expect(frame.style.width).toBe('');
+            expect(frame.style.height).toBe('');
+            expect(frame.style.transitionDuration).toBe('');
+        });
+
+        it('should reset a pending zoom on unload, so the slide is never left off-screen', function () {
+            // Given une désactivation alors que la vue est zoomée
+            const { frame } = buildCurrentSlide();
+            vi.spyOn(frame, 'getBoundingClientRect').mockReturnValue({ width: 800, height: 600 } as DOMRect);
+            instance.init();
+            instance._toggleZoom('0%', '0%');
+            expect(instance.zooming).toBe(true);
+
+            // When
+            instance.unload();
+
+            // Then
+            expect(frame.style.transform).toBe('');
+            expect(instance.zooming).toBe(false);
+        });
+
+        it('should detach the message listener on unload so it can be re-registered later', function () {
+            // Given
+            const removeEventListenerSpy = vi.spyOn(globalThis, 'removeEventListener');
+            instance.init();
+
+            // When
+            instance.unload();
+
+            // Then
+            expect(removeEventListenerSpy).toHaveBeenCalledWith('message', expect.any(Function));
+            expect(instance.messageEventRegistered).toBe(false);
+        });
+
+        it('should stop reacting to messages once unloaded', function () {
+            // Given
+            const { shadowRoot } = buildCurrentSlide();
+            instance.init();
+            instance.unload();
+
+            // When un message arrive après la désactivation
+            dispatchEvent(new MessageEvent('message', { data: { type: 'x', data: { type: 'pointerMove', payload: { x: '5%', y: '5%' } } } }));
+
+            // Then rien n'est recréé
+            expect(shadowRoot.getElementById('pointer')).toBeNull();
+        });
     });
 
     describe('_addArea() / _removeArea()', function () {
diff --git a/test/plugins/input/touch/index.spec.ts b/test/plugins/input/touch/index.spec.ts
index 726908ca..6fe273b1 100644
--- a/test/plugins/input/touch/index.spec.ts
+++ b/test/plugins/input/touch/index.spec.ts
@@ -41,6 +41,25 @@ describe('TouchInput', function () {
         });
     });
 
+    describe('unload()', function () {
+        // Même contrat que keyboard : la base remet `initialized` à false, donc les
+        // listeners doivent partir sous peine d'être doublés au réactivage (#42).
+        it('should detach both listeners with the same capture flag used to attach them', function () {
+            // Given
+            const removeEventListenerSpy = vi.spyOn(globalThis, 'removeEventListener');
+            instance.init();
+
+            // When
+            instance.unload();
+
+            // Then
+            expect(removeEventListenerSpy).toHaveBeenCalledWith('touchstart', expect.any(Function), false);
+            expect(removeEventListenerSpy).toHaveBeenCalledWith('touchend', expect.any(Function), false);
+            expect(instance.initialized).toBe(false);
+            vi.restoreAllMocks();
+        });
+    });
+
     describe('_captureTouchEvent()', function () {
         it('should do nothing when the event has no view', function () {
             // Given
diff --git a/test/plugins/plugin.spec.ts b/test/plugins/plugin.spec.ts
new file mode 100644
index 00000000..614ac2a3
--- /dev/null
+++ b/test/plugins/plugin.spec.ts
@@ -0,0 +1,47 @@
+import { Plugin } from '@plugins/plugin';
+
+describe('Plugin', function () {
+    describe('unload()', function () {
+        // Sans purge, activateOnComponent empile un callback à chaque activation
+        // (mesuré : 1, 2, 3 sur trois cycles activer/désactiver — issue #42) et chaque
+        // événement du plugin part alors en autant d'exemplaires.
+        it('should drop every registered callback', function () {
+            // Given
+            const plugin = new Plugin();
+            plugin.onEvent(() => {});
+            plugin.onEvent(() => {});
+            expect(plugin.callbacks).toHaveLength(2);
+
+            // When
+            plugin.unload();
+
+            // Then
+            expect(plugin.callbacks).toHaveLength(0);
+        });
+
+        it('should mark the plugin as uninitialized so a later activation re-runs init', function () {
+            // Given
+            const plugin = new Plugin();
+            plugin.initialized = true;
+
+            // When
+            plugin.unload();
+
+            // Then
+            expect(plugin.initialized).toBe(false);
+        });
+
+        it('should be idempotent', function () {
+            // Given
+            const plugin = new Plugin();
+            plugin.onEvent(() => {});
+
+            // When / Then
+            expect(() => {
+                plugin.unload();
+                plugin.unload();
+            }).not.toThrow();
+            expect(plugin.callbacks).toHaveLength(0);
+        });
+    });
+});

From 11f3f1634e489ee6663763b9a22803fefbcdd2b3 Mon Sep 17 00:00:00 2001
From: jefbinomed <jean.francois.garreau@gmail.com>
Date: Thu, 13 Aug 2026 13:49:49 +0200
Subject: [PATCH 5/7] =?UTF-8?q?=F0=9F=94=92=20fix(deps):=20r=C3=A9sorber?=
 =?UTF-8?q?=20les=205=20vuln=C3=A9rabilit=C3=A9s=20high=20et=20les=20surve?=
 =?UTF-8?q?iller=20en=20CI?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

npm audit remontait 5 failles high sur develop, toutes transitives, sans
que rien n'échoue : le contrôle vivait dans scripts/verify.sh mais
n'avait aucun job dans la CI. Les vulnérabilités pouvaient donc dériver
indéfiniment tant que personne ne lançait le script en local.

- npm audit fix (sans --force) : brace-expansion 5.0.7 → 5.0.9,
  nanoid 3.3.15 → 3.3.18, postcss 8.5.16 → 8.5.26,
  socket.io-parser 4.2.6 → 4.2.7, undici 7.28.0 → 7.29.0.
  Cinq bumps patch/mineurs sur des dépendances transitives ;
  package.json est inchangé, aucune dépendance directe ne bouge ;
- job `audit` ajouté à develop.yml. npm audit sort en code non nul dès
  qu'il trouve quelque chose, donc aucune commande supplémentaire n'est
  nécessaire pour faire échouer le job ;
- CLAUDE.md : verify.sh y était présenté comme le miroir de la CI, ce
  qui est faux au niveau ligne à ligne et m'a fait conclure à tort que
  develop était déjà rouge sur l'audit. Nuance ajoutée.

./scripts/verify.sh : typecheck, lint, coverage, e2e, build, audit et
docs OK — audit inclus pour la première fois.
---
 .github/workflows/develop.yml | 31 ++++++++++++++++
 CLAUDE.md                     |  6 ++++
 package-lock.json             | 66 +++++++++++++++++------------------
 3 files changed, 70 insertions(+), 33 deletions(-)

diff --git a/.github/workflows/develop.yml b/.github/workflows/develop.yml
index 8257adfb..9eab7c60 100644
--- a/.github/workflows/develop.yml
+++ b/.github/workflows/develop.yml
@@ -38,6 +38,37 @@ jobs:
             - name: Lint check
               run: npm run lint:check
 
+    # ----------------------------------------------------------------
+    # Job 1bis — Audit des dépendances
+    #
+    # `npm audit` figurait dans scripts/verify.sh mais dans aucun job : les
+    # vulnérabilités remontaient en local et passaient en CI. Cinq failles high
+    # (nanoid, postcss, socket.io-parser, undici, brace-expansion) ont ainsi
+    # vécu sur develop sans rien faire échouer.
+    #
+    # `npm audit` sort en code non nul dès qu'il trouve quelque chose au niveau
+    # demandé — c'est ce qui fait échouer le job, aucune commande de plus n'est
+    # nécessaire.
+    # ----------------------------------------------------------------
+    audit:
+        name: Dependency audit — Node 24
+        runs-on: ubuntu-latest
+        timeout-minutes: 10
+        steps:
+            - uses: actions/checkout@v7
+
+            - name: Setup Node 24
+              uses: actions/setup-node@v6
+              with:
+                  node-version: '24'
+                  cache: 'npm'
+
+            - name: Install dependencies
+              run: npm ci
+
+            - name: Audit dependencies
+              run: npm audit
+
     # ----------------------------------------------------------------
     # Job 2 — TypeScript strict
     # ----------------------------------------------------------------
diff --git a/CLAUDE.md b/CLAUDE.md
index 2f339336..e12bf68f 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -44,6 +44,12 @@ soit : `tsc --noEmit`, `lint:check`, `NODE_ENV=test npm run coverage` (jsdom + b
 les suites tournent DANS coverage, ne pas les relancer à part : IMP-013), `test:e2e` (Playwright
 démarre lui-même les 3 services), `build`, `npm audit` (0 vulnérabilité attendu), `docs:build`.
 
+Le script couvre les mêmes contrôles que la CI, mais **il n'en est pas la copie exacte** : la
+correspondance vaut job par job, pas ligne par ligne. Avant de conclure « la CI échoue déjà
+là-dessus » à partir d'un échec local, vérifier que le contrôle en question a bien un job dans
+`.github/workflows/develop.yml` — `npm audit` n'en avait aucun jusqu'à la mise en place du job
+`audit`, et un échec local ne rendait donc pas la CI rouge.
+
 ## Contrat iso-fonctionnel
 
 `docs/migration/golden-path.md` fait foi : le comportement utilisateur décrit là est le contrat,
diff --git a/package-lock.json b/package-lock.json
index 85cb9f4f..4977b745 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -3460,16 +3460,16 @@
             }
         },
         "node_modules/brace-expansion": {
-            "version": "5.0.7",
-            "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.7.tgz",
-            "integrity": "sha512-7oFy703dxfY3/NLxC1fh2SUCQ0H9rmAY+5EpDVfXjUTTs+HEwR2nYaqLv+GWcTsumwxPfiz6CzCNkwXwBUwqCA==",
+            "version": "5.0.9",
+            "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.9.tgz",
+            "integrity": "sha512-ScQ4IuvIEF1TMlP7Zt+vjJ//9zlPb2SDcxWxM3bk8s6t6GGdJ7KO1dCcTidOPJKePW30LE/2cT7wCyPho9/Wxg==",
             "dev": true,
             "license": "MIT",
             "dependencies": {
                 "balanced-match": "^4.0.2"
             },
             "engines": {
-                "node": "18 || 20 || >=22"
+                "node": "20 || >=22"
             }
         },
         "node_modules/bulma": {
@@ -6734,9 +6734,9 @@
             "license": "MIT"
         },
         "node_modules/nanoid": {
-            "version": "3.3.15",
-            "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.15.tgz",
-            "integrity": "sha512-y7Wygv/7mEOvxTuEQDB8StXdMRBWf1kR/tlhAzBRUFkB2jfcLOAxO/SHmOO2zgz1pVgK29/kyupn059/bCHdjA==",
+            "version": "3.3.18",
+            "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.18.tgz",
+            "integrity": "sha512-DTg4MJbGMWkfi6VZFdNt2/caMbQy4Ou+Op/hJQvGEWcnVfoA1QA+xzRKAzw9jD6+GVOOeYr/mIcuDSdug6F6+w==",
             "dev": true,
             "funding": [
                 {
@@ -7318,9 +7318,9 @@
             }
         },
         "node_modules/postcss": {
-            "version": "8.5.16",
-            "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.16.tgz",
-            "integrity": "sha512-vuwillviilfKZsg0VGj5R/YwwcHx4SLsIOI/7K6mQkWx+l5cUHTjj5g0AasTBcyXsbfTgrwsUNmVUb5xVwyPwg==",
+            "version": "8.5.26",
+            "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.26.tgz",
+            "integrity": "sha512-u82N74LFzG8ca+dD8puPnplTXoGH4fTPpVGuIbt36G3qvNlkvfD0lEAZSxaly3KX8TS/L1A1gsCEmvKmBcVbkQ==",
             "dev": true,
             "funding": [
                 {
@@ -7338,7 +7338,7 @@
             ],
             "license": "MIT",
             "dependencies": {
-                "nanoid": "^3.3.12",
+                "nanoid": "^3.3.17",
                 "picocolors": "^1.1.1",
                 "source-map-js": "^1.2.1"
             },
@@ -8292,9 +8292,9 @@
             }
         },
         "node_modules/socket.io-parser": {
-            "version": "4.2.6",
-            "resolved": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-4.2.6.tgz",
-            "integrity": "sha512-asJqbVBDsBCJx0pTqw3WfesSY0iRX+2xzWEWzrpcH7L6fLzrhyF8WPI8UaeM4YCuDfpwA/cgsdugMsmtz8EJeg==",
+            "version": "4.2.7",
+            "resolved": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-4.2.7.tgz",
+            "integrity": "sha512-IH/iSeO9T6gz1KkFleGDWkG9N3dl4jXVYUtMhIqH10Md0ttMer8nUNWiP1DKuNrybD2xBrixLJdCC9J6ECoYkg==",
             "license": "MIT",
             "dependencies": {
                 "@socket.io/component-emitter": "~3.1.0",
@@ -8864,9 +8864,9 @@
             "license": "MIT"
         },
         "node_modules/undici": {
-            "version": "7.28.0",
-            "resolved": "https://registry.npmjs.org/undici/-/undici-7.28.0.tgz",
-            "integrity": "sha512-cRZYrTDwWznlnRiPjggAGxZXanty6M8RV1ff8Wm4LWXBp7/IG8v5DnOm74DtUBp9OONpK75YlPnIjQqX0dBDtA==",
+            "version": "7.29.0",
+            "resolved": "https://registry.npmjs.org/undici/-/undici-7.29.0.tgz",
+            "integrity": "sha512-IDxfleLmmbSskfWSUATiN1nfn2rDuvnMOqb5CWR92iIfojA0Ud+ulOAAEQ57LPr9rWmsreUyf5lwyao+7GNNVw==",
             "dev": true,
             "license": "MIT",
             "engines": {
@@ -11559,9 +11559,9 @@
             }
         },
         "brace-expansion": {
-            "version": "5.0.7",
-            "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.7.tgz",
-            "integrity": "sha512-7oFy703dxfY3/NLxC1fh2SUCQ0H9rmAY+5EpDVfXjUTTs+HEwR2nYaqLv+GWcTsumwxPfiz6CzCNkwXwBUwqCA==",
+            "version": "5.0.9",
+            "resolved": "https://registry.npmjs.org/brace-expansion/-/brace-expansion-5.0.9.tgz",
+            "integrity": "sha512-ScQ4IuvIEF1TMlP7Zt+vjJ//9zlPb2SDcxWxM3bk8s6t6GGdJ7KO1dCcTidOPJKePW30LE/2cT7wCyPho9/Wxg==",
             "dev": true,
             "requires": {
                 "balanced-match": "^4.0.2"
@@ -13603,9 +13603,9 @@
             "integrity": "sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA=="
         },
         "nanoid": {
-            "version": "3.3.15",
-            "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.15.tgz",
-            "integrity": "sha512-y7Wygv/7mEOvxTuEQDB8StXdMRBWf1kR/tlhAzBRUFkB2jfcLOAxO/SHmOO2zgz1pVgK29/kyupn059/bCHdjA==",
+            "version": "3.3.18",
+            "resolved": "https://registry.npmjs.org/nanoid/-/nanoid-3.3.18.tgz",
+            "integrity": "sha512-DTg4MJbGMWkfi6VZFdNt2/caMbQy4Ou+Op/hJQvGEWcnVfoA1QA+xzRKAzw9jD6+GVOOeYr/mIcuDSdug6F6+w==",
             "dev": true
         },
         "natural-compare": {
@@ -13972,12 +13972,12 @@
             }
         },
         "postcss": {
-            "version": "8.5.16",
-            "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.16.tgz",
-            "integrity": "sha512-vuwillviilfKZsg0VGj5R/YwwcHx4SLsIOI/7K6mQkWx+l5cUHTjj5g0AasTBcyXsbfTgrwsUNmVUb5xVwyPwg==",
+            "version": "8.5.26",
+            "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.26.tgz",
+            "integrity": "sha512-u82N74LFzG8ca+dD8puPnplTXoGH4fTPpVGuIbt36G3qvNlkvfD0lEAZSxaly3KX8TS/L1A1gsCEmvKmBcVbkQ==",
             "dev": true,
             "requires": {
-                "nanoid": "^3.3.12",
+                "nanoid": "^3.3.17",
                 "picocolors": "^1.1.1",
                 "source-map-js": "^1.2.1"
             }
@@ -14614,9 +14614,9 @@
             }
         },
         "socket.io-parser": {
-            "version": "4.2.6",
-            "resolved": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-4.2.6.tgz",
-            "integrity": "sha512-asJqbVBDsBCJx0pTqw3WfesSY0iRX+2xzWEWzrpcH7L6fLzrhyF8WPI8UaeM4YCuDfpwA/cgsdugMsmtz8EJeg==",
+            "version": "4.2.7",
+            "resolved": "https://registry.npmjs.org/socket.io-parser/-/socket.io-parser-4.2.7.tgz",
+            "integrity": "sha512-IH/iSeO9T6gz1KkFleGDWkG9N3dl4jXVYUtMhIqH10Md0ttMer8nUNWiP1DKuNrybD2xBrixLJdCC9J6ECoYkg==",
             "requires": {
                 "@socket.io/component-emitter": "~3.1.0",
                 "debug": "~4.4.1"
@@ -14980,9 +14980,9 @@
             "dev": true
         },
         "undici": {
-            "version": "7.28.0",
-            "resolved": "https://registry.npmjs.org/undici/-/undici-7.28.0.tgz",
-            "integrity": "sha512-cRZYrTDwWznlnRiPjggAGxZXanty6M8RV1ff8Wm4LWXBp7/IG8v5DnOm74DtUBp9OONpK75YlPnIjQqX0dBDtA==",
+            "version": "7.29.0",
+            "resolved": "https://registry.npmjs.org/undici/-/undici-7.29.0.tgz",
+            "integrity": "sha512-IDxfleLmmbSskfWSUATiN1nfn2rDuvnMOqb5CWR92iIfojA0Ud+ulOAAEQ57LPr9rWmsreUyf5lwyao+7GNNVw==",
             "dev": true
         },
         "undici-types": {

From ae2ff84e63ac8cbabcfd18dbb84d92d0263964db Mon Sep 17 00:00:00 2001
From: jefbinomed <jean.francois.garreau@gmail.com>
Date: Thu, 13 Aug 2026 14:03:46 +0200
Subject: [PATCH 6/7] =?UTF-8?q?=F0=9F=94=A7=20chore(ci):=20cadrer=20l'audi?=
 =?UTF-8?q?t=20sur=20le=20seuil=20high?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Le défaut de `--audit-level` est `null`, soit un échec sur n'importe
quelle sévérité, `info` comprise. Le job tel qu'ajouté au commit
précédent était donc plus strict que ce qui l'a motivé : les 5 failles
corrigées étaient toutes `high`, mais un simple avis `low` sur une
transitive de build aurait bloqué la CI.

Le coût n'est pas théorique : `npm audit` interroge la base d'avis du
registre à l'instant du run, alors que le lockfile est gelé. Un avis
publié entre deux commits rend rouge la PR suivante, quels que soient
son auteur et son sujet — le job n'accuse pas le coupable, il accuse le
prochain qui passe. Autant réserver cette interruption aux failles qui
la justifient.

- job CI et scripts/verify.sh alignés sur `--audit-level=high` : un
  écart entre les deux ferait échouer localement ce qui passe en CI,
  alors que le script sert de garde avant PR ;
- CLAUDE.md mis en cohérence : le seuil est explicite, et `npm audit`
  sans option reste la commande pour la photo complète.

Les alertes Dependabot du dépôt, déjà actives, couvrent la veille de
fond sur les sévérités inférieures.
---
 .github/workflows/develop.yml | 15 +++++++++++++--
 CLAUDE.md                     |  4 +++-
 scripts/verify.sh             |  5 ++++-
 3 files changed, 20 insertions(+), 4 deletions(-)

diff --git a/.github/workflows/develop.yml b/.github/workflows/develop.yml
index 9eab7c60..2fdab610 100644
--- a/.github/workflows/develop.yml
+++ b/.github/workflows/develop.yml
@@ -49,6 +49,17 @@ jobs:
     # `npm audit` sort en code non nul dès qu'il trouve quelque chose au niveau
     # demandé — c'est ce qui fait échouer le job, aucune commande de plus n'est
     # nécessaire.
+    #
+    # Seuil `high` et non le défaut (`null` = échec sur n'importe quelle
+    # sévérité, jusqu'à `info`). `npm audit` interroge la base d'avis du registre
+    # à l'instant du run : le lockfile est gelé, la base ne l'est pas. Un avis
+    # publié entre deux commits rend donc rouge la PR suivante, quel qu'en soit
+    # l'auteur et le sujet. Au seuil par défaut, un simple `low` sur une
+    # transitive de build suffirait à bloquer un contributeur sur un problème
+    # qui n'est pas le sien. `high` cadre le job sur ce qui justifie une
+    # interruption. scripts/verify.sh applique le même seuil pour ne pas diverger ;
+    # pour la photo complète (low et moderate compris), lancer `npm audit` sans
+    # option. Les alertes Dependabot du dépôt couvrent la veille de fond.
     # ----------------------------------------------------------------
     audit:
         name: Dependency audit — Node 24
@@ -66,8 +77,8 @@ jobs:
             - name: Install dependencies
               run: npm ci
 
-            - name: Audit dependencies
-              run: npm audit
+            - name: Audit dependencies (high and above)
+              run: npm audit --audit-level=high
 
     # ----------------------------------------------------------------
     # Job 2 — TypeScript strict
diff --git a/CLAUDE.md b/CLAUDE.md
index e12bf68f..bc9cb317 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -42,7 +42,9 @@ Avant commit / PR — **validation complète, miroir de la CI** (`.github/workfl
 
 soit : `tsc --noEmit`, `lint:check`, `NODE_ENV=test npm run coverage` (jsdom + browser + merge —
 les suites tournent DANS coverage, ne pas les relancer à part : IMP-013), `test:e2e` (Playwright
-démarre lui-même les 3 services), `build`, `npm audit` (0 vulnérabilité attendu), `docs:build`.
+démarre lui-même les 3 services), `build`, `npm audit --audit-level=high` (0 vulnérabilité `high`
+ou `critical` attendu — même seuil que le job CI `audit` ; `npm audit` sans option montre aussi
+les `low`/`moderate`, qui ne bloquent pas), `docs:build`.
 
 Le script couvre les mêmes contrôles que la CI, mais **il n'en est pas la copie exacte** : la
 correspondance vaut job par job, pas ligne par ligne. Avant de conclure « la CI échoue déjà
diff --git a/scripts/verify.sh b/scripts/verify.sh
index 1ca7bf22..30024686 100755
--- a/scripts/verify.sh
+++ b/scripts/verify.sh
@@ -27,7 +27,10 @@ run "lint        " npm run lint:check
 run "coverage    " env NODE_ENV=test npm run coverage
 run "e2e         " npm run test:e2e
 run "build       " npm run build
-run "audit       " npm audit
+# Même seuil que le job `audit` de la CI : un écart ferait échouer ici ce qui passe
+# là-bas (ou l'inverse), et ce script sert justement de garde avant PR.
+# Pour la photo complète, low et moderate compris : `npm audit` sans option.
+run "audit       " npm audit --audit-level=high
 run "docs        " npm run docs:build
 
 echo ""

From 5e5b609c8f77b5bb637b7fc010d9987ce19a683e Mon Sep 17 00:00:00 2001
From: jefbinomed <jean.francois.garreau@gmail.com>
Date: Thu, 13 Aug 2026 14:18:11 +0200
Subject: [PATCH 7/7] =?UTF-8?q?=F0=9F=94=A7=20chore(ci):=20faire=20tourner?=
 =?UTF-8?q?=20la=20CI=20sur=20main=20aussi?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Aucune PR ciblant `main` ne déclenchait le moindre contrôle : le
workflow ne s'abonnait qu'à `develop`. Les trois PR Dependabot ouvertes
(#68, #69, #70), qui visent `main`, affichent littéralement
« no checks reported » — et `main` est la branche par défaut du dépôt,
donc celle où atterrissent les mises à jour de sécurité.

- `push` et `pull_request` couvrent désormais `develop` et `main` ;
- workflow renommé « CI — Node 24 », l'intitulé « Develop CI » étant
  devenu faux. Le nom de FICHIER reste `develop.yml` : il est référencé
  par le badge du README, CLAUDE.md et plusieurs docs d'amélioration, et
  le renommer casserait les liens vers les runs existants ;
- `docs-deploy` est déjà conditionné à `refs/heads/develop`, il skippe
  donc sur `main` sans rien changer au déploiement des docs.

Aucune protection de branche n'est configurée sur le dépôt, donc le
renommage du workflow ne casse aucune règle de checks requis.
---
 .github/workflows/develop.yml | 9 ++++++++-
 CLAUDE.md                     | 5 +++++
 2 files changed, 13 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/develop.yml b/.github/workflows/develop.yml
index 2fdab610..f093b1d9 100644
--- a/.github/workflows/develop.yml
+++ b/.github/workflows/develop.yml
@@ -1,12 +1,19 @@
-name: Develop CI — Node 24
+# Nom de fichier historique (`develop.yml`) : le workflow couvre aussi `main`
+# depuis qu'on a constaté que les PR vers la branche par défaut ne déclenchaient
+# strictement aucun contrôle — les PR Dependabot #68/#69/#70 affichaient
+# « no checks reported ». Renommer le fichier casserait les liens existants vers
+# les runs, on garde donc le nom et on corrige l'intitulé.
+name: CI — Node 24
 
 on:
     push:
         branches:
             - develop
+            - main
     pull_request:
         branches:
             - develop
+            - main
 
 concurrency:
     group: ${{ github.workflow }}-${{ github.ref }}
diff --git a/CLAUDE.md b/CLAUDE.md
index bc9cb317..9deb6f00 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -52,6 +52,11 @@ là-dessus » à partir d'un échec local, vérifier que le contrôle en questio
 `.github/workflows/develop.yml` — `npm audit` n'en avait aucun jusqu'à la mise en place du job
 `audit`, et un échec local ne rendait donc pas la CI rouge.
 
+Le workflow s'appelle `develop.yml` pour des raisons historiques mais couvre **`develop` ET `main`**
+(push et pull_request). Avant, aucune PR vers `main` — la branche par défaut, cible des PR
+Dependabot — ne déclenchait le moindre contrôle. Seul `docs-deploy` reste conditionné à
+`refs/heads/develop` et skippe sur `main`.
+
 ## Contrat iso-fonctionnel
 
 `docs/migration/golden-path.md` fait foi : le comportement utilisateur décrit là est le contrat,