@entelligentsia/forgecli 0.20.3 → 1.0.2

package/dist/forge-payload/commands/health.md

@@ -43,9 +43,9 @@ node "$FORGE_ROOT/tools/banners.cjs" --subtitle "Reading the project's pulse —
 
 `banners.cjs` strips ANSI in `NO_COLOR` / non-tty / `--plain` contexts.
 
-Parse `$ARGUMENTS` for a `--path <dir>` argument:
-- If present, `PROJECT_ROOT = <dir>` (absolute or relative to the current working directory — resolve to absolute).
-- If absent, `PROJECT_ROOT = .` (current working directory).
+Parse `$ARGUMENTS` for:
+- `--path <dir>` → `PROJECT_ROOT = <dir>` (absolute or relative to the current working directory — resolve to absolute). If absent, `PROJECT_ROOT = .` (current working directory).
+- `--fix` → `FIX_MODE=true`. When present, run the Fix Phase (drift detection and patch application) after the standard diagnostics. Prompts for confirmation before applying any changes.
 
 All file paths below are relative to `PROJECT_ROOT`. All shell tool invocations must be run from `PROJECT_ROOT`:
 ```sh
@@ -70,7 +70,7 @@ cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/..."
      Do **not** cascade into subsequent checks that may fail on incomplete config.
 2. **KB freshness check** — Read `calibrationBaseline` from `$PROJECT_ROOT/.forge/config.json`.
    - If `calibrationBaseline` is absent, emit:
-     > △ No calibration baseline found — run `/forge:calibrate` to establish one.
+     > △ No calibration baseline found — run `/forge:health --fix` to establish one.
      Skip the freshness check and proceed to step 3.
    - If `calibrationBaseline` exists, compute the current hash of `MASTER_INDEX.md` using the same algorithm as `/forge:init`:
      ```sh
@@ -85,7 +85,7 @@ cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/..."
        If changes are only in technical sections: emit "technical". If only in business sections: emit "business". If in both: emit "technical + business".
        Emit:
        > △ KB drifted — <category> changes detected since last calibration (last calibrated: `calibrationBaseline.lastCalibrated`)
-       >   Run `/forge:calibrate` to re-align the knowledge base.
+       >   Run `/forge:health --fix` to re-align the knowledge base.
 3. Read the knowledge base files in `$PROJECT_ROOT/engineering/`
 4. Read the store in `$PROJECT_ROOT/.forge/store/` for sprint/task history
 5. Scan the codebase for entities not in the knowledge base (Grep for model/type definitions)
@@ -101,7 +101,7 @@ cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/..."
    If any modified or missing files are reported, include them in the health
    report under **Modified generated files** with the note:
    > These files were manually edited after generation. Regeneration will warn
-   > before overwriting them. Run `/forge:regenerate` to review and update.
+   > before overwriting them. Run `/forge:rebuild` to review and update.
    If all files are pristine (or the tool is absent), omit this section.
 8. Check generated file structure:
    ```sh
@@ -110,7 +110,7 @@ cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/..."
    If missing files are reported, include them in the health report under
    **Generated file structure** with note:
    > N expected file(s) are missing from generated output. Run `/forge:update` to
-   > regenerate missing files, or `/forge:regenerate <namespace>` for targeted repair.
+   > regenerate missing files, or `/forge:rebuild <namespace>` for targeted repair.
    If all files are present (exit 0), emit:
    > 〇 Generated file structure — all expected files present.
    If the tool is absent (file not found), skip this check silently.
@@ -134,15 +134,15 @@ cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/..."
     - If any concept doc is older than the newest schema change, emit a notice that it may be stale.
 12. Check persona pack freshness:
     - If `$PROJECT_ROOT/.forge/cache/persona-pack.json` does not exist, emit:
-      > △ Persona pack missing — run `/forge:regenerate` to build it.
+      > △ Persona pack missing — run `/forge:rebuild` to build it.
       (The pack is consumed by `meta-orchestrate` and `meta-fix-bug` when `FORGE_PROMPT_MODE=reference`.)
     - Otherwise read the pack's `source_hash`, then compute the current hash:
       ```sh
       CURRENT=$(node -e "const t=require('$FORGE_ROOT/tools/build-persona-pack.cjs'); console.log(t.computeSourceHash({personaDir:'$FORGE_ROOT/meta/personas', skillDir:'$FORGE_ROOT/meta/skills'}))")
-      STORED=$(node -e "console.log(require('$PROJECT_ROOT/.forge/cache/persona-pack.json').source_hash)")
+      STORED=$(node -e "try{console.log(require('$PROJECT_ROOT/.forge/cache/persona-pack.json').source_hash)}catch{console.log('MISSING')}")
       ```
       If `CURRENT != STORED`, emit:
-      > △ Persona pack stale — meta/ has changed since last build. Run `/forge:regenerate` to refresh.
+      > △ Persona pack stale — meta/ has changed since last build. Run `/forge:rebuild` to refresh.
       Otherwise emit:
       > 〇 Persona pack fresh.
 13. Check context pack freshness:
@@ -156,14 +156,14 @@ cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/..."
       ```
     - If `engineering/architecture/` does not exist, skip this check silently.
     - If `.forge/cache/context-pack.json` does not exist, emit:
-      > △ Context pack missing — run `/forge:regenerate` to build it.
+      > △ Context pack missing — run `/forge:rebuild` to build it.
       (The pack is injected by `meta-orchestrate` and `meta-fix-bug` to reduce per-phase architecture reads.)
     - Otherwise read `source_hash` from `.forge/cache/context-pack.json` and compare:
       ```sh
       STORED=$(node -e "console.log(require('$PROJECT_ROOT/.forge/cache/context-pack.json').source_hash)")
       ```
       If `CURRENT != STORED` (and `CURRENT != 'n/a'`), emit:
-      > △ Context pack stale — architecture docs have changed since last build. Run `/forge:regenerate` or `/forge:collate` to rebuild.
+      > △ Context pack stale — architecture docs have changed since last build. Run `/forge:rebuild` to rebuild.
       Otherwise emit:
       > 〇 Context pack fresh.
 14. Check plugin integrity:
@@ -188,9 +188,150 @@ cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/..."
     If `--path` was used, open the report with: `Health report for: $PROJECT_ROOT`
 16. Close the report with: `If you've found a bug in Forge itself, run /forge:report-bug`
 
