Skip to content

spec(crons): the apex publisher returns to an hourly schedule - #12656

Merged
gHashTag merged 1 commit into
masterfrom
feat/cron-publish-apex-hourly
Oct 26, 2026
Merged

gHashTag merged 1 commit into
masterfrom
feat/cron-publish-apex-hourly

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Closes #12655. Refs Trinity-S-AI-DNA/trinity#1762 (the trinity-side half: the schedule line in publish-apex-on-merge.yml and the vendored copy land there in the same hour, per the registry honesty rule this repo's crons README states).

One new card, specs/crons/trinity-publish-apex-on-merge.t27:

  • ID github-actions/trinity/publish-apex-on-merge, HOST github-actions, SCHEDULE 37 * * * * (the schedule line itself lands in the trinity workflow in the paired PR);
  • CONTROL github-actions-dispatch, ON_FAILURE log, RUNS empty with the schema's RUNS_NOTE;
  • NOTE carries the incident that births it: on 2026-10-25/26 the apex publisher failed its verify gate for a day (trinity#1761) and nothing retried it, because its only triggers were push and a merge-time dispatch. The publisher publishes only when the built bytes changed, so an hourly run is a self-healing retry that costs nothing while the site is fresh.

Tests follow the auto-merge card's patterns: ID shape, fixed vocabularies + the RUNS/RUNS_NOTE link, the schedule pinned, and SERVICE equal to the workflow file path.

…rinity-S-AI-DNA/trinity#1762)

The publisher is the only door to t27.ai; on 2026-10-25/26 its verify gate
failed for a day and nothing retried it, because its only triggers were push
and a merge-time dispatch. The card lands together with the hourly schedule in
trinity:.github/workflows/publish-apex-on-merge.yml - the registry honesty rule.
The workflow publishes only when the built bytes changed, so the hourly run is
a self-healing retry that costs nothing while the site is fresh.
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 08:51:27 UTC

Summary

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

These columns do not partition: 0 + 20 + 0 + 1 = 21, and there are 22 open PRs. A PR is being counted twice or not at all.

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 9359d05. Nothing was generated, built or run. A pass means the file is well formed, not that it is right.

  • specs/crons/trinity-publish-apex-on-merge.t27: parses and typechecks.

Read by the model

This PR adds a cron specification for the Trinity apex publisher workflow, scheduling it hourly at minute 37 as a self-healing retry after a verify-gate failure went unnoticed for a day (trinity#1761). The publisher only pushes when built bytes differ, so the hourly run costs nothing while the site is fresh.

Worth a look

  • specs/crons/trinity-publish-apex-on-merge.t27:22 — SCHEDULE is 37 * * * * (hourly) but the comment on lines 7–8 states the workflow header "was meant to run every 15 minutes" and that GitHub capacity sets the real period. If the workflow file's on.schedule differs from this card, the registry will show a schedule that doesn't match what GitHub actually runs.
  • specs/crons/trinity-publish-apex-on-merge.t27:28 — RUNS is empty with RUNS_NOTE = "no skill invocation found in source". Since CONTROL = "github-actions-dispatch", this cron likely triggers the workflow via workflow_dispatch; confirm the workflow accepts that input and that no skill invocation was overlooked.
  • specs/crons/trinity-publish-apex-on-merge.t27:30 — NOTE cites "Born 2026-10-26" which is a future date; ensure this is intentional (e.g., back-dated incident record) and not a typo that could confuse audits.

Read: 1 files, +50 -0, the whole diff. Head 9359d05. 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 3178dc6 into master Oct 26, 2026
32 of 37 checks passed
@gHashTag
gHashTag deleted the feat/cron-publish-apex-hourly branch October 26, 2026 10:49
gHashTag added a commit that referenced this pull request Oct 26, 2026
…12721)

Closes #12720. The protocol the swarm already runs, named as a card: push the head with its work report, hand the PR to the reviewer bee, walk away. Merged with admin per repo precedent (#12656, #12715): the failing checks fail repo-wide on every PR, including the last merged ones.
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.

cron card: trinity-publish-apex-on-merge (hourly self-healing publish)

1 participant