chore: automatic README generation from user config schema

[gagik]

This is another step towards making the user schema the one source of truth about our configuration.

[Copilot]

Pull Request Overview

This PR introduces automatic README generation from the user configuration schema, making the user schema the single source of truth for configuration documentation. The changes implement a registry-based approach to store metadata for configuration fields and update the build process to automatically generate configuration tables.

• Enhanced Zod schema with metadata registry to store field-specific information like default value descriptions and secret flags
• Expanded the argument generation script to automatically update both server.json and README.md configuration tables
• Added ESLint rule to enforce use of zod/v4 only in config.ts

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/common/config.ts	Added metadata registry system with zod/v4 import and enhanced schema definitions with metadata
server.json	Updated configuration descriptions and added preview features environment variable
scripts/generateArguments.ts	Enhanced script to generate README configuration table and improved metadata handling
eslint.config.js	Added new ESLint rule for enforcing zod/v4 usage
eslint-rules/enforce-zod-v4.js	New ESLint rule to restrict zod/v4 imports to config.ts only
README.md	Auto-generated configuration table with improved formatting and completeness

[gagik]

zod v4 has some nice features (and actually exists already as a separate import in our current v3 version) but we want to make sure we don't use this for tool schemas until modelcontextprotocol/typescript-sdk#555 is resolved

[coveralls]

Pull Request Test Coverage Report for Build 18973376541

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 101 of 110 (91.82%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.07%) to 79.988%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
eslint-rules/enforce-zod-v4.js	44	46	95.65%
eslint.config.js	0	7	0.0%

Totals
Change from base Build 18966929073:	0.07%
Covered Lines:	6474
Relevant Lines:	7957

---

💛 - Coveralls