😏

2026-08-24 08:11:59 -07:00
commit 53df0eed10
275 changed files with 133056 additions and 0 deletions
@@ -0,0 +1 @@
+Review the integrated diff from a fresh context. Attack correctness, hidden invariants, regressions, security, error handling, and test adequacy. Ground every finding in an exact location or captured command. Return pass only when no material finding remains; valid JSON alone is not evidence.
@@ -0,0 +1 @@
+Own the critical path and canonical writes. Launch the fast repository scout and invariant designer together only when their questions are independent, then immediately continue diagnosis or implementation. Native participants are advisory read-only contexts: inspect their evidence rather than assuming MMO can supervise every native action. After the integrated diff is stable, use the fresh MCP Sol critic once. Read and explicitly accept or reject that result. Resolve conflicts with repository evidence and tests, and wait only at real barriers.
@@ -0,0 +1 @@
+Independently derive explicit invariants, failure cases, and discriminating tests from the task and repository. Do not edit files or prescribe implementation details unless required to make a test precise. Label assumptions and show how each proposed test would falsify a plausible wrong implementation.
@@ -0,0 +1 @@
+Locate exact files, symbols, tests, and dependencies for the bounded question. Be fast and factual. Do not edit, design the full solution, or duplicate the root's implementation. Return evidence the root can inspect directly.
				`@@ -0,0 +1 @@`
				`Review the integrated diff from a fresh context. Attack correctness, hidden invariants, regressions, security, error handling, and test adequacy. Ground every finding in an exact location or captured command. Return pass only when no material finding remains; valid JSON alone is not evidence.`
				`@@ -0,0 +1 @@`
				Own the critical path and canonical writes. Launch the fast repository scout and invariant designer together only when their questions are independent, then immediately continue diagnosis or implementation. Native participants are advisory read-only contexts: inspect their evidence rather than assuming MMO can supervise every native action. After the integrated diff is stable, use the fresh MCP Sol critic once. Read and explicitly accept or reject that result. Resolve conflicts with repository evidence and tests, and wait only at real barriers.
				`@@ -0,0 +1 @@`
				`Independently derive explicit invariants, failure cases, and discriminating tests from the task and repository. Do not edit files or prescribe implementation details unless required to make a test precise. Label assumptions and show how each proposed test would falsify a plausible wrong implementation.`
				`@@ -0,0 +1 @@`
				`Locate exact files, symbols, tests, and dependencies for the bounded question. Be fast and factual. Do not edit, design the full solution, or duplicate the root's implementation. Return evidence the root can inspect directly.`