Replaces the "Reusing a userId" subsection with a clearer
"userId is session-scoped" note that captures the actual
GRAccess/MxAccess contract:
- AuthenticateUser returns an int that is bound to the LMX session
hServer it was issued against, exactly like tag handles from
AddItem. When the session unregisters (i.e. the MxSession is
disposed, which happens when the process exits) the userId is
no longer valid.
- Each mxa write invocation creates a fresh MxSession, so an
authenticated write must include --username/--password (or a
userId resolved within the current process).
- --user-id <N> is a hand-off for in-process callers, not a
persistable credential.
This matches the user's observation that userIds behave like
tag/item handles in scope, and explains why batch flows benefit
from a future session-mode mxa daemon (modeled on graccesscli's
session) that holds one MxSession across many commands.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Joseph Doherty
a842f67b54