Skip to content

[Upstream Orca] post-fork semantic sync master tracker #38

Description

@TsekaLuk

Fork determination

  • Upstream repository: stablyai/orca.
  • Common-history baseline: dacb84b, tag v1.4.124-rc.8.
  • Baseline published: 2026-07-06 05:51:34 UTC (2026-07-06 13:51:34 Asia/Shanghai).
  • Pebble migration commit: 6d4078174, 2026-07-08 19:14:05 Asia/Shanghai.
  • Latest stable reviewed: v1.4.158. Latest prerelease: v1.4.159-rc.0.
  • Upstream baseline-to-main delta at audit time: 1,326 commits, 5,884 files, 1,093 unique release-note PRs.

Analysis conclusion

Pebble is not a shallow fork of an early prototype. Its Git history contains Orca through v1.4.124-rc.8; divergence begins after that release, followed by the brand migration and then the Electron-to-Tauri/Go ownership change. Therefore normal Git cherry-picks are only trustworthy for small renderer/shared changes.

Upstream source Pebble treatment
src/renderer, shared pure TypeScript Compare behavior and tests; selective semantic cherry-pick may be possible after path/import adaptation.
src/main, daemon, PTY, persistence, SSH Port the contract into runtime/go and apps/desktop/src-tauri; never accept an Electron implementation as the final patch.
src/preload IPC Map request/event semantics into typed Tauri/runtime RPC bridges.
Mobile/relay protocol Preserve wire compatibility and remote/SSH behavior; review both desktop and mobile consumers.
Electron builder/updater/signing/branding Review the bug intent, then implement only if Pebble Tauri release architecture has the same invariant.
Orca account/branding/domain-only changes Usually not-applicable, unless they reveal a generic product contract.

Priority order inside every release issue

  1. Security, data loss, persistence durability, destructive worktree/PTY behavior.
  2. Crash/OOM, daemon/PTY/session recovery, SSH and remote-runtime correctness.
  3. Cross-platform Windows/Linux/macOS and updater/release integrity.
  4. Source control/provider correctness, including GitLab and non-GitHub behavior.
  5. Renderer UX, performance, mobile, localization, and optional features.

Release migration issues

Completion contract

  • Every changelog bullet is classified in its release issue.
  • Every port item links a Pebble issue/PR/commit and regression test.
  • Every already-present item links evidence in Pebble history.
  • Every superseded-by-Pebble item names the replacement Go/Tauri contract.
  • Every not-applicable item records why the Orca-only behavior does not transfer.
  • The unreleased-main issue is refreshed when upstream advances.

Metadata

Metadata

Assignees

No one assigned

    Labels

    semantic-portRequires semantic adaptation across Pebble architecture boundariesupstream-orcaSemantic ports and review of upstream stablyai/orca changes

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions