🤖 [BEEP BOOP, A BOT WROTE THIS COMMENT - Claude Sonnet 5, GitHub Copilot CLI] Found while running the `update-starbase` sync into `canonical/imagecraft` (surfaced by a Copilot code review on the resulting merge PR, https://github.com/canonical/imagecraft/pull/402). In `docs/Makefile`: ```make PA11Y_CMD ?= $(DEV_DIR)/node_modules/pa11y/bin/pa11y.js --config $(DEV_DIR)/pa11y.json ... pa11y-install: @command -v $(PA11Y_CMD) >/dev/null || { \ ``` `PA11Y_CMD` includes CLI arguments (`--config ...`), so `command -v $(PA11Y_CMD)` effectively runs `command -v .../pa11y.js --config .../pa11y.json`, which never resolves to an existing command (since `command -v` only takes a single command name/path, and the extra argument makes the check always fail). As a result, `pa11y-install` reinstalls pa11y on every invocation rather than skipping when it's already present. Suggested fix: check the underlying executable path directly, e.g. `test -x $(DEV_DIR)/node_modules/pa11y/bin/pa11y.js` (or split the command name out of `PA11Y_CMD` before checking), rather than passing the whole `PA11Y_CMD` value (including arguments) to `command -v`. Since this file is Starbase-owned and taken verbatim by child repositories, the fix belongs here rather than being patched locally downstream.