Repository navigation
spec(crons): the apex publisher returns to an hourly schedule - #12656
Merged
Merged
Conversation
…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.
Contributor
Summary by t27-beesChecked by the t27 compilert27c parse, parse-complete and typecheck on each changed .t27 file at
Read by the modelThis 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
Read: 1 files, +50 -0, the whole diff. Head |
This was referenced Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:github-actions/trinity/publish-apex-on-merge, HOSTgithub-actions, SCHEDULE37 * * * *(the schedule line itself lands in the trinity workflow in the paired PR);github-actions-dispatch, ON_FAILURElog, RUNS empty with the schema's RUNS_NOTE;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.