AIWG 2026.8.19 - Scoped graph links, complete index visibility

Release date: 2026-08-24 Channel: stable

AIWG 2026.8.19 tightens the artifact index around the way people actually write and inspect project context. Markdown links between indexed artifacts now show up as graph edges, global graphs declared in user configuration appear in `aiwg index stats`, and symlinked artifact directories are counted consistently by both build and coverage paths.

This is a small release, but it removes a few blind spots that made the graph harder to trust. If the index says a graph has no edges, no global entries, or missing coverage, that result should reflect the project, not a scanner shortcut.

What this changes for you

Markdown links can show scoped relationships

Relative Markdown links between indexed artifacts now create typed `markdown-link` edges in the dependency graph. This lets normal reader-facing navigation contribute to graph traversal when the linked target is part of the same active graph.

The scope is intentionally narrow. External URLs, anchor-only links, image links, and paths that resolve outside the active graph do not create edges. @-mentions remain the durable syntax for traceability and provenance; Markdown-link edges represent local document navigation.

Inspect the result with:

aiwg index build
aiwg index graph --json
aiwg index stats

`aiwg index stats` now reports the Markdown-link edge count when the current index was built with this extractor version.

Global graph stats match default builds

Graphs declared in the user AIWG config and marked for default build now load before `aiwg index stats` reports aggregate or single-graph results. That means the stats output includes those global graphs instead of only project-local graphs.

Coverage uses the global graph's configured scan roots, so the reported indexed count and total file count are calculated over the same source set. Explicit-build user roots still stay out of default aggregate stats unless the operator builds or selects them intentionally.

Symlinked artifact directories are no longer invisible

Artifact discovery now follows symlinked and junctioned directories, while tracking real directories to avoid cycles. Broken links are skipped without failing the scan.

This matters for split-root and shared-corpus setups where a project links to a common artifact directory. Build and coverage now see the same linked files, and an unknown graph name fails explicitly instead of quietly falling back to the project graph.

Release reliability

The GitHub trusted-publishing workflow now preserves Git workspace trust after its isolated checkout step. This keeps follow-on npmjs.org release steps from failing because the working tree lost its safe-directory registration.

Package matrix

[email protected]
@aiwg/[email protected]
@aiwg/[email protected]

Upgrade

Upgrade the package set together, then regenerate provider context:

npm install --global [email protected]
npm install --global @aiwg/[email protected]
npm install --global @aiwg/[email protected]
aiwg regenerate

After upgrading, rebuild artifact indexes that should include Markdown-link edges:

aiwg index build

Rollback

Roll all three npm packages back together to `2026.8.18`, then regenerate provider context. Indexes built with `2026.8.19` remain readable, but older extractors will not add new Markdown-link edge metadata until the index is rebuilt again on `2026.8.19` or later.