v1.2.5

Release Notes 1.2.5

1.2.5 is a GA-assurance release-captain patch for the LCO 1.2 stable
train. It keeps the 1.2 claim boundary unchanged and adds the aggregate-only
loo release ga-smoke command so release evidence can be checked as one
public-safe go/no-go packet.

This remains Codex-first local orchestration.

What Changed

• Adds loo release ga-smoke --package-version <version> --candidate-sha <sha> --evidence-dir <dir> --strict.
• Aggregates existing release reports instead of running hidden release actions:
  release status, release finalization status, published package smoke,
  OpenClaw dogfood, OpenClaw tool smoke, scenario sweep, scorecard sweep,
  release preflight, release bundle, and privacy scan.
• Emits one lco.release.gaSmoke.v1 packet with P0-P2 blockers, setup
  blockers, warnings, deferred/non-action statements, sanitized evidence refs,
  recovery commands, and explicit no-action proof fields.
• Fails closed when evidence is missing, mismatched to the package version or
  candidate SHA, unsafe, outside the evidence directory, or carrying raw
  transcript/SQLite/screenshot/token-style artifacts.
• Keeps fresh-profile OpenClaw setup blockers separate from package defects.
  --allow-setup-required only passes when setup blockers are explicit and
  configured-gateway proof is clean.
• Keeps legacy release-status evidence compatible when it predates embedded
  candidateSha, while mismatched embedded SHA evidence still fails closed.
• Updates README, VISION, claim audit, and release runbooks to include the GA
  smoke gate.

Current Claim Scope

Claim scope: codex-read-search-expand-dry-run.

Allowed stable claim:

Collaborate with local Codex sessions through OpenClaw using local indexing,
prepared-state recall, bounded expansion, and approval-gated dry-run/control
boundaries.

This release adds release-captain aggregation only. It does not broaden the
runtime, control, GUI, Claude, customer, or enterprise-security proof boundary.

Carried-Forward Desktop Proof Boundary

The Desktop proof-action hardening from #160 is still included. The public tool
surface includes loo_desktop_proof_action and the CLI command
loo desktop proof-action, but they remain bounded to the same proof boundary as beta.35: a CUA Driver TextEdit scratch proof only. The exact tuple is:
exact backend, target app, target window, action hash, approval ref, permission state, scratch file path, and execute: true.

A generic gateway invocation without exact proof args fails closed. The expected
OpenClaw failure shape is openclaw_tool_result_not_ok:<tool> with
output.details.ok: false; it is not proof of generic GUI mutation.

Release Gate Notes

• Parent 1.2 tracker: #405.
• GA assurance tracker: #478.
• GA smoke aggregator issue: #502.
• Patch release issue: #511.
• Baseline stable release: v1.2.4.
• Candidate package: lossless-openclaw-orchestrator@1.2.5.
• Expected npm dist-tag: latest.
• Expected git tag: v1.2.5.
• Example aggregate GA smoke gate:
  loo release ga-smoke --package-version 1.2.5 --candidate-sha <sha> --evidence-dir <public-safe-evidence> --strict.
• Example release status with all required non-GUI approvals: loo release status --candidate-sha <sha> --github-ci-evidence <ci.json> --codeql-evidence <codeql.json> --approved-live-control-evidence <live-control.json> --npm-publish-approval-evidence <npm-approval.json> --github-release-approval-evidence <github-release-approval.json> --strict.
• Reduced-scope read/search/expand/dry-run status example: loo release status --claim-scope codex-read-search-expand-dry-run --candidate-sha <sha> --github-ci-evidence <ci.json> --codeql-evidence <codeql.json> --npm-publish-approval-evidence <npm-approval.json> --github-release-approval-evidence <github-release-approval.json> --strict.
• Working-app or live-control claim attempts without exact approved live-control proof must continue to report approved_live_control_smoke_missing.
• loo release ga-smoke writes release-ga-smoke.json; it does not publish to npm, does not create tags, does not create a GitHub Release, does not run live Codex control, does not mutate a desktop GUI, and does not read raw transcripts.
• Required stable gates: focused GA smoke tests, full npm run check, package
  dry-run, GitHub CI, CodeQL, current-head review threads clear, npm publish to
  latest, GitHub Release, post-publish finalization status, fresh npm install,
  OpenClaw dogfood/tool-smoke, scenario/scorecard sweeps, privacy scan, and
  final loo release ga-smoke --strict.

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 raw model compaction by default and no default model access to raw transcript
or current safe_text.
No raw transcript upload and no OpenClaw LCM merge.
No source-store mutation.
No Notion, support-control, Stripe, or Company Brain P1 adapter proof.
No cloud sync.
No unattended desktop takeover.
No release-grade enterprise security or customer-ready security claim.

