v2026.5.2

Previous release

AIWG v2026.5.2 — Tester-report sweep, kernel issue/PR skills, config-driven release flow

Released: 2026-05-11 Channel: stable (`npm install -g aiwg`) Previous: v2026.5.1 Pipeline: this release is the first to dogfood the new `flow-release` skill — driven mechanically by `.aiwg/release.config` rather than by hand-walking the prose checklist.

What's in it

This release lands a multi-commit fix sweep driven by an external tester report (`sebuh-infsol` on `jmagly/aiwg#108–#112`), plus the infrastructure changes that came out of taking that report seriously: kernel skills for filing issues and PRs, a config-driven release flow, and a doctor gate that catches discovery-surface degradation before it confuses an agent.

If you only read one line: every bug `sebuh-infsol` reported on May 11 is fixed, the release process is now an executable spec, and filing high-quality issues/PRs is now a kernel skill instead of a wiki page.

Headline changes

`aiwg steward` works end-to-end

Two stacked bugs blocked `aiwg steward capabilities` for any user not in a dev-mode source checkout:

1. Path resolution — the handler walked a fixed number of `..` segments from its compiled location, landing inside `dist/` instead of the package root where `agentic/` ships. 2. Schema mismatch — the handler read a schema (`provider.capabilities[id].native_tool`, `matrix.baseline`, etc.) that didn't exist in the YAML.

Both fixed. The canonical types in `src/providers/capability-matrix.ts` are now the single source of truth, and feature names accept both hyphenated (`agent-teams`) and underscored (`agent_teams`) forms.

$ aiwg steward capabilities --provider claude-code
  Provider: Claude Code (claude-code)
  Status:   stable
  Daemon:   native (+ pty-adapter)
  ─────────────────────────────────
  cron — ✓ native
    Scheduled task execution (recurring triggers)
  ...

Slash invocations on Claude finally deterministic

Pre-release, `/aiwg-refresh --dry-run` in a Claude Code session would invoke the instructional skill, which asked for Bash permissions repeatedly and churned. Two fixes converge:

`.claude/commands/aiwg-refresh.md` (and `aiwg-doctor`, `aiwg-status`, `aiwg-help`, `aiwg-regenerate`, `aiwg-issue`, `aiwg-pr`) deploy automatically with `aiwg use`. Slash invocations route to the deterministic CLI.
The kernel skills now carry `script:` frontmatter pointing at `run.sh` entrypoints, so `aiwg run skill aiwg-refresh -- <flags>` works on every platform.

`aiwg regenerate` is a real CLI command

Context-only regen of `AIWG.md` + `AGENTS.md` without redeploying frameworks. Faster than `aiwg refresh` when context drift is the only thing you need to fix.

$ aiwg regenerate --dry-run
◆ aiwg regenerate  (dry run)
  Provider: claude
  Target:   /your/project

  Would regenerate:
    - /your/project/AIWG.md
    - /your/project/AGENTS.md

  Dry run complete — no changes made

Kernel skills for filing issues and PRs

Two new always-loaded kernel skills put the filing-guidance in your agent's context, no docs lookup required:

`aiwg-issue` — template selection, environment capture, duplicate detection, the cross-tracker import flow.
`aiwg-pr` — delivery-policy compliance (direct vs feature-branch vs pr-required), the no-attribution rule, the verification gate, CI-green-before-done.

Companion `steward-prep-delivery` skill bundles a duplicate-detection helper that searches both `aiwg discover` and the configured Gitea tracker before you file.

For humans, the same guidance is at `docs/contributing/filing-issues.md` and `docs/contributing/filing-pull-requests.md`. Templates at `.gitea/ISSUE_TEMPLATE/` and `.github/ISSUE_TEMPLATE/`.

Config-driven release flow

The `flow-release` skill is a portable gate-runner. What gates exist, in what order, hard-stop or warn-only — all declared in `.aiwg/release.config` rather than hardcoded.

AIWG's own config declares 7 gates:

1. local-build-test — typecheck, unit tests, build, UAT (stable only) 2. ci-green — poll Gitea actions on the release commit 3. doc-sync — invoke `doc-sync` skill with code-to-docs direction, guidance scoped to `agentic/**/*.md` + `docs/**/*.md` 4. changelog-and-announcement — `CHANGELOG.md` section + announcement doc must exist (stable only) 5. readme-freshness — diff-against-`latest-stable` prompt (soft gate) 6. release — tag, push origin, push GitHub mirror, npm dist-tag 7. post-release — close imported issues with thanks; create release entries

Any project can author its own `.aiwg/release.config` from the schema at `agentic/code/frameworks/sdlc-complete/schemas/flows/release-config.yaml`.

Doctor surfaces discovery degradation

`aiwg doctor` now smoke-probes four discovery-kernel commands:

✓ Discovery: aiwg discover: `aiwg discover doctor --json --limit 1` succeeded
✓ Discovery: aiwg show: `aiwg show skill aiwg-doctor` succeeded
⚠ Discovery: aiwg index: aiwg index pipeline unavailable — project-local artifact index may be missing
✓ Discovery: aiwg runtime-info: `aiwg runtime-info --check aiwg` succeeded

Each is a warning (not a hard fail), because doctor must work even on a partially installed system. But a degraded discovery surface is now legible before an agent tries to use it.

Six other CLI fixes

`aiwg runtime-info --discover` — `mkdir -p` parent dir before write (no more ENOENT on a fresh project)
`aiwg new <name> --help` — no longer scaffolds a project as a side effect
`aiwg catalog list/search` — JSON data files now ship in `dist/`
Three import-path fixes (`workspace-migrate.mjs`, `optimize-prompt.mjs`, `diversify-content.mjs`) — all corrected to `dist/src/...` per the tsc `rootDir=.` layout
Doctor no longer recommends the unimplemented `aiwg install-skill-seekers` (the integration is intact via `doc-intelligence` + `skill-factory` addons)

Installation

# Stable
npm install -g aiwg

# Verify
aiwg version           # 2026.5.2 [stable]
aiwg doctor            # workspace health check
aiwg discover release  # finds flow-release

If you're upgrading from `2026.5.1`, just `aiwg refresh` to redeploy with the new kernel skills and command stubs.

Try the new skills

# Filing issues
aiwg show skill aiwg-issue
aiwg run skill steward-prep-delivery -- "your search terms"

# Filing PRs
aiwg show skill aiwg-pr

# Running a release (in your own project)
aiwg show skill flow-release
# (writes .aiwg/release.config from the schema if absent)

# Regenerating context files only
aiwg regenerate --dry-run

Migration notes

`aiwg install-skill-seekers` was never an actual CLI command. The skill-authoring surface is the `skill-factory` addon — `aiwg use skill-factory`.
The Release Checklist in `CLAUDE.md` is preserved for browsability but is now annotated as "mechanically driven by `flow-release`."
The kernel-skill count grew from 6 → 9 (added `aiwg-regenerate`, `aiwg-issue`, `aiwg-pr`); the `aiwg-utils-quickref` and `CLAUDE.md` self-maintenance sections reflect the new total.

Acknowledgements

This release exists because `@sebuh-infsol` filed five high-quality issues with full reproductions and suggested fixes on the GitHub mirror (`jmagly/aiwg#108–#112`). Every one of those reports turned into a discrete fix landing in this version. The import flow you can see in `docs/contributing/filing-issues.md` was codified directly from how those reports were handled.

Thank you.