chore(mcp): bump fsb-mcp-server 0.9.1 -> 0.9.2 to ship numeric-param coercion#64
Merged
Merged
Conversation
…coercion
Bumps `mcp/package.json`, `mcp/server.json` (top-level + packages[0]),
`mcp/src/version.ts` (FSB_MCP_VERSION), the parity test's canonical
target, and the rebuilt `mcp/build/version.{js,d.ts}` artifacts from
0.9.1 to 0.9.2 in lockstep. Prepends a 0.9.2 entry to `mcp/CHANGELOG.md`
referencing PR #63 (commit `fae2aa01`).
Pure release plumbing -- the numeric-param coercion fix landed via
PR #63 on 2026-05-16, but npm-published 0.9.1 still rejects every
MCP client (e.g. Claude Code) that serializes integer params as
JSON strings with `Expected number, received string`. Bumping to
0.9.2 unblocks the next `npm publish fsb-mcp-server`.
No code logic changes, no protocol changes, no dependency bumps.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
LakshmanTurlapati
added a commit
that referenced
this pull request
May 18, 2026
* docs: start milestone v0.9.70 Showcase Dashboard Reliability (Streaming + Sync + Viewport) Three target features: (1) diagnose-first dashboard DOM-streaming fix continuing STREAM-07 attempt 2 of 5 from v0.9.69 Phase 276; (2) Sync-tab remote-control restoration on full-selfbrowsing.com; (3) 16:10 desktop viewport lock on the dashboard preview pane (mobile out of scope). PROJECT.md "Current Milestone" rewritten to v0.9.70 with goals + target features + key constraints + deferred candidates. Footer "Last updated" bumped to 2026-05-16. "Last shipped" updated to reflect v0.9.69 SHIP + four post-milestone fixes (PR #57/59/61/62/63/64) and the published artifacts (extension v0.9.67 zip, mcp-v0.9.2 npm, Fly auto-deploy). STATE.md frontmatter reset (milestone v0.9.70, status in_progress, progress 0%). Current Position set to "Not started (defining requirements)". Active Milestone Risk Register replaced with Active Milestone Carry-Forward (STREAM-07 attempt 2 + CWS click-through). Quick Tasks Completed table extended with PRs #59 / #61 / #62 / #63 / #64. Pending User-Gated Actions: v0.9.0 npm publish marked superseded by v0.9.2; added v0.9.67 -> extension-v0.9.67 retag decision. Phases dir cleared (8 v0.9.69 phase directories removed by gsd-tools phases clear). Carries over: 999.1-mcp-tool-gaps, INTEGRATION-CHECK.md, v0.9.63-INTEGRATION-CHECK.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(showcase): lock dashboard preview pane to 16:10 on desktop Phase 280 VIEWPORT requirement: the live DOM preview frame in the showcase dashboard had no fixed aspect ratio and stretched freely to container height, producing inconsistent letterboxing and the bug visible in milestone 0.9.70. Pin it to 16/10 on desktop, unset on mobile (<=768px and <=480px) where vertical layout takes over, and keep Maximized (100vh) and PiP layouts coherent (auto for maximized, explicit 16/10 for PiP). Adds tests/dashboard-preview-aspect-ratio.test.js — parses the SCSS and asserts the rule lives in the right selectors (desktop, both mobile media queries, Maximized, PiP). Wired into the root `npm test` chain. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release plumbing for the numeric-param coercion fix landed in PR #63 (commit `fae2aa01`). Bumps the package version across all 5 in-tree sites + rebuilds the version artifact so the next `npm publish fsb-mcp-server` carries the fix to MCP clients.
Why now
PR #63 fixed the server-side schema so MCP clients (observed: Claude Code) can pass tool params with string-encoded integers (`tabId: "695936610"`) without being rejected by Zod. That fix is on `main` but NOT on npm — the published `fsb-mcp-server@0.9.1` (2026-05-16) still has the bug. Every Claude-Code-as-MCP-client call to `switch_tab` / `close_tab` / `read_page` / etc. fails today.
Changes
Anti-scope
Test plan
Operational follow-up (user-gated)
After merge:
```
cd mcp && npm publish
```
Tag + GitHub release optional per prior pattern.
🤖 Generated with Claude Code