Repository navigation
Add selected Precise footer to IssuePages - #28
Merged
sarthakagrawal927 merged 4 commits intoOct 5, 2026
Merged
Conversation
This was referenced Oct 4, 2026
sarthakagrawal927
marked this pull request as ready for review
October 5, 2026 16:29
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.
IssuePages now uses the selected C Precise footer on successful shared layouts, with the existing native footer retained for opt-out and error responses. The integration keeps IssuePages home/search/publish/repository navigation, newsletter capture behavior, and host-only AI controls. Original artwork and exact OFL font files are served from same-origin static assets with public hash/license provenance; the existing CSP needs no expansion.
The focused regression coverage checks successful homepage/article markup and native error opt-outs. The static-asset smoke starts the actual local Wrangler asset server and verifies GET/HEAD, MIME, exact art/font hashes, public provenance without local paths, unknown-file 404s, and rejected POST/OPTIONS.
Validation: managed
pnpm checkpassed (format, lint, both TypeScript configs, 78 tests, client asset budgets, Wrangler dry-run, and the local static-asset smoke). Actual browser rendering and final design review remain pending; no production deployment is claimed.Closes #26 after rendered review and release qualification.