Adds a dated incident-style file at the tool root recording the full
arc of the User_Name attribution work over the last two days:
- Six runs tabulated (galaxy mode x advise variant x write variant x
resulting User_Name) so the next agent can see what's already been
ruled out.
- Current state of the CLI (auth, advise routing, WriteSecured) and
the galaxy (eOSUserBased, ArchestraUsers role, engines deployed
before the security change).
- Leading hypothesis: running aaEngine processes still operate under
the original eNone security context because galaxy security is
compiled at deploy time. Until the platform/engines are
redeployed, auth_user_id stays at 1 and User_Name stays NULL.
- Concrete pick-up commands: undeploy/redeploy DevPlatform ->
DevAppEngine -> TestArea -> TestMachine_001 via graccesscli, then
re-run the trigger / ack-as-dohertj2 / clear sequence and query
Events.
- Fallbacks if a clean redeploy doesn't change the answer
(aaBootstrap restart, two-person Verified Write, attribute
security classification check, cross-tool comparison vs Object
Viewer / InTouch).
Linked from README.md's resource index so an agent landing on the
tool finds the open thread without spelunking commit history.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Joseph Doherty