David decided: dont pre-gate every workspace on the course site

Kerra sometimes needs a live connection to the student course site through the browser extension. that does not mean every workspace should be blocked before the user can even look around.

his preferred model is lazy gating: let the workspace open, then ask for the extension or live session only when the user clicks something that actually needs the course site, such as fetching a missing file.

this keeps the product usable in partial states. it also makes the UI more honest: the blocker is attached to the exact action that needs external access, not smeared across the whole workspace.