Republish the board when the board's own code changes - #263
Merged
Conversation
#262 changed the hero and merged green, and the published page kept showing the old emoji for hours: `brain_board.yml` republishes on the 05:30 cron, a manual dispatch, or a `state/devbox_board.json` push — and a renderer change is none of those. The repo said one thing and the live page showed another, which is the one thing a morning surface must never do. `board/**` and `config/policy.yaml` join the push paths: the two inputs that decide what the page looks like and what vocabulary it speaks. The board is cheap to rebuild, so rebuild it when it changes rather than waiting a day. The daily cron stays — the board's content is time-varying, so most refreshes still have nothing to do with a commit. Co-Authored-By: Claude Opus 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01FhsBsESQUAoJQ2fvLiDD5j
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.
#262 changed the hero and merged green, and the published board kept showing the old emoji for hours afterwards — long enough for a human to report it as a bug twice.
The cause isn't the renderer.
brain_board.ymlrepublishes on three things: the 05:30 cron, a manual dispatch, and astate/devbox_board.jsonpush. A change to the board's own code is none of them. So the repo said one thing and the live page showed another, which is the one failure mode a morning surface cannot have.board/**andconfig/policy.yamljoin the push paths — the two inputs that decide what the page looks like and what vocabulary it speaks. The board is cheap to rebuild, so rebuild it when it changes rather than waiting for tomorrow. The daily cron stays: the board's content is time-varying, so most refreshes still have nothing to do with a commit.The live page is already current — I dispatched the workflow by hand (run #10) when the gap was reported. This is so the next renderer change doesn't need someone to notice.
Verification
pytest tests/ -q— 449 passed.brain_board.ymlparses as YAML; the change is additive to an existingpaths:list.Generated by Claude Code