AIWG 2026.8.0 - Secure external jobs and operational intelligence

AIWG 2026.8.0 - Secure external jobs and operational intelligence

Released: 2026-08-01 Channel: stable

AIWG 2026.8.0 opens the August release line with a durable, auditable way to run bounded provider jobs from external schedulers. It also expands session intelligence, promotes Fortemi full-v1 interoperability, adds reusable design theme operations, and hardens Cockpit and dependency boundaries.

External-trigger single-shot jobs

The new `aiwg job` surface lets cron, systemd timers, or Gitea Actions own time while AIWG owns the reviewed execution contract:

aiwg job validate path/to/job.yaml
aiwg job render-cron path/to/job.yaml --format systemd
aiwg job run path/to/job.yaml --once

The `jobs.aiwg.io/v1` contract describes the provider executor, Gitea work source, approval policy, and required completion evidence. Codex execution receives its prompt on stdin and writes a structured result. Stable idempotency keys, host locks, cross-host claim election, approval rechecks, and completion markers prevent duplicate external actions.

Runtime records are private, bounded, and redacted. External targets require exact allowed origins and accounts, and attachment paths must resolve beneath approved canonical roots. Publication remains approval-gated by default.

Session and artifact intelligence

  • Session import and reindex maintain one versioned, content-free analytics

index with stable citations for authorized forensic views.

  • `sessions analytics` provides filtered operational facts, while explicitly

authorized `sessions forensics` emits sanitized timelines without executing or exporting historical provider payloads.

  • Fortemi shard export now defaults to the `full-v1` receipt contract and binds

producer, converter, and consumer evidence. Legacy core-only output remains available through an explicit compatibility mode.

Design and automation clarity

  • The media-marketing framework adds a theme manager, schemas, candidate and

comparison templates, cross-channel adaptation guidance, and design QA workflows.

  • Provider capability reporting and automation documentation now distinguish

external scheduling from AIWG orchestration. AIWG generates or validates the bounded job; the external scheduler owns the clock.

Security and reliability

  • Cockpit no longer places reusable launch material in URLs and keeps scoped

handoff state out of history, referrer, UI, and routine logging surfaces.

  • Cockpit live acceptance waits for runtime re-adoption, observes the expected

transient disconnect, and records the executor-reported version.

  • The static server uses the fixed Hono node-server v2 line and rejects encoded

Windows backslashes before filesystem resolution.

  • Production dependency floors advance across Hono, MCP SDK, js-yaml, ws,

yaml, glob/minimatch, and routed validator dependencies while retaining the minimum-release-age supply-chain policy.

Package matrix

All three packages publish in CalVer lockstep:

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

Upgrade

Full local-corpus distribution:

npm install --global [email protected]

Lightweight signed-web distribution:

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

Install or refresh Cockpit through the base CLI:

aiwg use cockpit
aiwg cockpit

Rollback

Roll back all three packages together to `2026.7.25`. Existing external-job flow files are inert unless an external scheduler invokes them, so disable the corresponding cron, timer, or workflow before rolling back a deployed job.