docs: revise v2 specs based on PR feedback

Address reviewer feedback from cliffhall, pcarleton, KKonstantinov, mattzcarey:

v2_ux.md changes:
- Add Server Settings Modal for per-server config (headers, metadata, timeouts, OAuth)
- Add Clone button to Server Card Actions
- Add OAuth Debugger section for debugging auth flows
- Change Resources Screen from resizable panes to accordion pattern
- Update Logging Screen to all 8 RFC 5424 levels with distinct colors
- Clarify Browse button as local file picker
- Expand JSON-RPC Tester to support all methods with custom headers
- Add multi-select support for anyOf/oneOf enums in Form Generation

v2_tech_stack.md changes:
- Select Hono over Express based on community consensus
- Add Hono Rationale section with comparison table

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

specification/v2_tech_stack.md

@@ -29,9 +29,34 @@ Let's choose a feature-rich component set with easy theming control
 
 ### Transport Operation
 Let's consider how to operate the server transports.
-* -[x] [Express](https://expressjs.com/)
+* -[x] [Hono](https://hono.dev/)
+* -[ ] [Express](https://expressjs.com/)
 * -[ ] Node:[http](https://nodejs.org/docs/v22.18.0/api/http.html)
 
+#### Hono Rationale
+
+Hono is selected based on community consensus (PR #945 discussion) for alignment with modern web standards and the TypeScript SDK v2 direction.
+
+**Why Hono over Express:**
+
+| Requirement | Hono | Express |
+|-------------|------|---------|
+| Bundle size | 12kb | ~1mb |
+| Web Standards (Request/Response) | Yes - Native | No - Shimmed |
+| TypeScript native | Yes | No - @types package |
+| Tree-shakable | Yes - Fully | No |
+| HTTP/2 support | Yes | No (SPDY dropped) |
+| Built-in middleware | Yes - Body parsing, auth, etc. | No - Requires plugins |
+| Edge/serverless deployment | Yes - Native | Partial - Requires adapters |
+
+**Benefits:**
+
+1. **Web Standards Alignment** - Uses native `Request`/`Response` objects, enabling deployment across Node, Deno, Bun, serverless, and edge environments
+2. **TypeScript Native** - Full type safety without external type packages, no monkey-patching of request objects
+3. **Future-proofing** - HTTP/2 support enables potential gRPC transport; aligns with TypeScript SDK v2 plans
+4. **Developer Experience** - Simpler API, type-safe context, smaller learning curve
+5. **Bundle Efficiency** - Dramatically smaller footprint benefits both development and deployment
+
 ### Logging
 Let's step up our logging capability with an advanced logger:
 * -[ ] [Winston](https://github.com/winstonjs/winston?tab=readme-ov-file#winston)