Joseph Ferano
651d04496f
Step 2 claimed (Vec T) unblocks (fn [c] (push errors c) ...) and it does not. check.ml's captured reads ctx.outer only to raise a better refusal and lookup never reads it at all, so closure capture — spec-memory.md's case 2 — is unbuilt. And the same spec captures a Vec by pointer rather than by value, a split no capture path has needed because every capturable type today is a value type. Two separate items, named as such under step 2. Item 1 stops restating the four decisions and points at the section holding them, keeping only the consequence the build order turns on. The Carp line numbers were checked and are right, so they come out of the bug entry.
