@lumenflow/cli 3.13.1 → 3.13.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lumenflow/cli",
-  "version": "3.13.1",
+  "version": "3.13.2",
   "description": "Command-line interface for LumenFlow workflow framework",
   "keywords": [
     "lumenflow",
@@ -185,13 +185,13 @@
     "xstate": "^5.28.0",
     "yaml": "^2.8.2",
     "zod": "^4.3.6",
-    "@lumenflow/agent": "3.13.1",
-    "@lumenflow/control-plane-sdk": "3.13.1",
-    "@lumenflow/initiatives": "3.13.1",
-    "@lumenflow/kernel": "3.13.1",
-    "@lumenflow/core": "3.13.1",
-    "@lumenflow/memory": "3.13.1",
-    "@lumenflow/metrics": "3.13.1"
+    "@lumenflow/agent": "3.13.2",
+    "@lumenflow/control-plane-sdk": "3.13.2",
+    "@lumenflow/core": "3.13.2",
+    "@lumenflow/initiatives": "3.13.2",
+    "@lumenflow/kernel": "3.13.2",
+    "@lumenflow/metrics": "3.13.2",
+    "@lumenflow/memory": "3.13.2"
   },
   "devDependencies": {
     "@vitest/coverage-v8": "^4.0.18",

package/packs/sidekick/.turbo/turbo-build.log

@@ -1,4 +1,4 @@
 
-> @lumenflow/packs-sidekick@3.13.1 build /home/runner/work/lumenflow-dev/lumenflow-dev/packages/@lumenflow/packs/sidekick
+> @lumenflow/packs-sidekick@3.13.2 build /home/runner/work/lumenflow-dev/lumenflow-dev/packages/@lumenflow/packs/sidekick
 > tsc
 

package/packs/sidekick/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lumenflow/packs-sidekick",
-  "version": "3.13.1",
+  "version": "3.13.2",
   "description": "Sidekick personal assistant pack for LumenFlow — 16 tools for task management, typed memory, channels, routines, and audit",
   "keywords": [
     "lumenflow",

package/packs/software-delivery/.turbo/turbo-build.log

@@ -1,4 +1,4 @@
 
-> @lumenflow/packs-software-delivery@3.13.1 build /home/runner/work/lumenflow-dev/lumenflow-dev/packages/@lumenflow/packs/software-delivery
+> @lumenflow/packs-software-delivery@3.13.2 build /home/runner/work/lumenflow-dev/lumenflow-dev/packages/@lumenflow/packs/software-delivery
 > tsc
 

package/packs/software-delivery/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lumenflow/packs-software-delivery",
-  "version": "3.13.1",
+  "version": "3.13.2",
   "description": "Software delivery pack for LumenFlow — work units, gates, lanes, initiatives, and agent coordination",
   "keywords": [
     "lumenflow",

package/templates/core/LUMENFLOW.md.template

@@ -72,7 +72,16 @@ pnpm initiative:add-wu --initiative INIT-001 --wu WU-XXX --phase 1
 pnpm initiative:status --id INIT-001
 ```
 
-**Skip initiatives** for: single-file bug fixes, small docs updates, isolated refactoring.
+**Skip initiatives whenever the work is still one coherent WU**, even if it spans several files or needs checkpoint-resume.
+
+Typical no-initiative cases:
+
+- Single coherent bug fixes
+- Small or medium documentation updates
+- Isolated refactors that land as one atomic change
+- One feature WU that needs checkpoint-resume but does not need decomposition
+
+Create an initiative when you genuinely need multiple independently completable WUs, multiple lane owners, or staged rollout across phases. File count alone is not the split signal.
 
 ---
 
@@ -244,6 +253,7 @@ For the full worktree lifecycle (parallel execution, bootstrap, isolation guaran
 | `pnpm wu:brief`           | Generate handoff prompt + record evidence                 |
 | `pnpm wu:delegate`        | Generate prompt + record lineage + brief hash attestation |
 | `pnpm wu:escalate`        | Show or resolve WU escalation status                      |
+| `pnpm wu:verify`          | Verify WU completion (stamp, commit, clean tree)          |
 | `pnpm wu:delete`          | Delete WU spec and cleanup                                |
 | `pnpm gates`              | Run quality gates (`--docs-only` for docs WUs)            |
 | `pnpm lumenflow:commands` | List all public commands (primary + alias + legacy)       |

package/templates/core/ai/onboarding/first-wu-mistakes.md.template

@@ -298,7 +298,7 @@ Agent: [ignores the warning, proceeds without sizing metadata]
 
 ### Right
 
-When `wu:create` or `wu:brief` emits a sizing advisory warning, either:
+When `wu:create` or `wu:brief` emits a sizing advisory warning, choose the smallest valid strategy:
 
 1. **Add exception metadata** if the oversize WU is justified:
 
@@ -311,7 +311,16 @@ sizing_estimate:
   exception_reason: All markdown documentation files, low complexity
 ```
 
-2. **Split the WU** if the estimate genuinely exceeds session capacity (see [wu-sizing-guide.md](./wu-sizing-guide.md) section 3 for splitting patterns).
+2. **Keep one WU with a stronger execution strategy** if the work is still one coherent outcome:
+
+```yaml
+sizing_estimate:
+  estimated_files: 32
+  estimated_tool_calls: 90
+  strategy: checkpoint-resume
+```
+
+3. **Split the WU** only if the work is no longer atomic or should land independently (see [wu-sizing-guide.md](./wu-sizing-guide.md) section 3 for splitting patterns).
 
 **Strict mode:** Teams can enforce sizing compliance for delegated work with `--strict-sizing` on `wu:brief`. In strict mode, missing or non-compliant sizing metadata blocks the operation.
 

package/templates/core/ai/onboarding/initiative-orchestration.md.template

@@ -14,6 +14,7 @@ Before orchestrating an initiative, ensure:
 2. All WUs are linked to the initiative via `initiative:add-wu`
 3. Dependencies between WUs are defined (blocking relationships)
 4. Lane lifecycle is locked (`pnpm lane:status` shows `locked`)
+5. The initiative is not made of artificial micro-WUs that should really be one coherent WU
 
 ---
 
@@ -35,6 +36,8 @@ The dry-run output shows:
 - **Bottleneck WUs**: WUs that block the most downstream work (prioritize these)
 - **Recommended execution mode**: Checkpoint-per-wave vs continuous
 
+Before accepting the wave plan, sanity-check the decomposition. If several WUs sit in the same lane, describe one atomic outcome, and cannot ship independently, consolidate them instead of orchestrating them.
+
 ### Step 2: Choose Execution Mode
 
 | Mode                  | Command                                              | When to use                            |

package/templates/core/ai/onboarding/quick-ref-commands.md.template

@@ -154,20 +154,20 @@ automatically, and `.lumenflow/templates/` remains optional unless you want cust
 
 ### WU Maintenance
 
-| Command                          | Description                              |
-| -------------------------------- | ---------------------------------------- |
-| `pnpm wu:validate --id WU-XXX`   | Validate WU spec                         |
-| `pnpm wu:preflight --id WU-XXX`  | Pre-flight checks before wu:done         |
-| `pnpm wu:verify --id WU-XXX`    | Verify WU completion (stamp, commit, clean tree) |
-| `pnpm wu:recover --id WU-XXX`    | Analyze and fix WU state inconsistencies |
-| `pnpm wu:repair --id WU-XXX`     | Repair WU state issues                   |
-| `pnpm wu:prune`                  | Clean stale worktrees                    |
-| `pnpm wu:cleanup --id WU-XXX`    | Cleanup after PR merge (PR-only)         |
-| `pnpm wu:deps --id WU-XXX`       | Show WU dependencies                     |
-| `pnpm wu:infer-lane --id WU-XXX` | Infer lane from code paths/description   |
-| `pnpm wu:delete --id WU-XXX`     | Delete WU spec and cleanup               |
-| `pnpm wu:unlock-lane --lane <L>` | Unlock stuck lane                        |
-| `pnpm wu:proto --lane <Lane>`    | Create WU prototype (lightweight draft)  |
+| Command                          | Description                                      |
+| -------------------------------- | ------------------------------------------------ |
+| `pnpm wu:validate --id WU-XXX`   | Validate WU spec                                 |
+| `pnpm wu:preflight --id WU-XXX`  | Pre-flight checks before wu:done                 |
+| `pnpm wu:verify --id WU-XXX`     | Verify WU completion (stamp, commit, clean tree) |
+| `pnpm wu:recover --id WU-XXX`    | Analyze and fix WU state inconsistencies         |
+| `pnpm wu:repair --id WU-XXX`     | Repair WU state issues                           |
+| `pnpm wu:prune`                  | Clean stale worktrees                            |
+| `pnpm wu:cleanup --id WU-XXX`    | Cleanup after PR merge (PR-only)                 |
+| `pnpm wu:deps --id WU-XXX`       | Show WU dependencies                             |
+| `pnpm wu:infer-lane --id WU-XXX` | Infer lane from code paths/description           |
+| `pnpm wu:delete --id WU-XXX`     | Delete WU spec and cleanup                       |
+| `pnpm wu:unlock-lane --lane <L>` | Unlock stuck lane                                |
+| `pnpm wu:proto --lane <Lane>`    | Create WU prototype (lightweight draft)          |
 
 ---
 

package/templates/core/ai/onboarding/starting-prompt.md.template

@@ -91,13 +91,16 @@ If you are starting a new project or feature from a product vision (e.g., "Build
 
 ### When to Skip Initiatives
 
-Only skip initiatives for:
+Skip initiatives whenever the work is still one coherent WU, even if it spans several files or needs checkpoint-resume.
 
-- Single-file bug fixes
-- Small documentation updates
-- Isolated refactoring tasks
+Typical no-initiative cases:
 
-If work spans multiple WUs or multiple days, create an initiative first.
+- Single coherent bug fixes
+- Small or medium documentation updates
+- Isolated refactors that land as one atomic change
+- One feature WU that may need checkpoint-resume but does not need decomposition
+
+Create an initiative when you genuinely need multiple independently completable WUs, multiple lane owners, or staged rollout across phases. File count or execution strategy alone is not the split signal.
 
 ### Lane-Fit Reasoning
 
@@ -547,23 +550,23 @@ Domain-specific commands must come from local configuration, not core framework
 
 ## WU Lifecycle Commands
 
-| Command                                        | Description                                     | When to Use                 |
-| ---------------------------------------------- | ----------------------------------------------- | --------------------------- |
-| `pnpm wu:status --id WU-XXX`                   | Show WU state and valid commands                | Check current state         |
-| `pnpm wu:claim --id WU-XXX --lane "Lane"`      | Claim WU and create worktree (default)          | Start working (local)       |
-| `pnpm wu:claim --id WU-XXX --lane "L" --cloud` | Claim WU in branch-pr mode (no worktree)        | Start working (cloud)       |
-| `pnpm wu:edit --id WU-XXX --field value`       | Edit WU spec fields                             | Update notes/desc           |
-| `pnpm wu:brief --id WU-XXX --client X`         | Generate handoff prompt + evidence              | Complex WUs                 |
-| `pnpm wu:brief --id WU-XXX --evidence-only`    | Record evidence only (no prompt output)         | Self-implementation path    |
-| `pnpm wu:delegate --id WU-XXX --parent-wu P`   | Generate prompt + record delegation             | Auditable delegation flows  |
-| `pnpm wu:prep --id WU-XXX`                     | Run gates in claimed workspace, prep completion | Before wu:done              |
-| `pnpm wu:done --id WU-XXX`                     | Complete WU (merge or PR, cleanup)              | After gates pass            |
-| `pnpm wu:cleanup --id WU-XXX`                  | Post-merge cleanup (branch-pr)                  | After PR merge (cloud only) |
-| `pnpm wu:escalate --id WU-XXX`                 | Show or resolve escalation status               | Escalation-triggered WUs    |
-| `pnpm wu:escalate --resolve --id WU-XXX`       | Resolve human escalation                        | Before wu:done (escalation) |
+| Command                                        | Description                                      | When to Use                 |
+| ---------------------------------------------- | ------------------------------------------------ | --------------------------- |
+| `pnpm wu:status --id WU-XXX`                   | Show WU state and valid commands                 | Check current state         |
+| `pnpm wu:claim --id WU-XXX --lane "Lane"`      | Claim WU and create worktree (default)           | Start working (local)       |
+| `pnpm wu:claim --id WU-XXX --lane "L" --cloud` | Claim WU in branch-pr mode (no worktree)         | Start working (cloud)       |
+| `pnpm wu:edit --id WU-XXX --field value`       | Edit WU spec fields                              | Update notes/desc           |
+| `pnpm wu:brief --id WU-XXX --client X`         | Generate handoff prompt + evidence               | Complex WUs                 |
+| `pnpm wu:brief --id WU-XXX --evidence-only`    | Record evidence only (no prompt output)          | Self-implementation path    |
+| `pnpm wu:delegate --id WU-XXX --parent-wu P`   | Generate prompt + record delegation              | Auditable delegation flows  |
+| `pnpm wu:prep --id WU-XXX`                     | Run gates in claimed workspace, prep completion  | Before wu:done              |
+| `pnpm wu:done --id WU-XXX`                     | Complete WU (merge or PR, cleanup)               | After gates pass            |
+| `pnpm wu:cleanup --id WU-XXX`                  | Post-merge cleanup (branch-pr)                   | After PR merge (cloud only) |
+| `pnpm wu:escalate --id WU-XXX`                 | Show or resolve escalation status                | Escalation-triggered WUs    |
+| `pnpm wu:escalate --resolve --id WU-XXX`       | Resolve human escalation                         | Before wu:done (escalation) |
 | `pnpm wu:verify --id WU-XXX`                   | Verify WU completion (stamp, commit, clean tree) | After wu:done               |
-| `pnpm wu:delete --id WU-XXX`                   | Delete WU spec and cleanup                      | Cancel stale/throwaway WUs  |
-| `pnpm wu:recover --id WU-XXX`                  | Fix inconsistent WU state                       | When state is broken        |
+| `pnpm wu:delete --id WU-XXX`                   | Delete WU spec and cleanup                       | Cancel stale/throwaway WUs  |
+| `pnpm wu:recover --id WU-XXX`                  | Fix inconsistent WU state                        | When state is broken        |
 
 ---
 

package/templates/core/ai/onboarding/wu-sizing-guide.md.template

@@ -2,20 +2,41 @@
 
 **Last updated:** {{DATE}}
 
-Use this summary when deciding whether a WU still fits in a single agent session.
+Use this summary to decide whether work should stay as one WU and what execution strategy it needs.
+
+---
+
+## Default Bias
+
+Bias toward **one coherent outcome = one WU**.
+
+Do not split a WU just because it has multiple implementation steps, tests, or docs, or because it may need another session. Split only when the work is no longer one coherent deliverable.
+
+Keep one WU when:
+
+- The acceptance criteria describe one user-visible or operator-visible outcome
+- One agent can still complete it with `single-session`, `checkpoint-resume`, or `orchestrator-worker`
+- The touched files support the same change, even if there are several of them
+
+Split when:
+
+- Parts can ship or be reviewed independently
+- Different lanes or owners should deliver different parts
+- Risk isolation matters, such as tracer-bullet, feature-flag, or adapter-first rollout
+- The work keeps widening and no longer has a clean stopping point
 
 ---
 
 ## Baseline Heuristics
 
-| Complexity | Files | Tool Calls | Suggested Strategy          |
-| ---------- | ----- | ---------- | --------------------------- |
-| Simple     | <20   | <50        | Single session              |
-| Medium     | 20-50 | 50-100     | Checkpoint and resume       |
-| Complex    | 50+   | 100+       | Decompose or orchestrate    |
-| Oversized  | 100+  | 200+       | Split before implementation |
+| Complexity | Files | Tool Calls | Suggested Strategy                                      |
+| ---------- | ----- | ---------- | ------------------------------------------------------- |
+| Simple     | <20   | <50        | Single session                                          |
+| Medium     | 20-50 | 50-100     | Checkpoint and resume                                   |
+| Complex    | 50+   | 100+       | Orchestrate or split only if the WU is non-atomic       |
+| Oversized  | 100+  | 200+       | Split before implementation unless an exception applies |
 
-These are guardrails, not a license to keep pushing once context is clearly degrading.
+These are guardrails for session strategy, not a license to multiply WUs that still belong together.
 
 ---
 
@@ -28,6 +49,8 @@ Checkpoint and hand off when any of these happen:
 - File churn keeps widening without clear closure
 - You have to repeatedly rediscover the same repo rules
 
+If a trigger fires, first ask whether the WU is still atomic. If yes, checkpoint or hand off. If no, split it.
+
 ---
 
 ## Recovery Pattern
@@ -37,7 +60,7 @@ pnpm mem:checkpoint "state before handoff" --wu WU-XXX
 pnpm wu:brief --id WU-XXX --client codex-cli
 ```
 
-If the WU is clearly too large, split it instead of relying on a heroic handoff.
+Use handoff when the WU is still coherent but the session is getting tired. Split only when the work itself is no longer coherent.
 
 ---
 
@@ -46,3 +69,7 @@ If the WU is clearly too large, split it instead of relying on a heroic handoff.
 Documentation WUs can tolerate broader file counts when the change pattern is shallow and mechanical, but they still need to stay understandable in one session.
 
 If the docs work starts spilling into CLI, core, or packaging changes, treat it like a normal cross-code WU again.
+
+## Shallow Multi-File Exception
+
+Code WUs may also stay as one WU when the change is mechanical across many files, such as a rename or import rewrite, and each file change stays shallow and uniform.