fleet-state

What problem does it solve?

Fleet operators waste time stitching together multiple weekly agent outputs to understand how the overall fork “fleet” is changing (health buckets, releases, and the current contributor spotlight).

Core Features & Use Cases

• Weekly synthesis digest: Combines fork-cohort status, release activity, and contributor spotlight into one consistent “state of the fleet” narrative with week-over-week deltas.
• Graceful degradation: Produces partial output when one or two source state/artifact files are missing, while avoiding hard failures when upstream skills haven’t run.
• No new data collection: Reads authoritative inputs from existing memory/topics and latest articles, composing insights without re-querying fork repositories.
• Operator-ready transitions: Extracts movement highlights (bucket transitions), release highlights, and the spotlight summary from recent articles to make Monday readouts actionable.

Quick Start

Run fleet-state with no extra var to generate a weekly digest and notification from the latest fork-cohort, fork-release, and contributor-spotlight data for the parent repo.