Lifecycle detail
Validate state and sequence.
Capture CreateTaskResult followed by each tasks/get state in chronological order. The first object uses resultType task; subsequent operation results use complete. Preserve taskId, createdAt and lastUpdatedAt exactly as sent.
Fix individual field errors first, then cross-snapshot transitions. Static success should be followed by tests for durable storage, per-request capability negotiation, routing and authorization.
Continue debugging
- Run the lifecycle validator.
- Review status-specific payloads.
- Check 2025-to-2026 migration.
- Test storage, routing, permissions and polling with the official SDK used in production.
MCP Task Trace is independent and is not affiliated with the Model Context Protocol project.