Skip to content

v2026.8.9

Choose a tag to compare

View all tags
@jmagly jmagly released this 15 Aug 16:31
· 155 commits to main since this release
v2026.8.9
This tag was signed with the committer’s verified signature.
jmagly Joseph Magly
GPG key ID: 839584D0E25E5126
Verified
Learn about vigilant mode.
80ec389
This commit was signed with the committer’s verified signature.
jmagly Joseph Magly
GPG key ID: 454C68C4A2174CE9
Verified
Learn about vigilant mode.

AIWG 2026.8.9 - Prompt-first docs and verified setup

Release date: 2026-08-15
Channel: stable

AIWG 2026.8.9 updates the public website, documentation, setup flow, and
distribution-trust planning around a simpler operating contract: people install
and repair AIWG directly, while agents and scripts handle deeper capability
routing. It also advances the aiwg use deployment path so the command can
deploy, index, regenerate context, and verify that a project is ready.

What changed

  • Public docs keep advanced discovery and orchestration commands in the
    dedicated docs/cli/ corpus. User-facing pages keep install and repair
    commands visible, and describe deeper workflows as natural-language prompts
    plus stable asset IDs.
  • The website release work exposes generated Pagenary content through the
    main site design, including blog and release-history pages that can paginate
    larger result sets without URL or filter oddities.
  • aiwg use composes deployment, capability indexing, canonical context
    generation, and scoped verification into one command. Human output reports a
    concise readiness result; JSON output emits the aiwg.use.result.v1 envelope.
  • The Devin Desktop provider selector is available as a tested selector:
    devin is preferred,
    devin-desktop remains equivalent, windsurf remains a compatibility alias,
    and the distinct devin-cli surface is still rejected explicitly.
  • Issue authoring assesses final drafts before tracker mutation, preserves
    safe drafts, gates flagged drafts, and splits deterministically separable
    rejected drafts into linked atomic issues.
  • AIWG accepted the cross-asset authenticity research contract: DSSE plus
    in-toto Statement envelopes, exact-byte digest rules, publisher delegation,
    rotation and revocation policy, verifier outcomes, JSON Schemas, conformance
    vectors, and a phased implementation roadmap.
  • Deployment verification distinguishes real failures from advisory-only
    limitations and preserves machine-readable JSON on failure paths.
  • The default aiwg use report separates copied provider artifacts from
    the authoritative framework inventory indexed for discovery, suppressing
    registry scan chatter unless verbose diagnostics are requested.
  • AIWG's active release configuration and npm release-plan sidecar now match
    the current schema and pre-tag CI contract. Schema-validated public examples
    keep that dogfood path covered in clean clones as well as maintainer
    workspaces with an attached project artifact corpus.
  • The web build advances to Vite 6.4.3 and refreshes its locked Babel, Nano ID,
    and PostCSS dependencies, leaving the web workspace with no reported npm
    audit vulnerabilities and an unchanged production bundle.
  • Provider deployment defaults now enforce the compact kernel-and-quickref
    skill profile. Codex repairs stale full-copy deployments without removing
    operator-owned skills, and every supported provider exercises the same
    default, opt-in full-copy, and repair conformance checks.
  • Release version checks now include the Cockpit package and both of its
    lockfile version fields, keeping all three published npm packages aligned.
  • Release and documentation-sync workflows now resolve the effective artifact
    corpus with aiwg artifacts path, preventing split-root workspaces from
    recreating release state or reports in the local control-plane directory.
  • Canonical component documentation has been reconciled with the collected
    public corpus so subsequent documentation builds remain deterministic.

Verification

The release candidate must pass version and marketplace lockstep validation,
TypeScript, production builds, generated public-docs checks, audience and CLI
surface audits, Fortemi discovery gates, automated unit and UAT suites, hosted
CI, signed-tag verification, and post-publication checks for release assets,
checksums, npm packages, and installer surfaces.

Package matrix

aiwg@2026.8.9
@aiwg/cli@2026.8.9
@aiwg/cockpit@2026.8.9

Upgrade

Use npm to install the aiwg package at version 2026.8.9.

For the lightweight signed-web distribution:

Use npm to install the @aiwg/cli package at version 2026.8.9.

After upgrading, ask your coding agent to deploy AIWG for the provider you use
and verify that the project is engaged. Operators who prefer direct CLI checks
can use aiwg doctor --deployment and aiwg status --probe --json.

Rollback

Roll all three npm packages back together to 2026.8.8, then redeploy the
project's provider assets and regenerate its context files.

Assets 2
Loading