Skip to content

Backlog: v2.1.34 deferred upstream ports #585

Description

@100yenadmin

Backlog: v2.1.34 deferred upstream ports

Summary

This tracker owns every upstream v2.1.28-v2.1.30 and post-release main item that the v2.1.34 audit classified as defer or avoid for first PR.

defer and avoid for first PR do not mean abandoned. They mean the item is not part of the first low-risk #584 PR and needs its own isolated proof, guardrails, or product review before porting.

Source Links

Guardrails

  • No broad rebase.
  • Do not touch Matt's setup.
  • Preserve evaOS-owned modules: evaOS, Hermes, Mission Control, Shared Browser, Design Workspace, Creative Studio, Terminal, Support, Connected Apps, People & Access, Company Brain, Mac & iPhone.
  • Do not touch Mac connector, broker contracts, release workflows, app identity, update channel, or no-ACP packaging unless the child issue explicitly requires it.
  • Preserve live broker canary, installed-app proof, direct Mac-control proof, and customer/admin diagnostics gating.
  • Do not claim upstream parity until every upstream item is classified and accepted items are ported/proven.

Deferred / Avoided Issue Map

Reuse existing issues:

Create or track child backlog issues for:

Acceptance Criteria

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:releasePackaging, signing, updater, rollbackdeferred-upstreamDeferred upstream port/backlog item from v2.1.34 audit.evaosevaOS public beta R&D workkind:integrationIntegration implementation issuepublic-betaBlocks or contributes to the public beta gateready-for-agentIssue has enough handoff detail for an agent to startrelease-train:runtime-reliabilityCross-version Workbench/runtime reliability release trainrisk:upstream-conflictLikely conflict with upstream AionUi changes

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions