AIWG 2026.8.27 - Qualified storage scale-out

AIWG 2026.8.27 - Qualified storage scale-out

Release date: 2026-08-28

Channel: stable

AIWG 2026.8.27 turns the shared-server storage path into an evidence-backed
release surface. PostgreSQL and PostgREST now have executable qualification
jobs and versioned reference results, storage migrations must prove semantic
parity before cutover, and every artifact-index backend follows the same
ordering and pagination contract. The release also restores the fully
templated tracker response for address-issues cycles.

What this changes for you

Shared-server claims are tied to current evidence

Dedicated CI jobs obtain short-lived PostgreSQL and PostgREST runtime
configuration from Vault, exercise the live server adapters, and produce
reports that declare the environment and scope they actually tested. Published
reference evidence lets reviewers reproduce the supported claims, while
release gates reject stale or incomplete benchmark evidence.

This separates measured behavior from assumptions: local SQLite, direct
PostgreSQL, and PostgREST results each identify their own qualification surface.

Migrations prove meaning, not only row movement

The migration protocol now checks logical identities, snapshot and replay
integrity, tombstones, revisions, digests, parity, cutover approval, and
rollback readiness. A copied record set is not sufficient when relationships,
deletions, or revisions differ at the destination.

Index behavior is portable across backends

Graphology, JSON, and SQLite artifact indexes now use deterministic traversal
ordering and common cursor semantics. Consumers can paginate without backend-
specific ordering surprises, and the golden conformance corpus protects that
contract.

Address-issues comments retain the complete cycle record

Native goal and resume paths now use one canonical AL CYCLE renderer and
validator. Before a tracker comment is posted, the flow checks that the
templated status, work details, evidence, verification results, and continuation
state are present.

Package matrix

aiwg@2026.8.27
@aiwg/cli@2026.8.27
@aiwg/cockpit@2026.8.27

Upgrade

Run aiwg refresh to update through the installation method recorded for the
current machine and redeploy installed frameworks. Keep all three managed
packages on 2026.8.27. Source checkouts should update through their normal Git
workflow, build, and then run aiwg refresh --skip-update.

Rollback

Pin aiwg, @aiwg/cli, and @aiwg/cockpit to 2026.8.26 with the same
package manager used for installation, then run aiwg regenerate so deployed
provider context matches the restored version. For a storage deployment, use
the migration's recorded rollback plan and receipt; do not reverse a cutover by
changing package versions alone.

Release boundaries

• Shared-server reference evidence covers only its declared PostgreSQL and
  PostgREST versions, configuration, topology, and workload. It is not a
  general performance guarantee for other environments.
• Migration cutover remains approval-bound and requires a deployment-specific
  rollback plan. Passing qualification does not authorize unattended
  production migration.
• Vault-backed CI validates runtime configuration and live qualification while
  keeping protected values outside the release artifacts.