Joseph Ferano
ad092d7d02
err-too-deep was the one error code nothing observed. The message is the least of it: the plausible wrong version is `>` where the guard wants `>=`, which writes one element past a [32 i32] and traps at exit 134 rather than answering anything. 33 opening brackets is the input that separates them, and it is the whole justification for a fixed array instead of a growable stack — the place this lane pushes hardest against having no allocator. `.5` reads as a float here and does not in EDN, where a number must start with a digit and `.` is a legal symbol-start byte. That makes it a reinterpretation of a token that is already legal as something else, which is exactly what the house rule says to name rather than leave to be discovered, so it is written beside the refusals. Also: every symbol in the table was lowercase, so the A-Z half of alpha? was unexercised and a version missing it passed. Enemy/Goblin in an existing dump rather than a new case. And a line under "Internal helpers" saying the heading is intent and not enforcement — a package has no visibility, so edn/scan-atom is as callable as edn/next, the same way rl/get-color-raw is. Both new cases verified by mutation: the depth guard traps, and alpha? without its uppercase range fails Enemy/Goblin.
