YonerAI v0.23.0-alpha.1 Public CLI Sync Client Alpha
Pre-releaseRelease date: 2026-06-30
Tag: v0.23.0-alpha.1
Status: prerelease Public CLI sync-client alpha
Previous prerelease: v0.22.0-alpha.1
Summary
YonerAI v0.23.0-alpha.1 cuts the Public repository release for the CLI
sync-client receiver path proven by the owner-only staging Web-to-CLI smoke.
In that staging path, the Public CLI received a body-free SyncEvent and fetched
the matching message body only from authenticated AWS.
This release is Public repository only. It does not claim production readiness,
general sync approval, external alpha approval, Web AI chat execution, Phase B
Native Run readiness, Windows worker readiness, or private repository release
completion.
Runnable Changes
- Public CLI sync receiver accepts the closed-alpha owner allowlist smoke mode.
- Public CLI reads Firestore
sync_eventsthrough RESTrunQuery, not
documents:list. - The receiver query is account-scoped with
account_idequality and
body_ref.body_included=false. - The receiver query orders by
created_at ASC, uses a bounded limit, and uses
no offset, no broad list, and no collection-group query. - Duplicate/idempotency handling can still fetch the AWS body for an already
observed body-free event. - Cursor retry handling no longer rolls
last_event_idor cursor state
backward after a duplicate retry. - Message body fetch remains authenticated AWS-only.
- Firestore body fallback remains absent.
Install / Run
Download the release archive from GitHub Releases, extract it, and install the
CLI in a Python 3.11 environment:
py -3.11 -m venv .venv
.\.venv\Scripts\python.exe -m pip install --upgrade pip
.\.venv\Scripts\python.exe -m pip install -e clients\cliFor staging-only auth and diagnostics, set the staging API origin in the same
PowerShell process before running the CLI:
$env:YONERAI_STAGING_AUTH_ORIGIN = "https://api-staging.yonerai.com"
$env:PYTHONPATH = (Resolve-Path .\clients\cli).Path
.\.venv\Scripts\python.exe -m yonerai_cli whoami --jsonDo not run sync receiver smoke unless a fresh owner-only staging window is open
and the current coordination ledger explicitly requests it.
Validation
Public repository validation on origin/main included:
YonerAI Core CI / core-test: success on commit5dc4275.YonerAI Core Tests / build-and-test (3.11): success on commit5dc4275.YonerAI Quality Wall: core, CLI, TUI, provider boundary, hybrid zero-trust,
installer manifest, Windows CLI, Windows installer, macOS CLI, macOS
installer, static security, and release-gate jobs succeeded on commit
5dc4275.- Dependabot open alerts: 0.
- Secret scanning open alerts: 0.
- Code scanning API returned no configured analysis for this repository.
Release gate validation for this release prep:
python scripts/release_gate.py --tag v0.23.0-alpha.1 --artifact YonerAI-0.23.0-alpha.1.zip --github-prerelease truepython scripts/yonerai_release_gate.py --release-issue 592 --release-notes docs/releases/0.23.0-alpha.1.md
Staging E2E Evidence
Issue #552 contains the passing owner-only staging Web-to-CLI smoke tags for the
same smoke window:
- AWS ready:
#552 (comment) - YonerAIWEB client ready:
#552 (comment) - Public CLI client ready:
#552 (comment) - Web-to-CLI E2E passed:
#552 (comment)
The passing smoke was staging owner-account-only and synthetic-data-only. AWS
rollback completed after the smoke; sync is off, token issuance is off, and
projection is off after rollback.
Known Limitations
- This is an alpha prerelease line, not the stable CLI Local Runtime channel.
- The proven sync path is staging owner-only and synthetic-data-only.
- Production/general sync/external alpha are not enabled.
- Production AWS backend code is not included in the Public repository.
- Private repositories are not fully released by this Public tag.
- Actual AI conversation through the full Web-to-local worker path still
requires Phase B. - Phase B Native Run and the Windows worker path are not included.
- Web AI chat execution is not included.
- Provider sharing and paid fallback are unchanged.
src/cogs/ora.pyremains a legacy boundary and is not solved by this release.reference_clawdbotis not touched.
Not Included
- No production deployment.
- No general sync enablement.
- No external alpha enablement.
- No Web AI chat execution claim.
- No Phase B claim.
- No Windows worker claim.
- No private repository release completion claim.
- No provider-sharing policy change.
- No paid fallback enablement.
Traceability
Primary compare range: v0.22.0-alpha.1..v0.23.0-alpha.1.
| Change | Evidence | Boundary |
|---|---|---|
Firestore receiver query uses runQuery |
Public PR #589 | Account-scoped and body-free only. |
| Duplicate SyncEvent can still fetch AWS body | Public PR #590 | AWS-only body fetch remains required. |
| Duplicate retry no longer rolls cursor backward | Public PR #591 | Cursor/idempotency safety for receiver retries. |
| v0.23 release gate governance | Public PR #594 | Public release gate only; private repo release completion is not claimed. |
| Owner-only staging E2E passed | Issue #552 comments 4846791122, 4846798667, 4846811538 |
Staging owner-account-only, synthetic data, rollback completed. |