Module cache 

What we have learned about the organisations, kept between runs.

There is exactly one thing here and one reason for it. A bare LMS-12 is ambiguous when two profiles can both see a queue called LMS, but finding that out costs a request per profile — far too much to pay on every command. So the map is recorded when something already had to list queues (auth status, auth login) and consulted for free afterwards.

The cache is an optimisation and is treated as one: missing, stale or unreadable, the tool works exactly as it did before, it just cannot warn about a collision it has never seen.

Structs

Cache

Functions

path_for

Where the cache lives: beside the config, not inside it. It is derived data, and nobody should have to read it or keep it in version control.

queue_of

The queue part of an issue key: LMS from LMS-12.