@open-agent-toolkit/cli 0.0.65 → 0.0.68

package/assets/public-package-versions.json

@@ -1,6 +1,6 @@
 {
-  "cli": "0.0.65",
-  "docs-config": "0.0.65",
-  "docs-theme": "0.0.65",
-  "docs-transforms": "0.0.65"
+  "cli": "0.0.68",
+  "docs-config": "0.0.68",
+  "docs-theme": "0.0.68",
+  "docs-transforms": "0.0.68"
 }

package/assets/skills/oat-project-complete/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-complete
-version: 1.4.5
+version: 1.4.7
 description: Use when all implementation work is finished and the project is ready to close. Marks the OAT project lifecycle as complete.
 disable-model-invocation: true
 user-invocable: true
@@ -27,7 +27,7 @@ When executing this skill, provide lightweight progress feedback so the user can
   - `[3/6] Completing lifecycle…`
   - `[4/6] Generating PR description + archiving…`
   - `[5/6] Refreshing dashboard + committing…`
-  - `[6/6] Opening PR…`
+  - `[6/6] Opening PR or syncing description…`
 
 ## Process
 
@@ -64,6 +64,17 @@ Ask all user questions at once so the user can answer them in a single interacti
 
 Before asking the batched questions, read `oat_pr_status` and `oat_pr_url` from `state.md` frontmatter.
 
+**Capture pre-mutation PR state for later steps.** The skill mutates `state.md` (Step 5) and the project tree (Step 8) before Step 11.5 needs to know whether the PR was already open at the start. Persist that decision in a shell variable now:
+
+```bash
+WAS_PR_OPEN_AT_START="false"
+if [[ "${oat_pr_status:-}" == "open" ]]; then
+  WAS_PR_OPEN_AT_START="true"
+fi
+```
+
+Use the same `state.md` read you already perform for `oat_pr_status`/`oat_pr_url` — do not re-read after Step 5. Step 11.5 (Sync Open-PR Description on GitHub) consumes this value.
+
 **Workflow preference checks (before asking questions):**
 
 Some questions can be answered automatically from workflow preferences. Read each preference before deciding whether to include its question in the batched prompt:
@@ -299,7 +310,29 @@ fi
 
 5. **Write PR description artifact** — write to `{PROJECT_PATH}/pr/project-pr-YYYY-MM-DD.md` following the template and policies from `oat-project-pr-final` Step 4 (frontmatter policy, reference links policy, local path exclusion).
 
-If a PR description artifact already exists at `{PROJECT_PATH}/pr/project-pr-*.md`, skip generation and use the existing one instead.
+If a PR description artifact already exists at `{PROJECT_PATH}/pr/project-pr-*.md`:
+
+- When `SHOULD_ARCHIVE` is `true`, regenerate it (overwrite). The existing artifact was authored by `oat-project-pr-final` before any archive intent existed and links to artifact paths that will be local-only after Step 8. Regenerating ensures Step 11 / Step 11.5 push a body whose links still resolve on the remote.
+- When `SHOULD_ARCHIVE` is `false`, skip generation and use the existing artifact as-is. No archive means the existing blob links remain valid.
+
+**Archive-aware References (required when `SHOULD_ARCHIVE` is `true`):**
+
+When archiving, the project artifacts at `{PROJECT_PATH}/{plan,implementation,discovery,spec,design,summary}.md` will move to a gitignored archive location in Step 8. After commit + push (Step 10), those paths no longer exist on the branch and any blob link to them returns 404 on GitHub. The PR description must anticipate this:
+
+- **Drop References bullets** that point to artifacts about to become local-only:
+  - `plan.md`, `implementation.md`, `discovery.md`, `spec.md`, `design.md`, `summary.md`, `references/imported-plan.md`
+  - Active `reviews/` (the active project tree, including `reviews/`, moves with the archive)
+- **Add a canonical project-record bullet** when `archive.summaryExportPath` is configured and `summary.md` exists:
+  - Resolve the export filename: `${SUMMARY_EXPORT_PATH}/$(date +%Y%m%d)-${PROJECT_NAME}.md` (matches `archive-utils.ts` naming).
+  - Reference it as a tracked, post-archive blob link, e.g.:
+    `- Project record: [${SUMMARY_EXPORT_PATH}/${YYYYMMDD}-${PROJECT_NAME}.md]({REPO_WEB}/blob/{BRANCH}/${SUMMARY_EXPORT_PATH}/${YYYYMMDD}-${PROJECT_NAME}.md)`
+  - Use the **current/head branch** for the blob link (the same `{BRANCH}` value used by `oat-project-pr-final` Step 4 for every other reference). Step 8 creates the export on the current checkout and Step 10 commits + pushes it on the feature branch, so the link resolves immediately while the PR is open and continues to resolve after merge once the file lands on the base branch.
+  - Anti-pattern: do **not** point this link at the base branch (`main` / resolved default branch). The export does not exist on the base branch until the PR merges, so a `blob/main/...` link 404s for the entire window the PR is open — the same class of broken link this whole step exists to prevent.
+  - When `archive.summaryExportPath` is unset or `summary.md` is missing, omit this bullet rather than emit a broken link.
+- **Keep References bullets** that resolve independently of the archive: backlog item links under `.oat/repo/reference/backlog/`, decision-record links under `.oat/repo/reference/decisions/`, repo-reference docs, ticket URLs, and anything else under tracked paths outside the project directory.
+- Apply the existing `localPaths`-based exclusion rule from `oat-project-pr-final` Step 4 on top of these rules — it already covers `.oat/**/pr` and `.oat/**/reviews/archived` and may catch additional patterns configured per repo.
+
+Anti-pattern: do not "rescue" a dropped artifact by linking to its archived path under `.oat/projects/archived/<name>/...`. That path is gitignored on every checkout and never reaches the remote.
 
 ### Step 8: Archive Project (Conditional)
 
