David decided: Removed LMS session gate from personal workspaces

During the session investigating workspace generation failures, David corrected the agent's proposed fix direction:

personal workspaces must never pre-gate on LMS

He broadened the rule beyond personal workspaces:

no workspace should, not just personal. if the model tries to make a call that requires the lms and the call fails cause it returns some error signalling the session is invalid then the reply for that turn can default to the message about hwo they need to sign into amathuba

He also specified the correct gate location — clicking a file that isn't already cached:

clicking files in the files view, or clicking a file tab, or clicking the banner of a file in the fiels view, to access a file that isnt on S3 or redis and will need to be fetched from the users lms, that shoudl do a gate check and if the lms session is invalid or if the extension isnt conencted, then the respective popup mechanism shoidl come up

This separated proactive gates from reactive failure handling in the workspace product.