v1.2.4

Release Notes 1.2.4

1.2.4 is a GA-assurance privacy hygiene patch for the LCO 1.2 stable train.
It keeps the 1.2 claim boundary unchanged and fixes a public-safe rendering gap
found during the M11 launch packet pass.

What Changed

• Redacts local absolute paths from loo expand-query, loo expand-ref, and
  expandSession human-readable expansion text.
• Keeps relative project paths visible where they are already public-safe, while
  replacing local /Volumes/..., /Users/..., .codex, and tmp-style paths
  with <redacted-path>.
• Keeps exact touched-file metadata in the local index for matching and recall;
  only the rendered expansion text is sanitized.
• Updates bounded expansion snapshots and regression tests so future releases
  fail if expansion evidence leaks local absolute paths.
• Carries forward the 1.2.3 recursive evidence scanner hardening for nested raw
  artifacts, SQLite sidecars, symlinked evidence entries, and deep evidence
  trees.
• Clarifies launch-truth wording from 1.2.0/1.2.3 to the current 1.2.4
  stable patch line.

Current Claim Scope

Claim scope: codex-read-search-expand-dry-run.

Allowed stable claim:

Collaborate with local Codex sessions through OpenClaw using local indexing,
prepared-state recall, bounded expansion, and approval-gated dry-run/control
boundaries.

When finalization evidence proves this candidate on the stable channel, the
scoped prepared-state and cockpit-management surface is ready as a public
local-Codex release. It does not broaden the control, GUI, Claude, customer, or
enterprise-security proof boundary.

This remains a Codex-first local orchestration release.

Carried-Forward Desktop Proof Boundary

The Desktop proof-action hardening from #160 is still included. The public tool
surface includes loo_desktop_proof_action and the CLI command
loo desktop proof-action, but they remain bounded to the same proof boundary as beta.35: a CUA Driver TextEdit scratch proof only. The exact tuple is:
exact backend, target app, target window, action hash, approval ref, permission state, scratch file path, and execute: true.

A generic gateway invocation without exact proof args fails closed. The expected
OpenClaw failure shape is openclaw_tool_result_not_ok:<tool> with
output.details.ok: false; it is not proof of generic GUI mutation.

Release Gate Notes

• Parent 1.2 tracker: #405.
• GA assurance tracker: #478.
• Path-redaction issue: #508.
• Hygiene patch issue: #506.
• Baseline stable release: v1.2.3.
• Candidate package: lossless-openclaw-orchestrator@1.2.4.
• Expected npm dist-tag: latest.
• Expected git tag: v1.2.4.
• Example reduced-scope release preflight:
  loo release preflight --claim-scope codex-read-search-expand-dry-run --evidence-dir <public-safe-evidence> --strict.
• Example release status with all required non-GUI approvals:
  loo release status --candidate-sha <sha> --github-ci-evidence <ci.json> --codeql-evidence <codeql.json> --approved-live-control-evidence <live-control.json> --npm-publish-approval-evidence <npm-approval.json> --github-release-approval-evidence <github-release-approval.json> --strict.
• Reduced-scope release status may keep approved_live_control_smoke_missing
  only when --claim-scope codex-read-search-expand-dry-run is explicit and
  live Codex control is recorded as excluded.
• Required stable gates: focused path-redaction tests, full npm run check,
  release preflight/bundle/status, npm pack --dry-run, GitHub CI, CodeQL,
  review threads clear, npm publish to latest, GitHub Release, post-publish
  finalization status, fresh npm install, OpenClaw dogfood/tool-smoke,
  scenario/scorecard sweeps, and privacy scan.
• loo release bundle prepares public-safe local artifacts; it does not publish to npm and does 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 raw model compaction by default and no default model access to raw transcript
or current safe_text.
No raw transcript upload and no OpenClaw LCM merge.
No source-store mutation.
No Notion, support-control, Stripe, or Company Brain P1 adapter proof.
No cloud sync.
No unattended desktop takeover.
No release-grade enterprise security or customer-ready security claim.

LCO 1.2.3

Release Notes 1.2.3

1.2.3 is the GA-assurance hygiene patch for the LCO 1.2 stable train and Codex-first local orchestration. It fixes the recursive release-evidence scan gap found during M11 adversarial review and keeps the 1.2 claim boundary unchanged.

This release is focused on local Codex sessions. Prepared state remains an advisory local derived cache, not source authority for PR, CI, release, runtime, customer, or business truth.

What Changed

• Fixes loo release preflight raw-artifact detection so it scans nested evidence folders instead of only immediate files in --evidence-dir.
• Adds recursive detection for SQLite sidecars such as .sqlite-wal, .sqlite-shm, .sqlite3-wal, .sqlite3-shm, .db-wal, and .db-shm.
• Skips symlinked evidence entries and reports evidence_scan_depth_exceeded
  when an evidence tree is too deep to scan deterministically.
• Keeps raw artifact findings public-safe by reporting relative evidence names and blocker reasons, not raw artifact contents.
• Sanitizes the M11 final evidence packet by removing generated clean-profile runtime HOME/prefix artifacts while preserving public-safe summary reports.
• Carries forward the 1.2.2 readiness-smoke semantics clarification: ok / packagePathOk are package-path claims, while publishedSmokeReady is the clean-profile gateway-ready claim.
• Carries forward --gateway-ready-strict so operators and CI can explicitly fail when a fresh published profile still needs gateway credentials or device setup.
• Carries forward the hardened loo release general-readiness proof-boundary label so an unexpected package version string cannot inject uncontrolled text into the public proof boundary.
• Carries forward the frozen readinessSemantics metadata object emitted by published-smoke, keeping machine-readable exit semantics stable for release scripts and audits.
• Carries forward the 1.2.1 facade smoke fix for resume dry-run proof, including the distinction between resume packets and message-carrying send/steer packets.
• 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 stable claim:

Collaborate with local Codex sessions through OpenClaw using local indexing,
prepared-state recall, bounded expansion, and approval-gated dry-run/control
boundaries.

The stable channel means the scoped prepared-state and cockpit-management
surface is ready as a public local-Codex release. It does not broaden the
control, GUI, Claude, customer, or enterprise-security proof boundary.

Release Gate Notes

• Parent 1.2 tracker: #405.
• GA assurance tracker: #478.
• Hygiene patch issue: #506.
• Previous patch-release issue: #503.
• Readiness-semantics issue: #494.
• Patch PRs: #499, #505, and the 1.2.3 release PR.
• Baseline stable release: v1.2.2.
• Candidate package: lossless-openclaw-orchestrator@1.2.3.
• Expected npm dist-tag: latest.
• Expected git tag: v1.2.3.
• Required stable gates: focused release-smoke tests, release claim audit,
  build/typecheck, npm pack --dry-run, release bundle/status checks, GitHub
  CI, CodeQL, current-head review threads clear, npm publish to latest,
  GitHub Release, and post-publish finalization status.
• Bundle/status/finalization dry-run checks do not publish to npm and will not create a GitHub Release.
• 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
• 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.

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 raw model compaction by default and no default model access to raw transcript
or current safe_text.
No raw transcript upload and no OpenClaw LCM merge.
No source-store mutation.
No Notion, support-control, Stripe, or Company Brain P1 adapter proof.
No cloud sync.
No unattended desktop takeover.
No release-grade enterprise security or customer-ready security claim.

v1.2.2

Release Notes 1.2.2

1.2.2 is a patch release for the LCO 1.2 stable train and Codex-first local orchestration.
It publishes the readiness-smoke semantics clarification from
#494 / #499 to the npm latest channel without widening the 1.2 claim
boundary.

This release is focused on local Codex sessions. Prepared state remains an
advisory local derived cache, not source authority for PR, CI, release,
runtime, customer, or business truth.

What Changed

• Clarifies loo openclaw published-smoke strictness semantics:
  ok / packagePathOk are package-path claims, while
  publishedSmokeReady is the clean-profile gateway-ready claim.
• Adds --gateway-ready-strict so operators and CI can explicitly fail when a
  fresh published profile still needs gateway credentials or device setup.
• Documents the combined --strict plus --gateway-ready-strict behavior:
  either a package-path failure or clean-profile gateway-readiness failure exits
  non-zero.
• Hardens the public loo release general-readiness proof-boundary label so an
  unexpected package version string cannot inject uncontrolled text into the
  public proof boundary.
• Freezes the readinessSemantics metadata object emitted by
  published-smoke, keeping machine-readable exit semantics stable for
  release scripts and audits.
• Carries forward the 1.2.1 facade smoke fix for resume dry-run proof, including
  the distinction between resume packets and message-carrying send/steer
  packets.
• 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 stable claim:

Collaborate with local Codex sessions through OpenClaw using local indexing,
prepared-state recall, bounded expansion, and approval-gated dry-run/control
boundaries.

The stable channel means the scoped prepared-state and cockpit-management
surface is ready as a public local-Codex release. It does not broaden the
control, GUI, Claude, customer, or enterprise-security proof boundary.

Release Gate Notes

• Parent 1.2 tracker: #405.
• GA assurance tracker: #478.
• Patch-release issue: #503.
• Readiness-semantics issue: #494.
• Patch PRs: #499 and the 1.2.2 release PR.
• Baseline stable release: v1.2.1.
• Candidate package: lossless-openclaw-orchestrator@1.2.2.
• Expected npm dist-tag: latest.
• Expected git tag: v1.2.2.
• Required stable gates: focused release-smoke tests, release claim audit,
  build/typecheck, npm pack --dry-run, release bundle/status checks, GitHub
  CI, CodeQL, current-head review threads clear, npm publish to latest,
  GitHub Release, and post-publish finalization status.
• Bundle/status/finalization dry-run checks do not publish to npm and will not create a GitHub Release.
• 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
• 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.

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 raw model compaction by default and no default model access to raw transcript
or current safe_text.
No raw transcript upload and no OpenClaw LCM merge.
No source-store mutation.
No Notion, support-control, Stripe, or Company Brain P1 adapter proof.
No cloud sync.
No unattended desktop takeover.
No release-grade enterprise security or customer-ready security claim.

v1.2.1

Release Notes 1.2.1

1.2.1 is a patch release for the LCO 1.2 prepared-state sprint and
Codex-first local orchestration. It publishes the OpenClaw facade dogfood fix
from #497 / #498 to the stable npm latest channel without widening the 1.2
claim boundary.

This release is focused on local Codex sessions. Prepared state remains an
advisory local derived cache, not source authority for PR, CI, release,
runtime, customer, or business truth.

What Changed

• Fixes the OpenClaw facade smoke validator so loo_codex_resume_thread
  dry-run proof accepts the actual resume packet shape: live: false,
  approvalAuditId, paramsHash, method: "thread/resume", and
  action: "codex_resume_thread".
• Keeps message hashes required for message-carrying send/steer dry-run
  proofs such as loo_codex_control_dry_run with turn/start or
  turn/steer.
• Adds regression coverage proving resume dry-run proof does not require a
  message hash while send-message dry-runs still fail closed without one.
• Carries forward additive prepared-state storage for source events, source
  ranges, summary leaves, summary edges, prepared cards, watcher observations,
  hook capture packets, and state-prep jobs.
• Carries forward deterministic summary leaves from user prompts, proposed
  plans, finals, closeout envelopes, touched-file metadata, tool-call metadata,
  and compaction markers while ignoring huge raw tool-call payloads by default.
• Carries forward bounded summary expansion with source ranges, max-depth and
  max-node limits, cycle rejection, and explicit omission markers.
• Carries forward prepared cards and prepared inbox routing with freshness,
  confidence, privacy class, source coverage, authority coverage, and
  stale/partial/unknown downgrades.
• Carries forward persisted watcher observations and an execute-false local
  attention queue for safe advisory automation.
• Carries forward hook sidecar commands for closeout capture, state prep, and
  compaction marker capture without opening transcript paths by default.
• Carries forward OpenClaw gateway dogfood coverage for the prepared-state
  workflow.
• Carries forward optional local model compaction spike gates and a
  Codex-native compaction-summary capture proposal without claiming true native
  capture.
• Carries forward semantic lifecycle states for prepared cards and prepared
  inbox routing: completed, blocked_missing_info, waiting_approval,
  watching_external_check, needs_resume, dirty_worktree_handoff,
  ready_for_review, stale_or_partial, and unknown_lifecycle.
• Carries forward the shared core lifecycle registry, MCP tool schema,
  OpenClaw plugin manifests, and OpenClaw gateway smoke validation.
• Carries forward deterministic lifecycle reason codes, lifecycle-aware next
  actions, and urgency ranking for advisory prepared cards.
• Carries forward the completed-card summary counter so finished lanes remain
  visible in prepared-card summaries.
• Carries forward lifecycle classification hardening so generic words such as
  resume, monitor, and ci do not become lifecycle states without
  operator-action context.
• Carries forward completed prepared-card target coverage so a fresh public
  completed card counts as target coverage ok and does not make
  loo_prepared_state_status report stale/partial coverage for a fully
  materialized completed lane.
• Carries forward stale, partial, unknown, unsafe-row, and stale-freshness
  downgrades for incomplete or unsafe prepared-state evidence.
• 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 stable claim:

Local prepared Codex state and summary-leaf recall for OpenClaw/Eva, including
semantic prepared-card lifecycle routing, prepared inbox prioritization,
bounded summary expansion, visible Codex sidebar inventory, hook sidecar
foundations, watcher observations, and approval-gated start-thread proof
packets without raw transcript reads.

The stable channel means the scoped prepared-state and cockpit-management
surface is ready as a public local-Codex release. It does not broaden the
control, GUI, Claude, customer, or enterprise-security proof boundary.

Release Gate Notes

• Parent 1.2 tracker: #405.
• GA assurance tracker: #478.
• Patch-release issue: #500.
• Facade dogfood bug: #497.
• Patch PRs: #498 and the 1.2.1 release PR.
• Baseline stable release: v1.2.0.
• Candidate package: lossless-openclaw-orchestrator@1.2.1.
• Expected npm dist-tag: latest.
• Expected git tag: v1.2.1.
• Required stable gates: focused OpenClaw tool-smoke tests, release claim
  audit, build/typecheck, npm pack --dry-run, release bundle/status checks,
  GitHub CI, CodeQL, current-head review threads clear, npm publish to
  latest, GitHub release, and post-publish finalization status.
