Grey.ooo/symfony-brand-kit
Watch
2
0
Fork
You've already forked symfony-brand-kit
 0
Code Issues 2 Pull requests 1 Projects Releases Packages Wiki Activity Actions

Brand kit drift: Grey's PrintShop #16

New issue
Closed
opened 2026-08-09 10:15:10 +00:00 by forgejo-actions · 1 comment
forgejo-actions commented 2026-08-09 10:15:10 +00:00
Copy link

Grey's PrintShop at https://printshop.grey.ooo is not rendering the current grey.ooo chrome.

Grey.ooo/PrintShop consumes the roster through grey-ooo/brand-kit, so it is pinned to an older release of this bundle. Run composer update grey-ooo/brand-kit there and redeploy.

What does not match

  • top bar is 1394px, expected 44px — brand-kit.css does not appear to have loaded

What it looks like

The app

Checked 2026-08-09T10:12:43.083Z against GreyOooApps::ALL in this repo · workflow run. Filed and updated automatically by tools/conformance; it closes itself when Grey's PrintShop conforms.

<!-- brandkit-conformance:printshop --> **Grey's PrintShop** at https://printshop.grey.ooo is not rendering the current grey.ooo chrome. [Grey.ooo/PrintShop](https://git.grey.ooo/Grey.ooo/PrintShop) consumes the roster through `grey-ooo/brand-kit`, so it is pinned to an older release of this bundle. Run `composer update grey-ooo/brand-kit` there and redeploy. ### What does not match - top bar is `1394px`, expected `44px` — brand-kit.css does not appear to have loaded ### What it looks like **The app** <img src="https://git.grey.ooo/attachments/763271f8-8d58-4d72-b55b-0a2ac6f393f2" width="640"> --- <sub>Checked 2026-08-09T10:12:43.083Z against `GreyOooApps::ALL` in this repo · [workflow run](https://git.grey.ooo/Grey.ooo/symfony-brand-kit/actions/runs/2). Filed and updated automatically by `tools/conformance`; it closes itself when Grey's PrintShop conforms.</sub>
bk-conf-printshop-page.png
28 KiB
geusebio commented 2026-08-09 11:00:14 +00:00
Owner
Copy link

Closing as a false positive — PrintShop is not stale, and this ticket should never have been filed.

From the CI runner, printshop.grey.ooo answered with its @splash interstitial (visible in the debug toolbar of the screenshot above). That page carries the topbar markup and the full six-entry roster, but not brand-kit.css — so it measured as an auto-height 1394px bar with every --gooo-* token empty, and nothing was logged as an error because nothing had actually failed. It reproduced on the confirming visit too, since a cold hit gets the splash consistently, which is exactly the blind spot the second visit cannot cover.

Expected behaviour rather than a defect: printshop.grey.ooo is a staging deployment, so it runs in debug mode and serves its assets through PHP, which is what makes a cold hit slow enough to show an interstitial.

Fixed by #17: the audit now waits for the stylesheet to have visibly applied, and if it never does it refuses to judge the app at all — the run goes red as "did not find out" and no drift ticket is filed. Verified by blocking brand-kit.css against a live app, which reproduces this exact signature.

The screenshots are deliberately left attached: they are the evidence for the diagnosis.

Closing as a false positive — PrintShop is not stale, and this ticket should never have been filed. From the CI runner, `printshop.grey.ooo` answered with its `@splash` interstitial (visible in the debug toolbar of the screenshot above). That page carries the topbar markup and the full six-entry roster, but not `brand-kit.css` — so it measured as an auto-height `1394px` bar with every `--gooo-*` token empty, and nothing was logged as an error because nothing had actually failed. It reproduced on the confirming visit too, since a cold hit gets the splash consistently, which is exactly the blind spot the second visit cannot cover. Expected behaviour rather than a defect: `printshop.grey.ooo` is a staging deployment, so it runs in debug mode and serves its assets through PHP, which is what makes a cold hit slow enough to show an interstitial. Fixed by #17: the audit now waits for the stylesheet to have visibly applied, and if it never does it refuses to judge the app at all — the run goes red as "did not find out" and no drift ticket is filed. Verified by blocking `brand-kit.css` against a live app, which reproduces this exact signature. The screenshots are deliberately left attached: they are the evidence for the diagnosis.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
renovate/submodules
feature/publish-composer-registry
No results found.
Labels
Clear labels   
brandkit-conformance
Filed automatically: a deployed app is not rendering the current grey.ooo chrome

No labels
brandkit-conformance
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Grey.ooo/symfony-brand-kit#16
No description provided.