Roadmap: Workbench runtime reliability release train

[100yenadmin]

Roadmap: Workbench runtime reliability release train

Created: 2026-07-09T04:34:12Z

Governing Priority 1 / P0 Gate — Pristine-Mac Onboarding And Truthful Readiness

Fresh customer evidence supersedes every later Current Checkpoint, Current state, Exact next action, and lane-order sentence in this body where they conflict. The durable security, release, evidence, and customer-safety guardrails remain in force.

Decision: #662 and #655 are one conjunctive Priority 1 / P0 Workbench release gate. #662 owns self-contained pristine-Mac onboarding; #655 owns truthful end-to-end broker/runtime readiness for the exact candidate. #480 supplies Mac-control contract and safety dependencies; it is not an alternate exit gate.

Exit rule: Do not claim signed-candidate, public-release, updater-promotion, customer-onboarding, or customer-ready status until both #662 and #655 satisfy their stated acceptance and release-proof requirements for the same exact artifact/candidate. A merged source/UI fix, including #657, is not substitute proof.

Paused scope: Do not start or prioritize feature-polish work, including #574 and #332, ahead of this gate. Such work may resume only after both P0 issues close with their required proof, or an explicit owner decision recorded in this tracker changes the priority.

Resume order: Read this section, then #662, then #655, then #480. Work only the smallest implementation/proof slice required by #662 or #655; keep #480 invariants intact. Re-read live refs, PR state, release-object state, and exact artifact identity before making a readiness claim.

Ref snapshot at declaration (2026-07-12T09:20Z): evaos/beta-rc-20260612 = a881fd9edb85c4ce68d581e87b5f857c0fb02464; main = 26807abd3a76e4161243a03ec426161d35e96480; v2.1.32 release/tag targets 408ee2bee0b52ceebf511896302f8a8f4108932a. These are routing anchors only, not release or customer-readiness proof.

Implementation preflight: The shared checkout at /Volumes/LEXAR/repos/evaOS-GUI contains user-owned changes and is behind the live release branch. Create an isolated current-head worktree before code changes; do not alter Matt's setup.

Exact next action: Decompose and execute #662 first with failing tests: self-contained Bridge runtime packaging; guided private-network install/start/enrollment with explicit state; optional CUA and bundled Peekaboo fallback behavior; clean-host CI; and a real pristine supported-Mac acceptance lane. In parallel, keep #655 ready for exact-target staging proof once the approved Mac is online. Do not resume Lane 7 or any customer-facing release action before both P0 gates are green.

Proof boundary: A tag, merged PR, local/fixture check, or prepared-Mac success does not satisfy this gate. Preserve redaction and do not place secrets, private addresses, connector material, customer data, or raw logs in this tracker or its evidence.

Current Checkpoint (2026-07-11)

This checkpoint supersedes the older head/version/open-lane snapshot below; the durable guardrails and proof contract remain in force.

