[LesleyMurfin]

ELI5

Lesley's PC runs Orca from an extracted AppImage in WSL. The Revive fork is more than a thousand commits behind upstream, and several leftover PRs look unfinished. This PR is only a map: what already landed, what is still open, what must wait for factory canary, and how to refresh the PC without rewriting ~/.local/bin/orca.

What Changed

• Added docs/reference/pc-wsl-orca-update-path.md — inventory of LesleyMurfin/orca and stablyai/orca PC/WSL/AppImage/CLI/pairing work, landing targets (upstream vs fork/revive_labs), safe payload-only update steps, and explicit GO steps for a WSL launcher retarget.
• Allow-listed that file in .gitignore (same pattern as the other tracked docs/reference/ pages).

No runtime, CLI installer, or launcher code changed.

Why

PC/WSL is stuck on a PRD-5175 bridge-free extract (~/.local/share/orca/squashfs-root) while upstream stablyai#15081 (merged, in v1.4.195+) wants to retarget the registered CLI to ~/.cache/orca/appimage/.../launcher/orca-ide. The WSL CLI is LOCKED until Lesley says GO. Factory stablyai#18790 canary is already in flight — do not duplicate it here.

Linked Issue

N/A — inventory / ops tracking for the PC/WSL lane (Lesley ask 2). No product bug being fixed.

Visual Proof

N/A — documentation only; no UI or rendered behavior change.

Testing

Inventory was gathered from GitHub (gh pr / gh release / compare) on 2026-09-06:

• Fork main bc98655a3 (2026-08-25) is 1,146 commits behind stablyai/orca main 6fcd82918.
• revive_labs was not accessible from this token; Drive had mtl-02 factory settings only. Confirm canary status on that repo before any serve cutover.
• Did not run live WSL commands, did not retarget ~/.local/bin/orca, did not apply factory.

Platforms: GitHub API + this cloud checkout only (Linux). No PC/WSL host access.

• I manually tested these changes locally
• Automated tests added/updated, or explained why not below

Docs-only; no test surface.

Review

Do not self-merge. Draft, same rule as the other LesleyMurfin/orca PRs.

Do not treat merge of this PR as a WSL retarget GO.

Agent skill upstream boundary

• Not applicable, or this change follows docs/reference/agent-skill-sharing-upstream-boundary.md and copies or mechanically translates no upstream skill-installer source, tests, fixtures, registry entries, path tables, comments, or documentation.

Notes

Ensure no issues in: Security, Cross-platoform support (Linux, Windows, Mac), Remote SSH, Mobile, general backwards compatibility, performance

This stays on the Revive fork. Do not open a twin on stablyai/orca — the locks and factory/canary notes are Revive-ops, not product.

Checklist

• This PR is small and focused
• I explained what changed and why (including ELI5)
• Before/after screenshots or videos attached for UI changes, or N/A with reason
• Self-reviewed for correctness, security, and performance
• Cross-platform, SSH/remote, and path/shortcut impact considered (or N/A)
• pnpm lint, pnpm typecheck, pnpm test, and pnpm build pass (or CI will cover; local preferred)

Docs + one .gitignore line; product gates N/A.

Existing PRs this inventory points at (do not duplicate)

Land	URL
Upstream PTY reap (canary in flight)	stablyai#18790
Upstream local worktree owner fallback	stablyai#16829
Upstream orca serve stats (stale draft)	stablyai#10612
Upstream AppImage extract-once (merged, GO to adopt)	stablyai#15081
Fork drafts #15–#22, #24	#15 … #24

  

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 79c8076e-435b-49af-ae46-ec074383c51a

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[svc-orca]

Merge order: land #26 before #49

This is a merge-ordering note, not a review blocker. The coupling below is file adjacency and rebase churn only — it is not a functional dependency. This PR is correct and self-contained on its own: merging out of the suggested order produces a merge conflict someone has to resolve, not a broken build or a missing symbol.

Shared file: .gitignore — and here the hunks genuinely overlap, so a conflict is likely rather than merely possible:

• This PR (docs(pc-wsl): inventory unfinished Orca work vs upstream — WSL CLI LOCKED #26) edits the docs/** allowlist block at lines 116–121 (adds 2 lines).
• feat(ssh): dual-channel multiplexer to isolate interactive traffic from background scans #49 rewrites the same allowlist block, lines 98–121.

#26 is 2 files; #49 is 13. Landing #26 first means #49 rebases once over a small, easy-to-read .gitignore change. The reverse order makes the #26 author re-derive their two lines on top of a wholesale rewrite of the surrounding block.

Either way the resolution is mechanical: keep both allowlist entries. Nothing functional depends on the order.