diff --git a/AGENTS.md b/AGENTS.md
index ffad425..7ad7507 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -11,6 +11,7 @@ Also see the other related technical documentation: README.md.
 - After every iteration, evaluate if the test coverage would fall below 100%, and write tests if necessary.
 - After every iteration, run "scripts/ci-local.ps1" and ensure that nothing broke.
 - After every iteration, update all related documentation according to the change, and evaluate if a FAQ entry would help the users, serving as public documentation for this project.
+- After every frontend change, verify the results using playwright.
 - After every iteration, do a git commit with a brief summary of the changes as a commit message.
 - Keep changes small and commit often. If one iteration encompasses many smaller tasks with more than one commit, create a git branch and do the commits there. Let me review the branch before merging it back to master.
 - If you find unexpected changes in the code (deletions, changes, diff results that were not communicated), never revert them and never restore the old state. Assume that those changes happened with intent.
diff --git a/TASKS.md b/TASKS.md
index 5d2575d..eeaa7a4 100644
--- a/TASKS.md
+++ b/TASKS.md
@@ -4,7 +4,7 @@
 
 Reduce the risk of future Blazor Server circuit disconnects by shrinking payloads, removing unnecessary serialization hops, and making live refreshes more granular.
 
-The current payload split fixed the immediate failure, but it did not remove the most expensive transport pattern:
+The most expensive transport pattern is:
 
 - browser `fetch`
 - JSON parse in JavaScript
@@ -64,7 +64,9 @@ Introduce a server-side workspace query facade and call it directly from Blazor
 - `GetCampaign`
 - `GetCharacterSheet`
 - `GetCampaignLog`
-- Keep browser JS interop only for browser-only concerns:
+
+Keep browser JS interop only for browser-only concerns:
+
 - session storage
 - SSE wiring
 - DOM scrolling helpers