Part of #6065.
Problem
.loopover.yml.example has TWO review: top-level keys, 546 lines apart: a "live" one at line ~434 containing only auto_review, and a second, fully-commented-out review: at line ~980 holding everything else -- including footer, note, and fields, i.e. exactly the keys that control what renders in the PR comment. The section-3 divider comment at line ~419 ("GENERIC SETTINGS (settings:)") is also positioned before the review: block instead of before settings:, so the file's own table of contents doesn't match its structure.
This is the single biggest source of "which file has the setting I want" confusion in the config surface.
Proposed fix
- Merge the commented-out block (line ~980) into the live block (line ~434) so there is exactly ONE contiguous
review: section, with every sub-key uncommented and showing its real default (matching the file's own stated convention: "every value shown is the documented default unless a comment says otherwise -- delete any block to inherit it").
- Fix the section-3 divider comment placement/label.
- Mirror the same structure into config/examples/loopover.full.yml (kept in parity by test/unit/config-templates.test.ts -- run it after the edit).
- Do NOT change any parsing behavior (packages/loopover-engine/src/focus-manifest.ts) -- this is a documentation/example-file reorganization only.
Files
- .loopover.yml.example
- config/examples/loopover.full.yml
- test/unit/config-templates.test.ts (should pass unchanged if parity is preserved)
Part of #6065.
Problem
.loopover.yml.examplehas TWOreview:top-level keys, 546 lines apart: a "live" one at line ~434 containing onlyauto_review, and a second, fully-commented-outreview:at line ~980 holding everything else -- includingfooter,note, andfields, i.e. exactly the keys that control what renders in the PR comment. The section-3 divider comment at line ~419 ("GENERIC SETTINGS (settings:)") is also positioned before thereview:block instead of beforesettings:, so the file's own table of contents doesn't match its structure.This is the single biggest source of "which file has the setting I want" confusion in the config surface.
Proposed fix
review:section, with every sub-key uncommented and showing its real default (matching the file's own stated convention: "every value shown is the documented default unless a comment says otherwise -- delete any block to inherit it").Files