chore(mcp): release 0.29.0 — ship the guided first-run walkthrough

[ArtyETH06]

Version bump only — no behaviour change. This is the release that makes "Walk me through Leadbay." actually work.

Why

The walkthrough merged in #175 and #179 (Aug 10–11) and has never shipped:

Latest tag	mcp-v0.28.0, 2026-08-03
npm latest	0.28.0
Contains leadbay_getting_started?	No — the tag predates both PRs

A user on the live connector who types "Walk me through Leadbay" today gets nothing; the prompt isn't registered.

CHANGELOG.md also filed the feature under ## 0.28.0 — a version already published without it. Retitled to 0.29.0 and dated. The entry's content was already correct; only its number was wrong.

What changed

The four version carriers, bumped together because packages/mcp/test/audit/server-json-version.test.ts enforces they stay on the same line:

File	Change
packages/mcp/package.json	0.28.0 → 0.29.0
packages/mcp/server.json	top-level version, packages[].version, and the @leadbay/mcp@0.29 npx pin
.claude-plugin/plugins/leadbay/.claude-plugin/plugin.json	version + its own npx pin
CHANGELOG.md	## 0.28.0 — … → ## 0.29.0 — 2026-08-17 — …

Scope of the release

Everything on main since mcp-v0.28.0 is the walkthrough, plus an eval-runner restore (9e31ac4) and a telemetry test (1e6a819). Nothing else user-facing, so no other CHANGELOG entry is owed.

What merging does

auto-tag.yml fires on a packages/mcp/package.json change to main: it pushes mcp-v0.29.0 and dispatches release.yml (npm + MCP Registry + .dxt/.mcpb assets) and build-image.yml (the hosted mcp.leadbay.app connector). One merge redeploys both surfaces.

Gates

Full workspace pass on this branch:

• pnpm -r build ✅ (dxt bundle builds as leadbay-0.29.0.dxt / .mcpb)
• pnpm -r test ✅ — 1368 tests, 203 files (core 646, mcp 659, components 47, promptforge 16)
• pnpm -r typecheck ✅
• pnpm prompts:check ✅ — generated files up to date

Merge order

1. This PR → cuts mcp-v0.29.0 and publishes.
2. Then docs(mcp): document the introduction path — "Walk me through Leadbay" (EN + FR) userdoc#23, which documents the walkthrough and is held draft precisely because it describes a feature users can't reach yet.