Review and heal ecosystem drift¶
Freshness budgets turn maintenance signals into a common status without making
every warning release-blocking. The script owns deterministic collection and
rendering; the audit-drift skill owns triage and judgment.
Execution status
Spine CI validates the scoreboard registry on pull requests, main pushes, and Mondays at 05:45 UTC. It does not run the procedures below. Rendering a previously gathered snapshot is a manual, offline operation; gathering live state and performing triage require an authenticated maintainer or scheduled-agent session.
Render the newest local snapshot¶
This is offline and does not change state. If no snapshot exists, gather one:
Gathering queries live GitHub state through gh and writes a dated snapshot to
the tracked drift history. Those operational snapshots are intentionally
excluded from this public site.
Triage with the owning workflow¶
Invoke the audit-drift skill in a Spine agent session. It distinguishes a
mechanical repair—such as a stale pin or lock—from a change that needs human
judgment. It may propose focused repository work, but release, merge, and
external publication decisions remain human-gated.
Verify the result¶
Record durable exceptions in the tracked ledger referenced by the drift workflow. Do not copy task prompts, machine-specific paths, or transient issue details into reader-facing documentation. See scheduled maintenance for the operating model.