[vanessa-livamap-ai]

Problem and root cause

The upstream-sync follow-up (dd26ca3aaff0, failed task t-11100621-cebd) was blocked before its coding agent started by Unicode filename handling in golden tree transfer. The fork's upstream mirror advanced, but livemap did not. This authorized recovery cloned the public repository directly inside an isolated Boxy VM with Codex, preserving real Git histories and avoiding the broken transfer path.

The mobile thread-header conflict is caused by upstream moving mutable pane state into useWorkspacePaneState and removing the keyboard/compact AppBar API, while the fork wraps the header with its relay provenance badge.

Resolution and changed files

• The only manual merge resolution is apps/mobile/src/features/threads/ThreadHeader.tsx: adopt upstream hook ownership and remove the obsolete compact prop while retaining AriProvenanceBadge, nullable detailRef, and the non-null mount guard. Draft/server detail gating from PR25 remains intact.
• Preserve the existing Limrun hosts, livemap/ branding/scripts, ARI sidebar/settings/badges, thread flags and the latest blank-thread fix. The agent audited fork deltas; the host independently inspected the merge's remerge diff, which contains only the header resolution.
• This is a full upstream integration: 199 files, +158407/-80877 relative to the destination, mostly generated highlights C. Existing fork delta relative to upstream: 161 files, +6027/-181. Upstream changes include mobile/CI workflows; no extra local workflow edits were added.
• The dispatcher transfer repair is a separate artifact and is NOT included in this PR or installed on the host.

Exact inputs and tested output

Destination/first parent: 8dd22671da212675b632c714d8caffe81c81fe34 (livemap).
Upstream/second parent: 4c361199f47f6ea32a2c14835df392640d0f7c63 (pingdotgg/t3code/main).
Head: 50ed872fe3acb5c20eb96adabf4101e303725b18.
Tree: 2fb7399df0ab7298ee1e889f48ebba878ff6937f.

Host retrieved and verified the complete-history Git bundle, exact head/tree/ordered parents, and the manual resolution. Both remote input heads were refreshed and unchanged before publication; no overlapping open PR existed. Publication preserves the merge commit, not a flattened format-patch.

Verification executed on Boxy

Working directory: /task/t3code; Vite+ 1.4.0, package-script Node 26.12.1.

• vp install — PASS.
• vp run check:changed 8dd22671da212675b632c714d8caffe81c81fe34 --concurrency 2 — PASS against all 199 merge-delta files: format/lint, both knip passes, unused patches, generated GraphQL checks, typecheck of 41 affected packages, 82 test files/1549 tests, Node tests, and React Compiler coverage (73 selected files/78 assertions). Repeated on committed final head; cache reported nothing changed since passing run.
• vp test run apps/mobile/src/features/threads/threadContentPresentation.test.ts apps/mobile/src/features/threads/thread-route-hydration.test.ts apps/mobile/src/features/threads/thread-route-state.test.ts apps/mobile/src/features/threads/thread-inspector-navigation.test.tsx apps/mobile/src/features/layout/workspace/workspace-tabs-state.test.ts packages/contracts/src/ari.test.ts packages/client-runtime/src/device/limrunStream.test.ts packages/client-runtime/src/state/threadFlags.test.ts — PASS, 8 files/57 tests.
• vp run --filter @t3tools/mobile typecheck — PASS, non-fatal Effect suggestions.
• vp run --filter @t3tools/web build — PASS, chunk-size warnings.
• git bundle verify /task/merge.bundle and import/fsck in a separate bare VM repository — PASS. Host bundle verification and identity checks also passed.
• Private web preview with free Replay(dev): streaming/persisted messages, relay badge and ARI settings viewed. First Replay turn stopped at approval; no completed first turn is claimed. This is not native-mobile proof.

The first changed-check run failed because the fresh VM lacked Chromium; installed using node apps/web/node_modules/playwright/cli.js install --only-shell chromium, then reran successfully. No source change was needed for this environment failure. git diff --check reports inherited upstream generated/vendor whitespace (highlights.c and existing patch files); the agent compared the upstream-only delta and found matching counts. The header-only whitespace check passed. Unrelated upstream generated files were not reformatted.

Risks and reviewer checks

• Native device tools were unavailable: iOS/Android header layout, keyboard transitions, inspector controls and draft-to-server behavior have NOT been visually verified. Please test these on a real device/simulator before merging. No native screenshots were fabricated.
• Full CI suites, Electron desktop build/launch, release smoke, Rust/native lint, live Limrun/relay/tunnel operation were not run locally. GitHub CI is pending at publication, not claimed green.
• Check relay badges remain absent until server detail exists, and upstream pane/keyboard behavior is intact.
• livemap is the default/integration AND release-trigger branch. Merging triggers the existing Livemap desktop/CLI release workflow; latest observed release is v0.1.8-livemap.9939. PR creation alone does not deploy or publish that release. No merge, deploy or direct write to livemap/main was performed.

Prepared with GPT-6 / Codex harness on Boxy; host independently reviewed the merge artifact and published the PR.