Update arena configs from maDisplayTools - #147
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
auto/sync-arena-configs
branch
from
July 5, 2026 00:22
d47b443 to
33ac3fe
Compare
mbreiser
added a commit
that referenced
this pull request
Jul 6, 2026
Brings in #144 (closed-loop runner FicTrac apply + in-protocol disconnect + course-repo default), #145/#146 (fictrac_direction_test open_dur/cl_dur durations), #147 (arena-configs sync), #149, and the deploy-pages split. Only conflict was arena_studio.html (2 hunks), resolved: - footer: kept v0.7's one-line footer (the full changelog moved to docs/development/arena-studio-release-notes.md; #144's code auto-merged). - course-repo default: kept #144's Studio.DEFAULT_COURSE_REPO fallback so the Repo field display matches the already-merged courseSettings() resolver and the change handler (all "empty -> course repo"); dropped v0.7's never-set seeding / explicit-clear-sticks nuance in favor of #144's coherent default. #144's runner FicTrac-apply is the fix for the "closed loop doesn't run in the runner" checklist note; keeping it was the point of merging rather than replacing. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Jul 27, 2026
mbreiser
added a commit
that referenced
this pull request
Jul 27, 2026
scripts/generate-arena-configs.js stamped `Last updated: <new Date()>` into the generated header, so js/arena-configs.js changed on every run regardless of whether any arena YAML had changed. The sync-arena-configs workflow's "Check for changes" step was therefore always true, and the workflow opened a PR every Sunday whose entire diff was that one timestamp line (#169, and the merged #158/#147/#122/#117 before it). Drops the timestamp so the output is a pure function of the input YAML. The generator is now byte-idempotent (verified: three consecutive runs produce an identical file), which makes "Check for changes" mean an actual config change. Git history already records when the file last changed. js/arena-configs.js is regenerated here; it is prettier-ignored by design (LAB-111 follow-up) and the diff is the removed header line only. Regenerated from configs fetched the same way the workflow fetches them (GitHub contents API against reiserlab/maDisplayTools), so the next CI run reproduces this file byte-for-byte and reports no changes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
2 participants
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.
Automated Arena Config Sync
This PR was automatically generated by the
sync-arena-configsworkflow.Source:
maDisplayTools/configs/arenas/+configs/arena_registry/index.yamlChanges
The
js/arena-configs.jsfile has been regenerated from the latest YAML configs in maDisplayTools.Review Checklist