feat: US-003 - Clarify .loop/ changes are expected in explore evaluator
This commit is contained in:
@@ -4,9 +4,11 @@ You are evaluating an analysis/exploration task. The generator claims to have an
|
|||||||
|
|
||||||
## Read-Only Enforcement (CHECK FIRST)
|
## Read-Only Enforcement (CHECK FIRST)
|
||||||
|
|
||||||
|
> **Note:** Changes to `.loop/` files (`prd.json`, `progress.md`, `contracts/`) are permitted and expected — the generator updates these as part of normal operation. Only changes to files **outside** `.loop/` violate the read-only constraint.
|
||||||
|
|
||||||
Before any other checks, verify explore mode's read-only constraint:
|
Before any other checks, verify explore mode's read-only constraint:
|
||||||
1. Run `git diff {{PRE_GENERATOR_SHA}}..HEAD --name-only`
|
1. Run `git diff {{PRE_GENERATOR_SHA}}..HEAD --name-only`
|
||||||
2. If ANY file outside `.loop/` was modified or committed, **REJECT immediately** — explore mode is read-only. The generator must not modify host project files. (Files inside `.loop/` like `prd.json` and `progress.md` are expected.)
|
2. If ANY file outside `.loop/` was modified or committed, **REJECT immediately** — explore mode is read-only. The generator must not modify host project files.
|
||||||
|
|
||||||
## Exploration-Specific Checks
|
## Exploration-Specific Checks
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user