[dodeja]

What

Removes files that ship to users or sit in the repo without a reader, and stops the @terminal49/sdk tarball from carrying test and dev output. Each change is its own commit: docs, then SDK and MCP code, then tooling.

Commit	Change
docs:	Delete docs/content/analytics.js, a fully commented-out Segment snippet. Mintlify loads every .js under docs/ on every page. docs/segment.js is the live loader.
docs:	Delete 14 unreferenced images in docs/images/ (4.2 MiB).
docs(mcp):	Delete EXECUTION_SUMMARY.md, IMPROVEMENT_PLAN.md, and TEST_RESULTS_V2.md (October 2025 notes about MCP SDK 0.5 and 1.20), and the TESTING.md link to them.
fix(sdk):	Stop publishing compiled tests, type tests, test helpers, dev scripts, and source maps that point at unshipped src/. Delete the unused src/scripts/example-deserialize.ts.
chore(mcp):	Mark @terminal49/mcp "private": true.
chore:	Delete public/.gitkeep and sdks/typescript-sdk/src/fixtures/.gitkeep. Both directories hold tracked files.

SDK tarball

package.json files now excludes dist/**/*.test.*, dist/**/*.test-d.*, dist/test, and dist/scripts. tsconfig.json no longer emits sourceMap or declarationMap. The maps referenced ../src/*.ts, which the tarball never included, so bundlers reported them as broken. The build itself is unchanged, so npm run smoke and npm run example still run from dist/scripts. The publish workflow runs the same npm run build.

npm pack --dry-run --workspace @terminal49/sdk	Before	After
Files	214	54
Packed	223.7 kB	109.8 kB
Unpacked	1.54 MB	748 kB

Before, the 214 files were 54 library files, 42 test outputs (205 kB), 106 maps (575 kB), 8 script outputs, and 4 test-helper outputs. After, only the 54 library files remain: dist/index.*, dist/client.*, dist/client/**, dist/generated/**, dist/types/**, README.md, and package.json.

I checked the packed tarball from a clean consumer project. npm install ./terminal49-sdk-0.6.0.tgz succeeds. import('@terminal49/sdk') returns Terminal49Client. tsc --strict --module nodenext type-checks new Terminal49Client({ apiToken }) against the shipped .d.ts.

Evidence for the deletions

• Images. unref.mjs (a script that lists tracked assets whose basename no other tracked text file mentions) reports these 14 on main. I also searched docs/openapi.json, the Postman collection, and all 309 remote branches. Only stale branches reference any of them. The one open PR among them, [CHORE] add current status filter docs #221, has carriers_screenshot.png and new_webhook.png only in its old base, and its diff against main does not add them. The four *_route* and *vessel_positions* screenshots lost their last reference in 28c2fe3 (Add map_geojson documentation). The docs site serves docs/images/ under /images/, so an external link to one of these URLs would now 404. I can't rule that out from the repo.
• MCP notes. Only TESTING.md linked to them, and that link is removed here. None of the three files is in the mcp-v2 stack diff.
• @terminal49/mcp private. npm view @terminal49/mcp returns 404. No workflow publishes it. The MCP registry entry (server.json in the mcp-v2 stack) lists only the hosted remote. Release-please only rewrites its @terminal49/sdk dependency. npm install --package-lock-only leaves the packages/mcp lockfile entry unchanged.

Verification

On this branch, Node 24.11.0:

Check	Result
npx vp run check	pass
npx vp run test	pass (CLI 153, SDK 418, MCP 550)
npx vp run build	pass
git merge-tree against #458, #461, #462, #459, #465, and mcp-v2/08-release	no conflicts

Follow-ups

• ci.yml still has dead branch filters (cursor/vite-plus-toolchain-cdbd, master). ci.yml is in the mcp-v2 stack diff and in chore(deps): update MCP, gateway, and SDK dependencies and clear npm audit #458, so this PR leaves it alone.
• packages/mcp/scripts/sdk-setup.mjs pins @terminal49/sdk@0.2.0 in its published mode. The docs that describe sdk:setup are in the mcp-v2 stack.
• On main, npm install with npm 11 rewrites package-lock.json into a lockfile that npm ci rejects. It drops @modelcontextprotocol/sdk and @anthropic-ai/sdk, which are optional peers under mintlify. chore(deps): update MCP, gateway, and SDK dependencies and clear npm audit #458 removes mintlify. This PR does not touch the lockfile.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking cleanup needed for SDK packages made from previously built checkouts.

Findings

1.  Old maps still ship ▶

Fix with agent prompt

### Issue 1
sdks/typescript-sdk/package.json:11
If a developer built the base branch before switching to this branch, rebuilding leaves the old `.js.map` and `.d.ts.map` files in `dist`. Disabling map output does not delete existing files, and `"dist/**/*"` still includes them. A local `npm pack` therefore still ships maps that point to missing source files.

Exclude map files explicitly or clean `dist` before building. The fresh checkout used by the publish workflow avoids this case.

```suggestion
    "dist/**/*",
    "!dist/**/*.map",
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Removes unused docs assets and historical MCP notes, marks @terminal49/mcp private, and trims the published SDK.

• The published SDK package leaves tests and development files out.
• The docs tree drops an inactive analytics snippet and unused images.
• MCP docs no longer include old SDK plans or test results.
• The MCP package is marked as private.
• Unused helper files and placeholder files leave the repository.

Acknowledged by dodeja: external links to the deleted images may return 404. The PR explicitly accepts this possibility because external use cannot be ruled out.

_{Reviews (1) · Last reviewed commit: "chore: delete .gitkeep files from direct..." · Reviewed by Greptile}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
terminal49	🟢 Ready	View Preview	Oct 19, 2026, 12:27 AM

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
api	Ready	Preview	Oct 19, 2026 2:50am UTC

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T02:50:55.632309Z	2292fcf	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[greptile-apps]

Old maps still ship

If a developer built the base branch before switching to this branch, rebuilding leaves the old .js.map and .d.ts.map files in dist. Disabling map output does not delete existing files, and "dist/**/*" still includes them. A local npm pack therefore still ships maps that point to missing source files.

Exclude map files explicitly or clean dist before building. The fresh checkout used by the publish workflow avoids this case.

Suggested change

	"dist/**/*",
	"dist/**/*",
	"!dist/**/*.map",

Prompt To Fix With AI

This is a comment left during a code review.
Path: sdks/typescript-sdk/package.json
Line: 11

Comment:
**Old maps still ship**

If a developer built the base branch before switching to this branch, rebuilding leaves the old `.js.map` and `.d.ts.map` files in `dist`. Disabling map output does not delete existing files, and `"dist/**/*"` still includes them. A local `npm pack` therefore still ships maps that point to missing source files.

Exclude map files explicitly or clean `dist` before building. The fresh checkout used by the publish workflow avoids this case.

```suggestion
    "dist/**/*",
    "!dist/**/*.map",
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[dodeja]

Fixed in d862ac4 with !dist/**/*.map in files. To check it, I created a stale dist/stale-dummy.js.map and dist/client/stale-dummy.d.ts.map. Before the change, npm pack --dry-run --workspace @terminal49/sdk listed both. After the change it lists no .map files, and the pack keeps its 54 files, including dist/index.js and dist/index.d.ts.