ek9_explain_error

Returns the curated rich explanation for one EK9 error code - [DIAGNOSIS], [EXAMPLES] (as ek9_ask 'Q<id>' routes), the first example's source inlined as [WORKED EXAMPLE Q<id>], [ACTION], [SEE ALSO] and, when tooling is mapped, [REMEDIATION].

Category: Enquiry

When to use it

'What does E07235 mean and how do I fix it' is one call with errorCode:'E07235' - the curated diagnosis, action steps and compilable examples. Take the code verbatim from ek9_compile / ek9_query_diagnostics; call once per distinct code before proposing a fix.

When not to use it

• What is currently broken in the workspace (the errors themselves) - use ek9_query_diagnostics.
• A keyword, type or topic with no error code involved - use ek9_help.
• Conceptual 'why does EK9 do X?' questions not tied to a code - use ek9_ask (also the fallback when a syntax error carries no code).
• Priming a session with broad EK9 design rationale - use ek9_paradigm.

Details

Exact lookup against the bundled rich-error corpus after normalisation: case, a missing 'E' and missing leading zeros are corrected and announced (e07235, E7235, 7235 all reach E07235); anything that is not digits after an optional E is a miss. A miss is an ERROR naming what a code looks like and where a real one comes from - syntax errors arrive with no code at all, so nothing invented for them will resolve. Sections beyond [DIAGNOSIS]/[ACTION]/[SEE ALSO] vary by code ([COMMON CAUSES]/[RATIONALE] are optional); [WORKED EXAMPLE Q<id>] inlines the first cited example's whole source when it is 60 lines or fewer (a longer one stays a pointer - ek9_ask 'Q<id>' returns it whole); [REMEDIATION] lists mapped MCP tools in recommended order, or a deliberate no-tool note. Pure static read - no workspace, no compile phase; identical output whether or not the workspace compiles.

Arguments