Skip to content

spec(crons): the weekly branch sweep as law -- classify, record, delete (Refs #1453) - #12652

Merged
gHashTag merged 1 commit into
masterfrom
crons/branch-sweep-card
Oct 26, 2026
Merged

gHashTag merged 1 commit into
masterfrom
crons/branch-sweep-card

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Refs #1453 (today's sweep record -- the measured run this card encodes).

What

The branch sweep as a cron card: skip open-PR heads, skip tips <24h old (in-flight agent work), contained tips (ancestor of master) delete with nothing orphaned, orphans get branch+SHA+file-count recorded in a tracking issue BEFORE deletion.

Honest state

  • ENABLED=false: the card is the law; the host workflow (.github/workflows/branch-sweep.yml) lands as an owner-approved-foreign follow-up -- a yml cannot ride this train without the label.
  • Verdict fn + test travel with the card (0 -> skip-open, 1 -> skip-young, 2 -> delete-contained, 3 -> record-then-delete).
  • Today's measured run: 6391 -> 678 branches; 1453 contained + 4466 recorded orphans deleted; 31 protected.

@gHashTag
gHashTag enabled auto-merge (squash) October 26, 2026 08:29
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 08:31:52 UTC

Summary

Status Count
Total Open PRs 22
PRs with Failing Checks 21
PRs with All Checks Green 1
READY 0
FAILING 21
PENDING 0
NO CHECKS YET 1

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=6fb540d220f7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@tri-claw

tri-claw Bot commented Oct 26, 2026

Copy link
Copy Markdown

Summary by t27-bees

Checked by the t27 compiler

t27c parse, parse-complete and typecheck on each changed .t27 file at 1075eae. Nothing was generated, built or run. A pass means the file is well formed, not that it is right.

  • specs/crons/t27-branch-sweep.t27: parses and typechecks.

Read by the model

This PR adds a cron specification (t27-branch-sweep.t27) that codifies the weekly branch-sweep policy: classify every remote branch, skip open-PR heads and tips younger than 24 h, delete contained branches (ancestors of master), and record orphans (branch + tip SHA + file-count) in a tracking issue before deleting them. The card is the "law"; the host workflow will land separately with ENABLED=false here.

Worth a look

  • specs/crons/t27-branch-sweep.t27:22 — sweep_verdict checks age_s < 86400 before is_ancestor. A branch that is both <24 h old and an ancestor of master returns SKIP_YOUNG (1) instead of DELETE_CONTAINED (2). The comment calls this "in-flight agent work," so the ordering is intentional, but it means young contained branches survive the sweep.
  • specs/crons/t27-branch-sweep.t27:14 — NOTE claims "5305 deleted" but the breakdown (1453 contained + 4466 orphans) sums to 5919. The discrepancy is only in the comment, not in executable code.
  • specs/crons/t27-branch-sweep.t27:10 — ENABLED = false with a note that the workflow wiring follows as an "owner-approved-foreign" PR. The spec cannot enforce that the follow-up actually creates the tracking issue before each deletion; that guarantee lives in the not-yet-present workflow.

Read: 1 files, +40 -0, the whole diff. Head 1075eae. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

@gHashTag
gHashTag merged commit d3c52fa into master Oct 26, 2026
33 of 37 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant