@entelligentsia/forgecli 1.0.25 → 1.0.36

package/dist/forge-payload/init/generation/generate-template.md

@@ -0,0 +1,60 @@
+# Template Generation — Per-Subagent Instructions
+
+You are generating **ONE** template file. You have been given two inputs:
+
+1. A **project brief** (`.forge/init-context.md`) — authoritative for all names,
+   paths, command values, and entity names
+2. A **meta-template source** — the document structure and Generation Instructions
+
+Your job is to produce exactly one file and return a one-line status.
+
+---
+
+## Inputs
+
+Read these two sources before writing anything:
+
+- `$FORGE_ROOT/meta/templates/{meta}` — the meta-template for your assigned document
+- `.forge/init-context.md` — the project brief (passed inline in your prompt)
+
+---
+
+## Rules
+
+1. **Write EXACTLY ONE file:** `.forge/templates/{filename}.md`
+
+2. **Stack-specific sections** — add framework-specific subsections based on the
+   stack information in the brief. Use the detected languages and frameworks to
+   decide which optional sections to include.
+
+3. **Project substitution** — replace all `{Project}`, `{PREFIX}`, entity name
+   placeholders, and ID format examples with actual values from the brief.
+   All entity names and command values MUST come from the brief. Do not invent.
+
+4. **Test output formats** — reference the project's actual test runner output
+   format in any template sections that involve test results.
+
+5. **Follow Generation Instructions** — each meta-template has a
+   `## Generation Instructions` section. Follow it fully. Do not add sections
+   or notes beyond what it prescribes.
+
+---
+
+## Self-check (mandatory last step)
+
+After writing the file, verify before returning:
+
+1. Read back `.forge/templates/{filename}.md`
+2. Confirm **no unsubstituted placeholders** remain (no literal `{Project}`,
+   `{PREFIX}`, `{TEST_COMMAND}`, etc.)
+3. Record in the manifest:
+   ```sh
+   node "$FORGE_ROOT/tools/generation-manifest.cjs" record ".forge/templates/{filename}.md"
+   ```
+   (If generation-manifest.cjs is not yet installed, skip silently.)
+
+4. Return **exactly one line**:
+   - `done: <first 80 chars of the written file>` — on success
+   - `FAILED: <reason>` — if any step above failed or the file could not be written
+
+Do not output anything else after the status line.

package/dist/forge-payload/init/generation/generate-templates.md

@@ -0,0 +1,39 @@
+# Generation: Templates
+
+## Purpose
+
+Generate project-specific document templates from meta-templates,
+adding stack-specific sections.
+
+## Inputs
+
+- `$FORGE_ROOT/meta/templates/meta-*.md` (8 meta-templates)
+- Discovery context (from Phase 1)
+- Generated knowledge base (from Phase 2)
+
+## Outputs
+
+`.forge/templates/` with project-specific templates:
+- `TASK_PROMPT_TEMPLATE.md`
+- `PLAN_TEMPLATE.md`
+- `PROGRESS_TEMPLATE.md`
+- `CODE_REVIEW_TEMPLATE.md`
+- `PLAN_REVIEW_TEMPLATE.md`
+- `SPRINT_REQUIREMENTS_TEMPLATE.md`
+- `SPRINT_MANIFEST_TEMPLATE.md`
+- `RETROSPECTIVE_TEMPLATE.md`
+
+## Instructions
+
+For each meta-template:
+1. Read its sections and Generation Instructions
+2. Add framework-specific subsections based on the detected stack
+3. Reference the project's actual entity names and test output formats
+4. Use the project's ID format in template headers
+
+After writing each template file, record it in the generation manifest:
+```sh
+node {paths.tools}/generation-manifest.cjs record {paths.templates}/{filename}.md
+```
+
+If `generation-manifest.cjs` is not yet installed, skip silently.

package/dist/forge-payload/init/generation/generate-tools.md