@@ -528,6 +561,46 @@ gh pr create --base main --title "{title}" --body-file "$TMP_BODY"
 
 Do not assume `gh` is installed; if missing, instruct manual PR creation using the file contents.
 
+### Step 11.5: Sync Open-PR Description on GitHub (Conditional)
+
+**Run only when `WAS_PR_OPEN_AT_START="true"` AND `SHOULD_ARCHIVE="true"`.**
+
+When the PR was already open at the start of this skill (typically because `oat-project-pr-final` ran earlier in the lifecycle) AND we just archived, the GitHub PR description authored by `oat-project-pr-final` still points to the active artifact paths. Step 8 moved those artifacts to a gitignored archive location and Step 10 pushed the move, so any blob link in the open PR body now 404s. Push the regenerated archive-aware body to the existing PR.
+
+Skip this step when:
+
+- The PR was not yet open at the start (`WAS_PR_OPEN_AT_START="false"`) — Step 11 already created the PR with the archive-aware body.
+- No archive happened (`SHOULD_ARCHIVE="false"`) — the original blob links still resolve.
+- `IS_SHARED_PROJECT="false"` — non-shared projects are not archived in this skill, so no link breakage.
+
+Steps:
+
+1. Locate the PR description artifact at `{PROJECT_PATH}/pr/project-pr-*.md`. After Step 8, `PROJECT_PATH` points at the archived location, so the artifact lives at `{ARCHIVE_PATH}/pr/project-pr-*.md`.
+2. Strip YAML frontmatter (everything from the opening `---` through and including the closing `---`) and write the result to a temporary file. Verify the temp file does not start with YAML frontmatter keys.
+3. Resolve the open PR. Prefer the tracked URL captured in Step 2:
+
+   ```bash
+   PR_REF="${oat_pr_url:-}"
+   if [[ -z "$PR_REF" ]]; then
+     # Fall back to the head branch — gh auto-resolves to the open PR for the current branch.
+     PR_REF=$(git rev-parse --abbrev-ref HEAD)
+   fi
+   ```
+
+4. Push the updated body:
+
+   ```bash
+   gh pr edit "$PR_REF" --body-file "$TMP_BODY"
+   ```
+
+5. Clean up the temp file.
+
+Failure handling:
+
+- If `gh` is missing, warn and print the path to the regenerated artifact body so the user can paste it into the PR manually. Do not fail the skill.
+- If `gh pr edit` fails (e.g. PR was merged between Step 2 and now, or the auth token lacks edit permission), warn and continue. Step 12's completion summary should call out that the PR body was not updated and surface the artifact path so the user can update it manually.
+- Never re-archive or re-commit on failure here — the lifecycle bookkeeping in Step 10 already shipped.
+
 ### Step 12: Confirm to User
 
 Show user:
