Repository navigation
Fix landing icon naming and root favicon path - #6
Conversation
|
@codex review Please review exact current head |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Chef's kiss. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Fix the organisation landing icon URLs so browsers can resolve
/favicon.icoand all icon/manifest references from the served root. Rename the existing Direction A assets to the approved usage names without changing their bytes, colours or sizes; remove obsolete generated paths and update the landing snippet and regression checks.Validation:
node scripts/build-site-icons.mjssucceeded;npm testpassed all 36 tests. The five new icon-path regression tests failed on the unchanged main baseline and passed after the port.git diff --checkpassed. No workflows or deployment settings changed.The optional AGENTS.md and site-icons/install.md updates were omitted because their combined diff check reported two placeholder/doc findings. Existing placeholder patterns remain outside this change.
Publication scan (advisory):
id-token: <REDACTED>gs:///...and, and use <PROJECT_ID> values in