Skip to content

Upstream integration cycle: close remaining functional exceptions #526

Description

@rynfar

The maintainer explicitly reopened the four remaining functional exceptions after the completed catch-up cycle #516. Work through them while preserving Pylon capabilities, with independent adversarial review and green CI before landing. Existing approval covers routine adaptations, PR merges and the automatic relay deploy; it does not request a manual desktop/mobile release or installation.

Verified starting Pylon: 6e879c2b665a373b758b81ec28367b2f730fdab4. Reviewed cursor: b1e223e2b0d87124883b1410ab52dd6a1338e40d. Fresh upstream bound: d1d15c67f4a5fb82fd8d5e01e5e3b288296789c3 (one newly arrived sidebar source after that cursor).

The explicit request reopens the named deferrals before their former revisit dates. Other deferred/watch entries are unchanged. Update this issue with verified PR heads and concrete remaining limits; do not equate the reviewed cursor with full feature parity.

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