@@ -0,0 +1,133 @@
+# Generation: Tools
+
+## Purpose
+
+Vendor the plugin tools closure and validation schemas into the project so
+generated workflows can invoke tools via `node .forge/tools/<tool>.cjs` from
+the project root without resolving `$FORGE_ROOT` at runtime.
+
+Store validation schemas are loaded at runtime from `.forge/schemas/`
+(project-installed), `forge/schemas/` (in-tree fallback), or
+`$FORGE_ROOT/schemas/` (plugin-installed fallback). During init, schemas
+are copied to `.forge/schemas/` so that validation works without relying
+on fallback paths.
+
+## Inputs
+
+- `.forge/config.json` — target paths
+
+## Outputs
+
+- `.forge/tools/` — vendored plugin tools closure
+- `.forge/tools/.forge-tools-version` — version marker for `/forge:health` staleness check
+- `.forge/schemas/` — JSON Schema copies from the installed plugin
+
+## Instructions
+
+Read `.forge/config.json` for:
+- `paths.store` (default: `.forge/store`)
+
+### Step 1 — Copy validation schemas
+
+Copy all JSON Schema files from the installed plugin to the project:
+
+```sh
+mkdir -p .forge/schemas
+cp "$FORGE_ROOT/schemas/"*.schema.json .forge/schemas/
+```
+
+This ensures `store-cli.cjs` and `validate-store.cjs` can validate records
+using the full schema (not the minimal fallback) even when the project is
+not inside the Forge source tree.
+
+### Step 2 — Vendor plugin tools
+
+Copy the plugin tools closure into the project's `.forge/tools/` so that
+generated artifacts can invoke `node .forge/tools/<tool>.cjs` from the
+project root without resolving `$FORGE_ROOT`:
+
+Copy BOTH `.cjs` and `.js` files. Some tools require `.js` helpers at load
+time — e.g. `store-cli.cjs` does a top-level `require('./lib/validate.js')`
+and `collate.cjs` requires `./lib/result.js` — so a `.cjs`-only copy leaves
+`store-cli.cjs` dead-on-arrival and breaks KB collation. `-maxdepth 1`
+excludes the `__tests__/` subtree without copying any `*.test.*` files.
+
+```sh
+mkdir -p .forge/tools/lib
+
+# Copy top-level tool files (.cjs and .js — e.g. list-skills.js)
+find "$FORGE_ROOT/tools" -maxdepth 1 -type f \( -name '*.cjs' -o -name '*.js' \) \
+  -exec cp {} .forge/tools/ \;
+
+# Copy lib/ helper files (.cjs and .js — e.g. result.js, validate.js)
+find "$FORGE_ROOT/tools/lib" -maxdepth 1 -type f \( -name '*.cjs' -o -name '*.js' \) \
+  -exec cp {} .forge/tools/lib/ \;
+```
+
+After copying, record each vendored file in the generation manifest so that
+`/forge:health` can detect modifications or stale copies:
+
+```sh
+for f in $(find .forge/tools .forge/tools/lib -maxdepth 1 -type f \( -name '*.cjs' -o -name '*.js' \)); do
+  node "$FORGE_ROOT/tools/generation-manifest.cjs" record "$f"
+done
+```
+
+### Step 2b — Write version marker
+
+After the tool copy loop, write the version marker so `/forge:health` can
+detect whether the vendored tools are stale relative to the active plugin:
+
+```sh
+ACTIVE_VERSION=$(node -e "console.log(require('$FORGE_ROOT/.claude-plugin/plugin.json').version)")
+node -e "
+const fs = require('fs');
+fs.writeFileSync('.forge/tools/.forge-tools-version', JSON.stringify({ version: '${ACTIVE_VERSION}' }) + '\n');
+"
+```
+
+### Step 3 — Verify
+
+```sh
+node "$FORGE_ROOT/tools/validate-store.cjs" --dry-run
+```
+
+If it exits non-zero, report the error. Do not proceed to Phase 9 until this passes.
+
+### Step 4 — Register the Forge root
+
+Write the project-relative Forge root into config. In the CLI-first vendored
+world the `.forge/` directory IS the Forge root (tools, schemas, hooks, init,
+meta are all vendored there) — NEVER write an absolute path (plugin cache,
+npm global payload, …): absolute paths break on version upgrades, nvm/node
+switches, and machine moves.
+
+```sh
+node .forge/tools/manage-config.cjs set paths.forgeRoot '".forge"'
+```
+
+### Step 5 — Record hashes
+
+Record all generated artifacts in the generation manifest so health checks
+can detect later modifications:
+
+```sh
+for f in .forge/schemas/*.schema.json; do
+  node "$FORGE_ROOT/tools/generation-manifest.cjs" record "$f"
+done
+node "$FORGE_ROOT/tools/generation-manifest.cjs" record .forge/config.json
+```
+
+## Notes
+
+- `/forge:update` automatically refreshes schemas and re-vendors tools as part
+  of its normal flow — run it after upgrades to pick up any changed tools or
+  schema updates from the new version.
+- Generated workflow files invoke tools using the vendored project-relative path:
+  ```
+  node .forge/tools/<tool>.cjs
+  ```
+  This works from the project root without resolving `$FORGE_ROOT` at runtime.
+- `paths.forgeRef` in config records the plugin version the project was generated
+  against. `forge-preflight.cjs` uses it to resolve the plugin root via cache
+  lookup when runtime telemetry requires the original plugin path.

package/dist/forge-payload/init/generation/generate-workflows.md

@@ -0,0 +1,78 @@
+# Workflow Generation — Per-Subagent Instructions
+
+You are generating **ONE** workflow file. You have been given three inputs:
+
+1. A **project brief** (`.forge/init-context.md`) — authoritative for all names,
+   paths, and placeholder values
+2. A **meta-workflow source** — your generation algorithm and Generation Instructions
+3. A **persona file** (already generated) — embed verbatim as the opening section
+
+Your job is to produce exactly one file and return a one-line status.
+
+---
+
+## Inputs
+
+Read these three sources before writing anything:
+
+- `.forge/init-context.md` — the project brief (passed inline in your prompt)
+- `$FORGE_ROOT/meta/workflows/{meta}` — the meta-workflow for your assigned workflow
+- `.forge/personas/{persona}.md` — the persona file for your assigned role
+
+---
+
+## Rules
+
+1. **Write EXACTLY ONE file:** `.forge/workflows/{id}.md`
+
+2. **Opening section** — the generated file must begin with:
+   a. The meta-workflow's YAML frontmatter block (`---` … `---`) verbatim,
+      if present. This carries `requirements:` fields used for runtime model
+      selection and must be preserved exactly.
+   b. Immediately after the closing `---`, embed the persona file content
+      verbatim as the first section. Do not paraphrase or summarise.
+
+3. **Placeholder substitution** — all `{SYNTAX_CHECK}`, `{TEST_COMMAND}`,
+   `{BUILD_COMMAND}`, `{LINT_COMMAND}` values come from the brief's
+   `## Commands` section. Do not invent values.
+
+4. **Name vocabulary** — all persona names, template names, architecture doc
+   names, and entity names MUST appear in the brief. Do not invent or rename
+   anything not listed there.
+
+5. **Required steps** — follow the meta-workflow's Generation Instructions.
+   Include the Knowledge Writeback step and the Event Emission step as defined
+   in the meta-workflow (unless the meta explicitly omits them, e.g. quiz_agent).
+
+6. **Enforcement quality** — for review workflows, include:
+   - A Rationalization Table of common agent excuses and factual rebuttals
+   - "YOU MUST" / "No exceptions" gate language at critical checks
+   - An announcement pattern: the agent declares intent at workflow start
+
+7. **No free-form additions** — do not add sections, steps, or notes beyond
+   what the meta-workflow and project brief prescribe.
+
+---
+
+## Self-check (mandatory last step)
+
+After writing the file, verify before returning:
+
+1. Read back `.forge/workflows/{id}.md`
+2. Confirm the persona symbol appears as the **first non-blank line after the
+   closing `---`** of the frontmatter block (or as the absolute first non-blank
+   line if the meta-workflow had no frontmatter). The symbol is listed in the
+   brief's `## Personas` section for this workflow's role.
+3. Confirm **no unsubstituted placeholders** remain (no literal `{TEST_COMMAND}`,
+   `{BUILD_COMMAND}`, `{SYNTAX_CHECK}`, or `{LINT_COMMAND}` in the file)
+4. Record in the manifest:
+   ```sh
+   node "$FORGE_ROOT/tools/generation-manifest.cjs" record ".forge/workflows/{id}.md"
+   ```
+   (If generation-manifest.cjs is not yet installed, skip silently.)
+
+5. Return **exactly one line**:
+   - `done: <first 80 chars of the written file>` — on success
+   - `FAILED: <reason>` — if any step above failed or the file could not be written
+
+Do not output anything else after the status line.

package/dist/forge-payload/init/phases/phase-1-collect.md

@@ -9,6 +9,10 @@ parent directory — the folder containing `meta/` and `init/`).
 
 ## Pre-flight — Knowledge Base Folder
 
+> **Orchestrator note:** If your orchestrator (e.g. the `wfl:init` driver or the CLI-first
+> wrapper) has already supplied a `kbFolder` value, use it directly — skip this prompt.
+> This interactive block applies only to unmediated orchestrator-free execution.
+
 Before Phase 1 begins, ask the user where to create the knowledge base folder:
 
 ```
@@ -74,13 +78,13 @@ Using your discovery findings, write `.forge/config.json` with this structure:
     "engineering": "engineering",
     "store": ".forge/store",
     "workflows": ".forge/workflows",
-    "commands": ".claude/commands/<prefix-lowercased>",
+    "commands": ".claude/commands/forge",
     "templates": ".forge/templates"
   }
 }
 ```
 
-`<prefix-lowercased>` = the `project.prefix` value you chose, lowercased. For example, if prefix is `HELLO`, write `".claude/commands/hello"`.
+`paths.commands` is ALWAYS `".claude/commands/forge"` — the command namespace is fixed (CLI-first redesign); it does NOT derive from the project prefix.
 
 Write using:
 ```sh
@@ -103,6 +107,10 @@ If any key is missing or empty, fix it now before proceeding.
 
 ### Step 5 — Marketplace Skills
 
+> **Orchestrator note:** If your orchestrator handles the skills install offer post-workflow
+> (e.g. the `init.md` wrapper does this after `wfl:init` returns), skip this step. Return
+> `{ matches, alreadyInstalled }` from the config-writer agent instead.
+
 Read `$FORGE_ROOT/meta/skill-recommendations.md` for the full mapping.
 
 Using the stack discovered above, look up matching skills from the recommendation

package/dist/forge-payload/init/phases/phase-3-materialize.md

@@ -63,7 +63,7 @@ node "$FORGE_ROOT/tools/substitute-placeholders.cjs" \
 ```
 
 Output directories (managed by the tool's `SUBDIR_OUTPUT_MAP`):
-- `base-pack/commands/`     → `.claude/commands/<prefix-lowercased>/`
+- `base-pack/commands/`     → `.claude/commands/forge/`  (fixed namespace — CLI-first redesign)
 - `base-pack/personas/`     → `.forge/personas/`
 - `base-pack/skills/`       → `.forge/skills/`
 - `base-pack/workflows/`    → `.forge/workflows/`

package/dist/forge-payload/init/phases/phase-4-register.md

@@ -102,6 +102,10 @@ console.log('ノ update-check-cache.json written');
 
 ### Step 11 — Tomoshibi (refresh-kb-links)
 
+> **Orchestrator note:** This step is orchestrator-owned. When running under `wfl:init`, the
+> register agent returns `pendingActions: ["refresh-kb-links"]` and the command wrapper
+> invokes the Skill. Do NOT execute this step if your orchestrator owns it.
+
 Use the Skill tool:
 ```
 skill: "forge:refresh-kb-links"
@@ -134,6 +138,10 @@ Fallback if unavailable:
 
 ### Step 13 — Agent instruction file linking
 
+> **Orchestrator note:** If your orchestrator pre-answered the CLAUDE.md creation prompt
+> (via `args.createClaudeMd`), use that value directly — skip the interactive prompt.
+> Execute the file creation only if `createClaudeMd === true`.
+
 Check whether any agent instruction file exists at the project root:
 ```sh
 ls CLAUDE.md AGENTS.md CLAUDE.local.md .cursorrules 2>/dev/null

package/dist/forge-payload/init/workflow-gen-plan.json

@@ -0,0 +1,17 @@
+[
+  {"id": "architect_sprint_intake",            "meta": "meta-new-sprint.md",              "persona": "product-manager"},
+  {"id": "architect_sprint_plan",              "meta": "meta-plan-sprint.md",             "persona": "architect"},
+  {"id": "architect_approve",                  "meta": "meta-approve.md",                 "persona": "architect"},
+  {"id": "architect_review_sprint_completion", "meta": "meta-review-sprint-completion.md","persona": "architect"},
+  {"id": "plan_task",                          "meta": "meta-plan-task.md",               "persona": "architect"},
+  {"id": "implement_plan",                     "meta": "meta-implement.md",               "persona": "engineer"},
+  {"id": "update_plan",                        "meta": "meta-update-plan.md",             "persona": "architect"},
+  {"id": "update_implementation",              "meta": "meta-update-implementation.md",   "persona": "engineer"},
+  {"id": "commit_task",                        "meta": "meta-commit.md",                  "persona": "engineer"},
+  {"id": "review_plan",                        "meta": "meta-review-plan.md",             "persona": "supervisor"},
+  {"id": "review_code",                        "meta": "meta-review-implementation.md",   "persona": "supervisor"},
+  {"id": "collator_agent",                     "meta": "meta-collate.md",                 "persona": "collator"},
+  {"id": "sprint_retrospective",               "meta": "meta-retro.md",                   "persona": "architect"},
+  {"id": "validate_task",                      "meta": "meta-validate.md",               "persona": "qa-engineer"},
+  {"id": "quiz_agent",                         "meta": "meta-check-agent.md",             "persona": "qa-engineer"}
+]

package/dist/forge-payload/integrity.json

@@ -1,23 +1,23 @@
 {
-  "version": "1.2.21",
-  "generated": "2026-06-06",
+  "version": "1.4.4",
+  "generated": "2026-06-07",
   "note": "Tamper-evident only. Authoritative source: /forge:update from remote.",
   "files": {
-    "commands/add-pipeline.md": "529a2fc01be49815efa2cf1147528827ff1bfc12ce2ac8663b5a3a9781f8682e",
-    "commands/add-task.md": "ce3d66fc38e7e0a7592705c559425c6e122f25280b838b631ad44e514bd64e04",
-    "commands/ask.md": "df15f0aa68c93d65bfef05adb514c377bfc65617cafcd79534eb9b4149302657",
-    "commands/check-agent.md": "f92121cb150d4cf601654e25c28d0c13389039518d05433f1040d727054b127e",
-    "commands/config.md": "e67185f98cf0b045890398083991b9d48f32bf0d53bafda1eaca3ce0337ce49c",
+    "commands/add-pipeline.md": "ed4e666b38542d959287116ff6f25e8f51b10c2f18d1fc54974a996fdaf9d8f7",
+    "commands/add-task.md": "1782818b31d602194a2bbab12dda00e3b5a947dd5410ca9078777e79df1ad3ee",
+    "commands/ask.md": "9b53c7636533811d689cfc27e5eeb847c92f8f740434657c61db090a53a4e21f",
+    "commands/check-agent.md": "89d2ebac4910447af22380df5d1b99511d6dae3581374ddb6780e686d8163ce6",
+    "commands/config.md": "e9af723a2cf782d167d75aa29cbbec71e937507b9d7576ad254a5a35acae9df0",
     "commands/enhance.md": "d28f6414119e84973809d32900bb7245b51f565aed86112bc7a994bc6941b547",
-    "commands/health.md": "8f8160d67c09eed9be12445674fc2ab76cf31d548c6268c71f9777dca30c4e47",
-    "commands/init.md": "cf7a70d55f718304820c310465071d3eea9d14a43131623f46b686499f630d4d",
-    "commands/rebuild.md": "9de3a3c1e41169e18758c8598e297c2f395f9daefdd9772783b9b676982cf1c2",
-    "commands/remove.md": "0ca5ec94d52959afaadd74910bd2c81c9872b71c9cc1ce8b89e5af69c06b304f",
-    "commands/repair.md": "22e21614eee31ee630ead3f587b0b948b8c537e54ecef3b65e7d819c55c0ebd4",
-    "commands/report-bug.md": "af8a54bf8887b35e5c880898dd45783f6c2e80d3dc031d6479a6be613ac43053",
+    "commands/health.md": "d92d81ab8614608c383a01f4788fa9aa17a9b07c0d62caebad264a6459b45d58",
+    "commands/init.md": "846e719a85aea6cd706287d6b3bd764d023dae463c0d646c5bf02481c179f4d9",
+    "commands/rebuild.md": "be7cc69c79883d3caae52b1ce8904404ac6d622b84fc17a278f3fd697230842f",
+    "commands/remove.md": "3044c58c699047e94bea4bb26bbe0e8d81425cba1ef2afc7243968e2ee8ab483",
+    "commands/repair.md": "90dd34c87768aef50a46224a21280047ed2376ca59785ecf6403cae3177dfc2f",
+    "commands/report-bug.md": "ae4eb28b54d171de20e89250daadc2a0859887f1d59845a895bd9543b0c1db6f",
     "commands/search.md": "befc4ba9f3146e7599308b35b95ec315e16895c0c18c9c2bab7549619d79bf1c",
-    "commands/status.md": "2fa82a0b11d493918781aec6d95c39411f84fa923662ff3152b6de0cc830d755",
-    "commands/update.md": "c8b69b43567fa5fc328bb3dde31f386d0f577bbcc65dafd525400ae2fb16b132",
+    "commands/status.md": "d1f5e9295b472553fafcd270e34be00560beadfb18b98d4b696845fb794102eb",
+    "commands/update.md": "00cf09b7fa6e84b7bd137a543a11e52c3dbfe3dfe463982dbd6224435ba52345",
     "agents/store-query-validator.md": "f4c3573edcf6e28809515705362df611806a805c5269404fb17e31433cf3a81c",
     "agents/tomoshibi.md": "0c1032df80dfc25a4f482b1276965b5318754d95ccde9f24820846d564e49a27",
     "hooks/check-update.cjs": "9607cc0c51bedcbc123f5ea1d7a492916f29ee1f838846eec64776d5df70bbea",
@@ -30,7 +30,7 @@
     "schemas/transitions/bug.json": "27b17da42d1cebffbd4f61ab3dcd432a0017aa71997d548ed80d22c2fc3fad6a",
     "schemas/transitions/sprint.json": "2e0a629396e687b0ca88e1814ac3e35d84533a5d55b25237ab67feddce3c9deb",
     "schemas/transitions/task.json": "4c71849747baa0d585756e57c56325ff6219c078178374e60815dff91e25e3e7",
-    "schemas/enum-catalog.json": "68260bed8e6fe347bc4a1c870fa1ea51ca1ebc45873aae929624837afe8f0bdb",
+    "schemas/enum-catalog.json": "031b5888c3092dccb23e7fafe6cad3462cd4c8a4af3b055fcd503595818efaa0",
     "tools/verify-integrity.cjs": "3ec3c970dd3d7c3001f8f373bcc40556803eadd2fc2afafb14f1c232cba4cc3f"
   }
 }

package/dist/forge-payload/meta/workflows/meta-collate.md

@@ -80,12 +80,11 @@ Never set `FORGE_SKIP_WRITE_VALIDATION=1` — operator-only emergency switch.
      }
      ```
      The orchestrator reads this file directly to compose the collation event narrative. Do NOT call `set-summary` to register it — that would mutate the store in violation of Iron Law 1.
-   - Invoke Tomoshibi via Skill tool to refresh KB and workflow links in agent
-     instruction files:
-     ```
-     Use the Skill tool:
-       skill: "forge:refresh-kb-links"
-     ```
+   - KB link refresh (best-effort; skip if unavailable):
+     When running standalone in the Claude Code TUI, invoke via the Skill tool
+     (`skill: "forge:refresh-kb-links"`).
+     When running as a subagent within forge-cli (Pi runtime), the TS orchestrator
+     calls `runRefreshKbLinks` directly after this phase — skip this step.
 ```
 
 <!-- See _fragments/generation-instructions.md for Generation Instructions template -->

