wayfind 2.0.26 → 2.0.28

package/bin/team-context.js

@@ -14,7 +14,7 @@ if (!HOME) {
   process.exit(1);
 }
 
-const WAYFIND_DIR = path.join(HOME, '.claude', 'team-context');
+const WAYFIND_DIR = process.env.WAYFIND_DIR || path.join(HOME, '.claude', 'team-context');
 
 // --- Env var migration shim (v2.0.0) ---
 // Honor old MERIDIAN_* env vars with deprecation warning. Remove in v3.0.
@@ -4550,8 +4550,15 @@ const COMMANDS = {
       }
       let newVersion = '';
       try {
-        const pkg = require(path.join(ROOT, 'package.json'));
-        newVersion = pkg.version;
+        // After npm install, ROOT still points to the old code in memory.
+        // Resolve the freshly installed package path from npm global root.
+        const globalRoot = spawnSync('npm', ['root', '-g'], { stdio: 'pipe' });
+        const freshPkgPath = path.join((globalRoot.stdout || '').toString().trim(), 'wayfind', 'package.json');
+        if (fs.existsSync(freshPkgPath)) {
+          newVersion = JSON.parse(fs.readFileSync(freshPkgPath, 'utf8')).version;
+        } else {
+          newVersion = require(path.join(ROOT, 'package.json')).version;
+        }
       } catch (e) {
         // Can't read package.json
       }
@@ -4668,17 +4675,18 @@ const COMMANDS = {
   version: {
     desc: 'Print installed Wayfind version',
     run: () => {
-      const versionFile = path.join(HOME, '.claude', 'team-context', '.wayfind-version');
+      // Primary: read from package.json (always accurate after npm install)
       try {
-        const version = fs.readFileSync(versionFile, 'utf8').trim();
-        console.log(`Wayfind v${version}`);
-      } catch (err) {
-        // Fall back to package.json version if no installed version file
+        const pkg = require(path.join(ROOT, 'package.json'));
+        console.log(`Wayfind v${pkg.version}`);
+      } catch (e) {
+        // Fallback: cached version file (may be stale after update)
+        const versionFile = path.join(HOME, '.claude', 'team-context', '.wayfind-version');
         try {
-          const pkg = require(path.join(ROOT, 'package.json'));
-          console.log(`Wayfind v${pkg.version} (from package.json)`);
-        } catch (e) {
-          console.error('Version unknown (no .wayfind-version file found)');
+          const version = fs.readFileSync(versionFile, 'utf8').trim();
+          console.log(`Wayfind v${version}`);
+        } catch (err) {
+          console.error('Version unknown');
           process.exit(1);
         }
       }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wayfind",
-  "version": "2.0.26",
+  "version": "2.0.28",
   "description": "Team decision trail for AI-assisted development. The connective tissue between product, engineering, and strategy.",
   "bin": {
     "wayfind": "./bin/team-context.js"

package/templates/autopilot/strategy.md

@@ -1,6 +1,6 @@
 # Strategy Persona — Autopilot Prompt
 
-You are the Strategy persona for this team. You scan session journals and signal data to surface what a CTO or founder needs to know — and nothing else.
+You are the Strategy persona for this team. You scan session journals and signal data to surface what a CEO or business leader needs to know — and nothing else. Your reader is not an engineer. They think in customers, revenue, competitive position, and team capacity — not code, databases, or issue numbers.
 
 ## Your job
 
@@ -17,7 +17,10 @@ Find the 5 most consequential strategic items from this period. "Consequential"
 - **Each item: bold headline + one sentence of context.** The headline should make someone stop scrolling. The context sentence connects the dots — why this pattern matters at the company level.
 - **Include the "so what?"** Don't just state facts — say what's at risk strategically or what opportunity is being missed.
 - **Skip anything routine.** If it's business as usual, it's not digest-worthy.
-- **Reference specifics** — repos, team patterns, data points, timelines.
+- **Reference specifics** — team patterns, data points, timelines, customer impact.
+- **No engineering jargon.** Translate technical details into business language. "The data pipeline
+  is blocked" not "ODBC driver compilation fails in the container." No issue numbers, no repo
+  names, no library names. If you can't explain it without jargon, it's probably not strategic.
 - **Do not include a title or header line.** The digest system adds its own header.
 
 ## Tone