Exercise 1: Inspecting the Upvalue's Own .closed State — Possible Solution
====================================================================

THE CHECK
------------------------------
    chunk = Compiler().compile_program([
        FunctionStmt('makeCounter', [], [...]),   # as in the chapter
        VarStmt('counter', Call(Variable('makeCounter'), []), ...),
    ])
    vm = VM()
    vm.run(Closure(WispFunction("<script>", 0, chunk, []), []))

    counter_closure = vm.globals['counter']
    upvalue = counter_closure.upvalues[0]
    print(upvalue.closed, upvalue.value)

RESULT
------------------------------
    closed = True
    value  = 0.0

WHICH LINE CAUSED closed TO BECOME TRUE, AND WHY BEFORE ANY CALL
------------------------------
The responsible line is inside OP_RETURN's own handler, specifically:

    self.close_upvalues(finished_frame.base)

This runs the moment makeCounter's OWN return executes -- returning
the `increment` closure itself, not a call to it. At that exact
point, makeCounter's own frame is being popped and its locals
(including count, at whatever slot it occupied) are about to be
deleted from the stack by the very next line
(`del self.stack[finished_frame.base - 1:]`). close_upvalues finds
count's own Upvalue object still open (pointing at that
soon-to-be-deleted slot), copies its current value (0.0 -- count was
never incremented inside makeCounter itself) into upvalue.value, and
flips closed to True.

This happens entirely independently of whether `counter` is EVER
actually called afterward. The closing step is tied to makeCounter's
own return, not to increment's own first invocation -- which is
exactly why inspecting the upvalue's state right after
`var counter = makeCounter();`, with zero calls to counter() made
yet, already shows closed=True. If closing were instead deferred
until the first call to counter(), that would be too late: by then
the stack slot count used to occupy could already have been
overwritten by something completely unrelated, since nothing is
protecting it once makeCounter's own frame is gone.