Repository navigation
Document how core site changes reach benchbox.dev - #34
Merged
Merged
Conversation
Core keeps the source of six paths that this repository holds a copy of. A change to one of them in core does not deploy; it reaches benchbox.dev only when it is replayed here by pull request. The procedure existed only in earlier pull requests and in practice. Write it down in AGENTS.md: the path mapping, how to find the last replayed core commit, how to copy or merge three ways, how to record deliberate differences, the fidelity check, the CI commands to run and the adaptations to keep. Mirror core's updated blog publishing guide and publication schedule into drafts/, since both described the retired publication workflows. Correct the Explorer end-to-end and fixture-source READMEs, which described core's paths and generator, and list them in the replay allowlist as deliberate differences.
joeharris76
force-pushed
the
docs/replay-runbook
branch
from
October 14, 2026 23:23
45590d0 to
956037f
Compare
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
1 participant
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.
Core still holds the source for the site's Explorer, landing pages, website, blog, and inventory. Changes to those paths need a replay into this repository before they reach benchbox.dev. This adds the path mapping and replay procedure to the repository guide, including how to verify copied files and record deliberate site adaptations.
The blog publishing guide and schedule now describe the site repository's deploy path. The Explorer browser and fixture guides use this repository's paths and core bundle flow, with their intentional differences recorded in the replay allowlist.
Verification: repository boundary and comment checks, Markdown and spelling checks, and seeded-path replay fidelity against the corresponding core changes.