• Bundle/status/finalization dry-run checks do not publish to npm and do not create a GitHub Release.
• 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
• 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.

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 raw model compaction by default and no default model access to raw transcript
or current safe_text.
No raw transcript upload and no OpenClaw LCM merge.
No source-store mutation.
No Notion, support-control, Stripe, or Company Brain P1 adapter proof.
No cloud sync.
No unattended desktop takeover.
No release-grade enterprise security or customer-ready security claim.

1.2.0

Release Notes 1.2.0

1.2.0 is the first stable release for the LCO 1.2 prepared-state sprint and
Codex-first local orchestration. It promotes the scoped beta.3 work to the
stable npm latest channel after the 1.2 tracker, cockpit epic, release
finalization, and public-claim gates closed cleanly.

This release is focused on local Codex sessions. Prepared state remains an
advisory local derived cache, not source authority for PR, CI, release,
runtime, customer, or business truth.

What Changed

• Adds additive prepared-state storage for source events, source ranges,
  summary leaves, summary edges, prepared cards, watcher observations, hook
  capture packets, and state-prep jobs.
• Adds deterministic summary leaves from user prompts, proposed plans, finals,
  closeout envelopes, touched-file metadata, tool-call metadata, and compaction
  markers while ignoring huge raw tool-call payloads by default.
• Adds bounded summary expansion with source ranges, max-depth and max-node
  limits, cycle rejection, and explicit omission markers.
• Adds prepared cards and prepared inbox routing with freshness, confidence,
  privacy class, source coverage, authority coverage, and stale/partial/unknown
  downgrades.
• Adds persisted watcher observations and an execute-false local attention queue
  for safe advisory automation.
• Adds hook sidecar commands for closeout capture, state prep, and compaction
  marker capture without opening transcript paths by default.
• Adds OpenClaw gateway dogfood coverage for the prepared-state workflow.
• Adds optional local model compaction spike gates and a Codex-native
  compaction-summary capture proposal without claiming true native capture.
• Adds semantic lifecycle states for prepared cards and prepared inbox routing:
  completed, blocked_missing_info, waiting_approval,
  watching_external_check, needs_resume, dirty_worktree_handoff,
  ready_for_review, stale_or_partial, and unknown_lifecycle.
• Exposes the lifecycle state enum through the shared core registry, MCP tool
  schema, OpenClaw plugin manifests, and OpenClaw gateway smoke validation.
• Adds deterministic lifecycle reason codes, lifecycle-aware next actions, and
  urgency ranking for advisory prepared cards.
• Adds a completed-card summary counter so finished lanes remain visible in
  prepared-card summaries.
• Tightens lifecycle classification so generic words such as resume,
  monitor, and ci do not become lifecycle states without operator-action
  context.
• Fixes completed prepared-card target coverage so a fresh public completed card
  counts as target coverage ok and does not make loo_prepared_state_status
  report stale/partial coverage for a fully materialized completed lane.
• Preserves stale, partial, unknown, unsafe-row, and stale-freshness downgrades
  for incomplete or unsafe prepared-state evidence.
• 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 stable claim:

Local prepared Codex state and summary-leaf recall for OpenClaw/Eva, including
semantic prepared-card lifecycle routing, prepared inbox prioritization,
bounded summary expansion, visible Codex sidebar inventory, hook sidecar
foundations, watcher observations, and approval-gated start-thread proof
packets without raw transcript reads.

The stable channel means the scoped prepared-state and cockpit-management
surface is ready as a public local-Codex release. It does not broaden the
control, GUI, Claude, customer, or enterprise-security proof boundary.

Release Gate Notes

• Parent 1.2 tracker: #405.
• Cockpit tracker: #448.
• Stable promotion issue: #475.
• Included late implementation PRs: #452, #472, and #474.
• Baseline stable release: v1.1.4.
• Prior beta release: v1.2.0-beta.3.
• Candidate package: lossless-openclaw-orchestrator@1.2.0.
• Expected npm dist-tag: latest.
• Expected git tag: v1.2.0.
• Required stable gates: focused prepared-card/OpenClaw tool-smoke tests,
  release claim audit, build/typecheck, npm pack --dry-run, release
  bundle/status checks, GitHub CI, CodeQL, current-head review threads clear,
  npm publish to latest, GitHub release, and post-publish finalization status.
