v0.2.0b2 — Verified learning loop beta

v0.2.0b2 — First verify. Then learn.

v0.2.0b2 is a beta release of Morpheus's source-grounded truth layer and
local experimental learning path. It does not claim stable-release maturity or
evidence from broader real-repository use.

Highlights

• Reviewed active state now uses
  morpheus-active-state-review-authority/1: only exact reviewed
  candidate-to-claim and evidence bindings can authorize active-state datasets.
  Ordinary compile and wake receipts remain integrity records and cannot
  authorize learning.
• The adapter benchmark uses morpheus-benchmark-categories/1 with canonical
  coverage for product identity, commands and CLI behavior, architecture,
  safety rules, team conventions, stale-claim correction, and unsupported
  claim refusal.
• morpheus learn team-loop and POST /learning/team-loop share the
  morpheus-team-learning/2 reviewed-input contract for PR comments, rejected
  agent claims, human corrections, accepted review candidates, check results,
  and stale-claim corrections. New correction candidates remain pending.

Safety Boundaries

No accepted source span means no training example.

No eval pass means no adapter activation.

No rollback means no production activation.

Adapters never activate automatically. Pending, rejected, stale, inferred-only,
secret-like, and ignored claims do not become positive training facts. Cloud integrations remain opt-in. Adapter output is not the source of truth.

Install Or Upgrade

Pin the beta package explicitly:

uvx --from 'morpheus-wake==0.2.0b2' morpheus wake . --private

Or use pipx:

pipx run --spec 'morpheus-wake==0.2.0b2' morpheus wake .

Replace an earlier beta pin with morpheus-wake==0.2.0b2. Unpinned installers
may choose a stable release instead of this beta.

Local Gates

Run the local quality and provenance gates before relying on a project state:

ruff check .
pytest tests/ -q
morpheus wake . --private
morpheus verify --all

These gates verify repository state and receipt integrity; they do not authorize
adapter activation without the separate reviewed dataset, paired eval, readiness,
and rollback requirements.