[prophet-report] repent: Running 'commandments repent' with no scope flag rewrote 67 files repo-wide o…

[jessegall]

Reported automatically by a code-commandments agent.

Prophet	repent
Location	(no file given)

What's wrong

Running 'commandments repent' with no scope flag rewrote 67 files repo-wide on a focused refactor branch — including config files commandments.php and composer.json, and ~60 unrelated MCP tool files. A bare 'repent' should default to git/working-tree scope (like judge --git), never touch commandments.php/composer.json, and never sweep files outside the current changes. Had to stash the whole sweep to recover.

For the fixer

Decide whether this is a false positive (tighten/guard the prophet), a wrong rule (adjust the rule or its config), or correct-but-unclear (improve the message/scripture). Add a fixture from the flagged code above.

[jessegall]

Fixed in v2.65.1.

repent no longer sweeps the scroll repo-wide. Scope now defaults to the git working tree (the changed files, like judge --git) — a bare commandments repent only touches what you've changed. To widen it deliberately, pass --all (whole scroll); --file/--files narrow further; --git is just the explicit form of the new default. The commandments.php/commandments.self.php config is now always skipped (it's tool config, not source under judgment).

Root cause: RepentService::filesFor() fell through to a full-scroll scan when no scope flag was given. Regression test added (test_bare_repent_does_not_sweep_the_whole_scroll) pinning that a bare run leaves an out-of-changeset auto-fixable file untouched.