chore(mcp): release cases_list customField fix to npm under latest tag (#342)

* chore(packages): add changeset for cases_list customField value fix

Without a changeset the Changesets release workflow won't open a Version
Packages PR, so the fix would merge to main but never publish to npm.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* chore(mcp): publish to the latest dist-tag instead of beta

The MCP server is out of beta, so releases should land on the `latest`
npm tag (what `npm install @testplanit/mcp-server` resolves to) rather than
`beta`.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: therealbrad

.changeset/cases-list-customfield-value.md

@@ -0,0 +1,5 @@
+---
+"@testplanit/mcp-server": patch
+---
+
+Honor the `customField` value filter in `cases_list`. Passing `{ name, value }` now filters by value (resolving Dropdown/Multi-Select option names to the stored option ids), unknown keys are rejected by a strict schema, and an unknown field name or invalid option returns a validation error instead of silently returning unfiltered results. Fixes #333.

packages/mcp-server/package.json

@@ -52,7 +52,7 @@
   "publishConfig": {
     "provenance": true,
     "access": "public",
-    "tag": "beta"
+    "tag": "latest"
   },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",