Skip to content

Upstream integration cycle: snapshot preview sizing through a43f9b45 #536

Description

@rynfar

Continuation from #526 after its frozen upstream head d1d15c67f4a5fb82fd8d5e01e5e3b288296789c3. One completion-time fetch froze the next bound at a43f9b45ae85caf37e0be8270ad3d27365ece2bd; checked Pylon head cf4be419b31a19eb7611e8a912c198899ecd65ff.

Exact range: d1d15c67f4a5fb82fd8d5e01e5e3b288296789c3..a43f9b45ae85caf37e0be8270ad3d27365ece2bd, three sources:

  • 18d8cbfd920d0a53e5b5206456585aea767e852c — fix(mobile): pin expo-audio so the release smoke patch stays in use (#11426). Already covered: Pylon's mobile manifest and lockfile importer both pin 57.0.4; the release patch remains present. No new dependency change is needed.
  • 5349522108bec896bb6a69ae76c6e1b8d419ae16 — Delete .pnpm-store/v11 directory. Already covered: Pylon has no tracked .pnpm-store tree; upstream only deletes its cache database. Do not introduce a cache to replay its deletion.
  • a43f9b45ae85caf37e0be8270ad3d27365ece2bd — fix(web): preserve snapshot preview size in sent messages (#11429). Remaining port: snapshot image frames span both grid columns in MessagesTimeline; upstream removes the old contrary test assertion. Pylon still uses the frame class without col-span-2. Inspect Pylon's attachment layout and preserve environment/source behavior, port the sizing fix, run focused timeline tests/web types/lint, and obtain final-head adversarial review and green CI before merge.

The reviewed-through cursor remains d1d15c67f4a5fb82fd8d5e01e5e3b288296789c3 until the pending sizing change and compact accounting land together. Three new source commits means one remaining code change, not three missing features.

Standing maintainer scope: port upstream features while preserving Pylon capabilities; retain divergence only for genuine native capability limits. Reversible in-scope implementation, PRs and green-reviewed merges are authorized, including automatic relay deployment. Browser/native UI use and manual release/device installation have no new authorization. Do not restart the completed rollback implementations or agents.

WATCH-1 #8097 checked once on this bound: open/unmerged. WATCH-2 and WATCH-3 remain before their 2026-11-01 earliest check. Exact native rollback compatibility limits are documented in the #526 implementation ledger; no new provider trigger appears in this three-source range.

No implementation worktree has been created for this next cycle. Preserve unrelated worktrees and caller worktree. Detailed #526 landing/relay verification remains in that issue.

Model: GPT-6. Harness: Codex.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions