CI / changes (pull_request) Successful in 17s
CI / lint (pull_request) Successful in 56s
CI / frontend (pull_request) Successful in 2m31s
CI / backend (pull_request) Successful in 1m57s
CI / e2e (pull_request) Successful in 3m32s
CI / semgrep (pull_request) Successful in 1m13s
CI / api-client-drift (pull_request) Successful in 2m2s
CI / storybook-a11y (pull_request) Successful in 11m42s
WP-67's monorepo split renamed .storybook to .storybook-ssp/ .storybook-behandelportal, but test-storybook still defaulted to the (now nonexistent) plain .storybook dir -- it loads <config-dir>/main.js for test-runner hooks even in --url mode, so every invocation failed with "Could not load main.js in .storybook". Also: test-storybook:ci only ever built+served+tested the ssp instance. Since the split, behandelportal's stories (werkvoorraad, beoordeling, besluit-form, ...) were never axe-tested in CI at all. Added the :behandelportal siblings (mirroring the existing storybook/ build-storybook naming) and wired them into ci-local.sh's --full step and the storybook-a11y GitHub Actions job. Verified directly: ssp 62/180 stories green, behandelportal 45/112 green (including the new besluit-form story), full `ci-local.sh --full` green end-to-end. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>