Debugging And Diagnostics

Current implementation evidence: docs/diagnostics.html,

docs/language.html, and package/runtime docs.

Triage Order

1. Check the source form shape.

2. Check imports and package lock entries.

3. Check function arity.

4. Check simple type mismatches.

5. Check capability boundaries.

6. Check backend or runtime boundary docs.

Top-level forms are restricted. If the compiler rejects a form, compare it with

the language guide before assuming the feature exists.

The checker validates duplicate function names, duplicate parameters, unresolved

symbols, call heads, known function arity, builtin arity, simple type

mismatches, boolean conditions, equality operand compatibility, and pure

capability calls.

Package imports depend on the lockfile. Read docs/packages.html when pkg:

imports fail.

Runtime boundary failures should be documented by the relevant runtime boundary

doc. Do not treat a fake adapter's output as production runtime behavior.