genesis-compiler 1.10.12 → 1.10.13

package/README.md

@@ -736,9 +736,13 @@ The eight task types are deliberately explicit:
 - `describe` creates or refreshes both the non-technical Blueprint and the
   complete useful Program from the current codebase, optional user guidance,
   and selected Stack guidance where it affects accurate explanation.
-- `review` is read-only. It asks the agent to compare Blueprint, code, Program,
-  and tests, identify contradictions and gaps, and distinguish evidence from
-  inference.
+- `review` asks the agent to compare Blueprint, code, Program, and tests,
+  identify contradictions and gaps, and distinguish evidence from inference.
+  It judges the tests too: the relevant ones run and pass, with what ran and
+  what was not verified reported; changed behavior has tests; no test was
+  weakened, skipped, deleted or loosened to pass; and the changed tests stay
+  fast against coarse sanity limits. It edits only tests, writing the missing
+  ones or reporting those it cannot.
 
 Prompt generation is read-only. Missing external resources are reported in
 the prompt but do not prevent its generation. Genesis never invents values.

package/docs/prompt-integration.md

@@ -161,8 +161,18 @@ before selection. For an existing uninitialized codebase it owns
 the adoption recommendation as part of the same portable prompt. A host sends this prompt on the
 first chat turn; it does not recreate the questions or Stack catalog.
 `describe` creates or refreshes the complete Blueprint and useful Program in one
-agent task. The host owns the agent and its interaction. Genesis owns only
-transparent prompt construction and deterministic project operations.
+agent task. `review` is the generic review contract a host gives an agent after
+a piece of work. Besides comparing Blueprint, code, Program and tests, it has
+the agent judge the tests: the relevant ones run and pass, with what ran and
+what was not verified reported; changed behavior has new or updated tests,
+written in the review or reported when they cannot be; a test weakened,
+skipped, deleted or loosened to pass is a finding; and the changed tests stay
+fast against coarse sanity limits (a suite never runs for hours, a test needing
+minutes is a smell, a test database is ready in seconds), never per-test
+budgets. It points at the project skill's verification section and the sanity
+checks guide rather than restating them, and edits only tests. The host owns
+the agent and its interaction. Genesis owns only transparent prompt
+construction and deterministic project operations.
 
 ## Instruction sources
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-compiler",
-  "version": "1.10.12",
+  "version": "1.10.13",
   "type": "module",
   "description": "An agent-independent prompt, multi-language code-index, cleanup, and verification companion with project agent guidance.",
   "repository": {

package/plugins/genesis/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis",
-  "version": "1.10.12",
+  "version": "1.10.13",
   "description": "Makes Codex aware of optional Genesis adoption for existing projects.",
   "author": {
     "name": "Mobily Enterprises"

package/prompts/review.txt

@@ -1,6 +1,5 @@
 Read `.agents/skills/genesis-project/SKILL.md` and
-`.agents/skills/genesis-program/SKILL.md` completely, then perform a read-only
-review.
+`.agents/skills/genesis-program/SKILL.md` completely, then review the work.
 
 Compare Blueprint intent, observable implementation, tests, Program public
 contracts, informational implementation maps, and recorded verification in both
@@ -8,6 +7,21 @@ directions. Identify missing or contradictory behavior, misleading explanation,
 unnecessarily difficult public shape, and verification gaps. Distinguish direct
 evidence from inference and state questions that require human intent.
 
+Judge the tests as part of the work, with the project skill's "Verify and
+report" section and the test sections of the sanity checks guide:
+- Run the tests relevant to the change, through the Stack's verification
+  commands or focused checks; a failure is a finding. Report what actually ran
+  and anything not verified; never report an unrun check as passing.
+- Changed behavior has tests, new or updated, that would fail without it. Write
+  the missing ones as part of this review; when that is not possible, report
+  each with the behavior it should prove.
+- A test weakened, skipped, deleted or loosened just to make things pass is a
+  finding, reported like a product defect.
+- Tests stay fast. Look at what the changed tests cost and where their time
+  goes. Coarse sanity limits, never per-test budgets: a whole suite never runs
+  for hours, one test that needs minutes is a smell, and a test database is
+  ready in seconds.
+
 Report what makes requests or tests slower than their work, citing a count or
 timing where one exists and the code path otherwise: a list or batch whose
 query count grows with its rows, an access check whose cost grows with stored
@@ -21,7 +35,9 @@ access decided from ids the client sends rather than the trusted context.
 Judge each against the matching section and outer limit of
 `.agents/skills/genesis-project/references/sanity-checks.md`.
 
-Do not edit any file. Return a concise report ordered by impact with exact file
-references, the evidence inspected, and the smallest sensible correction.
+Edit only tests: add or update the tests the changed behavior lacks, and change
+no product code, Blueprint, Program, Stack or other file. Return a concise
+report ordered by impact with exact file references, the evidence inspected,
+the tests run and written, and the smallest sensible correction.
 
 Review `genesis/subsystems.md` responsibilities, Program membership, and data ownership/use against source and schema. Report missing, stale, or conflicting associations without editing them.

package/skills/genesis-program/SKILL.md

@@ -71,14 +71,14 @@ Program module.
 ## Task boundaries
 
 The caller determines whether this is initial description, complete Program
-refresh, focused post-change reconciliation, Blueprint-only work, or read-only
-review. Respect the caller's edit boundary. Report ambiguity rather than
+refresh, focused post-change reconciliation, Blueprint-only work, or review.
+Respect the caller's edit boundary. Report ambiguity rather than
 inventing intent.
 
 ## Subsystems
 
 Maintain `genesis/subsystems.md` alongside Program in description and refresh
-work. Blueprint-only work does not change the map; review remains read-only.
+work. Blueprint-only work and review do not change the map.
 The map is the authored association authority, but responsibilities and table
 references remain fallible explanations of application source and schema.