Follow-up from the Phase 7 (PR #2) merge review.
Gap
Phase 7 spec: "last error message if failed" / stopping criterion "Failed MCPs surface their error message in the panel."
Currently failed rows render a generic " (check ~/.cache/eca/eca-cli.log)" hint instead of the actual error.
Why deferred (blocked)
Verified against the ECA protocol: MCPServerUpdatedParams (../eca/docs/protocol.md:2747-2799) has fields command, args, url, status, disabled, hasAuth, tools, prompts, resources — no error field. The generic hint is the best available client-side. Surfacing the real error requires an upstream ECA protocol change to include an error/detail field on tool/serverUpdated.
Acceptance
- Upstream:
tool/serverUpdated carries a failure detail/error field.
- Client:
failed rows render that error in the panel (and/or on Enter-to-expand, see the expand ticket).
Follow-up from the Phase 7 (PR #2) merge review.
Gap
Phase 7 spec: "last error message if failed" / stopping criterion "Failed MCPs surface their error message in the panel."
Currently
failedrows render a generic" (check ~/.cache/eca/eca-cli.log)"hint instead of the actual error.Why deferred (blocked)
Verified against the ECA protocol:
MCPServerUpdatedParams(../eca/docs/protocol.md:2747-2799) has fieldscommand, args, url, status, disabled, hasAuth, tools, prompts, resources— no error field. The generic hint is the best available client-side. Surfacing the real error requires an upstream ECA protocol change to include an error/detail field ontool/serverUpdated.Acceptance
tool/serverUpdatedcarries a failure detail/error field.failedrows render that error in the panel (and/or on Enter-to-expand, see the expand ticket).