Skip to content

[Phase 3] Fan out the off-peak scheduling standard to consumer repos + defer AGENTS.md to the org standard #726

Open

Description

@github-actions

Rescoped 2026-09-01. AC1 (lift the standard into petry-projects/.github) and the org-repo's own cron offsets moved to combsmith/.github#1052, released to that repo's dev-lead. This issue now covers only what remains: the downstream fan-out and this repo's deferral note.

Story

As an org administrator,
I want the remaining minute-0 scheduled workflows across consumer repos offset, and this repo's local convention replaced by a pointer to the now-canonical org standard,
so that the whole fleet runs off-peak and there is exactly one source of truth for the rule.

Current state (verified 2026-09-01)

  • .github-private: 0 minute-0 of 20 crons — fully compliant, Phase 1 delivered.
  • petry-projects/.github: 11 of 14 — being fixed in .github#1052.
  • Consumer repos: 18 minute-0 crons across 9 repos — this issue's remaining scope:
Repo minute-0 crons
broodly 3
TalkTerm 3
bmad-bgreat-suite 2
ContentTwin 2
google-app-scripts 2
incubator 2
markets 2
broodminder-export 1
repo-template 1

(Counted from local checkouts; re-enumerate live before acting — a repo may have changed, and archived repos are excluded.)

Acceptance Criteria

  1. Every non-archived consumer repo's minute-0 scheduled workflows are offset off the top of the hour via PRs, changing only the cron minute field — never the hour, day, or frequency.
  2. repo-template's cron is fixed at the template level so newly-seeded repos start compliant, not just existing ones.
  3. .github-private/AGENTS.md's repo-local "Scheduled workflows" section is replaced by a deferral pointer to the canonical org standard in petry-projects/.github/standards/ci-standards.md, following the Cost-reporting promotion precedent.
  4. The rollout vehicle is recorded: either scripts/aw-standards-sync.sh is extended to open these PRs, or the one-off PRs are enumerated with links. Whichever is chosen, the decision and its rationale are written down.

Tasks / Subtasks

Blocked on

petry-projects/.github#1052 — AC3 cannot be written until the canonical standard section exists to defer to, and the fan-out should not start before the source-of-truth repo is itself compliant (dogfood first, per the Safe Release Strategy).

Why this stays dev-lead:hands-off

AC1 and AC2 mutate arbitrary downstream repos, which this repo's dev-lead cannot reach. Note that AC3 alone is in-repo and automatable — if the fan-out is deprioritised, split AC3 out and release it separately rather than leaving the whole issue held.

References

  • petry-projects/.github#1052 (the promoted standard)
  • AGENTS.md — repo-local Scheduled workflows section; Cost-reporting promotion precedent
  • scripts/aw-standards-sync.sh, .github/workflows/standards-sync.yml

Activity

  1. added
    initiativeEpic / initiative tracking issue
    initiative:holdInitiative driver must not release this issue (human hold)
    dev-lead:hands-offExclude from dev-lead agent automation
    on Jun 14, 2026
  2. changed the title [-][Phase 3] Roll the off-peak scheduling standard out org-wide[/-] [+][Phase 3] Fan out the off-peak scheduling standard to consumer repos + defer AGENTS.md to the org standard[/+] on Sep 1, 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

    dev-lead:hands-offExclude from dev-lead agent automationinitiativeEpic / initiative tracking issueinitiative:holdInitiative driver must not release this issue (human hold)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions