mindforge-cc 11.9.0 → 11.9.1

package/.claude/commands/mindforge/wf-workflow-optimizer.md

@@ -0,0 +1,51 @@
+---
+description: "Builder + scorer + a distinct process-optimizer role: proposes structural changes to the PROCESS itself across rounds, not just fixes to one output"
+---
+# /mindforge:wf-workflow-optimizer
+
+Runs the **Workflow Optimizer** dynamic workflow.
+
+## Usage
+`/mindforge:wf-workflow-optimizer [task family description, or { taskFamily, metric, maxRounds, priorHistory }]`
+
+## What it does
+- **Scope**: Pins the task family, the fixed outcome metric, and any prior round history
+  you supply (this script holds no state of its own between invocations)
+- **Cycle**: A builder agent runs under the *current* process instructions; a separate
+  scorer agent grades the output against the fixed metric; a **third, distinct
+  process-optimizer agent** — with no role in building or scoring — diagnoses *why* the
+  process produced that result and rewrites the builder's instructions for next round.
+  Repeats until the optimizer judges the process has converged or `maxRounds` is hit.
+- **Report**: The score trend across rounds alongside every round's structural diagnosis,
+  so you can see whether rising scores came from real process changes, not just luck.
+
+This is not "implementer vs. scorer, keep re-attempting the same task" (that's
+`/mindforge:wf-verification-loop`, one artifact, one metric, no separate optimizer role).
+This workflow's object of improvement is the **process itself** — the builder's own
+instructions evolve round to round, and the deliverable includes that evolution history,
+not just a final artifact.
+
+## Running
+
+Invoke via Claude Code's Workflow tool:
+
+```
+Workflow({
+  scriptPath: ".mindforge/dynamic-workflows/scripts/workflow-optimizer.js",
+  args: {
+    taskFamily: "Write a one-paragraph executive summary of a technical incident postmortem",
+    metric: "30 pts non-technical-reader clarity, 30 pts root-cause traceability, 40 pts action-item concreteness",
+    maxRounds: 5
+  }
+})
+```
+
+To continue optimizing the SAME process across separate sessions, pass the previous run's
+returned `processHistory` back in as `args.priorHistory` — the script itself has no
+filesystem access and keeps no state between invocations, so cross-session continuity is
+the caller's responsibility.
+
+Or discover via CLI:
+```bash
+node bin/mindforge-cli.js workflow info workflow-optimizer
+```

package/.claude/commands/mindforge/wf-writer-reviewer.md

@@ -0,0 +1,30 @@
+---
+description: "Anthropic Writer/Reviewer pattern: implement in Context A → fresh Context B reviews the diff"
+---
+# /mindforge:wf-writer-reviewer
+
+Runs the **Writer Reviewer** dynamic workflow.
+
+## Usage
+`/mindforge:wf-writer-reviewer <implementation task description>`
+
+## What it does
+- **Implement**: Writer agent implements the requested change
+- **Review**: Fresh reviewer agent inspects only the diff without implementation context
+- **Verdict**: Accept / request-changes verdict with specific actionable feedback
+
+## Running
+
+Invoke via Claude Code's Workflow tool:
+
+```
+Workflow({
+  scriptPath: ".mindforge/dynamic-workflows/scripts/writer-reviewer.js",
+  args: "<your input>"
+})
+```
+
+Or discover via CLI:
+```bash
+node bin/mindforge-cli.js workflow info writer-reviewer
+```

package/.mindforge/config.json

@@ -1,11 +1,11 @@
 {
-  "version": "11.9.0",
+  "version": "11.9.1",
   "environment": "development",
   "governance": {
     "drift_threshold": 0.75,
     "critical_drift_threshold": 0.5,
     "res_threshold": 0.8,
-    "active_did": "did:mindforge:7672fba0-0c90-429f-8f22-2c6aa7d2bc63"
+    "active_did": "did:mindforge:ea8ace55-c2f0-46f2-af28-4d5a8ee3293a"
   },
   "revops": {
     "market_registry": {

package/.mindforge/memory/sync-manifest.json

@@ -1,6 +1,6 @@
 {
   "pattern-library.jsonl": {
-    "lastSync": "2026-07-28T09:19:09.269Z",
+    "lastSync": "2026-07-29T10:18:46.944Z",
     "localCount": 1
   }
 }

package/.mindforge/personas/doc-auditor.md

@@ -35,7 +35,7 @@ updates every time code changes, it needs automation or deletion.
 <process>
 <step name="inventory">
 Identify all documentation files in the project:
-- README.md, CONTRIBUTING.md, CHANGELOG.md
+- README.md, CONTRIBUTING.md, CHANGELOG.md (rolling window), changelogs/ (full archive + README.md index)
 - docs/ directory (all files)
 - Inline API documentation (JSDoc, docstrings)
 - Architecture decision records (ADRs)

package/.mindforge/personas/monorepo-architect.md

@@ -156,7 +156,8 @@ git commit -m "feat(api)!: change auth header" → major bump
 - Build all packages in dependency order
 - Publish to npm (private registry or public)
 - Tag git commit with version
-- Generate CHANGELOG.md
+- Generate `changelogs/vX.Y.Z.md` for the release, then prepend the same entry
+  (or a one-line summary + link) into root `CHANGELOG.md`'s rolling window
 </step>
 
 <step name="developer_experience">

package/.mindforge/personas/release-manager.md

@@ -8,7 +8,7 @@ color: blue
 <role>
 You are the MindForge Release Manager. You own the transition from "Verification" to "Production."
 Your job is to ensure that MindForge versions are meaningful, stable, and perfectly documented.
-You are the final gatekeeper of the `CHANGELOG.md` and version tags.
+You are the final gatekeeper of the `CHANGELOG.md` rolling window, the `changelogs/` archive, and version tags.
 </role>
 
 <why_this_matters>
@@ -41,7 +41,9 @@ Check `STATE.md` to ensure all active workstreams are merged or paused.
 <step name="changelog_synthesis">
 Ingest the `SUMMARY.md` files from all completed phases.
 Group changes into: Added, Changed, Fixed, and Security.
-Write the entry to `CHANGELOG.md` using the Keep a Changelog standard.
+Create `changelogs/vX.Y.Z.md` for the new release using the Keep a Changelog standard,
+then prepend the same entry (or a one-line summary + link) to root `CHANGELOG.md`,
+trimming the oldest entry if the rolling window exceeds 10 versions.
 </step>
 
 <step name="version_bumping">
@@ -107,7 +109,7 @@ Draft the Pull Request (PR) or Release Note description.
 
 <success_criteria>
 - [ ] Version bump follows SemVer
-- [ ] CHANGELOG.md updated and logically grouped
+- [ ] changelogs/vX.Y.Z.md created and CHANGELOG.md rolling window updated (logically grouped)
 - [ ] All verification docs (UAT/Security) reviewed
 - [ ] Git tag created or staged
 - [ ] PR description finalized

package/.mindforge/skills/documentation/SKILL.md

@@ -75,7 +75,10 @@ export function verifyAccessToken(token: string): TokenPayload { ... }
 ```
 
 ## Changelog discipline
-Every user-visible change must appear in CHANGELOG.md before release.
+Every user-visible change must appear in the changelog before release: create
+`changelogs/vX.Y.Z.md` for the new release, then prepend the same entry (or a
+one-line summary + link) into root `CHANGELOG.md`'s rolling window, dropping
+the oldest entry if the window exceeds 10 versions.
 Format follows Keep a Changelog (keepachangelog.com).
 Categories: Added, Changed, Deprecated, Removed, Fixed, Security.