Repository navigation
Publish Hex Tactics architecture on the blog - #1
Merged
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Summary
/architecture/hex-tactics/(Chinese) and/architecture/hex-tactics/en.html(English).Systems affected
Test plan
npm run lint: no warnings or errors.npm run build: successful static export (70 pages).node scripts/check-architecture-bundle.mjs --export: exact static output and links verified.Scope / rollback
Both viewers remain byte-identical to the previously accepted upstream delivery; the evidence revision is
42f3a2b, not the blog merge SHA. This publishes a runtime architecture snapshot, not a new gameplay acceptance result. Revert this PR to remove the blog bundle, project entry and compatibility routes; no DNS or repository Pages-settings rollback is needed.