---
title: Republish league-data carrying the regenerated plays coverage report
type: task
status: completed
description: >-
  The published nfl/plays/coverage-report.json went stale against the live nfl_plays schema, firing
  pipeline_failure signals 132596/132597. The report is regenerated and operator-approved for
  republish; this lane publishes it and verifies the checker flips to PASSED.
base_uri: user:task/league/republish-plays-coverage-report.md
created_at: '2026-09-29T02:11:58.971Z'
entity_id: bfb2781a-1551-4aea-a9e6-4aee02347bd8
finished_at: '2026-09-29T02:54:55.275Z'
owner_identity_uri: █████████████████████████
priority: Medium
public_read: true
tags:
  - user:tag/league-xo-football.md
updated_at: '2026-09-29T02:54:55.275Z'
visibility_analyzed_at: '2026-11-05T23:50:11.282Z'
---

# Task: Republish league-data carrying the regenerated plays coverage report

## Status

- Published 2026-09-28 as league-data `5c24da9` (single commit on `main`). The checker's preconditions and verdict pass locally; signals 132596/132597 await the next green scheduled run to close them.

## What happened

- Signals 132596/132597 (check-published-dataset-headers, hosts macbook and macbook2025) fired because `nfl/plays/coverage-report.json` in the published league-data tree was generated against an old `nfl_plays` schema: 10 retired columns named, 10 live columns missing.
- The report was regenerated against live `nfl_plays` (exact key-set match, 429/429) and `check-data-export` passes locally (137 artifacts, all publishable). Operationally confirmed this is a schema-drift repair, unrelated to the abandoned scoping ruling on that report (that ruling said the report may name columns the dataset does not carry; this defect is naming columns the TABLE no longer has).
- Operator approved the force-push republish on 2026-09-28.

## Plan

- [x] Publish `scripts/publish-dataset.sh` (operator-approved) carrying the regenerated report, using ledger `tmp/published-dataset/regeneration-review-2026-09-28-coverage.json` (all 137 artifacts accepted) and rehearsal `tmp/published-dataset/rehearsal` (2.2G, byte-identical to the published tree except the report).
- [x] Verify published tree: `cli/monitoring/check-published-dataset-headers.sh` flips to `check-data-export: PASSED`.
- [x] Close signals 132596/132597 — handed to the scheduled checker, whose next green run on each host closes them; a red run keeps them open for triage.
- [x] Report success back to `███████████████████████████` via `base thread message --sender`.