v2026.7.16
AIWG 2026.7.16 - "Workspace context and provider orchestration"
Released: 2026-07-21
Channel: stable (npm install -g aiwg)
AIWG 2026.7.16 makes project context portable across providers, tightens
model-aware orchestration, and expands discovery for operational workflows. It
also separates durable testing guidance from generated execution evidence.
Highlights
- Canonical workspace context — new and existing projects can maintain a
protectedWORKSPACE.mdcontext graph with provider-specific adapters,
conflict-aware migration, credential checks, rollback, and doctor support. - Explicit regeneration modes —
aiwg regenerate --workspacemaintains
the canonical graph,--existing-projectextracts bounded project context,
and--full-injectretains the legacy compatibility path. - Provider-aware orchestration — Steward now emits capability-bound launch
envelopes, validates model-wrapper capabilities, and applies dynamic provider
catalogs and cheap-first role/tier policy consistently. - Operational discovery — procedural Markdown and declarative runbooks are
indexed as first-class assets with structured actions, verification,
rollback, inventory, targets, and step metadata. - Testing evidence hygiene — generated reports, logs, and dashboard state
now live under ignored.aiwg/testing/outputs/; durable plans, protocols,
and deterministic fixtures remain tracked. - Research incorporation portfolio — three routed model wrappers audited
1,901 local research records and identified 155 evidence-graded candidates
for future architecture and implementation work.
Reliability fixes
This release also hardens SDLC skill-first routing, Steward option parsing,
workspace regeneration limits, deployment verification, characterization-test
isolation, flow namespace matching, provider deployment cleanup, and release
discovery coverage.
Upgrade
npm install -g aiwg@latest
cd your-project
aiwg regenerate --workspace --provider codex
aiwg use all --provider codex --verboseReplace codex with the target provider configured for the project. The
regenerate command refreshes WORKSPACE.md, AIWG.md, and the provider's
startup adapter. The use all command redeploys frameworks, kernel skills,
agents, and the three model-aware subagent wrappers for that provider.
For providers with native agent definitions, a successful verbose deployment
prints:
Model wrappers verified: aiwg-model-reasoning-worker, aiwg-model-coding-worker, aiwg-model-efficiency-worker
That verification is part of aiwg use: missing, empty, stale, or incorrectly
pinned wrappers fail an unfiltered deployment. Providers without a native
per-agent model surface report the applicable inherited, global, or
informational policy instead of claiming an exact pin. Restart the provider
session after deployment so it reloads the refreshed kernel and agent files.
Existing projects can preview bounded context extraction with
aiwg regenerate --existing-project --dry-run before applying it. Projects
that need the previous inline behavior can continue using
aiwg regenerate --full-inject.