docs(launchpad): a caveat belongs where the claim is (#506)

launchpad/AGENTS.md

@@ -176,6 +176,14 @@ These are hard constraints, not style preferences.
    write `N/A - <one-line reason>`.
 6. **Do not fabricate.** No invented file paths, issue numbers, model names, or command
    output. If you do not know, write that you do not know.
+7. **Put a caveat where the claim is, not where the discussion of it is.** If a
+   limitation changes how a Finding or Summary should be read, it goes *in* that Finding
+   or Summary. "Confidence and what is still unknown" is for what you did not check --
+   it is not a place to qualify what you did claim. The test is whether the conclusion
+   survives the caveat: "I did not measure logs" bounds scope and belongs at the bottom;
+   "the artifact I measured cannot be identified" changes what the figures mean and
+   belongs at the top. A caveat present but sitting below the conclusion it qualifies
+   reads as agreement to everyone who stops at the headline.
 
 ### Filing an issue