mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-11-16 17:09:09 +00:00
Adversarial review of this branch, each finding reproduced before the fix: - Coverage floor in pr mode: the locator read any four slash-separated numbers, so editing the provider breaker's HTTP status list in AGENTS.md (`408/500/502/503/504`) failed as "edited a managed value". The diff and the rewrite plan now use only tuples that can be percentages; the release validator is unchanged. - Merge train: its detached worktree cannot tell a writer branch (the nightly refresh PR, a translation wave) from a feature, so a train boarding one went red on legitimate rewrites. The gate honours OMNIROUTE_GATE_BATCH=1 (skip the managed-value diff, like merge_group) and the train declares itself a batch. - workflow_dispatch on a feature branch ran the docs jobs in strict release mode, red by design: those steps now set OMNIROUTE_GATE_MODE=pr when the dispatch is not on main or release/v*. - i18n-mirror-refresh (schedule) ran check:docs-all in release mode and stopped opening the mirror PR whenever the base was behind the code: its docs check runs in pr mode (same line as the phase-4 PR, coordinated with that session). - Nightly refresh: a run with no diff now closes the robot's stale refresh PR (a hand-pushed tip is only reported). - Refresh: the plan lists the README mirrors' database row before README.md, so mirrors were rewritten first, the relay found nothing to carry and 66 locales turned into drifted targets. Sources now go first, a mirror the plan rewrote counts its rewrites as carried (local digits included), and a mirror is certified in sync only when every change reached it; a locale that was already stale keeps its source hash. - The snapshot test judged release-only checks (provider reference vs live modules) against the snapshot, which a provider PR that regenerates PROVIDER_REFERENCE.md would break; it now judges the derived and invariant checks only, with a floor on how many it judges.