• Historical source checkpoint: 0b0c2ee62952809a2fee6dbfc9684c7feca487a6 (feat(team): add multi-member creation #649 merge). The live execution ref is recorded in the Priority 1 / P0 reset above and must be re-fetched before work.
• Current source milestone truth: v2.1.34 Upstream Runtime Sync is 10/10 closed; v2.1.30 Customer Polish is 2/2 closed.
• Current package/release truth: package.json remains 2.1.32 and the newest real prerelease is evaos-beta-v2.1.32-evaos-beta, targeting 408ee2bee0b52ceebf511896302f8a8f4108932a. Later source work is not yet a later release.
• Lane 1 ws-proxy Path-gate Windows CI for macOS beta sprint #62 is complete. Lane 2/P2 Follow-up: Complete AionCore v0.1.43 direct Mac-control doctor command gates #622 and Lane 4 remain owner-gated on authenticated broker, active grant/device, TCC/live Mac-control, approval-backed stop/revoke/kill-switch, and customer setup proof.
• Lane 3 Admin Modules V1 is closed/shipped as v2.1.31; P2 Epic: employee mode broker-authorized route policy #217 and P2 Epic: native Connected Apps and People Access parity #262 remain deeper follow-ups outside that closed milestone.
• Lane 5 stdout purity is closed; visible ACP Mac-control remains externally owner-gated on ACP bridge should support Workbench session MCP for visible Mac-control tools openclaw/openclaw#100924's maintainer/product/security trust-boundary decision.
• Lane 6 active source work is closed. The remaining Backlog: v2.1.34 deferred upstream ports #585 children are explicitly deferred/manual-port, Windows-only, diagnostics-design, or post-Mac-control-stability work.
• Lane 7 remains deferred until runtime and permission gates are stable or explicitly reprioritized.

The next customer-facing version/name must be selected explicitly from intended release scope before notes, tags, appcast/update metadata, or artifacts are created.

Summary

This tracker consolidates the remaining Workbench/customer-runtime reliability backlog across versions instead of treating each issue as an isolated one-off.

The immediate Jackie-David dashboard/runtime outage lane is technically resolved and closed in electricsheephq/electric-sheep-website-dashboard-6158a244#634, but several related reliability surfaces remain open across Workbench, ws-proxy, dashboard publishing, AionCore, Mac-control, ACP, admin modules, and deferred upstream ports. This tracker is the cross-version execution map for those surfaces.

Durable Plan Contract

• Goal: Clear the remaining Workbench/customer-runtime reliability backlog across the versioned release train while preserving customer access, broker/Mac-control guardrails, release proof boundaries, and upstream/manual-port traceability.
• Resume identity: Primary tracker repo 100yenadmin/evaOS-GUI; checkout /Volumes/LEXAR/repos/evaOS-GUI; branch evaos/beta-rc-20260612; historical baseline head 19997d4a781084cd974ca55742a92c5cfc17a12a; the live execution ref is the re-fetched Priority 1 / P0 snapshot above; tracker milestone Workbench Runtime Reliability Release Train; label release-train:runtime-reliability. Cross-repo heads at audit: dashboard electricsheephq/electric-sheep-website-dashboard-6158a244@64988ee3e07fc0d6edb8639df859c01e42facff5; ws-proxy electricsheephq/evaos-ws-proxy@86e3c8a53cf7f01d33ea1dcb286175051a247694; desktop bridge electricsheephq/evaos-desktop-bridge@4753cbd8e17d30a3f0f344cc88d4cc86f3e97422.
• Tracking / source of truth: This issue, linked child issues/trackers, GitHub PRs/checks, Workbench release run artifacts, Supabase deploy checks, Lovable publish/preflight checks, ws-proxy Actions, and evidence under /Volumes/LEXAR/Codex/evidence/evaos-workbench-runtime-reliability-release-train/.
• Scope / non-goals: No broad rebase. Do not touch Matt's setup. Do not weaken broker/session, Mac-control, stop/revoke, kill-switch, customer/admin diagnostics, app identity, update channel, release workflows, or no-ACP packaging to make a proof pass. Do not mutate customer VM, Supabase, ws-proxy, Lovable production, support-control, or runtime config without the owning child issue and explicit approval/proof plan. Do not reopen the closed Jackie-David incident as unfixed without new live evidence.
• Current state: Jackie-David dashboard/direct/app-wrapper runtime access lane is closed/proven via dashboard tracker feat(evaos): guide macOS permission app setup #634 and Workbench fixed head 19997d4a. Remaining open reliability work is now backlog/release-train work: ws-proxy public/session smoke Path-gate Windows CI for macOS beta sprint #62; dashboard Lovable deploy path Stabilize Business Browser stop live canary #521; dashboard Golden VM target Port team chat capability propagation #602; AionCore/Mac-control doctor P2 Follow-up: Complete AionCore v0.1.43 direct Mac-control doctor command gates #622; v2.1.31 admin module parity; v2.1.32 TryCUA/Mac permission refresh; v2.1.33 ACP Mac-control; v2.1.34 deferred upstream backlog; v2.1.35 experience polish. Version naming drift exists: installed Workbench candidate 2.1.31 is already used for the incident proof while milestone v2.1.31 Admin Modules V1 remains open.
• Exact next action: Follow the superseding Priority 1 / P0 gate above: execute P0: Workbench fresh-Mac onboarding depends on unbundled Python and manual private-network setup #662 and P0: Mac & iPhone readiness can appear ready before end-to-end broker runtime control works #655 as conjunctive release blockers, using Sprint: Mac Control Contract Unification + Matt-Style Reconciler #480 only for required contract/safety dependencies. Feature polish and customer-facing release actions remain paused.
• Critical invariants: Customer-ready requires authenticated dashboard and installed app-wrapper proof, not only green public health. Release-ready requires Workbench Functional Smoke, live broker canary with non-internal target, installed-app proof, direct Mac-control non-regression when in scope, RC canary, distribution workflow, and exact artifact identity. Mac-control proof requires live bridge truth, Computer Use/accessibility proof or named equivalent, local OpenClaw, VM OpenClaw, Hermes, stop/revoke, kill-switch fail-closed, and post-reset recovery. Evidence must not contain raw tokens, connector URLs, desktop sessions, cookies, callback params, customer credentials, IPs/ports, provider grants, or raw customer transcripts.
• Execution lanes: Lane 0 Roadmap hygiene: link this tracker from Backlog: v2.1.34 deferred upstream ports #585, P2 Follow-up: Complete AionCore v0.1.43 direct Mac-control doctor command gates #622, dashboard feat(evaos): guide macOS permission app setup #634, and ws-proxy Path-gate Windows CI for macOS beta sprint #62. Lane 1 Runtime access hardening: ws-proxy Path-gate Windows CI for macOS beta sprint #62 plus dashboard Stabilize Business Browser stop live canary #521/Port team chat capability propagation #602 as needed. Lane 2 AionCore/direct Mac-control proof: P2 Follow-up: Complete AionCore v0.1.43 direct Mac-control doctor command gates #622 and related Mac-control trackers. Lane 3 v2.1.31 admin modules: P2 Epic: employee mode broker-authorized route policy #217, P2 Epic: native Connected Apps and People Access parity #262, P2: Company Brain native module parity #572 with broker-authorized route and permissions proof. Lane 4 v2.1.32 Mac-control refresh: Sprint: v2.1.32 TryCUA Mac Control Refresh #569, P1: Refresh CUA/TryCUA and Peekaboo fallback package proof #573, P2: Guided macOS permission onboarding for Workbench Mac control #380 plus desktop-bridge RC Parity: Upstream AionUi v2.1.12 Regression Reconciliation #134/P3: Restore Windows release lane separately from macOS controlled RC #305. Lane 5 v2.1.33 ACP Mac-control: Sprint: v2.1.33 ACP Chat Mac Control #570, P0: Workbench visible ACP Mac-control cannot consume session MCP #499, P2: OpenClaw ACP stdout purity follow-up for Workbench #468. Lane 6 v2.1.34 deferred upstream: Backlog: v2.1.34 deferred upstream ports #585, P1: Port upstream v2.1.30 Assistants/add-ons UX without breaking evaOS modules #582, P1: Port upstream slash command menu and Settings revamp safely #583, P3 Backlog: Evaluate upstream feedback diagnostics attachments #595, P3 Backlog: Review Windows NSIS installer hardening outside macOS Workbench lane #597, P3: Move evaos-desktop-bridge modules into evaOS-GUI after Mac-control release #419. Lane 7 v2.1.35 experience polish: Sprint: v2.1.35 Experience Polish + Desktop Pet #574/P3: Upgrade evaOS desktop pet with adoptable spritesheets and scoped authorization surfaces #332 only after runtime and permission gates are stable enough not to mask customer reliability regressions.
• Validation / eval gates:
  • Eval required: yes
  • Eval claim class: advisory
  • Required eval suites: issue classification audit, focused local checks for touched files only, GitHub Actions for broad checks, Workbench Functional Smoke, live broker canary with non-internal target, installed-app proof, direct Mac-control doctor gates where in scope, Supabase Production Deploy, Lovable hosted preflight/publish proof, ws-proxy public/session smoke, dashboard authenticated runtime smoke.
  • Eval name/version: Workbench Runtime Reliability Release Train v2026-07-09
  • Dataset/scenario refs: Jackie-David runtime incident proof under dashboard feat(evaos): guide macOS permission app setup #634; Workbench fixed head 19997d4a; upstream AionUi v2.1.28-v2.1.30 and post-release main deltas from Sprint: v2.1.34 Upstream Runtime Sync #571/Backlog: v2.1.34 deferred upstream ports #585; ws-proxy Path-gate Windows CI for macOS beta sprint #62 public/session smoke; desktop-bridge RC Parity: Upstream AionUi v2.1.12 Regression Reconciliation #134/P3: Restore Windows release lane separately from macOS controlled RC #305 TryCUA lane.
  • Baseline/comparison: Workbench 19997d4a781084cd974ca55742a92c5cfc17a12a; dashboard 64988ee3e07fc0d6edb8639df859c01e42facff5; ws-proxy 86e3c8a53cf7f01d33ea1dcb286175051a247694; desktop bridge 4753cbd8e17d30a3f0f344cc88d4cc86f3e97422.
  • Metrics and thresholds: every linked child issue has owner surface, release lane, guardrails, acceptance proof, stop conditions, evidence path, and proof boundary; no release/customer/parity claim until all required child gates for that claim class pass; no issue closes with raw secret evidence.
  • Runner/CI location: GitHub Actions for broad validation; local only for narrow checks from Lexar checkouts; live proof only through approved runbook gates.
  • Failure owner: the child issue owning the failed surface; release-proof failures route here and to the version tracker; runtime/customer failures route to the relevant incident/proxy/dashboard issue before mutation.
  • Eval evidence path: /Volumes/LEXAR/Codex/evidence/evaos-workbench-runtime-reliability-release-train/
  • Trace feedback target: this tracker, child issues, active PRs, and release/evidence comments.
  • Eval proof boundary: roadmap/advisory readiness only. This issue does not itself prove runtime safety, customer readiness, upstream parity, release readiness, or Mac-control closure.
• Proof-claim boundary: This tracker may claim the backlog is organized into a runbook-aligned release train. It must not claim any child issue is fixed, any version is release-ready, any customer is restored, or upstream parity is complete unless that child issue's own proof gates pass.
• Stop conditions: A planned action would broaden rebase scope, touch Matt/local setup, bypass broker/Mac-control guardrails, mutate live customer/runtime/deploy state without the owning issue and approval, expose secrets in evidence, collapse packaging/staging/release proof boundaries, or use screenshots as a substitute for live runtime/bridge truth.
• Evidence path / packet: /Volumes/LEXAR/Codex/evidence/evaos-workbench-runtime-reliability-release-train/

Versioned Release Train

Lane 0 - Tracker Hygiene

• Link this issue from 100yenadmin/evaOS-GUI#585, #622, electricsheephq/electric-sheep-website-dashboard-6158a244#634, and electricsheephq/evaos-ws-proxy#62.
• Apply release-train:runtime-reliability to central Workbench tracker issues.
• Keep child issues in their existing version milestones unless their owner explicitly changes release scope.

Lane 1 - Runtime Access Hardening

• electricsheephq/evaos-ws-proxy#62: public runtime host/session smoke and proxy diagnostics.
• electricsheephq/electric-sheep-website-dashboard-6158a244#521: Lovable production publish path remains a strategic reliability gate even though feat(evaos): guide macOS permission app setup #634 proved the backend-only incident lane.
• electricsheephq/electric-sheep-website-dashboard-6158a244#602: Golden VM as Workbench Mac-control target, only after account/policy proof is explicit.

Lane 2 - AionCore And Direct Mac-Control Proof

• 100yenadmin/evaOS-GUI#622: AionCore v0.1.43 direct Mac-control doctor command gates.
• 100yenadmin/evaOS-GUI#480: Mac Control Contract Unification + Matt-Style Reconciler.
• Required proof: exact installed app path, bridge readiness, Computer Use/accessibility evidence, local OpenClaw, VM OpenClaw, Hermes, stop/revoke, kill-switch fail-closed, and post-reset recovery.

Lane 3 - Admin Modules / Permissions

• 100yenadmin/evaOS-GUI#217: employee mode broker-authorized route policy.
• 100yenadmin/evaOS-GUI#262: native Connected Apps and People Access parity.
• 100yenadmin/evaOS-GUI#572: Company Brain native module parity.
• Required proof: account/role matrix, customer/admin diagnostics gating, no cross-user provider exposure, and dashboard/runtime non-regression.

Lane 4 - v2.1.32 TryCUA / Mac Permissions

• 100yenadmin/evaOS-GUI#569: sprint tracker.
• 100yenadmin/evaOS-GUI#573: CUA/TryCUA and Peekaboo fallback package proof.
• 100yenadmin/evaOS-GUI#380: guided macOS permission onboarding.
• electricsheephq/evaos-desktop-bridge#134 and #305: background/parallel Computer Use and TryCUA primary engine.
• Required proof: signed installed app identity, TCC identity, duplicate-app audit, TryCUA/Peekaboo fallback proof, and no permission-regression hidden behind ad-hoc artifacts.

Lane 5 - v2.1.33 ACP Mac-Control

• 100yenadmin/evaOS-GUI#570: sprint tracker.
• 100yenadmin/evaOS-GUI#499: visible ACP Mac-control cannot consume session MCP.
• 100yenadmin/evaOS-GUI#468: OpenClaw ACP stdout purity.
• Required proof: ACP stdout purity, session MCP consumption, direct Mac-control non-regression, and no weakening of no-ACP packaging boundaries.

Lane 6 - v2.1.34 Deferred Upstream

• 100yenadmin/evaOS-GUI#585: deferred upstream tracker.
• 100yenadmin/evaOS-GUI#582: remaining Assistants/add-ons runtime catalog/defaults.
• 100yenadmin/evaOS-GUI#583: remaining Settings shell revamp and assistant editor/settings polish.
• 100yenadmin/evaOS-GUI#595: feedback diagnostics attachments/redaction design.
• 100yenadmin/evaOS-GUI#597: Windows NSIS installer hardening outside macOS lane.
• 100yenadmin/evaOS-GUI#419: bridge modularization after Mac-control release stability.
• Required proof: upstream refs retained, accepted slices manually ported, deferred/avoid items never treated as abandoned, and no upstream parity claim until every accepted item is ported/proven.

Lane 7 - v2.1.35 Experience Polish

• 100yenadmin/evaOS-GUI#574: experience polish sprint.
• 100yenadmin/evaOS-GUI#332: desktop pet authorization surfaces.
• Required proof: only after runtime/security/release gates above are stable enough that visual polish cannot mask customer/runtime regressions.

Immediate Owner Notes

• Start with the superseding Priority 1 / P0 gate (P0: Workbench fresh-Mac onboarding depends on unbundled Python and manual private-network setup #662 plus P0: Mac & iPhone readiness can appear ready before end-to-end broker runtime control works #655), not Lane 7. Resume older lane ordering only after both gates close with exact proof or Roadmap: Workbench runtime reliability release train #623 records an explicit owner reprioritization.
• Use GitHub Actions for heavy suites.
• Local validation must be narrow and run from Lexar-backed checkouts.
• Before any release/customer-ready claim, require the exact candidate's Workbench Functional Smoke, live broker canary, installed-app proof, direct Mac-control proof where in scope, RC canary, distribution workflow, dashboard/runtime authenticated smoke, and public publish/deploy proof when dashboard/public bundle changes are involved.

[evaos-code-review-bot]

evaOS issue enrichment

Issue: #623 - Roadmap: Workbench runtime reliability release train
State: open; milestone: Workbench v2.1.36 Runtime Reliability

Related issues/PRs: #662, #655, #480, #657, #574, #332, #649, #62.
Existing labels: evaos, public-beta, ready-for-agent, area:shell, area:broker, area:release, risk:security, risk:upstream-conflict, kind:integration, blocked, release-train:runtime-reliability.
Suggested labels: bug, security, docs, tests, support.
Suggested owners: none.

Related context

• P0: Workbench fresh-Mac onboarding depends on unbundled Python and manual private-network setup #662 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• P0: Mac & iPhone readiness can appear ready before end-to-end broker runtime control works #655 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Sprint: Mac Control Contract Unification + Matt-Style Reconciler #480 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• P0: require end-to-end proof for Mac control readiness #657 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Sprint: v2.1.35 Experience Polish + Desktop Pet #574 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• P3: Upgrade evaOS desktop pet with adoptable spritesheets and scoped authorization surfaces #332 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• feat(team): add multi-member creation #649 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.
• Path-gate Windows CI for macOS beta sprint #62 - mentioned in issue metadata; inspect for dependency, duplicate, or prior-decision risk.

Agent-start packet

Problem shape: Roadmap: Workbench runtime reliability release train - # Roadmap: Workbench runtime reliability release train Created: 2026-07-09T04:34:12Z [hidden comment removed] ## Governing Priority 1 / P0 Gate — Pristine-Mac Onboarding And Truthful Readiness Fresh customer evidence
Product fit: Product/UX-sensitive issue; review against repo vision and user flow quality, not only technical P0/P1 risk.
Implementation wedge: Ship the smallest user-visible path or prototype that can be smoke-tested against the intended experience.

Build / borrow / buy scan:

• Build: identify the smallest implementation wedge that proves the issue without broad rollout.
• Borrow: inspect same-repo prior art, repo memory, GitNexus context, and allowlisted cross-repo examples first.
• Buy/use: run capped external OSS/library/API/current-market research with citations, observed dates, and why each source matters.
• Library choice: compare maintenance, API fit, license, bundle/runtime cost, and integration proof.

Candidate sources:

• VISION.md / repo policy / repo-memory.md / GitNexus packet.
• Same-repo issues and PRs referenced by issue metadata.
• Allowlisted cross-repo GitHub examples with direct issue/PR/repo URLs.
• External OSS repositories or library/API docs with freshness dates.
• Current market/product examples, capped and cited, only when they change implementation direction.

Acceptance criteria:

• Preserve and execute the issue's stated acceptance criteria.
• Include source citations for any external OSS/library/current-market claims.
• Keep issue-enrichment comments sticky and idempotent.
• Keep labels, owners, reviewers, and roadmap fields suggestion-only.

Proof plan:

• Focused unit/fixture test for the changed planner behavior.
• Dry-run issue-enrichment evidence packet before live comment posting.
• Redaction check for issue body, citations, and generated markdown.
• UX/product smoke or screenshot proof when implementation changes user flow.
• Contract or degraded-mode proof before runtime promotion.
• Dependency/license/API-fit note before adding or relying on a package.

Known traps:

• Do not treat related links as proof by themselves; each source needs a reason why it matters.
• Do not scan old issue backlogs or exceed repo-level enrichment throttles.
• External research must stay capped, cited, fresh-dated, and redacted.
• Technical severity alone can miss product/UX regressions; include product-manager review framing.

Non-goals:

• Do not auto-apply labels, owners, reviewers, roadmap fields, or milestones.
• Do not bulk-enrich old backlog issues from this planner output.
• Do not claim external market or OSS research was performed unless cited sources are present.

Context-source taxonomy:

• [enabled] vision_repo_policy_memory_gitnexus: Use repo vision, policy, memory, and GitNexus first before external research.
• [enabled] same_repo_issues_prs: Issue metadata contains same-repo references.
• [enabled] allowlisted_cross_repo_github: Triggered by issue class; keep to configured allowlist and source caps.
• [enabled] external_oss_examples: Use for build/borrow/buy precedent with citations and observed dates.
• [enabled] library_api_docs: Use when implementation may depend on a module, SDK, API, or framework choice.
• [enabled] current_market_examples: Use for product/UX/market positioning issues with freshness dates.
• [enabled] internal_mcp_docs: Use internal docs/MCP context when available; missing context is degraded, not blocking.

Validation suggestions

• Confirm owner, acceptance criteria, and validation evidence before implementation.

Triage gaps

• No obvious issue triage gap detected from issue metadata.

No labels, owners, reviewers, or roadmap fields were changed by this bot.

[coderabbitai]

🔗 Related PRs

#403 - fix: recover Mac control installed app states [merged]
#449 - Fix legacy app stale owner proof path [merged]
#455 - [codex] Path-gate Workbench PR package smoke [merged]
#462 - [codex] Document Workbench release proof lanes [merged]
#464 - Add no-acp managed resource bundle gate [merged]
#470 - Restore Workbench Bridge resource proof [merged]
#476 - Harden installed Mac-control proof scope [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[100yenadmin]

Release-manager handoff - 2026-07-10

Independent successor task created from a durable packet rather than chat history.

• Packet: /Volumes/LEXAR/Codex/evidence/evaos-workbench-runtime-reliability-release-train/handoff-20260710.md
• Codex task id: 019f4cec-c84a-7000-ace0-ffaac403ea1e
• Workbench checkout remains clean at 19997d4a781084cd974ca55742a92c5cfc17a12a, package version 2.1.31.
• Fresh upstream fetch found material audit drift: AionUi v2.1.31 e49cd94935f4e461f002a1260a47c1b7b2ce81ca, v2.1.32/main 0a903d835948fea6d2717a2cb93f85ed82f95245, 17 commits after v2.1.30.
• Current cross-repo heads: dashboard ef5cf162a84ca30b20e0bbbd8ee741144570da61; ws-proxy f8bf66dae7f3d0c821d0910ed6b775ab85143e1c; desktop bridge 4753cbd8e17d30a3f0f344cc88d4cc86f3e97422.
• The private v2.1.31 RC is a real GitHub prerelease with assets at evaos-beta-v2.1.31-evaos-beta.1-rc635-19997d4a, but its own notes still block customer readiness on manifest registration, RC canary, distribution workflow, and public/live URL proof.

Exact next action: refresh the upstream classification through v2.1.32/main and post the expanded matrix plus durable issue links to #623/#585 before changing code; reconcile evaOS package/candidate 2.1.31 with the still-open v2.1.31 milestone; then execute ws-proxy #62 and Workbench #622 before feature polish unless fresh evidence identifies a P0 customer-access regression.

Proof boundary: handoff/tracking update only. No code, deploy, runtime, customer VM, app install, release, npm publish, dashboard publish, or customer-ready claim was made.