Sergey KozyrenkoandClaude Opus 4.8 e51f686e5c refactor: drop the header-order comment and the rest of the narration ...

The comment on AppHeaderActions claimed the component pins itself to the right.
It does not — the sibling content block takes `flex-1` and pushes it there — and
the rule it stated was an instruction to call sites, not a fact about the twelve
characters below it. The convention now lives in docs/list_detail_pages.md, next
to the detail-page recipe that needs it.

Two more went the same way, by making the code carry the point instead: the
knowledge header's two ids are now `documentId` and `routeKnowledgeId`, so
there is nothing to warn about, and the separator that doubles up is gated on a
named `hasViewRow`. In the pager spec the injected delay is held by an assertion
that counts the samples taken before the sibling appears — removing the delay
now fails the test instead of quietly emptying it.

Across the e2e specs, six comments that only explained why a test exists are
gone and five more are down to one line.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-22 18:16:04 +07:00

..

e2e.md

docs(e2e): correct the stand-tier fork guard and document its env vars

2026-07-22 05:55:51 +07:00

list_detail_pages.md

refactor: drop the header-order comment and the rest of the narration

2026-07-22 18:16:04 +07:00