chore(upstream): adopt the 2026-08-15 T3 Code batch

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.

[rynfar]

Upstream had a hundred commits waiting since the last cursor, and it was mostly
backlog: 86 of the 99 candidates are fix, largely old community pull requests
that all merged the same day. Pylon carries the same inherited defects, so the
decision was to take everything that is not T3 infrastructure.

93 adopted, 6 skipped, reviewed through a5e29edee.

What landed

Server and orchestration repair (bounded activity hydration, the wire projection
for streaming tool.updated, receipt replay scoped to its own aggregate, SQLite
busy_timeout, surviving a write to a dead socket). Eleven provider fixes, six of
them Claude. The web styling refactor plus panels, sidebar, theme, markdown and
eight composer fixes. Desktop, mobile, source control, SSH, terminal, marketing.

Two features worth calling out: opening a remote environment in your local editor
over SSH (#6572), which serves the remote-ready pillar directly, and Chrome-style
hold-to-quit on desktop (#5508).

What was skipped, and why

• A feature and its own revert (#6657), both inside the range. They cancel
  exactly, so taking them is 32 conflicting files for a net no-op.
• AUR packaging (#4128) — t3code-bin PKGBUILDs against pingdotgg/t3code
  releases and a workflow needing T3's AUR secrets.
• Feature requests to Discussions (e9ae134c5) — T3 repository governance.
• A CLAUDE.md symlink fix (#3929) already true in Pylon.
• The mobile Grok mark fix (#4542) — Pylon fixed the same bug independently
  in ad1693bb3, tuned to Pylon's own resized hero. Upstream's coordinates assume
  T3's artwork.

Pylon-first resolutions

Branding: the new DMG installer backgrounds shipped a "T3 CODE" wordmark and
"Drag T3 Code to Applications"; the new PWA manifest hardcoded T3's #161616,
which would flash against Pylon's #0a0a0a; two docs/user/ pages picked up
"T3 Code" in shipped-product voice. All rebranded.

Two composition calls, both recorded in the ledger:

• #4781, send reachable while running. Pylon already solved this with a
  queue-follow-up button, but gated on a provider capability, so providers
  without a session input queue still had the bug. The two are composed rather
  than chosen between: the queue affordance wins where it exists, upstream's
  plain send is the fallback.
• #4755 imports lucide's TerminalIcon; Pylon draws that indicator with
  DotMatrix state="terminal", so the import was dropped.

Upstream also retired apps/desktop/resources/icon.* now that packaging and the
launcher read from assets/<channel>/. Pylon's icon exporter stopped emitting them.

One near-miss worth knowing about

Resolving the styling-refactor conflict reverted pnpm-lock.yaml, silently undoing
what the Windows update-install pick had added one commit earlier. The branch was
left requiring msgpackr-extract and @electron/asar without locking either, and
recording the old @ff-labs/fff-node patch hash against the new patch file — so
@t3tools/scripts would not typecheck and all 53 of its tests failed to load.
Fixed in d50270899, regenerated with Pylon's pinned pnpm.

Verification

Typecheck clean across all nine packages. vp lint exits 0 with three warnings,
all in upstream-authored code. vp fmt --check clean over 2,898 files. Tests: web
2,758 / client-runtime 658 / shared 355 / contracts 342 / scripts 239 / server
1,966 passing.

Two known failures, neither from this batch:

• accountDrainEndToEnd.test.ts hangs 120s — fails identically on a clean
  origin/pylon worktree, verified against a baseline checkout.
• build-desktop-artifact.test.ts fails when run from inside Pylon, because an
  Electron host exports ELECTRON_RUN_AS_NODE=1 and the code under test spreads
  process.env. With env -u ELECTRON_RUN_AS_NODE, 53/53 pass. CI is unaffected.

No integration pass in a real client. The batch touches the composer, sidebar,
theme, DMG chrome and the PWA manifest, so a web pass is the obvious next step —
worth doing before merge.

Claude Opus 5 (1M context) in Claude Code.

---

^{Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.}

[github-actions]

Thread transfer impact

⚠️ The latest CI run did not produce a thread transfer result for fccc704.

This comment will update automatically after the next completed run.