AIWG v2026.3.2 — Service Release

Release date: 2026-03-04 Type: Service release (bug fixes + dev workflow improvements)

Summary

This service release fixes three bugs in the `aiwg index` multi-graph subsystem introduced in v2026.3.1, and upgrades `--use-dev` so it now delegates the full CLI to your local build — not just framework content deployment.

What's Fixed

`aiwg index` without `--graph` now works

`stats`, `query`, and `deps` all failed with "No artifact index found" when called without `--graph`. The root cause was the same in all three: they checked for `.aiwg/.index/metadata.json` (the legacy pre-multi-graph path), which no longer exists. The index now lives in graph subdirectories:

.aiwg/.index/
├── project/       ← .aiwg/ artifacts
└── codebase/      ← src/, test/, tools/

All three commands now check graph subdirectories first, then fall back to the legacy root for backward compatibility.

Before:

$ aiwg index stats --json
Error: No artifact index found.
Run 'aiwg index build' first to create the index.

After:

{
  "project": { "totalArtifacts": 495, "coverage": { "percentage": 100 } },
  "codebase": { "totalArtifacts": 496, "coverage": { "percentage": 100 } }
}

`--use-dev` now delegates the full CLI

Previously `--use-dev` only changed where `aiwg use` read framework content from. The CLI binary itself still ran the npm-installed code, so changes to TypeScript files like `src/artifacts/stats.ts` had no effect until you ran `npm install -g .`.

Now when dev mode is active, the `aiwg` entry point dynamically imports `src/cli/facade.mjs` from your dev repo, making all commands run your local build:

# One-time setup (point at your local repo)
aiwg --use-dev /path/to/ai-writing-guide
# or from inside the repo:
aiwg --use-dev .

# Make changes, build, test immediately
npm run build
aiwg index stats   # runs local code
aiwg use sdlc      # deploys from local source

# Switch back
aiwg --use-stable

Also fixed: `--use-dev` previously hardcoded the npm package root as the dev path. It now accepts an explicit path argument.

What's New

Framework graph

You can now index the AIWG framework source (`agentic/code/`, `docs/`):

aiwg index build --graph framework
# Indexed 1,625 artifacts in 669ms

aiwg index stats --graph framework --json
# { "totalArtifacts": 1625, "graphMetrics": { "totalEdges": 890 } }

aiwg index query "artifact discovery" --graph framework --json

The framework graph is intentionally excluded from the default `aiwg index build` since it covers shared/global content. Build it explicitly when you need to navigate the framework source.

Multi-graph architecture documented

`docs/cli-reference.md` now covers the full multi-graph architecture:

• Graph types table (project, codebase, framework)
• `--graph` flag on all index subcommands
• Updated output structure paths
• Cross-graph default behavior for each command

Upgrade

npm update -g aiwg
aiwg version
# 2026.3.2

References

• Fixes #425 — `aiwg index stats` no-graph failure
• Issue #426 — Extensible graph types (future work)
• `src/artifacts/stats.ts` — multi-graph stats aggregation
• `src/artifacts/query-engine.ts` — cross-graph search
• `src/artifacts/dep-graph.ts` — merged dependency traversal
• `bin/aiwg.mjs` — dev mode CLI delegation
• `src/channel/manager.mjs` — `switchToDev()` path handling