Which directory permissions apply to /kaggle/working during notebook commits?

Filesystem Persistence in Kaggle Kernels

When transitioning a project from a local environment to a Kaggle Notebook, the filesystem structure changes from unrestricted local access to a specific Linux-based hierarchy. While /kaggle/input is read-only, the /kaggle/working directory is designated for writable output.

There is uncertainty regarding the exact behavior of file persistence during the 'Save Version' (Commit) process versus an interactive session. Specifically, it is unclear how the environment handles large temporary files generated in /kaggle/working that exceed the session's disk quota but are required for the final output of a background run.

Does the commit process maintain a separate disk quota from the interactive session? How does the environment handle write-permission failures when the /kaggle/working directory reaches its capacity during a production run?