Files
OmniRoute/docs/ops
diegosouzapw faa65df154 docs(ci): three omni-queue runbook sentences about withdrawals
docs/ops/OMNI_QUEUE.md:

- "Before a mode change or a stop", step 1: "history records no landed
  event" was too strong for the pause case. After a pause and a resume
  in live mode the next tick finds the candidate at the tip and records
  `landed`; only a base that then runs in shadow records none. The step
  now says both, and says to let the next live tick record a batch that
  is already the tip before pausing or changing the mode.
- Under the shadow table: a shadow tick also stores a withdrawal, when
  GitHub refuses its own withdrawal of a landing-stage batch. Reworded;
  the conclusion stays (every stored withdrawal comes from a batch live
  mode blessed, so a queue that was never live writes none).
- Step 2: a stored withdrawal dropped by the 20-entry limit leaves no
  field behind, so the operator also looks in the history for its error
  event, quoted as the code writes it ("<batchId>: stored withdrawal of
  <landing.statusContext> on <sha12> dropped (20 stored already); its
  newest status may still be success").
- "When the landing does not complete": the creator rule now says the
  rule of the previous commit (a status without a readable creator may
  only add a reason to withdraw, never remove one), and the prose lines
  past 100 columns are rewrapped.
2026-11-15 21:14:59 -03:00
..
2026-07-29 15:18:55 -03:00
2026-06-29 08:40:06 -03:00
2026-07-29 15:18:55 -03:00