`rails console --sandbox` allows for untracked read-only access to the database, including decryption of values

As the name suggests, storing console session data in the primary database results in the session record being rolled back in a transaction when running `rails console --sandbox` once it terminates.

While I'm not sure there's an actual "fix" to this behavior (it seems to be working as intended), I'd be interested to understand if the team would find an update to the README documenting this useful. I'd be happy to add a line or two about this if so.

Start by reviewing the README section covering `rails console --sandbox`. Confirm how the sandbox transaction behaves when the session ends, then document that database values can be read and decrypted without changes being persisted. Done means the README clearly explains this behavior and its limits.

Written by the indexing model from the issue text.