Skip to content

Port the fork UI patch stack to the app overlay: yellow-chunks (10 commits), #305 agent_order, #297b posture indicator #853

Description

@aarontrowbridge

Important

Problem — The fork is retiring, but the daily-driver UI lives only on its patch stack: the yellow-chunks branch (10 commits — yellow answers/WAAPI bubble lock, prose fragments, the slab, the docket, dropdown file rows/shell anatomy) is live on the hub via the dev build but structurally OUTSIDE the app-overlay extraction (which froze at d161eb0c, pre-yellow — audit #850 lens 3); #305 (agent_order picker sort, ready) and #297 slice (b) (titlebar posture indicator + mid-session switching, unstarted) are fork changes by design.
Approach — Port to packages/app-bundle (the overlay owns the app now): (1) the yellow-chunks UI grammar as overlay changes (the 10 commits' diff is the spec; the hub's live build is the reference rendering), (2) agent_order as an overlay/config capability (upstream ask if the config semantics belong stock), (3) the posture indicator composed on the committed message/event contract per #297's approach. Each piece rides the overlay's own gates (i18n parity, drift gate, boot proof). Retire the fork branch + dev-build path at the landing — the hub's binary reverts to the overlay-built shelf.

Rulings 5–6 of audit #850. Upstream asks (#281/#244/#212) are tracked separately with Aaron's public-outward gate.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    afkImplementable without human interaction

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions