Skip to content

v0.8.0

Choose a tag to compare

@github-actions github-actions released this 16 Jul 12:34
bd382a5

LoopCoder v0.8.0

v0.8.0 is the public native Darwin arm64 release. It includes multi-provider,
routing, nested-run, progress, waiter, detached-execution, and migration
building blocks. Its exact archive passed the documented publication,
integrity, deterministic smoke, and v0.7 migration gates. A later product-path
audit found that several orchestration building blocks are not connected end
to end or proven with real providers, so use v0.8.0 for controlled canary and
development work rather than unattended production orchestration.

The binding distinction between implemented code, reachable commands,
deterministic coverage, real-provider evidence, and production support is in
the
v0.8.0 capability and support matrix.

Platform Support

LoopCoder v0.8.0 supports native macOS Apple Silicon (darwin/arm64) only.
Windows, Linux/Ubuntu, WSL, containers used as a LoopCoder runtime, Intel
macOS, and Rosetta/amd64 macOS are unsupported and receive no v0.8 artifact,
native CI, smoke, or compatibility commitment. v0.7.0 remains the final legacy
multi-platform release for those users.

The release publishes one binary archive:

loopcoder_0.8.0_darwin_arm64.tar.gz

SHA256SUMS and its Sigstore bundle accompany that archive. This verifies
checksum provenance and archive integrity. The v0.8.0 Mach-O is not Apple
Developer ID signed or notarized, so this release does not provide Gatekeeper
trust.

Highlights

  • Provider intelligence infrastructure: bounded provider/account
    discovery, dynamic model capability catalogs, supported quota telemetry,
    optional CodexBar evidence, and a conservative local usage ledger. Inventory
    is diagnostic evidence, not proof of authentication or usable capacity.
  • Routing contracts: deterministic task requirements, capability
    eligibility, quota/reset-aware scoring, typed fallback, independent-verifier
    policy, and hierarchical budget records exist. Ordinary unpinned dispatch
    still defaults directly to Codex; automatic routing is not supported.
  • Grok integration: the grok worker provider, dynamic model inventory,
    bounded ACP billing when advertised and allowed, and native-agent capability
    probing without auto-install, auto-update, or login behavior.
  • Nested-run infrastructure: durable parent/child registrations, depth,
    fan-out, concurrency, permission, budget, cancellation, and one-writer
    records support deterministic fixtures. No real-provider nested execution
    mode is supported in v0.8.0.
  • Durable execution: non-interactive work defaults to detached supervision;
    provider PID, process group, birth identity, owner, and generation fence
    ps, status, kill, recovery, and Darwin guardian behavior.
  • Durable progress without model polling: five-minute receipt, outbox, and
    restartable waiter components persist local evidence without provider calls.
    The local CI waiter is connected; unsolicited host delivery and the other
    production waiter integrations are not supported.
  • Bounded orchestration cost: per-run calls, tokens when known, waiting,
    recovery, delivery, and verification overhead are measured and gated.
  • Auditable migration: migrate storage plans without side effects,
    verifies an owner-only v0.7 backup, atomically applies schema 9 through 30,
    and reports stable rollback limitations.

Upgrade From v0.7.0

On native Darwin arm64:

loopcoder upgrade --version 0.8.0
loopcoder version
loopcoder migrate storage --format json
loopcoder migrate storage --apply --format json
loopcoder skill install --repo .
loopcoder projects register --repo .
loopcoder doctor --repo . --format json

The storage command is plan-only unless --apply is present. Stop all
LoopCoder processes before migration or rollback. The apply path creates and
verifies one owner-only schema-9 backup before the write transaction; replay on
schema 30 returns no-op.

Backup And Rollback

Do not point a v0.7.0 binary at the migrated schema-30 database. To roll back:

  1. stop every LoopCoder process;
  2. retain the migrated database as evidence;
  3. copy, never move or mutate, the verified migration backup into an offline
    rollback home;
  4. select the published v0.7.0 binary; and
  5. run loopcoder doctor --repo . against the restored home.

Rollback discards v0.8-only state created after migration. The exact procedure
and stable limitation codes are in
docs/reference/storage-migration.md.

Completed Publication Gates

The immutable v0.8.0 tag resolves to
bd382a5bcc7e20ae29e239b43d896a1b25796d59. Publication completed after:

  • required verify, test, race, and security checks;
  • the complete repository race suite in the release build;
  • signed checksum and staged-archive identity verification;
  • fresh install, v0.7 upgrade, migration, rollback, self-bootstrap, and release
    smoke on pinned Darwin arm64;
  • zero open release blockers;
  • the protected release-publication environment approval; and
  • a completed v0.8.0 go/no-go report.

Those gates establish the published artifact's identity, integrity, migration
behavior, and deterministic release smoke. They did not include protected
exact-artifact Codex/Claude product-path canaries or Apple notarization, and do
not override the capability matrix.

Known Limitations

  • Automatic Worker routing, routed Verifier independence, typed fallback, and
    quota-reset waiting are not connected product paths. Explicitly pinned
    provider use is canary-only.

  • The accepted nested read-only path does not enforce mutation-free behavior
    inside the Worker adapter. Production-provider write and orchestrate modes
    are refused. Do not use real providers with nested run in v0.8.0.

  • Durable receipts do not prove unsolicited live visibility in the initiating
    host. Approval, outbox, and detached-terminal waiters are not fully wired.

  • Protected exact-v0.8.0 Codex and Claude canaries are absent. Grok and
    Antigravity have deterministic adapter coverage but no release-gated live
    canary.

  • The binary is not Apple Developer ID signed or notarized. The installer can
    place a binary in a custom directory, but its PATH/profile guidance assumes
    the default directory.

  • Exact quota and reset behavior is available only when a supported, fresh
    machine-readable source exposes it. Unavailable evidence is not guessed.

  • Antigravity has no verified read-only mode and therefore cannot run
    loopreview; direct gemini remains experimental.

  • Grok model and billing evidence depends on capabilities exposed by the local
    Grok CLI and explicit network permission.

  • Detached supervision is machine-local and does not replace the human
    conductor or production publication gate.