[Easy] Add zod schema unit tests for all 6 MCP tool input contracts

[hoainho]

🌟 Before claiming this issue

Two quick steps before you open a PR:

1. ⭐ Star the repository — low-friction signal that you'll follow through
2. 💬 Comment I'll take this (or similar) below — prevents two contributors racing on the same issue

Full policy: CONTRIBUTING.md → How to claim. If a claim is older than 7 days with no PR, you can reclaim it politely.

---

Context

MCP tools defined in openspec/changes/mcp-server-v1/specs/mcp-tools/spec.md use zod schemas for input validation. Each schema needs unit tests covering happy path plus invalid-input rejection so regressions are caught before hitting end-to-end.

Where to look

• The 6 tools: list_inspected_tabs, get_fiber_node, get_issues, get_renders_for, analyze_performance, explain_redux_action
• Implementation files: cli/src/tools/*.ts (created by tasks 4.1 to 4.5)
• Add test files: cli/src/tools/*.test.ts using Vitest

Expected outcome

• Each of the 6 tools has its own .test.ts file
• Each file covers valid input parses correctly, every required-field-missing rejection, every wrong-type rejection
• Tests use Vitest expect toThrow for rejection cases

Estimated effort

M (3 to 6h)

How to claim

Comment "@hoainho I will take this" to claim. PR within 10 days or unclaimed.

Acceptance criteria

• npm test cli/src/tools passes with at least 18 test cases (3 per tool minimum)
• Coverage report shows 100% line coverage on the zod schema definitions
• CI workflow runs these tests on PR

[gilangages]

Hi! @hoainho
I would love to work on this issue. Could you please assign it to me? Thank you!

[hoainho]

👋 Hi @gilangages — checking in on this one. No pressure at all, just don't want it sitting silently if you've moved on to other things.

Are you still planning to take this? If yes, no rush — just drop a quick "still on it" reply. If you'd rather unclaim and let someone else pick it up, that's totally fine too — just let me know and I'll re-open it for grabs.

For reference, the relevant spec is at openspec/changes/mcp-server-v1/specs/mcp-tools/spec.md — the 6 tools whose zod schemas need tests are list_inspected_tabs, get_fiber_node, get_issues, get_renders_for, analyze_performance, explain_redux_action. Each scenario in the spec is essentially a ready-made test case.

Happy to pair on a specific tool if any of them feel unclear.

[gilangages]

Hi there. Thank you for the reminder. Regrettably, I don't feel confident enough with this specific setup to complete it properly. I will unclaim the issue now so it can be re-opened for others. Apologies for the delay!

[yizhi-shi]

@hoainho I'll take this

[hoainho]

Hi @yizhi-shi — welcome and thanks for picking this up! 🎉

Quick orientation:

The task: Add a CHANGELOG.md entry for v2.0.0 release. Context lives in issue body — basically we shipped a major version but the CHANGELOG wasn't updated. Goal is a clean, readable v2.0.0 section under ## [Unreleased] (or promoted to ## [2.0.0] if you're confident on the date).

Reference commits for v2.0.0: eb14410 (major UI overhaul, Feb 22 2026) is the headliner. Run git log eb14410^..HEAD --oneline for the full picture.

Format: We use Keep a Changelog style. The existing ## [Unreleased] section in CHANGELOG.md already has M-A + M-B + claim-rule entries you can reference for tone/depth.

Pre-merge requirements (no surprises):

1. ⭐ Star the repo before opening the PR — Star Check workflow enforces this on merge
2. Soft 7-day claim window — totally flexible, just drop a comment if you need more time, no judgement

@gilangages thank you for unclaiming honestly — that's the right call and exactly the behavior the soft-claim rule is designed for. Always welcome to pick something else from good-first-issue when you feel ready. No hard feelings.

@yizhi-shi — claim accepted, the clock starts now. Ping me here if anything's unclear.