[OpenSpec] decidiq-mcp-adoption

[github-actions]

⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.

Artifacts

• ✅ Metadata
• ✅ Proposal
• ✅ Specs
• ✅ Design
• ✅ Tasks
• 🔲 Plan
• 🔲 Review

Summary

Adopt ADR-063 (MCP as Platform Abstraction) in Decidiq: replace the hand-written DecidiqToolProvider (5 tools, ~1280 lines) with OpenRegister's declarative surfaces. A curated set of 10 of Decidiq's 37 schemas opts in to schema-derived CRUD via the x-openregister-mcp dialect — read verbs only, zero declarative writes. Two of the five hand-written tools survive as genuine non-CRUD #[McpTool] methods on real service classes; two are deleted as derivable CRUD; and one — startMeeting — is deliberately removed from the agent surface entirely because advancing a meeting's governance lifecycle is a destructive, notification-emitting act that an LLM must not be able to misfire.

Specs

• 📄 mcp-tools

Tasks

• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test
• Implement
• Test
• All tasks checked off
• openspec validate decidiq-mcp-adoption --type change --strict passes
• Manual testing against acceptance criteria
• Code review against spec requirements
• PHPUnit unit tests for new/changed business logic (tests/Unit/) — dialect assertions (10-schema opt-in, filters resolve to real properties, no write verbs) + the two curated tools' happy/forbidden paths
• Newman/Postman tests for new/changed API endpoints — N/A: no Decidiq HTTP endpoint changes; the MCP surface is served by OpenRegister's /api/mcp
• Browser tests (Playwright MCP) for UI changes — N/A: no frontend changes
• All tests pass (composer test), with zero new failures against a self-measured baseline
• Feature documentation updated in docs/ — record the agent-visible tool surface and, explicitly, that starting a meeting is a human-only action
• Screenshot captured and committed to docs/images/ — N/A: no UI change
• N/A — no new user-facing strings. The dialect description fields are agent-facing prose read by the LLM, not UI copy, and are not translated.

Design

See design.md for technical design details.

---

Synced from openspec/changes/decidiq-mcp-adoption by OpenSpec workflow
App: decidiq