aiwg 2026.5.0 → 2026.5.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aiwg",
-  "version": "2026.5.0",
+  "version": "2026.5.1",
   "description": "Deployment tool and support utility for AI context. Copies agents, skills, commands, rules, and behaviors into the paths each AI platform reads (Claude Code, Codex, Copilot, Cursor, Warp, OpenClaw, and 4 more) so one source of truth works across 10 platforms. Optional utilities for persistent artifact memory, background orchestration, autonomous loops, and artifact indexing.",
   "type": "module",
   "bin": {

package/tools/cli/doctor.mjs

@@ -9,7 +9,14 @@ import os from 'os';
 import path from 'path';
 import { execSync } from 'child_process';
 import chalk from 'chalk';
-import { getFrameworkRoot, getVersionInfo } from '../../src/channel/manager.mjs';
+// Import from dist/ — the npm package ships compiled code under dist/, NOT
+// the source tree. Importing from `../../src/channel/manager.mjs` works in
+// dev (src/ exists at repo root) but breaks on npm-installed users with
+// "Cannot find module 'src/channel/manager.mjs'". This script is invoked
+// from within the AIWG package root by `dist/src/cli/handlers/utilities.js`
+// doctorHandler, so `../../dist/src/channel/manager.mjs` resolves correctly
+// in both dev (after `npm run build:cli`) and in `npm install -g aiwg`.
+import { getFrameworkRoot, getVersionInfo } from '../../dist/src/channel/manager.mjs';
 
 // AIWG_ROOT: env override > channel-manager resolved path > legacy edge path
 // getFrameworkRoot() resolves correctly for npm global installs, edge, and dev channels.

package/tools/cli/update.mjs

@@ -14,12 +14,14 @@
  */
 
 import { execSync } from 'child_process';
+// Import from dist/ (see tools/cli/doctor.mjs for the rationale — npm
+// package ships dist/, not src/).
 import {
   loadConfig,
   switchToNext,
   switchToNightly,
   switchToStable,
-} from '../../src/channel/manager.mjs';
+} from '../../dist/src/channel/manager.mjs';
 
 // Parse --channel <value> from argv
 function parseChannel(args) {

package/tools/cli/validate-writing.mjs

@@ -10,11 +10,20 @@ import { readdir, stat } from 'fs/promises';
 import { join, extname, resolve } from 'path';
 import { existsSync } from 'fs';
 
-// Note: In production, import from compiled dist/
-// For development, you may need to compile TypeScript first
-const enginePath = process.env.NODE_ENV === 'production'
-  ? '../../../dist/writing/validation-engine.js'
-  : '../../src/writing/validation-engine.js';
+// Resolve the validation engine path, preferring dist/ (always present in
+// the npm package) and falling back to src/ for dev environments without a
+// compiled build. The previous NODE_ENV gate broke npm-installed users
+// because NODE_ENV is not set to "production" by `npm install -g aiwg`.
+// Same class of bug as `tools/cli/doctor.mjs` (#1250). For a fully
+// general resolver, see _resolve-impl.mjs (future work — config-var
+// approach tracked separately).
+import { fileURLToPath } from 'url';
+import { dirname } from 'path';
+const __filename = fileURLToPath(import.meta.url);
+const __dirname = dirname(__filename);
+const distEnginePath = resolve(__dirname, '../../dist/writing/validation-engine.js');
+const srcEnginePath = resolve(__dirname, '../../src/writing/validation-engine.js');
+const enginePath = existsSync(distEnginePath) ? distEnginePath : srcEnginePath;
 
 let WritingValidationEngine;
 try {

package/tools/cli/version.mjs

@@ -8,7 +8,9 @@
  * @issue #685
  */
 
-import { getVersionInfo } from '../../src/channel/manager.mjs';
+// Import from dist/ (see tools/cli/doctor.mjs for the rationale — npm
+// package ships dist/, not src/).
+import { getVersionInfo } from '../../dist/src/channel/manager.mjs';
 
 const args = process.argv.slice(2);
 const json = args.includes('--json');