Skip to content

Upstream integration cycle: provider discovery, account homes and Claude rewind #611

Description

@rynfar

Continue the approved upstream catch-up after #608. User explicitly requested all five items, implementation in separate Pylon threads through Antigravity, and adversarial reviews before landing. Existing merge approval applies after review findings are resolved and final-head checks are green.

Frozen upstream head: 6d1d549441be84f19696ab59ed7e2fbf305280d4; cursor: bbedad0278bbf753503184c00e0c09a0eab6679c. Pylon base: 738b5ed9dc001ed49bbb6e9878e9291e1aa58479. 154 sources remain after #608; pending implementations do not reduce that count.

  • 2db675aeffd9cb1e8b5ad76ddd018433b45b02e9 (#11485): provider account homes in usage tracking.
  • 7931227977ca3e6f3354a63467caa634ab79796f (#11811): avoid refresh on every config subscription.
  • 8b1ea4dd2465f3cf3cfa02d6878beaa1ec22e71a (#11741): Node discovery for WSL providers.
  • 2a264adc6f6c65f98d4273acaa1af567eca83f2a (#11345): missing Codex executable diagnostics.
  • eed974c122e192de45b54b7dac7ca1a51448c08f (#11954): Claude rewind across fork history changes.

Five Antigravity implementation threads have isolated worktrees. Parent reviews combined changes and assigns separate adversarial reviews against completed commits. Keep Claude rewind separately reviewable from provider configuration/discovery. Preserve Pylon account isolation, admission, lifecycle, checkpoint/rollback ownership, remote auth, branding, and migration lineage. Focused regressions and affected package checks; CI owns the full suite. No release or device installation.

Activity

  1. rynfar commented on Sep 18, 2026

    @rynfar
    CollaboratorAuthor

    Completed all five selected sources in the frozen range through 6d1d549441be84f19696ab59ed7e2fbf305280d4.

    • PR fix(server): preserve Claude rewind across fork history changes #612 adopts Claude fork rewind alignment (eed974c122e192de45b54b7dac7ca1a51448c08f, #11954), retaining Pylon session/checkpoint ownership.
    • PR fix(providers): align usage homes, discovery and executable diagnostics #613 adopts provider-account usage (2db675aeffd9cb1e8b5ad76ddd018433b45b02e9, #11485), removes subscription-triggered full refreshes (7931227977ca3e6f3354a63467caa634ab79796f, #11811), and improves missing-Codex diagnostics (2a264adc6f6c65f98d4273acaa1af567eca83f2a, #11345).
    • WSL source 8b1ea4dd2465f3cf3cfa02d6878beaa1ec22e71a (#11741) is already covered by Pylon’s Node-based staged/mounted runtime preflight. Its standalone-runtime prerequisite #11511 has not been adopted. Regression coverage replaces the rejected unused-probe port.

    Five separate Pylon/Antigravity implementation threads and five independent adversarial review threads were used. Confirmed findings were resolved and re-reviewed: Claude-relative-home resolution, nine Claude fork fixture payloads, unused WSL probe code, and canonical-path assumptions in the macOS usage test harness. Contributor authorship/provenance is retained.

    Proof: 173 Claude adapter tests plus 374 focused provider/server/desktop tests passed, with 10 platform skips; scoped type/lint checks passed. The usage reviewer also passed all 92 usage tests. Uploaded browser screenshots show the same disabled custom account’s history changing from 0 to 12,000 tokens and the configured missing-Codex executable in the new diagnostic. Real WSL and a paid native Claude session are not claimed.

    Final-head CI was green before each merge. No release or installation was performed.

    Remaining: 149 unclassified source commits, down from 154, in the frozen range bbedad0278bbf753503184c00e0c09a0eab6679c..6d1d549441be84f19696ab59ed7e2fbf305280d4. Four sources were adopted and one already-covered source was verified. This is a source count, not a count of missing fixes. The decision cursor stays at bbedad0278bbf753503184c00e0c09a0eab6679c; later arrivals were not fetched or included. The compact index in .agents/upstream-review.md points to both implementation PRs.

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