• Bundle/status/finalization dry-run checks do not publish to npm and do not create a GitHub Release.
• 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
• 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.

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 raw model compaction by default and no default model access to raw transcript
or current safe_text.
No raw transcript upload and no OpenClaw LCM merge.
No source-store mutation.
No Notion, support-control, Stripe, or Company Brain P1 adapter proof.
No cloud sync.
No unattended desktop takeover.
No release-grade enterprise security or customer-ready security claim.

1.2.0-beta.3

Release Notes 1.2.0-beta.3

1.2.0-beta.3 is a scoped prerelease checkpoint for Codex-first local orchestration
and the LCO 1.2 prepared-state sprint. It publishes semantic
prepared-card lifecycle routing and the completed-card target coverage follow-up
merged after 1.2.0-beta.2.

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 semantic lifecycle states for prepared cards and prepared inbox routing:
  completed, blocked_missing_info, waiting_approval,
  watching_external_check, needs_resume, dirty_worktree_handoff,
  ready_for_review, stale_or_partial, and unknown_lifecycle.
• Exposed the lifecycle state enum through the shared core registry, MCP tool
  schema, OpenClaw plugin manifests, and OpenClaw gateway smoke validation.
• Added deterministic lifecycle reason codes, lifecycle-aware next actions, and
  urgency ranking for advisory prepared cards.
• Added a completed-card summary counter so finished lanes remain visible in
  prepared-card summaries instead of disappearing from stale/partial/unknown
  counters.
• Tightened lifecycle classification so generic words such as resume,
  monitor, and ci do not become lifecycle states without operator-action
  context.
• Fixed completed prepared-card target coverage so a fresh public completed card
  counts as target coverage ok and does not make loo_prepared_state_status
  report stale/partial coverage for a fully materialized completed lane.
• Preserved stale, partial, unknown, unsafe-row, and stale-freshness downgrades
  for incomplete or unsafe prepared-state evidence.
• 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
semantic prepared-card lifecycle routing, prepared inbox prioritization,
bounded summary expansion, visible Codex sidebar inventory, and
approval-gated start-thread proof packets 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.
• Cockpit tracker: #448.
• Release checkpoint issue: #473.
• Included implementation PRs: #452 and #472.
• Baseline stable release: v1.1.4.
• Prior beta release: v1.2.0-beta.2.
• Candidate package: lossless-openclaw-orchestrator@1.2.0-beta.3.
• Expected npm dist-tag: beta.
• Expected git tag: v1.2.0-beta.3.
• Expected GitHub Release:
  https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO/releases/tag/v1.2.0-beta.3.
• Required scoped prerelease gates: focused prepared-card/OpenClaw tool-smoke
  tests, build/typecheck, npm pack --dry-run, release bundle/status checks,
  GitHub CI, CodeQL, current-head review threads clear, npm publish to beta,
  GitHub prerelease, and post-publish finalization status.
• Bundle/status/finalization checks do not publish to npm and do not create a GitHub Release.
• 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
• 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.

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.

v1.2.0-beta.2

Release Notes 1.2.0-beta.2

1.2.0-beta.2 is a scoped prerelease checkpoint for Codex-first local orchestration
and the LCO 1.2 prepared-state and summary-leaf sprint. It publishes the
visible Codex sidebar inventory and approval-gated start-thread proof hardening
merged after 1.2.0-beta.1.

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

What Changed

• Hardened visible Codex sidebar inventory so generic action rows can expose
  real sidebar child titles while contained private or redacted residual child
  labels are rejected before public candidates are emitted.
• Preserved public-safe visible Codex extraction for already-sanitized bounded
  actionable rows that carry status or freshness signals.
• Added regression coverage for sidebar child-title extraction, duplicate child
  handling, and residual private child suppression.
• Hardened the approval-gated Codex start-thread workflow:
  • thread/start proof states now route callers to the read-only
    loo_codex_start_thread_post_create_proof follow-up packet;
  • caller instructions now explicitly require the bounded post-create proof
    before claiming the new thread completed, persisted, or is safe to build on;
  • post-create proof sends the full created thread id to the bounded
    thread/read metadata probe while keeping public output capped;
  • long created-thread ids no longer create false negative read-probe results.
• Refreshed OpenClaw plugin tool declarations and tool-surface metadata for the
  post-create proof surface.
• 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,
visible Codex sidebar inventory, and approval-gated start-thread proof packets
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: #469.
• Included implementation PRs: #459 and #464.
• Baseline stable release: v1.1.4.
• Candidate package: lossless-openclaw-orchestrator@1.2.0-beta.2.
• Expected npm dist-tag: beta.
• Expected git tag: v1.2.0-beta.2.
• Expected GitHub Release:
  https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO/releases/tag/v1.2.0-beta.2.
• 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.

1.2.0-beta.1

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.

1.2.0-beta.0

Release Notes 1.2.0-beta.0

1.2.0-beta.0 is a prerelease checkpoint for Codex-first local orchestration
over local Codex sessions and the LCO 1.2 prepared-state and summary-leaf
sprint. It publishes the local derived-cache foundations that let OpenClaw/Eva
start from public-safe prepared Codex state before asking for bounded expansion.

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 explicit mutation-family policy for local derived-cache writes, source
  store mutation, external writes, live control, GUI mutation, and release
  publication.
• Added additive prepared-state SQLite tables for source events, source ranges,
  summary leaves, prepared cards, watcher observations, hook capture packets,
  attention queue items, and state-prep jobs.
• Added deterministic summary leaves and bounded loo_summary_expand lineage
  over public-safe source ranges.
• Added prepared cards and deterministic prepared inbox tools:
  loo_prepared_state_status, loo_prepared_cards, and
  loo_prepared_inbox.
• Added persisted watcher observations, execute-false attention queue items,
  and deterministic prep-runner/job surfaces.
• Added hook sidecar capture for closeouts, state prep, and marker-only
  compaction capture. Marker mode records lifecycle boundaries only; it does
  not claim true Codex compaction-summary capture.
• Hardened OpenClaw tool-smoke evidence so public-safe validation failures stay
  bounded and do not echo raw plugin output.
• Added first-class Codex control proof states so transport acceptance is not
  represented as durable orchestration success.
• Improved legacy Codex session discovery recall for historical tool-call
  shapes, exact codex_thread:* refs, bare thread ids, and app-server display
  aliases.
• 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
additive local derived-cache tables, source ranges, deterministic summary
leaves, prepared cards, prepared inbox items, watcher observations,
marker-only hook capture, public-safe scorecards, and approval-gated control
proof states.

This release remains Codex-first and local-only by default. Prepared state is an
advisory cache, not source authority for PR, CI, release, runtime, customer, or
business truth.

Release Gate Notes

• Parent 1.2 tracker: #405.
• Release gate issue: #416.
• Baseline stable release: v1.1.4.
• Candidate package: lossless-openclaw-orchestrator@1.2.0-beta.0.
• Expected npm dist-tag: beta.
• Expected git tag: v1.2.0-beta.0.
• Expected GitHub Release:
  https://github.com/100yenadmin/Lossless-Codex-Orchestrator-LCO/releases/tag/v1.2.0-beta.0.
• Required scoped prerelease gates: focused release metadata tests, npm run check, npm pack --dry-run, release preflight, scorecard sweep, scenario
  sweep, OpenClaw dogfood/tool-smoke where gateway setup is available, 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.

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 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.
Bundle/status/finalization checks do not publish to npm and do not create a GitHub Release.
No release-grade enterprise security or customer-ready security claim.