Skip to content

Upstream integration cycle: catch-up through b1e223e2 (2026-09-12) #516

Description

@rynfar

Continue the maintainer-authorized upstream catch-up after completed cycle #497. Frozen range 4a4c6dd2adc350a68ba18bb28b24b5a7e4660dab..b1e223e2b0d87124883b1410ab52dd6a1338e40d contains exactly 4 upstream commits, compared against Pylon 6ea4ae45084fd00637bfd379d8edd728585a5d25. Keep this bound until all four have dispositions and final reviewed/green implementations land.

  • ca6416ec2d1d194738bc78a81df4b82a75cb72e2 — perf(client): reduce repeated sorting and date formatting (#11019)
  • 4fed6cfb3517ef9af9b2a361142152c079504530 — feat: add inline file previews and attachment chips across surfaces (#11265)
  • 57b23a09f9dff15d57e3fa288c111381259a9a12 — fix(desktop): preserve long offscreen text in SnapShots (#11250)
  • b1e223e2b0d87124883b1410ab52dd6a1338e40d — perf(server): avoid workspace scans when loading pull requests (#11299)

Port every upstream feature while retaining Pylon behavior, identity, Prime/provider ownership, exact rollback, queued compaction, scoped settings, remote authentication, and migration lineage. Reversible in-scope decisions and landing after adversarial review plus green CI remain authorized. Advance the ledger only after all source parts have dispositions. Never merge upstream ancestry or push directly to pylon.

The inline previews/context-chip commit spans 260 paths and will be integrated across contracts/server, web, and mobile before one combined review and CI run. Its accidentally tracked .pnpm-store/v11/index.db is a local package-cache artifact, not product functionality, and will not be imported. The other three commits are independent bounded units.

Opening trigger audit: upstream #8097 remains open/unmerged at 1e8276a76ff194d8b03bc65aa78750b4505ff036. DEF-7/WATCH-2/WATCH-3 retain their earliest 2026-11-01 checks; the four new sources do not add native Claude model-scoped overage identification, so DEF-16 remains unchanged. Preserve #479’s mobile Antigravity exception.

Previous cycle final relay deployment succeeded on 6ea4ae45084fd00637bfd379d8edd728585a5d25: https://github.com/pylon-code/pylon/actions/runs/34681853387 . Its post-merge CI remains watched separately. No manual deployment, desktop/mobile release, device installation, or local rendered/native visual evidence is claimed. Optional Vercel preview quota remains external.

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