`vibium frame` context doesn't persist to the next CLI command

[vincebln2]

Description

vibium frame "name" reports switching into the frame (exit 0), but the next CLI command runs in the main frame instead. The frame context doesn't persist across invocations.

Steps to reproduce:

vibium go http://the-internet.herokuapp.com/nested_frames
vibium wait load
vibium frame "frame-middle"
vibium eval 'document.body.textContent.trim()'

Expected:

eval runs inside the middle frame and returns MIDDLE

Actual:

frame succeeds but eval returns the main page's frameset text:

vibium frame "frame-middle"  → {"context":"...","url":".../frame_middle","name":"frame-middle"}, exit 0
vibium eval '...'            → Frames are not rendering.

Environment

vibium v26.5.31 · Chrome for Testing 149.0.7827.115 · macOS 26.5.1

References

#112 (B19)