package/dist/forge-payload/meta/workflows/meta-migrate.md

@@ -295,7 +295,7 @@ node .forge/tools/substitute-placeholders.cjs \
 ```
 
 This overwrites `.forge/personas/`, `.forge/skills/`, `.forge/workflows/`,
-`.forge/templates/`, and `.claude/commands/<prefix>/` with the freshly substituted
+`.forge/templates/`, and `.claude/commands/forge/` with the freshly substituted
 base-pack.
 
 If `substitute-placeholders.cjs` exits non-zero: halt, report the error to the

package/dist/forge-payload/schemas/enum-catalog.json

@@ -1,6 +1,6 @@
 {
-  "version": "1.2.21",
-  "generated": "2026-06-06",
+  "version": "1.4.3",
+  "generated": "2026-06-07",
   "note": "Authoritative enum catalog. Source: build-enum-catalog.cjs. Regenerate via node forge/tools/build-manifest.cjs.",
   "enums": {
     "task.status": [

package/dist/forge-payload/schemas/structure-manifest.json

@@ -1,6 +1,6 @@
 {
-  "version": "1.2.21",
-  "generatedAt": "2026-06-06T15:46:43.003Z",
+  "version": "1.4.3",
+  "generatedAt": "2026-06-07T14:06:39.707Z",
   "generatedByTool": "build-manifest.cjs",
   "namespaces": {
     "personas": {
@@ -109,6 +109,7 @@
       "dir": ".claude/workflows",
       "files": [
         "wfl-fix-bug.js",
+        "wfl-init.js",
         "wfl-run-sprint.js",
         "wfl-run-task.js"
       ]
@@ -142,43 +143,33 @@
         "artifact.cjs",
         "backfill-provider.cjs",
         "banners.cjs",
-        "build-base-pack.cjs",
         "build-context-pack.cjs",
-        "build-enum-catalog.cjs",
         "build-init-context.cjs",
-        "build-manifest.cjs",
         "build-overlay.cjs",
         "build-persona-pack.cjs",
-        "check-no-skipped-tests.cjs",
         "check-structure.cjs",
         "collate.cjs",
         "commit-task.cjs",
         "compression-gate.cjs",
         "delete-candidate-detector.cjs",
-        "estimate-usage.cjs",
         "forge-preflight.cjs",
         "friction-emit.cjs",
-        "gen-integrity.cjs",
         "generation-manifest.cjs",
         "judge-proposal.cjs",
         "manage-config.cjs",
         "manage-versions.cjs",
-        "migrate-slug-maxlen.cjs",
         "parse-gates.cjs",
         "postflight-gate.cjs",
         "preflight-gate.cjs",
-        "proposal-normalize.cjs",
         "query-logger.cjs",
         "queue-drain.cjs",
         "read-verdict.cjs",
         "replay-scoring.cjs",
-        "rewrite-plugin-urls.cjs",
         "seed-store.cjs",
         "store-cli.cjs",
         "store-query.cjs",
         "store.cjs",
         "substitute-placeholders.cjs",
-        "token-forensics.cjs",
         "validate-store.cjs",
         "verify-apply.cjs",
         "verify-integrity.cjs",