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=<path>` rather than the raw vitest invocation it needed while
the recipe swallowed its filter.

.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=<path>` does not filter** and
+- **Record one file with `make ui-visual-update UI_ARGS=<path>`**, and
-  re-records *every* baseline, blessing any stale one in silence:
+  check `git status` before committing either way. That filter is only
-  vitest's `--update` takes the following positional as its value. Until
+  honoured since #204: the recipe was a bare `--update`, and vitest
-  #204 lands, record one file with
+  takes the following positional as the flag's value, so the path was
-  `cd frontend && YJ_VISUAL=1 npx vitest run --update=true <path>`, and
+  swallowed and *every* baseline was re-recorded — blessing any stale
-  check `git status` before committing either way.
+  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 —