@lumenflow/cli 5.7.17 → 5.7.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lumenflow/cli",
-  "version": "5.7.17",
+  "version": "5.7.18",
   "description": "Command-line interface for LumenFlow workflow framework",
   "keywords": [
     "lumenflow",
@@ -201,16 +201,16 @@
     "xstate": "^5.28.0",
     "yaml": "^2.8.2",
     "zod": "^4.3.6",
-    "@lumenflow/initiatives": "5.7.17",
-    "@lumenflow/agent": "5.7.17",
-    "@lumenflow/control-plane-sdk": "5.7.17",
-    "@lumenflow/core": "5.7.17",
-    "@lumenflow/host": "^5.7.17",
-    "@lumenflow/memory": "5.7.17",
-    "@lumenflow/kernel": "5.7.17",
-    "@lumenflow/packs-software-delivery": "^5.7.17",
-    "@lumenflow/metrics": "5.7.17",
-    "@lumenflow/packs-agent-runtime": "^5.7.17"
+    "@lumenflow/agent": "5.7.18",
+    "@lumenflow/kernel": "5.7.18",
+    "@lumenflow/control-plane-sdk": "5.7.18",
+    "@lumenflow/core": "5.7.18",
+    "@lumenflow/initiatives": "5.7.18",
+    "@lumenflow/host": "^5.7.18",
+    "@lumenflow/memory": "5.7.18",
+    "@lumenflow/metrics": "5.7.18",
+    "@lumenflow/packs-agent-runtime": "^5.7.18",
+    "@lumenflow/packs-software-delivery": "^5.7.18"
   },
   "devDependencies": {
     "@vitest/coverage-v8": "^4.0.18",

package/packs/agent-runtime/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@lumenflow/packs-agent-runtime",
-  "version": "5.7.17",
+  "version": "5.7.18",
   "description": "Agent runtime pack scaffold for LumenFlow — governed model-turn execution, pack config, and provider capability baselines",
   "keywords": [
     "lumenflow",

package/packs/sidekick/package.json

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

package/packs/software-delivery/package.json

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

package/templates/core/ai/onboarding/existing-project-bootstrap.md.template

@@ -45,6 +45,23 @@ pnpm lumenflow --client <claude-code | cursor | windsurf>
 
 At this point `workspace.yaml` exists but is **untracked**. This is the trap.
 
+### Existing LumenFlow Projects: Upgrade First
+
+If the project already has LumenFlow files and package dependencies, do not reinstall or
+manually edit dependency versions. Run the managed upgrade command from the integration
+checkout:
+
+```bash
+pnpm lumenflow:upgrade --latest
+```
+
+After upgrade, `package.json` and `pnpm-lock.yaml` should contain the published
+`@lumenflow/*` packages managed by the command, with `@lumenflow/cli` as the CLI
+entrypoint. The old unscoped `lumenflow` wrapper is private/internal and should not
+remain in consumer dependencies or lockfile entries. If the command reports a
+non-fatal `NPM_TOKEN` config warning, set the token for private registry access or
+remove the stale placeholder from `.npmrc`; a successful install is still valid.
+
 ---
 
 ## Step 2: Commit the Baseline Before `lane:setup`

package/templates/core/ai/onboarding/wu-create-checklist.md.template

@@ -9,11 +9,16 @@ Use this checklist before running `pnpm wu:create`.
 ## Step 1: Confirm the Lane
 
 ```bash
+pnpm lane:setup --template react-vite   # or nextjs | node-cli | fastify
+pnpm lane:validate
+pnpm lane:lock
 pnpm lane:status
 pnpm wu:infer-lane --paths "packages/@lumenflow/cli/src/init.ts" --desc "Fix init docs drift"
 ```
 
-The lane should match the real implementation scope, not just the first file you noticed.
+Omit `--template` when you want LumenFlow to infer the stack from `package.json` and visible
+directories. The lane should match the real implementation scope, not just the first file you
+noticed.
 
 ---
 
@@ -33,17 +38,28 @@ The lane should match the real implementation scope, not just the first file you
 
 `--id` is optional. If omitted, `wu:create` allocates the next WU ID automatically.
 
+For `--exposure ui`, include concrete reachability evidence. User-flow features should use
+`navigation_path`, a page route in `code_paths`, or manual wording like
+`"Open /settings and verify ..."`. UI infrastructure/theme WUs can instead use manual wording like
+`"Run pnpm dev at http://localhost:3000 and confirm the component/theme state"`.
+
 ---
 
 ## Step 3: Decide Plan Storage
 
-If the work needs a plan, prefer repo-native or `lumenflow://plans/` references:
+If the work needs a plan, prefer repo-native `lumenflow://plans/` references:
 
 ```bash
 pnpm plan:create --id INIT-XXX --title "Plan title"
 pnpm wu:create --lane "Framework: CLI" --title "..." --plan
 ```
 
+Generated WU plans live in the repository plans directory
+(`software_delivery.directories.plansDir`, default `{{DOCS_OPERATIONS_PATH}}/plans`) so
+the same WU number can exist in separate projects without colliding. Older
+plans under `$LUMENFLOW_HOME/plans` still resolve as a compatibility fallback,
+but new WU work should use repo-local plans.
+
 Avoid pointing `--spec-refs` at random local filesystem notes that other agents cannot resolve.
 
 ---