No change: the ranking only chooses which 3 charts show; they show in Werkator's order, so the tiles do not jump when the ranking changes. The PR document says so (Scenario#34.01 Then: "in…
e5890e47be
Scenario#34.01 verified by a test of exactly its case; the plan names PR#34 for the retry
50dd2f5fb2
Only the three most critical charts of a Werkator; a failed history is read again at the next fetch
No change: the node already has [^], see line 33 of doc/werkregie.werkbaum at 0221945: - [^] #dash.requested: Dein Approval for a requested review, …. The deployment follows the merge at…
fixed in 0221945: Scenario#37.03 (an earlier review is no request) and #37.04 (a pending request counts) each have one Given and one Then.
Fixed in 637197b: "the server reports the version, the page's footer shows it, as Werkator's does".
637197b366
The comment on the version in the build says who reports and who shows it; two clearer sentences in the PR document
Fixed in d1f3323: the PR document cites the test only for the version the footer takes; the footer's text is checked by hand.
A test of the JavaScript needs a runtime the repository does not…
Fixed in d1f3323: the test is now "the page carries the version of the build".
The claim holds; the document now names the keys, in f0d2751.
persist() in index.html writes werkregie-settings with hidden (the source chips), project, windowHours, showHiddenTasks…
Not fixed, recorded as TODO.js-tests under Open Questions in f0d2751.
The repository has no runtime for tests of the page's JavaScript; a new one needs the consent of the human (agentic-workflo…