+## Health Summary
+
+After step 16, emit a pass/fail summary grid. One row per check category; substitute actual check result for status. Omit rows for checks that were skipped (not applicable to the project).
+
+| Check                          | Status |
+|--------------------------------|--------|
+| Config completeness            |   〇   |
+| KB freshness                   |   △   |
+| Store integrity                |   〇   |
+| Modified generated files       |   〇   |
+| Generated file structure       |   〇   |
+| Plugin integrity               |   〇   |
+| Persona pack freshness         |   △   |
+| Context pack freshness         |   〇   |
+| Skill gaps                     |   〇   |
+| Feature test coverage          |   〇   |
+| Stale docs / orphaned entities |   〇   |
+| Writeback backlog              |   〇   |
+| Concepts freshness             |   〇   |
+
+(Replace each status symbol with the actual result observed: 〇 = pass, △ = warning, × = failure.)
+
+## Recommended Actions
+
+After the summary grid, emit a "Recommended Actions" section only if one or more checks have a non-passing result (△ or ×). Each finding maps to exactly one command. Use v1.0 command names only.
+
+| Finding                        | Recommended Command                                          |
+|--------------------------------|--------------------------------------------------------------|
+| No calibration baseline        | `/forge:health --fix`                                        |
+| KB drifted                     | `/forge:health --fix`                                        |
+| Store integrity errors         | `/forge:repair`                                        |
+| Modified generated files       | `/forge:rebuild`                                             |
+| Missing generated files        | `/forge:update`                                              |
+| Plugin integrity modified      | `/forge:update`                                              |
+| Persona pack missing / stale   | `/forge:rebuild`                                             |
+| Context pack missing / stale   | `/forge:rebuild`                                             |
+| Skill gaps                     | `/plugin install <name>`                                     |
+| Features with zero tests       | *(no command — note: add tests for the listed FEAT-NNN IDs)* |
+| Stale docs                     | `/forge:rebuild`                                             |
+| Stale concepts                 | `/forge:rebuild knowledge-base`                              |
+| Config incomplete              | `/forge:init`                                                |
+
+Only emit rows for non-passing findings actually observed. If all checks pass, omit this section entirely.
+
+## Fix Phase
+
+When `FIX_MODE=true` (i.e. `--fix` was passed), run the following Fix Phase after the standard diagnostics and summary grid. The Fix Phase detects KB drift and applies surgical regeneration patches with user confirmation.
+
+**Step 1 — Structural-element readiness check:**
+Verify that the required structural elements for calibration exist:
+- `engineering/MASTER_INDEX.md`
+- `.forge/config.json` with `calibrationBaseline` section (or ready to create it)
+- `$FORGE_ROOT` accessible
+
+If any required element is missing, emit an error and stop the Fix Phase:
+> × Fix Phase aborted — required structural elements missing. Run `/forge:init` to set up the project first.
+
+**Step 2 — Establish or verify calibration baseline:**
+Read `calibrationBaseline` from `.forge/config.json`.
+- If absent, compute the current `MASTER_INDEX.md` hash (same algorithm as the KB freshness check in step 2 of diagnostics) and write it as the baseline. Emit:
+  > ✓ Calibration baseline established.
+- If present and hash matches current, emit:
+  > 〇 Calibration baseline is current — no drift detected.
+  Skip to Step 9.
+- If present and hash differs, proceed to Step 3.
+
+**Step 3 — Detect drift:**
+Compute the diff between the current `MASTER_INDEX.md` content and the version reflected by `calibrationBaseline.masterIndexHash`. Identify which sections have changed.
+
+**Step 4 — Categorize drift:**
+Categorize changed sections into four categories:
+- **Technical** — stack, routing, database, deployment, processes, architecture, schemas, conventions, stack-checklist
+- **Business** — entity-model, domain, features, acceptance criteria, business-domain
+- **Retrospective** — sprint retrospectives, lessons learned
+- **Acceptance criteria** — AC definitions, task prompts
+
+**Step 5 — Propose patches:**
+Print a **Calibration Drift Report**:
+```
+── Calibration Drift Report ──────────────────────────────
+Drift category:  <Technical | Business | Retrospective | Acceptance criteria | (combination)>
+Sections changed: <list>
+
+Proposed patches:
+  1. Regenerate <target> — <reason>
+  2. ...
+
+Skipped (no change detected):
+  - <targets with no relevant drift>
+──────────────────────────────────────────────────────────
+```
+
+Offer the enhancement agent opt-in:
+> Would you like to run the enhancement agent on the regenerated targets? It detects skill gaps and proposes improvements based on the new content. (Optional — recommended for large drift sets.)
+> [Y] Yes, run enhancement agent after patching  [n] Skip
+
+**Step 6 — Confirmation gate:**
+Prompt the user before applying any changes:
+```
+Apply patches? [Y] Apply all  [r] Review individually  [n] Skip
+```
+- `Y` → apply all proposed patches
+- `r` → walk through each patch individually, prompting `[Y/n]` per patch
+- `n` → skip all patches and exit the Fix Phase without modifying any files
+
+**Step 7 — Execute approved patches:**
+For each approved patch, run:
+```sh
+/forge:rebuild <target>
+```
+where `<target>` is the regeneration target identified in Step 5 (e.g. `knowledge-base`, `workflows`, `personas`).
+
+Report each patch as it is applied:
+> ✓ Rebuilt <target>
+
+**Step 8 — Update calibration state:**
+After all patches are applied, update `.forge/config.json`:
+- Recompute the current `MASTER_INDEX.md` hash
+- Write the new hash to `calibrationBaseline.masterIndexHash`
+- Update `calibrationBaseline.lastCalibrated` to today's date (ISO 8601, date only)
+- Update `calibrationBaseline.version` to the current Forge plugin version (from `plugin.json`)
+- Append a new entry to `calibrationHistory` with: `{ "date": "<today>", "drift": "<category>", "patchesApplied": <N> }`
+
+```sh
+# Use manage-config.cjs for atomic field writes:
+cd "$PROJECT_ROOT" && node "$FORGE_ROOT/tools/manage-config.cjs" set calibrationBaseline.masterIndexHash "<new-hash>"
+node "$FORGE_ROOT/tools/manage-config.cjs" set calibrationBaseline.lastCalibrated "<today>"
+```
+
+**Step 9 — Summary:**
+Print the Calibration Complete block:
+```
+── Calibration Complete ──────────────────────────────────
+Patches applied:  <N>
+Drift resolved:   <category>
+Baseline updated: <today>
+─────────────────────────────────────────────────────────
+```
+Close with:
+> ── Run `/forge:health` to verify knowledge base currency.
+
 ## Output
 
