Skip to content

1.2.0-beta.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@100yenadmin 100yenadmin released this 04 Jul 09:27
v1.2.0-beta.1
6fe9266
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Notes 1.2.0-beta.1

1.2.0-beta.1 is a scoped prerelease checkpoint for Codex-first local orchestration
and the LCO 1.2 prepared-state and summary-leaf sprint. It publishes the
prepared-state OpenClaw gateway dogfood hardening merged after 1.2.0-beta.0.

This release is intentionally on the npm beta channel. It does not promote
latest and it does not claim 1.2 GA.

What Changed

  • Added the prepared-cards-inbox-v1 OpenClaw gateway dogfood scenario as a
    first-class prepared-state handoff proof surface.
  • Hardened loo openclaw tool-smoke agent reasoning so prepared-state evidence
    is internally consistent:
    • prepared inbox, prepared cards, summary expansion, and summary leaves are
      prioritized before earlier search refs in agentReasoning.sourceRefs;
    • prepared-state thread ids win over earlier search/describe hits when a
      prepared inbox/card result is available;
    • expansion metadata binds to loo_summary_expand when summary expansion is
      part of the proof.
  • Added a regression test for mixed search/prepared evidence: search can point
    to one thread while prepared-state cards point to another, and the final
    recommendation must still follow the prepared-state evidence.
  • Updated the local-agent usability scorecard evidence pointer for the prepared
    gateway dogfood proof.
  • Carries forward the #160 desktop proof-action release boundary:
    loo_desktop_proof_action / loo desktop proof-action validates the CUA Driver TextEdit scratch proof gate and does not prove generic GUI mutation.
    The proof action still requires exact backend, target app, target window, action hash, approval ref, permission state, scratch file path, and execute: true before the backend can run.
    Generic gateway invocation without exact proof args fails closed. The desktop proof action keeps the same proof boundary as beta.35.
  • Carries forward strict OpenClaw gateway result handling: plugin output with
    output.details.ok: false is reported as openclaw_tool_result_not_ok:<tool>
    rather than successful tool proof.

Current Claim Scope

Allowed prerelease claim:

Local prepared Codex state and summary-leaf recall for OpenClaw/Eva, including
public-safe prepared cards, prepared inbox items, bounded summary expansion,
and an OpenClaw gateway dogfood smoke that emits an agent recommendation
without raw transcript reads.

Prepared state remains an advisory local derived cache, not source authority
for PR, CI, release, runtime, customer, or business truth.

This release remains focused on local Codex sessions.

Release Gate Notes

  • Parent 1.2 tracker: #405.
  • Release checkpoint issue: #445.
  • Included implementation PR: #444.
  • Baseline stable release: v1.1.4.
  • Candidate package: lossless-openclaw-orchestrator@1.2.0-beta.1.
  • Expected npm dist-tag: beta.
  • Expected git tag: v1.2.0-beta.1.
  • Expected GitHub Release:
    https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO/releases/tag/v1.2.0-beta.1.
  • Required scoped prerelease gates: focused release/tool-smoke tests, npm run check, npm pack --dry-run, prepared-state scenario sweep, scorecard/claim
    audit, GitHub CI, CodeQL, current-head review threads clear, npm publish to
    beta, GitHub prerelease, and post-publish finalization status.
  • Working-app status example:
    loo release status --claim-scope codex-working-app-proof --runtime-proof-dir <path> --approved-live-control-evidence <path> --npm-publish-approval-evidence <path> --github-release-approval-evidence <path> --candidate-sha <sha> --github-ci-evidence <path> --codeql-evidence <path> --evidence-dir <path> --strict
  • Reduced-scope status example:
    loo release status --claim-scope codex-read-search-expand-dry-run --npm-publish-approval-evidence <path> --github-release-approval-evidence <path> --candidate-sha <sha> --github-ci-evidence <path> --codeql-evidence <path> --evidence-dir <path> --strict
  • Post-publish finalization example:
    loo release finalization-status --evidence-dir <path> --candidate-sha <sha> --npm-publish-evidence <path> --git-tag-evidence <path> --github-release-evidence <path> --expected-dist-tag beta --expected-github-prerelease true --strict
  • approved_live_control_smoke_missing remains the expected blocker when a
    working-app or live-control claim is attempted without approved live-control
    smoke evidence for the exact candidate SHA.
  • Bundle/status/finalization checks do not publish to npm and do not create a GitHub Release.

Explicit Non-Claims

No new live Codex control smoke is run by this release.
It does not run generic GUI mutation and does not run Codex GUI mutation.
No automatic gateway authorization.
No broad gateway scope approval. No prompt typing. No clicking. No arbitrary app control.
No screenshots or videos are part of the public release evidence.
Claude Code remains an adapter stub, not an adapter-equivalence claim.
No true Codex compaction-summary capture.
No model compaction proof.
No raw transcript upload and no OpenClaw LCM merge.
No Notion, support-control, Stripe, or Company Brain P1 adapter proof.
No cloud sync.
No unattended desktop takeover.
No npm latest promotion.
No release-grade enterprise security or customer-ready security claim.

Assets 2
Loading