Skip to content

AWR 0.7.0

Choose a tag to compare

@FreeOnePlus FreeOnePlus released this 07 Nov 09:03
6859fcb

AWR 0.7.0 — Project Hub and Project Progress Overview

AWR 0.7.0 brings a local project workspace to the personal CLI/MCP packages.
Find your AWR-managed projects in one place, inspect their progress and dependencies,
and let your Agent keep working through the same CLI/MCP workflow.

Highlights

  • One local project hub: searchable cards ordered by latest AWR use, explicit
    takeover instructions for new projects, and persistent card hiding.
  • Three progress views: project nodes, mainline dependencies and collaboration
    swimlanes, with task details, dependency navigation and bounded graph layouts.
  • Practical inspection: filter and sort every work-table column, switch between
    English and Simplified Chinese, use narrow-screen layouts, and export interactive
    HTML or snapshot JSON.
  • Bundled and recoverable: npm and PyPI include the native web service and its
    assets. CLI/MCP use starts one background instance and restores it after termination.
  • Optional work governance: define goal contribution and acceptance examples,
    review decomposition and admission, and bound reassessment and rework.

Install and open

npm install -g @originoneai/awr@0.7.0
# Or in a Python virtual environment:
python -m pip install originoneai-awr==0.7.0
awr --version
awr-mcp --version
awr overview

Installation alone does not start a process. The first ordinary AWR command
(including awr --version) or Agent connection through the local awr-mcp
automatically starts the background service. After that, visit
http://127.0.0.1:7381 directly; awr overview is a browser shortcut.
If that port is occupied, AWR selects another loopback port. Use
awr overview status --json to find the actual URL. Recovery first tries the
previously recorded port, and concurrent callers reuse the running instance.

Prebuilt payloads support macOS 15+ Apple Silicon and Intel, Linux x64/arm64
with glibc 2.39+, and Windows x64. npm launchers require Node 22.14+; Python
launchers require Python 3.9+. Keep npm optional dependencies enabled.

Project Hub and progress views

Discovery recognizes existing AWR projects; ordinary Git repositories and package
manifests do not enroll new projects. Dated Codex working directories, caches,
dependencies and generated artifacts are excluded. Additional workspace roots can
be configured explicitly. Incomplete scans expose their coverage and errors.

Take over project accepts an existing absolute directory and creates a pending
card with Agent guidance. It does not initialize or rewrite that project. Delete
hides a card across scans and restarts; taking over the same directory restores it.
The list scans on service startup or an explicit Refresh projects, without a
60-second polling loop. Search operates on the loaded cards.

Each project opens with a fresh, coherent snapshot of its recorded SQLite state.
Refresh map rereads that state; Sync project sources explicitly imports
source-file changes. The page distinguishes recorded-state observation from source
verification. Unreported, unavailable and unknown values remain explicit.

The previous Inspector is replaced by Project Progress Overview. The legacy
tools/inspector source path moves to tools/project-progress-overview; Team
observation and its bridge belong to the separate Observer workspace. Native
Hub views use default display grouping. Custom --map-config remains an option
of the source Node viewer.

See the Hub guide and
progress viewer guide.

Work governance and continuity

  • Optional work definitions connect intent,
    goal contribution, responsibility, examples and test discrimination.
  • Opt-in plan admission,
    controlled decomposition,
    gaps, reassessment and
    findings bind decisions to the relevant work and
    current facts. A non-blocking finding can be deferred without reopening work.
    Existing projects without governance retain their ordinary flow.
  • Bounded action guidance states its condition,
    basis, next action and recheck trigger. Readiness, execution authorization,
    context completeness and completion remain separate results.
  • A versioned assessment advice policy
    can reduce optional advice and order supported reason codes without weakening
    hard guards. The read-only outcome history library
    reports recorded outcomes and missing observations without inventing quality
    scores or cost savings; it has no public CLI command yet.
  • Optional claim policy supplies default lifetimes
    and renewal on recorded activity. Source-terminal work releases stale claims
    when safely reconcilable; awr doctor repair finished-work offers a previewed
    cleanup for existing backlog.
  • awr work complete --end-session closes a session after durable completion.
    Completion/cancellation also returns bounded close-out guidance when applicable.
  • Specification references associate
    YAML work with explicit requirements. awr spec check reports missing, changed
    or contradictory bindings without inferring coverage.
  • New project:// registrations can bind the authored project external_key.
    Legacy project:/// locators remain readable; an explicit mismatched identity
    is refused before opening the file. CLI sensitive-argument errors retain safe
    categories, argument positions and repair guidance without echoing values.

Upgrade and rollback

The canonical installation names are now @originoneai/awr and
originoneai-awr. The product is AWR; commands remain awr / awr-mcp.
Remove the previous package before installing the new one, using the
package migration steps.
Old published versions remain available under their original names.

From 0.6.0, the project database remains SQLite schema 14. Stop existing writers
and the local Hub, then back up the project database with SQLite's backup API,
configuration, registered sources, old binaries and the per-user Hub state directory.
Install the new version and run awr source reindex once to refresh changed
projections, then inspect awr status and awr overview.

The Hub catalog upgrades to version three on a write and preserves explicit
takeover intent. Older catalog writers reject that version. Rollback needs the
matching per-user Hub backup as well as the project/runtime snapshot; preserve
post-upgrade history separately. Upgrades from 0.5.x still require schema 7 → 14.
See the installation and upgrade guide.

Availability and limits

This is a personal CLI/MCP release. The packages contain awr, awr-mcp,
the local Hub and PPO assets. Shared Team model code is compiled in but Team
entry points remain off by default. awr-server, the Team PostgreSQL service,
authenticated Team collaboration and Observer are outside the packaged promise.

The Hub binds to local loopback. Responsive layouts support narrow windows; they
do not establish cross-device access. Default progress snapshots cover at most
1,000 graph nodes, 100 goals and 100 active sessions, with a 256 MiB in-memory
snapshot limit. Truncation and unavailable data must be read as limitations, not
as complete project coverage.

The five-platform workflow verifies native behavior and real npm/Python installs,
including the bundled service and assets. The aggregate manifest binds the source
SHA and the eleven package files; GitHub carries the same packages plus the manifest
and checksums. These checks do not certify every Agent host or Team business scenario.

Special thanks

A heartfelt thank you to @LuJiu01, @shishenshashen, @zhouhanx, @ixzc, @ngchichi and @FreeOnePlus for contributing code, reviews, issue reports and release work since 0.6.0. Your contributions helped shape the personal release and the wider AWR project.

Full changelog: v0.6.0...v0.7.0