Muster

A muster is a roll-call: every hand named, present or absent. That is the job here. It lists what is in flight right now, the state each thread is actually in, and what to do next. It is not a summary of what you did.

Use it for "catch me up", "where did I leave off", "what is running", or before picking up work you started somewhere else.

The reason this earns a skill is concurrency. When several sessions run against the same repos, the expensive mistake is two agents standing on the same branch, or resuming a thread another session already merged, reverted or abandoned. Forgetting what you did is cheap next to that.

What counts as the record

Four sources, and no one of them is authoritative on its own.

• Your transcripts hold what was decided and why. They go stale the moment another session pushes.
• Live git and PR state holds what is actually true of the code right now.
• Peer sessions hold work in progress that exists nowhere else yet.
• The tracker holds what other people believe the state to be.

A transcript is history. A ticket is a claim. Only git and the running sessions are current.