Under the hood
Useful1 Signal3
A persistent summon session key is generated and saved to your config, though nothing visibly reads it.
A 32-byte summon session key is created and cached in config but no visible consumer exists in this build.
What's wrong with this entry?
Anonymous. No account, no email.
What
A new helper reads a summon session key from your config file, checks it against an expected pattern, and otherwise generates a fresh 32-byte random hex value, caching it for the session and writing it back to config. What reads the key is not wired up visibly in this build.
Evidence
summonSidKey
Strings lifted out of the shipped bundle, so the claim above can be checked against them.