[leomontigatti]

T3 update review: 0.1.4-nightly.20261028.3822 → 0.1.5-nightly.20261029.3873 (6 releases)

Needs you: nothing. No active entry broke and no watching entry became ready. The changes below
are evidence for the shared t3-dependencies.md; nothing else is proposed.

Improves

• shared, delegate-task-reviews: orchestrator_capabilities search now drops words that
  name the provider (pingdotgg/t3code#26448).
  Diff of listCapabilityModels in OrchestratorMcpService.ts: "Search words naming the
  provider are dropped; other words list matches." Before, every word had to appear in the
  model's slug, name or sub-provider, so a word naming the provider instance could match only
  some of its models. The PR title says such searches "showed only dead models". Finding a legacy
  model with search is now more reliable. Proposed edit: an evidence sentence on the entry. The workflow needs no
  change.
• shared, own-thread-readable: t3_thread_list takes allProjects: true, each item now
  has its projectId, and the result's top-level projectId is null for an all-projects list
  (#26442; OrchestratorMcpThreadListInput
  and OrchestratorMcpThreadListResult in packages/contracts/src/orchestratorMcp.ts).
  currentThreadId stays, and a call without the flag still lists the caller's project, so
  "A lost context is recovered from T3" and the housekeeping survey work as before. Proposed
  edit: an evidence sentence on the entry. Nothing to adopt: housekeeping sweeps one repo at a
  time.

Checked with no effect on us:

• ThreadLaunchService.ts only adds the launch's message sequence
  (thread-launch-workspace).
• ScheduledTaskService.ts lets a bound task follow its thread when a No project thread
  becomes a project (#26767). Our scheduled
  reviews are unbound (scheduled-reviews).
• The new device-tool instructions (#25661)
  apply only to sessions with the device capability. No project drives a simulator.
• #26164 adds a project fallback model for
  t3_thread_launch when no model is given. Our launches inherit the caller's model.
• Thread links for outside MCP clients (#26642).
• #26637 changes T3's own AGENTS.md, not the
  injected instructions. The browser section in orchestrationInstructions.ts is unchanged.

Not covered

• infra: no docs/agents/t3-dependencies.md on origin/master or on any branch.

Still ready

• shared, preview-tools-verification: adoption step one has been under way since 2026-10-26.
  Step two (dropping the browser CLI) waits for ten PRs verified with preview_snapshot and no
  lost click.

Other checks: the watched issues and PRs are unchanged. #17889, #17813, #22805, #11078 and
discussions 24108, 18047, 23245 and 23305 are all still open. #17813 has a new comment (Windows,
506 kept worktrees), but no fix has merged. No drift: every Used by file and heading exists,
and the project entries (en-escena, rubens, pcp, enescena, aldi) still hold.

Projects whose behaviour changes: none. This PR only adds evidence to the shared t3-dependencies.md.

Review

Tier: readback, reviewed 732e1e0

• readback (Luna): no surprises

Readback

The diff adds two notes from a T3 release to t3-dependencies.md: t3_thread_list can now list every project and returns each thread's project ID, and model search drops words that name the provider before matching, so they no longer narrow the results to stale models. Nothing surprising. 0 surprises; Would merge: yes.

🤖 Generated with Claude Code