Skip to content

spec_conformance D6: warn 7 days before any §12 row expires (issue + report line), never a surprise RED (post-0.70) #4652

Open

Description

@noahgift

Operator ruling C197 (2026-10-01). On 2026-10-01 the D6 expiry andon turned every PR and main RED at 00:00Z with no prior signal: rows 13, 15, 18, 19 and 21 of PP-LLAMA-001 §12 expired 2026-09-30. See the re-date ticket.

Ask: scripts/spec_conformance.sh emits a WARN for every undischarged row whose derived expiry is ≤7 days away. It opens or updates one issue per row and prints a line the cop report can read. The andon itself stays exactly as strict; this only adds the advance warning.

Acceptance:

  • a fixture case table (with SPEC_CONFORMANCE_TODAY) covers WARN at T-7, no WARN at T-8, and RED at T+1 unchanged;
  • a mutant that drops the warning fails the table.

Scheduled after v0.70.0 is on crates.io.

🤖 Generated with Claude Code

Activity

  1. added this to the 0.71.0 milestone on Oct 8, 2026
  2. noahgift commented on Oct 12, 2026

    @noahgift
    ContributorAuthor

    Status (aprender-w4664): implemented on branch feat/4652-d6-expiring @ 1317ef9, PR waits for a merge slot.

    • scripts/spec_conformance.sh --expiring [--file-issues] prints WARN D6-soon row=<id> expires=<date> days=<n> for every undischarged §12 row expiring in ≤7 days, and files/updates one issue per row. The plain run (what a PR/release reads) is unchanged, D6 included.
    • Case table under SPEC_CONFORMANCE_TODAY: T-7 warns, T-8 silent, T-0 warns and not RED, T+1 RED (D6) unchanged; 56 passed, 0 broken. A mutant that drops the warning breaks 7 rows; 9 mutants, all killed.
    • Run on main today: rows 13, 15, 18, 19, 21, 22 expire 2026-10-15 (3 days). Without a landing or a re-date, D6 turns every PR RED from 2026-10-16.

    🤖 Generated with Claude Code

  3. added
    P1High priority
    and removed
    P0Critical priority
    on Oct 14, 2026
  4. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    P0 to P1 (2026-10-14 P0 triage): P0 now means it blocks the next release or carries the operator's own words on it; this issue does neither, so it stays on the 0.71.0 milestone at P1.

  5. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Folded into #5307 as a checklist row (TRIAGE-100, 2026-10-14): the open-ticket cap is 100, so this ticket is now tracked on that master and closed as not planned. Nothing is lost: reopen it when its work resumes, and an open PR for it reopens it. Pushed branch: feat/4652-d6-expiring.

    Agent: aprender-clerk

  6. noahgift commented on Oct 14, 2026

    @noahgift
    ContributorAuthor

    Reopened: this ticket carries the operator's own words, and TRIAGE-100 keeps those open unless their owner agrees to the fold. The checklist row on #5307 is withdrawn; this ticket stays the record. Re-linked under #5307.

    Agent: aprender-clerk

  7. modified the milestones: 0.71.0, 0.73.0 on Oct 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions