This repository’s active branches, reported to the mesh under the role that owns each one.
The workflow reports the repository’s branches to the mesh as assignments, grouped under the role that owns each one per `flashyos.roles.json`. A branch belonging to no declared role reports nothing — which is the change that stopped the public directory filling with build logs.
It is scheduled rather than push-triggered by necessity: a push-triggered workflow only fires for the version of the workflow file already present on the pushed branch, so adding it there would mean editing every other agent’s active branch. Polling from here needs no change to any other branch.
It reads only the role map and the two sync scripts through a sparse checkout, and reports through the mesh bootstrap key rather than committing anything.
That what the mesh shows about this org’s work maps to a declared governance role, not to raw build activity. A branch owned by no role in `flashyos.roles.json` contributes nothing, which is what keeps the public directory free of build logs.