dev-playbooks 1.2.6 → 1.2.8

package/README.md

@@ -146,7 +146,7 @@ Run devbooks-code-review skill for change add-oauth2
 **4) Archive stage**
 
 ```
-Run devbooks-spec-gardener skill for change add-oauth2
+Run devbooks-archiver skill for change add-oauth2
 ```
 
 ---
@@ -185,7 +185,7 @@ Run devbooks-spec-gardener skill for change add-oauth2
 
 | Skill | Description |
 |-------|-------------|
-| devbooks-spec-gardener | Maintain/dedupe specs |
+| devbooks-archiver | Maintain/dedupe specs |
 | devbooks-delivery-workflow | End-to-end delivery workflow |
 
 ### Standalone Skills

package/bin/devbooks.js

@@ -806,7 +806,7 @@ ${DEVBOOKS_MARKERS.start}
 | \`devbooks-proposal-author\` | 创建变更提案 |
 | \`devbooks-design-doc\` | 创建设计文档 |
 | \`devbooks-test-owner / devbooks-coder\` | 执行实现 |
-| \`devbooks-spec-gardener\` | 归档变更包 |
+| \`devbooks-archiver\` | 归档变更包 |
 
 ${DEVBOOKS_MARKERS.end}
 `;
@@ -942,7 +942,7 @@ function generateAgentsContent(filename) {
 | \`devbooks-proposal-author\` | 创建变更提案 |
 | \`devbooks-design-doc\` | 创建设计文档 |
 | \`devbooks-test-owner / devbooks-coder\` | 执行实现（test-owner/coder/reviewer） |
-| \`devbooks-spec-gardener\` | 归档变更包 |
+| \`devbooks-archiver\` | 归档变更包 |
 
 ${DEVBOOKS_MARKERS.end}
 `;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dev-playbooks",
-  "version": "1.2.6",
+  "version": "1.2.8",
   "description": "AI-powered spec-driven development workflow",
   "keywords": [
     "devbooks",

package/skills/Skill-Development-Guide.md

@@ -95,7 +95,7 @@ echo "ok: verification passed"
 
 ### 1.5 Truth Source Separation
 
-- **Read-only truth**: Skills may read from `<truth-root>/` but must not modify it directly (except for archive-related Skills such as `spec-gardener`).
+- **Read-only truth**: Skills may read from `<truth-root>/` but must not modify it directly (except for archive-related Skills such as `archiver`).
 - **Write to workspace**: Skills should write to `<change-root>/<change-id>/`.
 - **Archive is merge**: archiving merges workspace outputs back into truth.
 

package/skills/Skills-Usage-Guide.md

@@ -245,7 +245,7 @@ If you are not using DevBooks, replace `dev-playbooks/specs` / `dev-playbooks/ch
 
 ---
 
-## `devbooks-spec-gardener` (Spec Gardener)
+## `devbooks-archiver` (Archiver)
 
 - Purpose: before archiving, prune and maintain `<truth-root>` (dedupe/merge/remove stale/reorganize/fix consistency) to prevent spec sprawl.
 - When to use:
@@ -253,7 +253,7 @@ If you are not using DevBooks, replace `dev-playbooks/specs` / `dev-playbooks/ch
   - You found duplicate/overlapping/stale entries in `<truth-root>`
 - Copy-paste prompt:
   ```text
-  You are Spec Gardener. Explicitly use `devbooks-spec-gardener`.
+  You are Archiver. Explicitly use `devbooks-archiver`.
   Inputs: `dev-playbooks/changes/<change-id>/specs/**` + `dev-playbooks/specs/**` + `dev-playbooks/changes/<change-id>/design.md` (if any).
   You may modify only `dev-playbooks/specs/**` to merge/dedupe/categorize/delete stale items; do not modify the change package contents.
   Output in order: operation list (CREATE/UPDATE/MOVE/DELETE) → full content for every CREATE/UPDATE file → merge mapping summary → Open Questions (<=3).

package/skills/_shared/mcp-enhancement-template.md

@@ -66,7 +66,7 @@ The following Skills do not depend on MCP and do not need an MCP Enhancement sec
 - devbooks-proposal-challenger (review-only)
 - devbooks-proposal-judge (verdict-only)
 - devbooks-design-backport (document backport)
-- devbooks-spec-gardener (file pruning)
+- devbooks-archiver (file pruning)
 - devbooks-test-reviewer (test review)
 
 For these Skills, the MCP Enhancement section should be:

package/skills/_shared/references/deviation-detection-routing-protocol.md

@@ -128,7 +128,7 @@ deviation-log.md is a **persistent file** unaffected by compact. Even if convers
 | coder | HANDOFF (test issue) | `devbooks-test-owner` |
 | test-owner | COMPLETED | `devbooks-coder` |
 | test-owner | HANDOFF (design issue) | `devbooks-design-backport` |
-| code-review | COMPLETED (has spec delta) | `devbooks-spec-gardener` |
+| code-review | COMPLETED (has spec delta) | `devbooks-archiver` |
 | code-review | COMPLETED (no spec delta) | Archive complete |
 | Any | BLOCKED | Record breakpoint, wait for user |
 | Any | FAILED | Fix and retry current skill |

package/skills/_shared/references/universal-gating-protocol.md

@@ -39,9 +39,9 @@ From now on, each time you write files, restate the `<truth-root>` and `<change-
 | Spec deltas | `<change-root>/<change-id>/specs/` | `./specs/` |
 | Traceability doc | `<change-root>/<change-id>/verification.md` | `./verification.md` |
 
-### DevBooks 2.0 Default Paths
+### Dev-Playbooks Default Paths
 
-When using DevBooks 2.0 protocol:
+When using Dev-Playbooks protocol:
 - `<change-root>` = `dev-playbooks/changes`
 - `<truth-root>` = `dev-playbooks/specs`
 

package/skills/_shared/workflow-next-steps.md

@@ -25,7 +25,7 @@ This document defines the canonical next step recommendations for each skill. Al
                               ↓
 ┌─────────────────────────────────────────────────────────────────┐
 │                     ARCHIVE STAGE                                │
-│                     spec-gardener                                │
+│                     archiver                                │
 └─────────────────────────────────────────────────────────────────┘
 ```
 
@@ -45,11 +45,11 @@ This document defines the canonical next step recommendations for each skill. Al
 | `devbooks-implementation-plan` | `devbooks-test-owner` | Always (must be separate chat) |
 | `devbooks-test-owner` | `devbooks-coder` | After Red baseline (must be separate chat) |
 | `devbooks-coder` | `devbooks-code-review` | After all tasks completed |
-| `devbooks-code-review` | `devbooks-spec-gardener` | If spec deltas exist |
+| `devbooks-code-review` | `devbooks-archiver` | If spec deltas exist |
 | `devbooks-code-review` | Archive complete | If no spec deltas |
 | `devbooks-test-reviewer` | `devbooks-coder` | If test issues found, hand back |
 | `devbooks-design-backport` | `devbooks-implementation-plan` | Rerun plan after design update |
-| `devbooks-spec-gardener` | Archive complete | Always |
+| `devbooks-archiver` | Archive complete | Always |
 
 ## Critical Constraints
 

package/skills/devbooks-archiver/SKILL.md

@@ -0,0 +1,315 @@
+---
+name: devbooks-archiver
+description: devbooks-archiver: The single entry point for the archive phase, responsible for the complete archive closed-loop (auto-backport → spec merge → doc sync check → change package archive move). Use when user says "archive/finalize/close-loop/merge to truth" etc.
+allowed-tools:
+  - Glob
+  - Grep
+  - Read
+  - Write
+  - Edit
+  - Bash
+---
+
+# DevBooks: Archiver
+
+## Workflow Position Awareness
+
+> **Core Principle**: Archiver is the **single entry point** for the archive phase, responsible for completing all finalization work from code review to change package archival.
+
+### My Position in the Overall Workflow
+
+```
+proposal → design → test-owner(P1) → coder → test-owner(P2) → code-review → [Archiver]
+                                                                                  ↓
+                                               Auto backport → Spec merge → Doc check → Archive move
+```
+
+### Why Renamed to Archiver?
+
+| Old Name | New Name | Reason for Change |
+|----------|----------|-------------------|
+| `spec-gardener` | `archiver` | Responsibilities expanded beyond just spec merging to complete archive closed-loop |
+
+### Archiver's Complete Responsibilities
+
+| Phase | Responsibility | Description |
+|-------|---------------|-------------|
+| 1 | Auto backport detection and handling | Detect deviation-log.md, auto-backport to design doc |
+| 2 | Spec merge | Merge specs/contracts into truth-root |
+| 3 | Architecture merge | Merge design.md's Architecture Impact into c4.md |
+| 4 | Documentation sync check | Check if design.md's Documentation Impact has been processed |
+| 5 | Change package archive move | Move change package to `<change-root>/archive/` |
+
+---
+
+## Prerequisites: Configuration Discovery (Protocol Agnostic)
+
+- `<truth-root>`: Current truth directory root
+- `<change-root>`: Change package directory root
+
+Before execution, **must** search for configuration in the following order (stop when found):
+1. `.devbooks/config.yaml` (if exists) → Parse and use the mappings within
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
+3. `project.md` (if exists) → Template protocol, use default mappings
+4. If still unable to determine → **Stop and ask the user**
+
+**Critical Constraints**:
+- If `agents_doc` (rules document) is specified in the configuration, **must read that document first** before executing any operations
+- Do not guess directory roots
+- Do not skip reading the rules document
+
+---
+
+## Complete Archive Flow
+
+### Step 1: Pre-checks
+
+```markdown
+Pre-check checklist:
+- [ ] Change package exists (<change-root>/<change-id>/)
+- [ ] verification.md Status = Ready or Done
+- [ ] evidence/green-final/ exists and is non-empty
+- [ ] tasks.md all tasks completed ([x])
+- [ ] Code review passed (verification.md Status = Done set by Reviewer)
+```
+
+If check fails → Stop and output missing items, suggest user complete prerequisite steps first.
+
+### Step 2: Auto Backport Detection and Handling
+
+> **Design Decision**: Archive phase automatically handles all pending backports, users don't need to manually call design-backport.
+
+**Detection Flow**:
+
+```
+1. Read <change-root>/<change-id>/deviation-log.md
+2. Check if there are "| ❌" pending backport records
+   → Yes: Execute auto backport (steps 3-5)
+   → No: Skip, proceed directly to merge phase
+
+3. For each pending record, determine if it's Design-level content:
+   - DESIGN_GAP, CONSTRAINT_CHANGE, API_CHANGE → Need backport
+   - Pure implementation details (filename/classname/temp steps) → Don't backport, mark as IMPL_ONLY
+
+4. Execute design backport:
+   - Read design.md
+   - Update according to design-backport protocol's "backportable content scope"
+   - Add change record at the end of design.md
+
+5. Update deviation-log.md:
+   - Mark backported records as ✅
+   - Record backport time and archive batch
+```
+
+**Auto Backport Content Scope** (inherited from design-backport):
+
+| Backportable | Not Backportable |
+|--------------|------------------|
+| External semantics/user-visible behavior | Specific file paths, class/function names |
+| System-level immutable constraints (Invariants) | PR splits, task execution order |
+| Core data contracts and evolution strategies | Overly detailed algorithm pseudocode |
+| Cross-phase governance strategies | Script commands |
+| Key tradeoffs and decisions | Table/field names |
+
+### Step 3: Spec Merge
+
+Merge change package spec artifacts into `<truth-root>`:
+
+| Source Path | Target Path | Merge Strategy |
+|-------------|-------------|----------------|
+| `<change-root>/<change-id>/specs/**` | `<truth-root>/specs/**` | Incremental merge |
+| `<change-root>/<change-id>/contracts/**` | `<truth-root>/contracts/**` | Versioned merge |
+
+### Step 4: Architecture Merge
+
+> **Design Decision**: C4 architecture changes are recorded in design.md's Architecture Impact section and merged into truth by Archiver during archiving.
+
+**C4 Merge Flow**:
+
+1. **Detect Architecture Changes**: Parse "Architecture Impact" section in `design.md`
+2. **Determine If Merge Needed**:
+   - If "No Architecture Changes" is checked → Skip merge
+   - If "Has Architecture Changes" → Execute merge
+3. **Execute Merge**:
+   - Read `<truth-root>/architecture/c4.md` (create if doesn't exist)
+   - Update corresponding sections based on Architecture Impact descriptions
+   - Update Container/Component tables
+   - Update dependency relationships
+   - Update layering constraints (if changed)
+4. **Record Merge Log**: Append change record at end of c4.md
+
+### Step 5: Documentation Sync Check
+
+Check "Documentation Impact" section in design.md:
+
+```markdown
+Check items:
+- [ ] If "Documents requiring updates" is declared, verify these documents have been updated
+- [ ] If "No updates needed" is checked, confirm reasonableness
+- [ ] Output documentation sync status report
+```
+
+**If there are unprocessed documentation updates**:
+- Output warning, list documents needing updates
+- Don't block archive, but mark as "Documentation pending update" in archive report
+
+### Step 6: Change Package Archive Move (New)
+
+Move completed change package to archive directory:
+
+```bash
+# Source path
+<change-root>/<change-id>/
+
+# Target path
+<change-root>/archive/<change-id>/
+```
+
+**Move Flow**:
+
+1. **Create archive directory** (if doesn't exist): `<change-root>/archive/`
+2. **Set final status**: Set `Status: Archived` in verification.md
+3. **Add archive timestamp**: Add `Archived-At: <timestamp>` at end of verification.md
+4. **Move change package**: `mv <change-root>/<change-id>/ <change-root>/archive/<change-id>/`
+5. **Output archive completion report**
+
+**verification.md Archive Status Update**:
+
+```markdown
+---
+status: Archived
+archived-at: 2024-01-16T10:30:00Z
+archived-by: devbooks-archiver
+---
+```
+
+---
+
+## Execution Method
+
+1) First read and follow: `_shared/references/universal-gating-protocol.md` (verifiability + structural quality gates).
+2) Strictly execute the complete prompt: `references/archiver-prompt.md`.
+
+---
+
+## Context Awareness
+
+This Skill automatically detects context before execution and selects the appropriate running mode.
+
+Detection rules reference: `skills/_shared/context-detection-template.md`
+
+### Detection Flow
+
+1. Detect `<truth-root>/` directory status
+2. If change-id is provided, detect change package archive conditions
+3. Detect duplicate/obsolete specs (maintenance mode)
+
+### Modes Supported by This Skill
+
+| Mode | Trigger Condition | Behavior |
+|------|-------------------|----------|
+| **Archive Mode** | change-id provided and gates pass | Execute complete archive flow (6 steps) |
+| **Maintenance Mode** | No change-id | Execute truth-root deduplication, cleanup, organization |
+| **Check Mode** | With --dry-run parameter | Output plan only, no actual modifications/moves |
+
+### Archive Mode Complete Flow Diagram
+
+```
+┌─────────────────────────────────────────────────────────────┐
+│                    Archive Mode Flow                         │
+├─────────────────────────────────────────────────────────────┤
+│                                                             │
+│  1. Pre-checks                                              │
+│     ├─ Change package exists?                               │
+│     ├─ verification.md Status = Ready/Done?                 │
+│     ├─ evidence/green-final/ exists?                        │
+│     └─ tasks.md all completed?                              │
+│              │                                               │
+│              ▼                                               │
+│  2. Auto backport                                           │
+│     ├─ Read deviation-log.md                                │
+│     ├─ Detect pending backport records                      │
+│     └─ Execute backport → Update marks                      │
+│              │                                               │
+│              ▼                                               │
+│  3. Spec merge                                              │
+│     ├─ specs/** → truth-root/specs/**                       │
+│     └─ contracts/** → truth-root/contracts/**               │
+│              │                                               │
+│              ▼                                               │
+│  4. Architecture merge                                      │
+│     └─ Architecture Impact → c4.md                          │
+│              │                                               │
+│              ▼                                               │
+│  5. Documentation sync check                                │
+│     └─ Check if Documentation Impact processed              │
+│              │                                               │
+│              ▼                                               │
+│  6. Change package archive move                             │
+│     ├─ Set Status: Archived                                 │
+│     └─ mv <change-id>/ → archive/<change-id>/               │
+│              │                                               │
+│              ▼                                               │
+│  ✅ Output archive completion report                        │
+│                                                             │
+└─────────────────────────────────────────────────────────────┘
+```
+
+### Detection Output Example
+
+```
+Detection Results:
+- truth-root: Exists, contains 12 spec files
+- Change package: Exists, all gates green
+- Backport status: 2 pending backport records
+- Running mode: Archive mode (complete flow)
+```
+
+---
+
+## Archive Report Template
+
+After archive completion, output the following report:
+
+```markdown
+## Archive Report
+
+### Change Package Info
+- Change ID: <change-id>
+- Archive Time: <timestamp>
+
+### Execution Summary
+| Step | Status | Notes |
+|------|--------|-------|
+| Pre-checks | ✅ | All passed |
+| Auto backport | ✅ | Backported 2 records |
+| Spec merge | ✅ | Merged 3 spec files |
+| Architecture merge | ⏭️ | No architecture changes |
+| Doc check | ⚠️ | README.md needs update |
+| Archive move | ✅ | Moved to archive/ |
+
+### Archive Location
+`<change-root>/archive/<change-id>/`
+
+### Follow-up Recommendations
+- [ ] Update README.md (doc check warning)
+```
+
+---
+
+## Maintenance Mode Responsibilities
+
+In maintenance mode (no change-id), execute:
+
+- Detect duplicate spec definitions
+- Clean up obsolete/deprecated specs
+- Organize directory structure
+- Fix consistency issues
+
+---
+
+## MCP Enhancement
+
+This Skill does not depend on MCP services; no runtime detection required.
+
+MCP enhancement rules reference: `skills/_shared/mcp-enhancement-template.md`

package/skills/devbooks-brownfield-bootstrap/SKILL.md

@@ -20,7 +20,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Create DevBooks directory structure and initialize basic configuration**
 
@@ -74,7 +74,7 @@ Generate in `<truth-root>/architecture/`:
 | Technical debt hotspots | `architecture/hotspots.md` | `mcp__ckb__getHotspots` |
 | Layering constraints | `architecture/layering-constraints.md` | Code analysis (optional) |
 
-> **Design Decision**: C4 architecture map is now generated by brownfield-bootstrap during initialization. Subsequent architecture changes are recorded in design.md's Architecture Impact section and merged by spec-gardener during archiving.
+> **Design Decision**: C4 architecture map is now generated by brownfield-bootstrap during initialization. Subsequent architecture changes are recorded in design.md's Architecture Impact section and merged by archiver during archiving.
 
 ### 4. Baseline Change Package
 

package/skills/devbooks-code-review/SKILL.md

@@ -45,7 +45,7 @@ proposal → design → test-owner(phase1) → coder → test-owner(phase2) →
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 4. If still undetermined -> **Stop and ask user**
 
@@ -172,7 +172,7 @@ After completing code-review, the next step depends on the situation:
 
 | Condition | Next Skill | Reason |
 |-----------|------------|--------|
-| Spec deltas exist | `devbooks-spec-gardener` | Merge specs into truth before archive |
+| Spec deltas exist | `devbooks-archiver` | Merge specs into truth before archive |
 | No spec deltas | Archive complete | No further skills needed |
 | Major issues found | Hand back to `devbooks-coder` | Fix issues before archive |
 
@@ -192,7 +192,7 @@ After completing code-review, output:
 ```markdown
 ## Recommended Next Step
 
-**Next: `devbooks-spec-gardener`** (if spec deltas exist)
+**Next: `devbooks-archiver`** (if spec deltas exist)
 OR
 **Archive complete** (if no spec deltas)
 

package/skills/devbooks-coder/SKILL.md

@@ -53,7 +53,7 @@ proposal → design → test-owner(phase1) → [Coder] → test-owner(phase2)
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 5. If still unable to determine -> **Stop and ask the user**
 
@@ -161,7 +161,7 @@ GOOD: 3 tests failed, see <change-root>/<change-id>/evidence/green-final/test-ou
 
 **Correct path examples**:
 ```bash
-# DevBooks 2.0 default path
+# Dev-Playbooks default path
 dev-playbooks/changes/<change-id>/evidence/green-final/test-$(date +%Y%m%d-%H%M%S).log
 
 # Using the script

package/skills/devbooks-delivery-workflow/SKILL.md

@@ -19,7 +19,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**
 
@@ -28,6 +28,58 @@ Before execution, **must** search for configuration in the following order (stop
 - Do not guess directory roots
 - Do not skip reading the rules document
 
+## Change Package Naming Convention (Mandatory)
+
+Change package ID (change-id) **must** follow this naming convention:
+
+### Format
+
+```
+<datetime>-<verb-prefixed-semantic-description>
+```
+
+### Rules
+
+| Component | Rule | Example |
+|-----------|------|---------|
+| Datetime | `YYYYMMDD-HHMM` format | `20240116-1030` |
+| Separator | Use `-` between datetime and semantic | `-` |
+| Semantic description | **Must start with a verb**, use lowercase and hyphens | `add-oauth2`, `fix-login-bug` |
+
+### Valid Examples
+
+```bash
+# ✅ Correct
+20240116-1030-add-oauth2-support
+20240116-1430-fix-user-auth-bug
+20240116-0900-refactor-payment-module
+20240115-2200-update-api-docs
+
+# ❌ Incorrect
+add-oauth2                    # Missing datetime
+20240116-oauth2               # Semantic doesn't start with verb
+2024-01-16-add-oauth2         # Wrong date format (shouldn't have -)
+oauth2-20240116               # Wrong order
+```
+
+### Common Verbs
+
+| Verb | Usage |
+|------|-------|
+| `add` | Add new feature |
+| `fix` | Fix defect |
+| `update` | Update existing feature |
+| `refactor` | Refactor code |
+| `remove` | Remove feature |
+| `improve` | Improve performance/experience |
+| `migrate` | Migrate data/system |
+
+### Why This Naming Convention?
+
+1. **Timestamp first**: Auto-sorts by time in archive directory
+2. **Verb prefix**: Clearly expresses change intent, aids code review
+3. **Lowercase hyphens**: Avoids cross-platform filename issues
+
 ## Reference Skeleton (Read as Needed)
 
 - Workflow: `references/delivery-acceptance-workflow.md`

package/skills/devbooks-delivery-workflow/references/delivery-acceptance-workflow.md

@@ -163,7 +163,7 @@ Checklist:
 - Update traceability statuses (DONE/BLOCKED/DEFERRED)
 - Update plan progress based on anchors only
 - Update value-stream evidence links in `verification.md`
-- Spec gardening (optional): use `devbooks-spec-gardener` to dedupe/merge/cleanup truth root
+- Spec gardening (optional): use `devbooks-archiver` to dedupe/merge/cleanup truth root
 
 ---
 

package/skills/devbooks-delivery-workflow/scripts/change-check.sh

@@ -529,7 +529,7 @@ check_spec_deltas() {
 }
 
 # =============================================================================
-# Constitution Check (DevBooks 2.0)
+# Constitution Check (Dev-Playbooks)
 # Verify project constitution is present and valid
 # =============================================================================
 check_constitution() {
@@ -557,7 +557,7 @@ check_constitution() {
 }
 
 # =============================================================================
-# Fitness Check (DevBooks 2.0)
+# Fitness Check (Dev-Playbooks)
 # Verify architecture fitness rules
 # =============================================================================
 check_fitness() {
@@ -1037,9 +1037,9 @@ else
   check_verification
   check_no_tests_changed
   check_implicit_changes
-  # DevBooks 2.0: Constitution check
+  # Dev-Playbooks: Constitution check
   check_constitution               # Constitution validity check (strict mode)
-  # DevBooks 2.0: Fitness check
+  # Dev-Playbooks: Fitness check
   check_fitness                    # Architecture fitness check (apply/archive/strict)
   # New quality gates (harden-devbooks-quality-gates)
   check_evidence_closure       # AC-001: Green evidence required for archive

package/skills/devbooks-design-backport/SKILL.md

@@ -13,7 +13,7 @@ allowed-tools:
 
 ## Workflow Position Awareness
 
-> **Core Principle**: Design Backport is now **primarily auto-invoked by Spec Gardener during archive phase**, users typically don't need to call it manually.
+> **Core Principle**: Design Backport is now **primarily auto-invoked by Archiver during archive phase**, users typically don't need to call it manually.
 
 ### My Position in the Overall Workflow
 
@@ -32,7 +32,7 @@ coder has deviations → user manually calls design-backport → then archive
 
 **New Flow** (auto handling):
 ```
-coder has deviations → spec-gardener auto-detects and backports during archive → archive
+coder has deviations → archiver auto-detects and backports during archive → archive
 ```
 
 ### When Manual Call is Still Needed
@@ -52,7 +52,7 @@ coder has deviations → spec-gardener auto-detects and backports during archive
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 4. If still undetermined → **Stop and ask the user**
 

package/skills/devbooks-design-doc/SKILL.md

@@ -40,7 +40,7 @@ proposal → [Design Doc] → spec-contract → implementation-plan → test-own
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask user**
 
@@ -100,7 +100,7 @@ The following change types **require** updating corresponding documentation:
 
 Design documents **must** include an "Architecture Impact" section declaring the impact of this change on system architecture. This is a key mechanism to ensure architecture changes go through verification closed-loops.
 
-> **Design Decision**: C4 architecture changes are no longer written directly to the truth directory by a standalone `devbooks-c4-map` skill. Instead, they are part of design.md and merged into truth by `devbooks-spec-gardener` after change acceptance.
+> **Design Decision**: C4 architecture changes are no longer written directly to the truth directory by a standalone `devbooks-c4-map` skill. Instead, they are part of design.md and merged into truth by `devbooks-archiver` after change acceptance.
 
 ### Template
 

package/skills/devbooks-docs-sync/SKILL.md

@@ -16,7 +16,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**
 

package/skills/devbooks-entropy-monitor/SKILL.md

@@ -19,7 +19,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask the user**
 

package/skills/devbooks-impact-analysis/SKILL.md

@@ -17,7 +17,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> template protocol, use default mappings
 5. If still unable to determine -> **Stop and ask the user**
 

package/skills/devbooks-implementation-plan/SKILL.md

@@ -54,7 +54,7 @@ proposal → design → [Implementation Plan] → test-owner(phase1) → coder
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask the user**
 

package/skills/devbooks-proposal-author/SKILL.md

@@ -18,7 +18,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**
 

package/skills/devbooks-proposal-challenger/SKILL.md

@@ -16,7 +16,7 @@ allowed-tools:
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 4. If still undetermined → **Stop and ask user**
 

package/skills/devbooks-proposal-judge/SKILL.md

@@ -18,7 +18,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask the user**
 

package/skills/devbooks-router/SKILL.md

@@ -32,7 +32,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 4. If still undetermined → **Stop and ask user**
 
@@ -251,7 +251,7 @@ Default routing:
 Trigger signals: User says "archive/merge specs/close out/wrap up" etc.
 
 Default routing:
-- If spec deltas were produced this time: `devbooks-spec-gardener` (prune `<truth-root>/**` before archive merge)
+- If spec deltas were produced this time: `devbooks-archiver` (prune `<truth-root>/**` before archive merge)
 - If design decisions need to be written back: `devbooks-design-backport` (as needed)
 - If user documentation affected: `devbooks-docs-sync` (ensure docs consistent with code)
 
@@ -302,7 +302,7 @@ Trigger signals: User says "prototype first/quick validation/spike/--prototype/t
 
 ## DevBooks Skill Adaptation
 
-DevBooks uses `devbooks-proposal-author skill`, `devbooks-test-owner/coder skill`, `devbooks-spec-gardener skill` as entry points.
+DevBooks uses `devbooks-proposal-author skill`, `devbooks-test-owner/coder skill`, `devbooks-archiver skill` as entry points.
 Route according to A/B/C/D above, artifact paths follow `<truth-root>/<change-root>` mappings in project signposts.
 
 ---

package/skills/devbooks-spec-contract/SKILL.md

@@ -21,7 +21,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 5. If still unable to determine -> **Stop and ask the user**
 

package/skills/devbooks-test-owner/SKILL.md

@@ -59,7 +59,7 @@ When user says "Coder is done, please verify" or similar, Test Owner enters **Ph
 
 Before execution, **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) → Parse and use its mappings
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) → Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) → Template protocol, use default mappings
 5. If still unable to determine → **Stop and ask user**
 
@@ -205,7 +205,7 @@ Test Owner must produce a structured `verification.md` that serves as both test
 
 **Correct path examples**:
 ```bash
-# DevBooks 2.0 default path
+# Dev-Playbooks default path
 dev-playbooks/changes/<change-id>/evidence/red-baseline/test-$(date +%Y%m%d-%H%M%S).log
 
 # Using the script

package/skills/devbooks-test-reviewer/SKILL.md

@@ -14,7 +14,7 @@ allowed-tools:
 
 Before execution, you **must** search for configuration in the following order (stop when found):
 1. `.devbooks/config.yaml` (if exists) -> Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) -> DevBooks 2.0 protocol, use default mappings
+2. `dev-playbooks/project.md` (if exists) -> Dev-Playbooks protocol, use default mappings
 3. `project.md` (if exists) -> Template protocol, use default mappings
 4. If still undetermined -> **Stop and ask the user**
 

package/templates/dev-playbooks/README.md

@@ -146,7 +146,7 @@ Run devbooks-code-review skill for change add-oauth2
 **4) Archive stage**
 
 ```
-Run devbooks-spec-gardener skill for change add-oauth2
+Run devbooks-archiver skill for change add-oauth2
 ```
 
 ---
@@ -185,7 +185,7 @@ Run devbooks-spec-gardener skill for change add-oauth2
 
 | Skill | Description |
 |-------|-------------|
-| devbooks-spec-gardener | Maintain/dedupe specs |
+| devbooks-archiver | Maintain/dedupe specs |
 | devbooks-delivery-workflow | End-to-end delivery workflow |
 
 ### Standalone Skills

package/templates/dev-playbooks/docs/devbooks-setup-guide.md

@@ -132,7 +132,7 @@ Each change must declare which gates are covered; missing items require reasons:
 | Test Owner | `devbooks-test-owner` | `verification.md` + `tests/` |
 | Coder | `devbooks-coder` | Implement per tasks (no tests) |
 | Reviewer | `devbooks-code-review` | Review feedback |
-| Spec Gardener | `devbooks-spec-gardener` | Archive pruning + C4 merge |
+| Archiver | `devbooks-archiver` | Archive pruning + C4 merge |
 | Design Backport | `devbooks-design-backport` | Backport design gaps |
 
 ### Workflow-Based

package/templates/dev-playbooks/docs/workflow-diagram.svg

@@ -115,7 +115,7 @@
     <text x="125" y="95" font-family="Arial, sans-serif" font-size="12" fill="#4a5568" text-anchor="middle">Code Review</text>
 
     <rect x="20" y="120" width="210" height="40" rx="8" fill="white" stroke="#8e2de2" stroke-width="2"/>
-    <text x="125" y="145" font-family="Arial, sans-serif" font-size="12" fill="#4a5568" text-anchor="middle">Spec Gardener</text>
+    <text x="125" y="145" font-family="Arial, sans-serif" font-size="12" fill="#4a5568" text-anchor="middle">Archiver</text>
 
     <rect x="20" y="170" width="210" height="40" rx="8" fill="white" stroke="#8e2de2" stroke-width="2"/>
     <text x="125" y="195" font-family="Arial, sans-serif" font-size="12" fill="#4a5568" text-anchor="middle">Merge to truth-root</text>
@@ -194,7 +194,7 @@
       <tspan>Test Owner and Coder must work in separate conversations. "Done" is defined by test/build evidence, not AI self-declaration.</tspan>
     </text>
     <text x="0" y="35" font-family="Arial, sans-serif" font-size="10" fill="#a0aec0">
-      <tspan>Skills: devbooks-proposal-author → devbooks-design-doc → devbooks-implementation-plan → devbooks-test-owner → devbooks-coder → devbooks-code-review → devbooks-spec-gardener</tspan>
+      <tspan>Skills: devbooks-proposal-author → devbooks-design-doc → devbooks-implementation-plan → devbooks-test-owner → devbooks-coder → devbooks-code-review → devbooks-archiver</tspan>
     </text>
   </g>
 </svg>

package/skills/devbooks-spec-gardener/SKILL.md

@@ -1,228 +0,0 @@
----
-name: devbooks-spec-gardener
-description: devbooks-spec-gardener: Prune and maintain <truth-root> before archiving (deduplicate/merge, remove obsolete, organize directories, fix inconsistencies) to prevent specs from accumulating out of control. Use when user says "spec gardener/deduplicate specs/pre-archive cleanup/clean obsolete specs", or during DevBooks archive/pre-archive finalization.
-allowed-tools:
-  - Glob
-  - Grep
-  - Read
-  - Write
-  - Edit
----
-
-# DevBooks: Spec Gardener
-
-## Workflow Position Awareness
-
-> **Core Principle**: Spec Gardener is the endpoint of the archive phase, responsible for merging change package artifacts into truth, **and automatically handling any pending backports**.
-
-### My Position in the Overall Workflow
-
-```
-proposal → design → test-owner → coder → test-owner(verify) → code-review → [Spec Gardener/Archive]
-                                                                                    ↓
-                                                               Auto backport + Merge to truth + Archive
-```
-
-### Spec Gardener's Responsibilities
-
-1. **Auto backport detection**: Check if deviation-log.md has pending backport records
-2. **Auto execute backport**: If pending records exist, automatically execute design backport
-3. **Merge to truth**: Merge specs/contracts/architecture into truth-root
-4. **Archive change package**: Set verification.md Status = Archived
-
-### Why Auto Backport in Archive Phase?
-
-**Design Decision**: Users only need to call skills linearly, no need to judge whether backport is needed.
-
-| Scenario | Old Design (Manual judgment) | New Design (Auto handling) |
-|----------|------------------------------|---------------------------|
-| Coder has deviations | User needs to call design-backport → then archive | Spec Gardener auto-detects and backports |
-| Coder has no deviations | Archive directly | Archive directly |
-
----
-
-## Prerequisites: Configuration Discovery (Protocol Agnostic)
-
-- `<truth-root>`: Current truth directory root
-- `<change-root>`: Change package directory root
-
-Before execution, **must** search for configuration in the following order (stop when found):
-1. `.devbooks/config.yaml` (if exists) → Parse and use the mappings within
-2. `dev-playbooks/project.md` (if exists) → DevBooks 2.0 protocol, use default mappings
-3. `project.md` (if exists) → Template protocol, use default mappings
-5. If still unable to determine → **Stop and ask the user**
-
-**Critical Constraints**:
-- If `agents_doc` (rules document) is specified in the configuration, **must read that document first** before executing any operations
-- Do not guess directory roots
-- Do not skip reading the rules document
-
----
-
-## Core Responsibilities
-
-### 0. Auto Backport Detection and Handling (Required Before Archive)
-
-> **Design Decision**: Archive phase automatically handles all pending backports, users don't need to manually call design-backport.
-
-**Detection Flow**:
-
-```
-1. Read <change-root>/<change-id>/deviation-log.md
-2. Check if there are "| ❌" pending backport records
-   → Yes: Execute auto backport (steps 3-5)
-   → No: Skip, proceed directly to merge phase
-
-3. For each pending record, determine if it's Design-level content:
-   - DESIGN_GAP, CONSTRAINT_CHANGE, API_CHANGE → Need backport
-   - Pure implementation details (filename/classname/temp steps) → Don't backport, mark as IMPL_ONLY
-
-4. Execute design backport:
-   - Read design.md
-   - Update according to design-backport protocol's "backportable content scope"
-   - Add change record at the end of design.md
-
-5. Update deviation-log.md:
-   - Mark backported records as ✅
-   - Record backport time and archive batch
-```
-
-**Auto Backport Content Scope** (inherited from design-backport):
-
-| Backportable | Not Backportable |
-|--------------|------------------|
-| External semantics/user-visible behavior | Specific file paths, class/function names |
-| System-level immutable constraints (Invariants) | PR splits, task execution order |
-| Core data contracts and evolution strategies | Overly detailed algorithm pseudocode |
-| Cross-phase governance strategies | Script commands |
-| Key tradeoffs and decisions | Table/field names |
-
-**deviation-log.md Update Format**:
-
-```markdown
-| Time | Type | Description | Affected Files | Backported | Batch |
-|------|------|-------------|----------------|:----------:|-------|
-| 2024-01-15 10:30 | DESIGN_GAP | Concurrent scenario | tests/... | ✅ | archive-2024-01-16 |
-| 2024-01-15 11:00 | IMPL_ONLY | Variable rename | src/... | ⏭️ | (skipped) |
-```
-
-### 1. Spec Merge and Maintenance
-
-During archive phase, merge change package spec artifacts into `<truth-root>`:
-
-| Source Path | Target Path | Merge Strategy |
-|-------------|-------------|----------------|
-| `<change-root>/<change-id>/specs/**` | `<truth-root>/specs/**` | Incremental merge |
-| `<change-root>/<change-id>/contracts/**` | `<truth-root>/contracts/**` | Versioned merge |
-
-### 2. C4 Architecture Map Merge (New)
-
-> **Design Decision**: C4 architecture changes are now recorded in design.md's Architecture Impact section and merged into truth by spec-gardener during archiving.
-
-During archive phase, detect and merge architecture changes:
-
-| Detection Source | Target Path | Merge Logic |
-|------------------|-------------|-------------|
-| "Architecture Impact" section in `<change-root>/<change-id>/design.md` | `<truth-root>/architecture/c4.md` | Incremental update |
-
-**C4 Merge Flow**:
-
-1. **Detect Architecture Changes**: Parse "Architecture Impact" section in `design.md`
-2. **Determine If Merge Needed**:
-   - If "No Architecture Changes" is checked → Skip merge
-   - If "Has Architecture Changes" → Execute merge
-3. **Execute Merge**:
-   - Read `<truth-root>/architecture/c4.md` (create if doesn't exist)
-   - Update corresponding sections based on Architecture Impact descriptions
-   - Update Container/Component tables
-   - Update dependency relationships
-   - Update layering constraints (if changed)
-4. **Record Merge Log**: Append change record at end of c4.md
-
-**Merge Output Format** (appended to c4.md):
-
-```markdown
-## Change History
-
-| Date | Change ID | Impact Summary |
-|------|-----------|----------------|
-| <date> | <change-id> | <brief description of architecture changes> |
-```
-
-### 3. Deduplication and Cleanup
-
-Execute in maintenance mode:
-
-- Detect duplicate spec definitions
-- Clean up obsolete/deprecated specs
-- Organize directory structure
-- Fix consistency issues
-
-## Execution Method
-
-1) First read and follow: `_shared/references/universal-gating-protocol.md` (verifiability + structural quality gates).
-2) Strictly execute the complete prompt: `references/spec-gardener-prompt.md`.
-
----
-
-## Context Awareness
-
-This Skill automatically detects context before execution and selects the appropriate maintenance mode.
-
-Detection rules reference: `skills/_shared/context-detection-template.md`
-
-### Detection Flow
-
-1. Detect `<truth-root>/` directory status
-2. If change-id is provided, detect change package archive conditions
-3. Detect duplicate/obsolete specs
-
-### Modes Supported by This Skill
-
-| Mode | Trigger Condition | Behavior |
-|------|-------------------|----------|
-| **Archive Mode** | change-id provided and gates pass | **Auto backport** → Merge to truth-root → Set Status=Archived |
-| **Maintenance Mode** | No change-id | Execute deduplication, cleanup, organization operations |
-| **Check Mode** | With --dry-run parameter | Output suggestions only, no actual modifications |
-
-### Archive Mode Complete Flow
-
-```
-1. Pre-checks:
-   - [ ] Change package exists
-   - [ ] verification.md Status = Ready or Done
-   - [ ] evidence/green-final/ exists
-   - [ ] tasks.md all [x]
-
-2. Auto backport (if needed):
-   - [ ] Detect deviation-log.md
-   - [ ] Backport to design.md
-   - [ ] Update deviation-log.md marks
-
-3. Merge to truth:
-   - [ ] Merge specs/**
-   - [ ] Merge contracts/**
-   - [ ] Merge Architecture Impact to c4.md
-
-4. Archive:
-   - [ ] Set verification.md Status = Archived
-   - [ ] Output archive report
-```
-
-### Detection Output Example
-
-```
-Detection Results:
-- truth-root: Exists, contains 12 spec files
-- Change package: Exists, all gates green
-- Running mode: Archive mode
-```
-
----
-
-## MCP Enhancement
-
-This Skill does not depend on MCP services; no runtime detection required.
-
-MCP enhancement rules reference: `skills/_shared/mcp-enhancement-template.md`
-