-A health report to stdout — no files modified.
+A health report to stdout — no files modified, unless `--fix` is passed and patches are approved.
 
 After the report's findings, close with a single status line that
 reflects the overall verdict (synthesized from check 12's findings):
@@ -217,6 +358,7 @@ $ARGUMENTS
 | Argument | Purpose |
 |----------|---------|
 | `--path <dir>` | Run health check against a different project directory instead of the current working directory. Accepts an absolute path or a path relative to the current directory. |
+| `--fix` | Run KB drift detection and patch application after diagnostics. Prompts for confirmation before applying any changes. |
 
 ## On error
 

package/dist/forge-payload/commands/init.md

@@ -1,6 +1,6 @@
 ---
 name: init
-description: Use when the current project has no Forge SDLC instance and you need to bootstrap one from scratch
+description: Use when the current project has no Forge SDLC instance and you need to bootstrap one from scratch. Use --migrate to migrate an existing store to Forge format (replaces the removed /forge:migrate command).
 ---
 
 # /forge:init
@@ -82,21 +82,31 @@ just emit the phase banner for the resume target phase.
 
 ### Flag handling
 
-**Conflict check first:** if `$ARGUMENTS` contains BOTH `--fast` AND `--full`, halt
-immediately with:
-```
-× Conflicting flags: --fast and --full cannot be combined.
-```
-Do not write `.forge/init-progress.json`. Do not proceed.
+`--fast` and `--full` are accepted as no-ops for backwards compatibility with
+scripts and CI pipelines. Both flags proceed with the standard 4-phase base-pack
+init. The fast/full distinction was removed in v0.40.0.
+
+**`--migrate` flag:** When `$ARGUMENTS` contains `--migrate`, run the store migration
+workflow instead of the standard init. This is the v1.0 replacement for the removed
+`/forge:migrate` command.
 
-**Single flag present (`--fast` or `--full`):** accept with a one-line acknowledgement
-and continue to **Pre-flight Plan** — both flags run the identical new 4-phase flow:
+1. Check that `.forge/config.json` exists. If it does not, stop and tell the user:
+   > "Forge has not been initialised in this project. Run `/forge:init` first, then come back to `/forge:init --migrate`."
 
-- `--fast` present → emit `〇 --fast accepted — running 4-phase base-pack init (fast and full are now equivalent)`
-- `--full` present → emit `〇 --full accepted — running 4-phase base-pack init`
+2. Check for `--structural` sub-flag in `$ARGUMENTS`:
+   - If present, load and run the structural migration workflow:
+     Read `"$FORGE_ROOT/meta/workflows/meta-migrate.md"` and follow it.
+   - If absent, run the standard store schema migration (Steps 1–7 of the former `migrate.md`):
+     Read `"$FORGE_ROOT/meta/workflows/meta-migrate.md"` and follow it, passing
+     `--store-schema` so it runs the schema migration path (Steps 2–7).
 
-**No flags:** proceed directly to **Pre-flight Plan**. There is no interactive mode
-prompt — the 4-phase flow is the only flow.
+3. If `--dry-run` is also present, pass it through so the migration runs Steps 1–4
+   only (no writes).
+
+4. Do NOT proceed to the Pre-flight Plan when `--migrate` is present.
+
+**Proceed directly to Pre-flight Plan** for all other invocations. There is no interactive mode prompt —
+the 4-phase flow is the only flow.
 
 ### Pre-flight Plan
 
@@ -123,9 +133,8 @@ Start from Phase 1? [Y] or specify phase (1–4): ___
 If the user specifies a valid phase (1–4), jump there directly.
 Any other input (including 0, 5+, or non-numeric text) re-prompts with the same table.
 
-If a `$ARGUMENTS` phase number was combined with a flag (e.g. `--fast 3`),
-skip both the flag acknowledgement and the pre-flight table and go straight
-to the specified phase.
+If a `$ARGUMENTS` phase number is provided (e.g. `3`), skip the pre-flight
+table and go straight to the specified phase.
 
 Read `$FORGE_ROOT/init/sdlc-init.md` — that document is your complete orchestration.
 Follow it exactly. It defines 4 phases:
@@ -143,21 +152,6 @@ in the project.
 
 $ARGUMENTS
 
-### Mode flags (backwards compatibility)
-
-`--fast` and `--full` are accepted for scripted and CI use. Both flags select the
-new 4-phase base-pack init — the distinction between fast and full mode is
-obsolete because base-pack template substitution is instant and always produces
-fully functional (non-stub) workflows.
-
-#### Conflicting flags
-
-`--fast` and `--full` together halt the run before any write:
-
-```
-× Conflicting flags: --fast and --full cannot be combined.
-```
-
 ## On error
 
 If any step above fails unexpectedly, describe what went wrong and ask:

package/dist/forge-payload/commands/migrate.md

@@ -1,160 +1,12 @@
 ---
 name: migrate
-description: Use after forge:init to migrate a pre-existing AI-SDLC store to Forge format — interviews you to define the project-specific mapping
+description: REMOVED in v1.0 — use /forge:init --migrate instead
 ---
 
-# /forge:migrate
+# /forge:migrate — Removed
 
-Migrate an existing project store to Forge format. Requires `forge:init` to have been completed first.
+× `/forge:migrate` was removed in v1.0. Store migration is now a flag on `/forge:init`:
 
-## Locate the Forge plugin
-
-```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
-```
-
-## Step 0 — Detect migration type
-
-Check whether a structural migration (v0.x prose-heavy → v0.40 base-pack
-format) is needed:
-
-- If the user passed `--structural` explicitly, OR
-- If `.forge/structure-versions.json` is absent (pre-T05 install detected):
-
-  → Load and run the structural migration workflow:
-    Read `"$FORGE_ROOT/meta/workflows/meta-migrate.md"` and follow it.
-  → Do NOT proceed to Step 1 of this command.
-
-If neither condition applies (post-T05 install and no `--structural` flag):
-continue to Step 1 (store schema migration).
-
-## Step 1 — Verify forge:init has run
-
-Check that `.forge/config.json` exists. If it does not, stop and tell the user:
-
-> "Forge has not been initialised in this project. Run `/forge:init` first, then come back to `/forge:migrate`."
-
-Read `.forge/config.json` to get `paths.store` (default: `.forge/store`).
-
-## Step 2 — Scan for non-Forge values
-
-Read every JSON file under `{paths.store}/sprints/`, `{paths.store}/tasks/`, and `{paths.store}/bugs/`.
-
-Collect the distinct values present in each `status` field and `severity` field (bugs only), grouped by record type. Cross-reference against the known Forge enums:
-
-**Sprint status:** `planning`, `active`, `completed`, `retrospective-done`, `blocked`, `partially-completed`, `abandoned`
-
-**Task status:** `draft`, `planned`, `plan-approved`, `implementing`, `implemented`, `review-approved`, `approved`, `committed`, `plan-revision-required`, `code-revision-required`, `blocked`, `escalated`, `abandoned`
-
-**Bug status:** `reported`, `triaged`, `in-progress`, `fixed`, `verified`
-
-**Bug severity:** `critical`, `major`, `minor`
-
-Report only the values that are **not** already valid Forge enums. If all values are already valid, tell the user:
-
-> "Store is already fully Forge-compatible — no migration needed. Run `node \"$FORGE_ROOT/tools/validate-store.cjs\"` to confirm."
-
-Then exit.
-
-## Step 3 — Interview the user
-
-Present the unrecognised values grouped by record type. For each value, ask the user to choose the Forge equivalent (or mark it as custom/skip):
-
-```
-Found values not in Forge format. Please map each one:
-
-Sprint status:
-  "✅ Complete"    → ? (Forge options: planning / active / completed / retrospective-done / blocked / partially-completed / abandoned)
-  "🔵 In Progress" → ?
-
-Task status:
-  "✅ Complete"    → ?
-  "📋 Prompt Ready" → ?
-  ...
-
-Bug severity:
-  "Major" → ? (Forge options: critical / major / minor)
-
-For each value above, enter the Forge equivalent. Type "skip" to leave that value unchanged (it will remain invalid and fail validate-store).
-```
-
-Wait for the user to provide the full mapping before proceeding.
-
-## Step 4 — Preview changes
-
-Count how many records will be affected per type. Show a preview table:
-
-```
-Migration preview:
-
-  Sprints:  N records — M values will change
-  Tasks:    N records — M values will change
-  Bugs:     N records — M values will change
-
-  Example changes:
-    sprints/S01.json  status: "✅ Complete"    → "completed"
-    tasks/WI-T001.json status: "✅ Complete"   → "committed"
-    bugs/WI-BUG-01.json severity: "Major"     → "major"
-
-Apply? [Y/n]
-```
-
-If the user declines, exit without changes.
-
-## Step 5 — Apply migration
-
-For each affected record, apply the migration via the store custodian:
-
-```sh
-export FORGE_ROOT
-node "$FORGE_ROOT/tools/store-cli.cjs" write <entity> '{updated-json}'
-```
-
-where `<entity>` is `sprint`, `task`, or `bug` as appropriate, and
-`'{updated-json}'` is the full record with the mapped field values applied.
-Construct the JSON by reading the current record (using the Read tool or
-`/forge:store read <entity> <id>`), applying only the agreed mapping, and
-passing the complete updated record to the custodian.
-
-**Error handling:** If the custodian exits with code 1, read stderr for the
-validation error, fix the data, and retry (max 2 retries). If the command still
-fails after retries, report the validation error to the user and stop. **Never
-fall back to writing store files directly.**
-
-Do not modify any field that was not part of the agreed mapping. Do not add or remove fields.
-
-## Step 6 — Verify
-
-Run:
-
-```sh
-export FORGE_ROOT
-node "$FORGE_ROOT/tools/validate-store.cjs" --dry-run
-```
-
-Report the result. If errors remain (e.g. values the user chose to skip), list them clearly so the user knows what still needs attention.
-
-## Step 7 — Close
-
-Report a summary:
-
-```
-Migration complete:
-  N sprint(s) updated
-  N task(s) updated
-  N bug(s) updated
-
-Run /forge:health to check overall knowledge base status.
-```
-
-## Arguments
-
-$ARGUMENTS
-
-If the user passes `--dry-run`, run Steps 1–4 only (no writes).
-
-## On error
-
-If any step above fails unexpectedly, describe what went wrong and ask:
-
-> "This looks like a Forge bug. Would you like to file a report to help improve it? Run `/forge:report-bug` — I'll pre-fill the report from this conversation."
+- `/forge:init --migrate` — interviews you to map existing store values to Forge format (equivalent to the old `forge:migrate`)
+- `/forge:init --migrate --structural` — runs structural migration for pre-v0.40 stores
+- `/forge:init --migrate --dry-run` — preview changes without applying them

package/dist/forge-payload/commands/quiz-agent.md

@@ -1,38 +1,6 @@
 ---
 name: quiz-agent
-description: Verify an agent has loaded and understood the project knowledge base — run a short factual quiz before starting high-stakes tasks
+description: Renamed in v1.0 — use /forge:check-agent
 ---
 
-# /forge:quiz-agent
-
-Verify that the active agent has correctly read and understood this project's
-knowledge base before beginning a high-stakes task (schema changes, migrations,
-release engineering, significant refactors).
-
-## Locate plugin root
-
-```
-FORGE_ROOT: !`echo "${CLAUDE_PLUGIN_ROOT}"`
-```
-
-## Arguments
-
-$ARGUMENTS
-
-## How to Run
-
-Read `.forge/workflows/quiz_agent.md` and follow it exactly.
-
-Pass `$ARGUMENTS` to the workflow so the agent can include task context in its
-responses if provided.
-
-## On error
-
-If `.forge/workflows/quiz_agent.md` does not exist, tell the user:
-
-> △ The quiz_agent workflow is missing. Run `/forge:regenerate workflows` to
-> regenerate it, then retry.
-
-If any other step fails unexpectedly, describe what went wrong and ask:
-
-> "This looks like a Forge bug. Would you like to file a report to help improve it? Run `/forge:report-bug` — I'll pre-fill the report from this conversation."
+× /forge:quiz-agent was renamed to /forge:check-agent in v1.0.