Skip to content

chore(fork): support isolated worktrees and local app builds - #2

Closed
Quicksaver wants to merge 6 commits into
base/mainfrom
base/fork
Closed

Quicksaver wants to merge 6 commits into
base/mainfrom
base/fork

Conversation

@Quicksaver

Copy link
Copy Markdown
Owner

Summary

This fork needs repeatable local builds and isolated development work across its Windows and macOS worktrees. Keep the shared build and verification tools on base/fork so feature branches can use them without carrying copies.

What changed

  • Coordinate worktree updates, PR publication, review, integration, and unattended builds through repository skills. Wait ten minutes after pushing before reviewing updated branches.
  • Isolate desktop state, coordinate desktop and mobile verification capacity, and cache upstream baseline results by host and toolchain.
  • Preserve single-origin development across loopback, LAN, and Tailscale connections, including host-aware proxy targets and larger development HTTP headers.
  • Prepare worktree-owned Android devices and native clients with short CMake paths, ordered dependency preparation, React Native ABI alignment, and bounded build retries.
  • Add local macOS certificate signing and desktop installer handoffs. Point mobile builds and updates at the fork's Expo project and Apple development team.

Validation

Four scoped typechecks passed; focused tests passed 216 checks with two unresolved failures.
  • vp run --filter @t3tools/shared typecheck passed.
  • vp exec tsc --noEmit -p scripts/tsconfig.json passed.
  • vp run --filter @t3tools/web --filter @t3tools/mobile typecheck passed for both clients.
  • Lint of changed TypeScript and JavaScript files passed with one no-control-regex warning in scripts/worktree-baseline.ts.
  • Focused tests across dev proxying, dev runner and sharing, desktop artifact building and signing, native clients, Android preparation, baseline caching, and runtime coordination: 216 passed, 2 failed across 11 files.
  • Both failures are in scripts/build-desktop-artifact.test.ts: Linux capture-helper staging expects bare cargo but resolves a Windows executable path, and the cross-architecture Windows payload test unexpectedly observes a native probe.
  • The same-host upstream baseline for 95030dc674883f0f2a7fd034b32ce742c8cf55d0 has no results for those desktop-build tests, so their upstream status remains unverified.
  • git diff --check passed. Integrated UI verification was excluded from this branch's assigned scope.

🤖 Generated by GPT-6 in Codex via T3 Code

Quicksaver and others added 6 commits September 27, 2026 00:51
🤖 Co-authored by GPT-6 in Codex via T3 Code
🤖 Co-authored by GPT-6 in Codex via T3 Code
…ree deletion

Describe the screenshot-unavailable reasons, host frame-liveness probe, display power-save block, broker eviction grace, and the idle Windows display limitation in the Preview Automation Reliability section, and the prune-then-delete and classified delete failures in the Version Control Panel section.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
🤖 Co-authored by GPT-6 in Codex via T3 Code
🤖 Co-authored by GPT-6 in Codex via T3 Code
@github-actions github-actions Bot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:XXL labels Sep 27, 2026
@Quicksaver Quicksaver closed this Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XXL vouch:trusted PR author is trusted by repo permissions or the VOUCHED list.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant