Elicitation-Driven Interactive Tool Library and Runtime

You are a product-minded engineer. Build a library and runtime for elicitation-driven interactive MCP tools that ask users for structured input mid-execution instead of failing or guessing. The first integrations are [INSERT TOOLS, e.g. deployment and database-migration tools] used inside a coding agent hosted by [INSERT HOST ENVIRONMENT]. Work in modules with approvals between them. Module 1 Interaction design: when to ask versus infer, question-ordering rules, sensible defaults, and an undo/escape path. Module 2 Schema forms: JSON-schema-to-UI mapping, conditional fields, oneOf selectors, validation, and localization hooks. Module 3 Runtime protocol: elicitation request/response/cancel semantics, timeouts, resumable answers after reconnect, and replay protection. Module 4 MCP integration: reference servers in TypeScript and Python demonstrating elicitation within tools, resources and workflow prompts. Module 5 Client SDKs: a headless handler for tests and automation, a CLI prompter, and a web component with streaming updates. Module 6 Pattern library: destructive-action confirmation, missing-parameter repair, choice between plans, and human review of generated diffs. Module 7 Data model: interaction sessions, answers, schema versions, and links to the originating tool call and trace. Module 8 Accessibility: keyboard navigation, screen-reader labeling, reduced-question mode, and rate limits against prompt fatigue. Module 9 Security: answer validation, size limits, secret-type fields masked and never logged, and spoofing-resistant UI provenance. Module 10 Testing: golden interaction transcripts, timeout/cancel matrices, cross-client conformance, and usability benchmark scripts. Module 11 Telemetry: ask rates, answer latency, abandonment, and downstream tool-success lift, all privacy-preserving. Module 12 Release: documentation, a live example server, semantic versioning, and a contribution guide for new patterns. Specify the contract guaranteeing headless automation never blocks indefinitely. Ask five questions first, covering host capabilities and whether silent defaults are acceptable. ================