From a82d29abd767ea8ea4ac2e6cdc664839b3067400 Mon Sep 17 00:00:00 2001 From: Logan Date: Tue, 25 Aug 2026 12:38:17 -0400 Subject: [PATCH] docs(agent): drop #204's workaround from the baseline rule #204 landed first, so the ui-tier rule can name `make ui-visual-update UI_ARGS=` rather than the raw vitest invocation it needed while the recipe swallowed its filter. --- .pi/skills/yellowjacket-dev/references/ui-tier.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.pi/skills/yellowjacket-dev/references/ui-tier.md b/.pi/skills/yellowjacket-dev/references/ui-tier.md index 66eb0d8..ce25126 100644 --- a/.pi/skills/yellowjacket-dev/references/ui-tier.md +++ b/.pi/skills/yellowjacket-dev/references/ui-tier.md @@ -117,12 +117,12 @@ is: so a visual case that sets nothing photographs whatever the previous case left behind — which is how the sidebar's baseline came to have Tracks lit and `now-playing`'s to be playing from a dynamic mix. -- **`make ui-visual-update UI_ARGS=` does not filter** and - re-records *every* baseline, blessing any stale one in silence: - vitest's `--update` takes the following positional as its value. Until - #204 lands, record one file with - `cd frontend && YJ_VISUAL=1 npx vitest run --update=true `, and - check `git status` before committing either way. +- **Record one file with `make ui-visual-update UI_ARGS=`**, and + check `git status` before committing either way. That filter is only + honoured since #204: the recipe was a bare `--update`, and vitest + takes the following positional as the flag's value, so the path was + swallowed and *every* baseline was re-recorded — blessing any stale + one in silence. What the tier is worth, for the record: it is a *layout* check, blind to colour (the component tier has no `:root`, so it renders the fallbacks —