@@ -538,3 +611,4 @@ Show user:
 - Include commit hash and push result for the bookkeeping changes.
 - If PR was opened: include the PR URL.
 - If `oat_pr_url` is present, show it in the completion summary even when PR creation was skipped because the project already tracked an open PR.
+- If Step 11.5 ran, report whether the PR description was synced (e.g. `PR description synced: <PR URL>`) or warn that the sync failed and surface the artifact path so the user can update it manually.

package/assets/skills/oat-project-implement/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-implement
-version: 2.0.6
+version: 2.0.7
 description: Use when plan.md is ready for execution. Dispatches phase-level subagents with bounded fix loops; supports plan-declared parallel phase groups with worktree-isolated execution and ordered fan-in.
 argument-hint: '[--retry-limit <N>] [--dry-run]'
 disable-model-invocation: true
@@ -23,7 +23,7 @@ Execute the implementation plan task-by-task with full state tracking.
 **Purpose:** Execute plan tasks with TDD discipline, track progress, handle blockers.
 
 **CRITICAL — Bookkeeping commits are mandatory, not optional.**
-After every code commit and after every phase/review-fix completion, you MUST commit the OAT tracking files (`implementation.md`, `state.md`, `plan.md`) as a separate bookkeeping commit. Do not defer, batch, or skip these commits under the reasoning that they "aren't related to the implementation." Skipping a bookkeeping commit is the primary cause of cross-session state drift and will cause the next implementation run to fail bookkeeping cross-checks. If bookkeeping commits feel frequent, that is the intended design — they are cheap and they prevent drift.
+After every code commit and after every phase/review-fix completion, you MUST commit the OAT tracking files (project: `implementation.md`, `state.md`, `plan.md`; repo dashboard: `.oat/state.md`) as a separate bookkeeping commit. Refresh the repo dashboard with `oat state refresh` immediately before staging so `.oat/state.md` reflects the just-completed phase/task. Do not defer, batch, or skip these commits under the reasoning that they "aren't related to the implementation." Skipping a bookkeeping commit (or skipping the dashboard refresh) is the primary cause of cross-session state drift and will cause the next implementation run to fail bookkeeping cross-checks. If bookkeeping commits feel frequent, that is the intended design — they are cheap and they prevent drift.
 
 **CRITICAL — Review boundaries require a committed artifact baseline.**
 Do not enter checkpoint review, final review, revise, or PR-final handoff with dirty core project artifacts (`discovery.md`, `spec.md`, `design.md`, `plan.md`, `implementation.md`, `state.md`, plus `.oat/state.md` when refreshed). If one of those boundaries is next and artifact bookkeeping is still uncommitted, stop and create the bookkeeping commit first.
@@ -646,7 +646,8 @@ For each phase that completed:
 **Bookkeeping commit (mandatory):**
 
 ```bash
-git add {PROJECT_PATH}/implementation.md {PROJECT_PATH}/state.md {PROJECT_PATH}/plan.md
+oat state refresh
+git add {PROJECT_PATH}/implementation.md {PROJECT_PATH}/state.md {PROJECT_PATH}/plan.md .oat/state.md
 git commit -m "chore(oat): bookkeeping after {pNN} {pass|fail}"
 ```
 
@@ -719,14 +720,15 @@ When pausing:
 
 **DO NOT SKIP.** This commit prevents state drift across sessions.
 
-After phase summary and task pointer advancement, commit all modified OAT tracking files:
+After phase summary and task pointer advancement, refresh the repo dashboard and commit all modified OAT tracking files:
 
 ```bash
-git add "$PROJECT_PATH/implementation.md" "$PROJECT_PATH/state.md" "$PROJECT_PATH/plan.md"
+oat state refresh
+git add "$PROJECT_PATH/implementation.md" "$PROJECT_PATH/state.md" "$PROJECT_PATH/plan.md" .oat/state.md
 git diff --cached --quiet || git commit -m "chore(oat): update tracking artifacts for {phase} completion"
 ```
 
