A value-type assignment copies its value. A reference-type assignment copies a reference to an object. The distinction doesn't tell you that every struct lives on the stack: a struct can be an array element, a field inside a heap object, or a boxed value. A struct can also contain a reference to a mutable list.
Boxing places a value into an object, and unboxing extracts the exact stored value type. A constrained generic call can often use a struct through its interface without creating that box.
The garbage collector follows reachable objects from roots such as active locals and static fields. A long-lived buffer that retains an unused reference can therefore retain its target. Generational collection groups objects by lifetime; generation details and promotion depend on the runtime. This browser uses Mono WebAssembly, so it isn't a server-GC profiling environment. The exercises check references and allocations, never a promise that collection occurs at a particular instant.
Boxing copies the value. Clearing a container reference removes one reachability path; it does not force a collection.