From d68855a7129bb6aaf0949778a33904ee85c70488 Mon Sep 17 00:00:00 2001
From: marcusquinn <6428977+marcusquinn@users.noreply.github.com>
Date: Tue, 27 Jan 2026 01:57:34 +0000
Subject: [PATCH 1/2] chore: add verification hierarchy guidance to system
 prompt and Build+

Agents should always find a way to verify their work rather than
assuming correctness. Adds a prioritised verification hierarchy:
tools > browser > primary sources > self-review > ask user.
---
 .agent/build-plus.md     | 6 ++++++
 .agent/prompts/build.txt | 1 +
 2 files changed, 7 insertions(+)

diff --git a/.agent/build-plus.md b/.agent/build-plus.md
index a224908c..ac2e92a3 100644
--- a/.agent/build-plus.md
+++ b/.agent/build-plus.md
@@ -222,6 +222,12 @@ See `tools/opencode/opencode.md` for CLI testing patterns.
 - After tests pass, think about the original intent
 - Write additional tests to ensure correctness
 - Remember there may be hidden tests that must also pass
+- **Verification hierarchy** -- always find a way to confirm your work:
+  1. Run available tools (tests, linters, type checkers, build commands)
+  2. Use browser tools to visually verify UI changes
+  3. Check primary sources (official docs, API responses, `git log`)
+  4. Review the output yourself and provide user experience commentary
+  5. If none of the above give confidence, ask the user how to verify
 
 ## Planning Workflow (Deliberation Mode)
 
diff --git a/.agent/prompts/build.txt b/.agent/prompts/build.txt
index 64f2f054..fc4525f9 100644
--- a/.agent/prompts/build.txt
+++ b/.agent/prompts/build.txt
@@ -105,3 +105,4 @@ These apply to all models but reinforce behaviours some need more than others:
 - Do not add code comments unless asked. Focus on why, not what.
 - After code changes, run lint/typecheck commands if available (check README or configs).
 - When making changes, read surrounding context first to ensure idiomatic integration.
+- Always find a way to verify your work. Prefer in order: run tests/linters, use browser tools to check UI, read primary sources (docs, APIs), or review the output yourself. If none of these give confidence, ask the user how to verify.

From 8583b624488e9391d7a3b31b05495fdd0a07cfa2 Mon Sep 17 00:00:00 2001
From: marcusquinn <6428977+marcusquinn@users.noreply.github.com>
Date: Tue, 27 Jan 2026 02:00:49 +0000
Subject: [PATCH 2/2] chore: align build.txt verification summary with full
 hierarchy

Address Gemini review feedback: include type checkers, build commands,
and git log to match the documented hierarchy in build-plus.md.
---
 .agent/prompts/build.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.agent/prompts/build.txt b/.agent/prompts/build.txt
index fc4525f9..ba6c992b 100644
--- a/.agent/prompts/build.txt
+++ b/.agent/prompts/build.txt
@@ -105,4 +105,4 @@ These apply to all models but reinforce behaviours some need more than others:
 - Do not add code comments unless asked. Focus on why, not what.
 - After code changes, run lint/typecheck commands if available (check README or configs).
 - When making changes, read surrounding context first to ensure idiomatic integration.
-- Always find a way to verify your work. Prefer in order: run tests/linters, use browser tools to check UI, read primary sources (docs, APIs), or review the output yourself. If none of these give confidence, ask the user how to verify.
+- Always verify your work. Hierarchy: 1. Tools (tests, lint, typecheck, build). 2. Browser for UI. 3. Primary sources (docs, APIs, git log). 4. Self-review with commentary. 5. Ask user how to verify.