-Do not use `git add -A` or glob patterns. Only commit the three OAT project files listed above.
+Do not use `git add -A` or glob patterns. Only commit the four files listed above (three project artifacts plus the regenerated repo dashboard).
 
 **Note on HiLL types:**
 
@@ -852,14 +854,15 @@ Implementation - Tasks complete; awaiting final review.
 
 **DO NOT SKIP.** This commit prevents state drift across sessions.
 
-After updating state.md to reflect implementation completion, commit all modified OAT tracking files:
+After updating state.md to reflect implementation completion, refresh the repo dashboard and commit all modified OAT tracking files:
 
 ```bash
-git add "$PROJECT_PATH/implementation.md" "$PROJECT_PATH/state.md" "$PROJECT_PATH/plan.md"
+oat state refresh
+git add "$PROJECT_PATH/implementation.md" "$PROJECT_PATH/state.md" "$PROJECT_PATH/plan.md" .oat/state.md
 git diff --cached --quiet || git commit -m "chore(oat): update tracking artifacts for implementation complete"
 ```
 
-Do not use `git add -A` or glob patterns. Only commit the three OAT project files listed above.
+Do not use `git add -A` or glob patterns. Only commit the four files listed above (three project artifacts plus the regenerated repo dashboard).
 
 ### Step 13: Final Verification
 

package/assets/skills/oat-project-next/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-next
-version: 1.0.3
+version: 1.0.4
 description: Use when continuing work on the active OAT project. Reads project state, determines the next lifecycle action, and invokes the appropriate skill automatically.
 disable-model-invocation: true
 user-invocable: true
@@ -178,10 +178,12 @@ Phase-to-skill mapping for HiLL override:
 | Phase     | Skill                  |
 | --------- | ---------------------- |
 | discovery | `oat-project-discover` |
-| spec      | `oat-project-spec`     |
+| spec      | `oat-project-design`   |
 | design    | `oat-project-design`   |
 | plan      | `oat-project-plan`     |
 
+Note: a `spec` HiLL phase only appears in legacy projects scaffolded before requirements confirmation was folded into `oat-project-design`. New projects scaffold with `['discovery', 'design']` HiLL checkpoints, so `spec` falls through to `oat-project-design` here as a graceful migration. The standalone `oat-project-spec` skill remains available as an opt-in for users who want to formalize requirements separately.
+
 Note: `implement` is intentionally omitted. Implementation-phase checkpoints are handled by `oat_plan_hill_phases` in plan.md (plan-phase-level gates), not by the workflow-level `oat_hill_checkpoints` in state.md.
 
 #### Step 3b: Phase Routing Tables
