AWR 0.3.0

GitHub에서 소스 보기

AWR 0.3.0 adds a stable host integration contract and source-preserving editing. Applications can use the native CLI to manage project work while Markdown/YAML remains authoritative and AWR retains execution history and checkpoints.

Install

npm install -g @originoneai/agent-work-runtime@0.3.0
# or, in a Python virtual environment
python -m pip install agent-work-runtime==0.3.0

Both packages provide awr and awr-mcp. npm uses the latest channel. Prebuilt targets are macOS 15+ arm64, Linux x64 with glibc 2.39+, and Windows x64. The npm launcher requires Node 22.14+; the Python launcher requires Python 3.9+. Embedded native binaries run without either language runtime.

Changes since 0.2.0

  • Host capability negotiation, exact project-intake previews, source configuration receipts and complete paginated object catalogs.
  • External execution references, deduplicated lifecycle checkpoints and explicit recovery checks, plus incremental source changes with retirement and failure semantics.
  • Source-preserving YAML field editing and bounded Markdown table/checklist editing, stable draft creation, batch imports and reversible logical archival.
  • Registered Markdown document editing and new drafts; explicit decision adoption and supersession tied to reviewed content versions.
  • Human saves and reviewed AI changes with stable request identities, source fingerprint checks and queryable outcomes. Related multi-file edits retain recoverable phases and report partial application explicitly.
  • Explicit ordinary-work completion policies distinguish user confirmation and business checks from engineering verification. Existing strict projects keep their completion requirements.
  • Immutable native host bundles with source identities, checksums and license notices, plus an isolated matched upgrade/rollback rehearsal.

See the host contract and host example for request shapes and supported adapter limits. Unsupported or ambiguous source structures remain read-only.

Upgrade from 0.2.0

The database schema advances from 3 to 4 to represent draft work. Preserve the original project directory, source mapping and project identity. Before opening an existing project with 0.3.0, stop its writers and retain a consistent snapshot of the previous executable, original sources, configuration and complete runtime history. AWR refreshes projections from registered sources; runtime history is not reconstructible from those sources alone.

Older executables reject schema 4. Rolling back requires the matching program, runtime, configuration and source snapshot, with review of any later source changes. Follow the matched upgrade and rollback procedure.

Release scope

This is a software package release. Installation and native CLI/MCP checks cover the listed platforms. Application UI integration, signing/notarization and acceptance through a particular native agent client remain host-specific work. Package checksums and the source commit are recorded in the release manifest; Apache-2.0 and applicable dependency notices accompany the native payloads.