[shhdwi]

Bumps both packages to 0.29.0. It ships everything Anirudh merged since 0.28.0, plus #707 and the 0.28.1 MCP listing. That listing (#742) was published but never merged into main, so this PR carries it.

What's in it

• Find why trail sync crashes a laptop, and fix it #736: background builds no longer pile up and hang a laptop. The build lock names its process, and builds run at low CPU priority.
• Cut trail's peak memory on big repos #737: lower peak memory on big repos (4.3 GB → 2.9 GB for one turn on a repo with 88k symbols).
• Install trail without sudo #734: install and upgrade without sudo, plus a plain message on an old Node.
• Clearer path from Trail Code to team.trailhq #730: the "sign in to Trail" link is on by default. It's still off with DO_NOT_TRACK, telemetry off, in CI, or with TRAIL_CLOUD=0.
• Init's always-follow offer says what the rule does #724: trail init's always-follow offers say what each one does.
• share-session sends a person's whole Claude setup #740: trail share-session bundles. These stay off unless TRAIL_SHARE_SESSION=1 for this release, as the PR planned.
• Fix npm downloads showing 0 after the rename #723: downloads badge (CI only, nothing in the package).
• Parse the depth tier on WASM, so installing compiles nothing #707: the depth tier parses on WASM, so installing compiles nothing. Native tree-sitter-* dependencies are gone from the package.

Checked on the packed tarballs

• Tests: 4,184 of 4,194 pass with a scratch HOME, and 8 are skipped. Two graft → trail move tests fail only on a laptop that already has a real trail on PATH. They fail the same way on main there, and pass with it off PATH.
• Both tarballs carry the same telemetry key as 0.28.1. mcpName is on trail-code only.
• A clean npm i -g of both tarballs adds 56 packages and has no .node files, so nothing compiles. trail share-session without the flag prints one line and exits 1.
• Upgrade in a real repo: pallets/click set up with the published 0.28.1, then upgraded to 0.29.0. A real Sonnet session fixed a planted off-by-one. SessionStart refreshed the wiring from 0.28.1 to 0.29.0, and the prompt, post-edit and Stop hooks all fired with no errors.
• Main's last Windows run failed one test once (skills-prompt.test.ts:132, the Cursor case got no context). The test file hasn't changed since feat(skills): trail init look-back, hook wiring with skills on by default, and learnings without repeats #658, so it looks like a slow runner. It's being re-run.

🤖 Generated with Claude Code

[trailhq-graft]

🌱 graft blast radius

Nothing outside this diff depends on it. 1 area changed; no indexed dependents at depth 2.
Tag: @anirudhkumar-nanonets — Trail Packing

Who knows this code — 1 person across 1 area

Area	Who knows it
Trail Packing · changed	@anirudhkumar-nanonets — 1 commit, last 24d ago

Ownership is git history over each area's own files, weighted towards recent work (120-day half-life). Merge commits and bots are dropped, and you are dropped from your own PR. A name with no @ has no GitHub handle in its commit email — tag them by hand, or add a .mailmap entry. A suggestion from history, not a CODEOWNERS rule.

Test signal per changed area — 1 –

Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.

• – Trail Packing — no function, method or class changed here

⚠️ 7 changed files not in the graph (.mcp.json, .trail/learnings/2026-10-29-the-mcp-registry-listing-reads-the-shrish.md, .trail/learnings/2026-10-30-the-mcp-registry-listing-reads-the-shrish.md, CHANGELOG.md, package-lock.json) — no parser claims the extension, or the index predates the file.

_{graft blast · origin/main...HEAD · depth 2 · 8 changed files}

Open the interactive graph → — click an area to see its dependent symbols at file:line.