Problem
This repo has a documented, recurring failure pattern (see #3047: 4 real LOOPOVER_REVIEW_*-equivalent flags and 5 gate-mode dimensions shipped and went undocumented until an audit caught them, because nothing forces a docs update when config surface ships). The backtest/calibration system this epic builds is exactly that shape of feature — new CLI flags (#8084), a new CI check with its own trigger/comment behavior (#8138, extended by #8139), a new gate-mode-adjacent policy decision (#8105) — and has no docs plan yet.
Area
Docs — likely apps/loopover-ui/src/routes/docs.*.tsx or wherever this repo's docs site currently lives by the time this is picked up (the docs architecture was mid-migration to an MDX pipeline as of this epic's filing — check current state first, do not assume the old route-file pattern still applies).
Proposal
Once #8138 (the advisory CI check) has actually shipped and its real, final shape (CLI flags, comment format, trigger conditions) is stable — not while it's still moving — write the docs page(s) covering: what the backtest check is, how to read its PR comment, how the baseline snapshot works, and (once #8105 resolves) whether/how a regressed verdict affects merge. Cover #8139's logic-backtest extension too if it has shipped by then; note it as "coming soon" if not.
Deliverables
Deliberately none yet — see Boundaries.
Resources
Boundaries
Do not write docs against #8138's design before it actually ships — docs written against a moving target just need rewriting. This issue exists so the need is tracked, not to be picked up early.
maintainer-only — docs follow-up, blocked on #8138 shipping first.
Problem
This repo has a documented, recurring failure pattern (see #3047: 4 real
LOOPOVER_REVIEW_*-equivalent flags and 5 gate-mode dimensions shipped and went undocumented until an audit caught them, because nothing forces a docs update when config surface ships). The backtest/calibration system this epic builds is exactly that shape of feature — new CLI flags (#8084), a new CI check with its own trigger/comment behavior (#8138, extended by #8139), a new gate-mode-adjacent policy decision (#8105) — and has no docs plan yet.Area
Docs — likely
apps/loopover-ui/src/routes/docs.*.tsxor wherever this repo's docs site currently lives by the time this is picked up (the docs architecture was mid-migration to an MDX pipeline as of this epic's filing — check current state first, do not assume the old route-file pattern still applies).Proposal
Once #8138 (the advisory CI check) has actually shipped and its real, final shape (CLI flags, comment format, trigger conditions) is stable — not while it's still moving — write the docs page(s) covering: what the backtest check is, how to read its PR comment, how the baseline snapshot works, and (once #8105 resolves) whether/how a regressed verdict affects merge. Cover #8139's logic-backtest extension too if it has shipped by then; note it as "coming soon" if not.
Deliverables
Deliberately none yet — see Boundaries.
Resources
Boundaries
Do not write docs against #8138's design before it actually ships — docs written against a moving target just need rewriting. This issue exists so the need is tracked, not to be picked up early.
maintainer-only — docs follow-up, blocked on #8138 shipping first.