@@ -196,9 +198,9 @@ Otherwise, look up the target skill from the routing table for the current `oat_
 | Current Phase | Phase Status | Boundary Tier        | Target Skill               |
 | ------------- | ------------ | -------------------- | -------------------------- |
 | discovery     | in_progress  | tier 3 (template)    | `oat-project-discover`     |
-| discovery     | in_progress  | tier 2 (substantive) | `oat-project-spec`         |
-| discovery     | complete     | tier 1               | `oat-project-spec`         |
-| spec          | in_progress  | tier 3               | `oat-project-spec`         |
+| discovery     | in_progress  | tier 2 (substantive) | `oat-project-design`       |
+| discovery     | complete     | tier 1               | `oat-project-design`       |
+| spec          | in_progress  | tier 3               | `oat-project-design`       |
 | spec          | in_progress  | tier 2               | `oat-project-design`       |
 | spec          | complete     | tier 1               | `oat-project-design`       |
 | design        | in_progress  | tier 3               | `oat-project-design`       |

package/assets/skills/oat-project-progress/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: oat-project-progress
-version: 1.2.3
+version: 1.2.4
 description: Use when resuming work, checking status, or unsure which OAT skill to run next. Evaluates project progress and routes to the appropriate next step.
 disable-model-invocation: true
 user-invocable: true
@@ -186,7 +186,7 @@ Read `oat_workflow_mode` from `state.md` frontmatter:
 - In that case, do **not** advance to the next phase even if `oat_phase_status: complete`.
 - Recommend continuing the current phase skill to capture explicit approval:
   - discovery gate pending -> `oat-project-discover`
-  - spec gate pending -> `oat-project-spec`
+  - spec gate pending (legacy projects only — newly scaffolded projects no longer use a spec HiLL gate) -> `oat-project-design`
   - design gate pending -> `oat-project-design`
 
 **Drift detection (apply before routing `implement | in_progress`):**
@@ -226,8 +226,8 @@ Routing matrix by mode:
 | oat_phase | oat_phase_status | Next Skill                                                                                                                                                                                                           |
 | --------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | discovery | in_progress      | Continue `oat-project-discover`                                                                                                                                                                                      |
-| discovery | complete         | `oat-project-spec`                                                                                                                                                                                                   |
-| spec      | in_progress      | Continue `oat-project-spec`                                                                                                                                                                                          |
+| discovery | complete         | `oat-project-design` (folds requirements confirmation in; standalone `oat-project-spec` remains an opt-in alternative)                                                                                               |
+| spec      | in_progress      | `oat-project-design` (legacy phase — design reuses any existing `spec.md`)                                                                                                                                           |
 | spec      | complete         | `oat-project-design`                                                                                                                                                                                                 |
 | design    | in_progress      | Continue `oat-project-design`                                                                                                                                                                                        |
 | design    | complete         | `oat-project-plan`                                                                                                                                                                                                   |
@@ -282,8 +282,8 @@ Workflow:
   oat-project-import-plan       - Import an external markdown plan and normalize plan.md
   oat-project-promote-spec-driven - Promote quick/import project to spec-driven lifecycle
   oat-project-discover          - Start discovery phase (requirements gathering)
-  oat-project-spec              - Create specification from discovery
-  oat-project-design            - Create technical design from spec
+  oat-project-design            - Confirm requirements + create technical design (folds spec authoring inline)
+  oat-project-spec              - Optional standalone specification (most projects skip this — design handles it)
   oat-project-plan              - Create implementation plan from design (spec-driven mode)
   oat-project-implement         - Execute implementation plan (sequential or parallel)
   oat-project-reconcile         - Reconcile manual/human commits with plan tasks

package/dist/commands/project/new/scaffold.js

@@ -18,13 +18,13 @@ const TEMPLATES_BY_MODE = {
 };
 const STATE_TEMPLATE_BY_MODE = {
     'spec-driven': {
-        hillCheckpoints: "['discovery', 'spec', 'design']",
+        hillCheckpoints: "['discovery', 'design']",
         phase: 'discovery',
         status: 'Discovery',
         currentPhase: 'Discovery - Gathering requirements and understanding the problem space',
         artifacts: [
             '- **Discovery:** `discovery.md` (in_progress)',
-            '- **Spec:** `spec.md` (scaffolded template — not started)',
+            '- **Spec:** `spec.md` (scaffolded template — authored inline by `oat-project-design`)',
             '- **Design:** `design.md` (scaffolded template — not started)',
             '- **Plan:** `plan.md` (scaffolded template — not started)',
             '- **Implementation:** `implementation.md` (scaffolded template — not started)',
@@ -34,7 +34,7 @@ const STATE_TEMPLATE_BY_MODE = {
             '- ✓ Downstream lifecycle files scaffolded',
             '- ⧗ Awaiting user input',
         ],
-        nextMilestone: 'Complete discovery and move to specification phase',
+        nextMilestone: 'Complete discovery and move to design phase',
     },
     quick: {
         hillCheckpoints: '[]',

package/dist/commands/state/generate.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"generate.d.ts","sourceRoot":"","sources":["../../../src/commands/state/generate.ts"],"names":[],"mappings":"AASA,MAAM,WAAW,aAAa;IAC5B,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC;IACjC,aAAa,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,MAAM,CAAC;CAClD;AAED,MAAM,WAAW,oBAAoB;IACnC,QAAQ,EAAE,MAAM,CAAC;IACjB,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACxB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,GAAG,CAAC,EAAE,aAAa,CAAC;CACrB;AAED,MAAM,WAAW,mBAAmB;IAClC,aAAa,EAAE,MAAM,CAAC;IACtB,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,aAAa,EAAE,MAAM,CAAC;IACtB,eAAe,EAAE,MAAM,CAAC;IACxB,eAAe,EAAE,MAAM,CAAC;IACxB,iBAAiB,EAAE,MAAM,CAAC;CAC3B;AA4GD,wBAAgB,eAAe,CAAC,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,OAAO,CAEvE;AAqaD,wBAAsB,sBAAsB,CAC1C,OAAO,EAAE,oBAAoB,GAC5B,OAAO,CAAC,mBAAmB,CAAC,CA2C9B"}
+{"version":3,"file":"generate.d.ts","sourceRoot":"","sources":["../../../src/commands/state/generate.ts"],"names":[],"mappings":"AASA,MAAM,WAAW,aAAa;IAC5B,SAAS,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC;IACjC,aAAa,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,EAAE,MAAM,GAAG,MAAM,CAAC;CAClD;AAED,MAAM,WAAW,oBAAoB;IACnC,QAAQ,EAAE,MAAM,CAAC;IACjB,GAAG,CAAC,EAAE,MAAM,CAAC,UAAU,CAAC;IACxB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,GAAG,CAAC,EAAE,aAAa,CAAC;CACrB;AAED,MAAM,WAAW,mBAAmB;IAClC,aAAa,EAAE,MAAM,CAAC;IACtB,WAAW,EAAE,MAAM,GAAG,IAAI,CAAC;IAC3B,aAAa,EAAE,MAAM,CAAC;IACtB,eAAe,EAAE,MAAM,CAAC;IACxB,eAAe,EAAE,MAAM,CAAC;IACxB,iBAAiB,EAAE,MAAM,CAAC;CAC3B;AA4GD,wBAAgB,eAAe,CAAC,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,GAAG,OAAO,CAEvE;AA8aD,wBAAsB,sBAAsB,CAC1C,OAAO,EAAE,oBAAoB,GAC5B,OAAO,CAAC,mBAAmB,CAAC,CA2C9B"}

package/dist/commands/state/generate.js

@@ -207,9 +207,14 @@ function computeNextStep(project, hasProjects, state) {
     if (state.phaseStatus === 'complete' &&
         phaseInHillList(state.phase, state.hillCheckpoints) &&
         !phaseInHillList(state.phase, state.hillCompleted)) {
+        // Spec is no longer a discrete HiLL checkpoint in newly-scaffolded projects —
+        // requirements confirmation is folded into oat-project-design. Legacy
+        // projects whose state.md still lists `spec` in oat_hill_checkpoints route
+        // to oat-project-design here so they finish through the consolidated flow
+        // rather than being pushed back at the deprecated standalone skill.
         const phaseSkillMap = {
             discovery: 'oat-project-discover',
-            spec: 'oat-project-spec',
+            spec: 'oat-project-design',
             design: 'oat-project-design',
             plan: 'oat-project-plan',
             implement: 'oat-project-implement',
@@ -227,12 +232,14 @@ function computeNextStep(project, hasProjects, state) {
             reason: 'Continue discovery phase',
         },
         'spec-driven:discovery:complete': {
-            step: 'oat-project-spec',
-            reason: 'Create specification from discovery',
+            step: 'oat-project-design',
+            reason: 'Confirm requirements and produce design (spec is folded into design)',
         },
+        // Legacy projects whose phase still reads `spec` route to design — the
+        // consolidated oat-project-design skill handles existing spec.md gracefully.
         'spec-driven:spec:in_progress': {
-            step: 'oat-project-spec',
-            reason: 'Continue specification phase',
+            step: 'oat-project-design',
+            reason: 'Continue into design (spec is folded into design — legacy phase)',
         },
         'spec-driven:spec:complete': {
             step: 'oat-project-design',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@open-agent-toolkit/cli",
-  "version": "0.0.65",
+  "version": "0.0.68",
   "private": false,
   "description": "Open Agent Toolkit CLI",
   "homepage": "https://github.com/voxmedia/open-agent-toolkit/tree/main/packages/cli",
@@ -33,7 +33,7 @@
     "ora": "^9.0.0",
     "yaml": "2.8.2",
     "zod": "^3.25.76",
-    "@open-agent-toolkit/control-plane": "0.0.65"
+    "@open-agent-toolkit/control-plane": "0.0.68"
   },
   "devDependencies": {
     "@types/node": "^22.10.0",