Verifying changes

Verification has six layers, and each one costs roughly ten times the one before it. Start with the cheapest, and move up only when the current layer cannot see what the diff changes.

hogli verify --changed classifies the diff against master, runs layers 1 and 2, and lists any higher layer you still have to run yourself. It does not report the diff as verified when a check was skipped, when a check only printed advice, or when no test covers the changed files. mypy is one of those advice-only checks. It runs repo-wide, so hogli verify prints its command instead of running it. Use --plan to see the classification without running anything.

For layer 4, set STORYBOOK_STORIES to the directories or story files you need instead of editing the stories list in main.ts. /working-with-storybook covers starting Storybook, opening a story by URL, screenshots, and writing the story itself.

Decision table

A diff that mixes kinds needs the highest layer among them, and only for the files of that kind.

Other rules still apply

• Reading the code does not confirm visual or UX work, as the root AGENTS.md says. A component or CSS change always needs at least a Storybook render.
• Layer 2 says where a test runs. Use /writing-tests to decide whether to add or change one. When a regression is hard to reach cheaply, extract the logic and test it at a lower layer.
• hogli ci:preflight stays the pre-push check, see /running-ci-preflight. hogli verify reuses its lint and format checks, so a pass here usually means a pass there too.

When the stack is required

Start the stack only when the behavior spans more than one process and no layer 2 test runs both sides:

• Settings, URL routing, middleware, or the Content Security Policy, because only the browser applies them.
• A Django template, because only Django renders it.
• A change that a person has to see in the app: a new scene, a navigation change, or data flowing from ingestion to a UI.
• A Celery task, Temporal workflow, or plugin-server path whose wiring changed. A change to its logic alone stays at layer 2.
• A Playwright spec you changed, because it runs against the stack.

Everything else can skip the stack. Django and ClickHouse-backed tests need the Postgres and ClickHouse services but not the web app, so hogli up -d plus a scoped hogli test still counts as layer 2.

Report what you ran

Say which layer you stopped at and why the next one was not needed. If you could not run a required layer, say so and name the command, so a reviewer knows what is unverified.