SILVER/NODEDC_MISSION_CORE
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix(k1): cease reset zero-dispatch checkpoint

Browse Source
This commit is contained in:
DCCONSTRUCTIONS
2026-08-20 13:16:56 +03:00
parent aee60f12b9
commit ac4a00c67d
3 changed files with 130 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/runbooks/K1_OPERATOR_FLOW_INCREMENTAL_ACCEPTANCE.md
+6 -3
View File
@@ -81,9 +81,12 @@ Current violations observed on 2026-08-14:
described below.
- `K1-P0-RESET-CHECKPOINT`: an explicit local scenario reset resolved a
zero-dispatch START as `not-dispatched`, but left its exact recovery
checkpoint revision 17 in `prepared`. No device/network command was sent;
the stale checkpoint blocks the next START and requires a local atomic
settlement fix before live acceptance continues.
checkpoint revision 17 in `prepared`. The reset now ceases that exact
checkpoint before publishing its replay marker; its reducer and the complete
scenario-reset suite are green. Live startup convergence is accepted:
checkpoint revision 18 is `ceased` against the unchanged physical
`not-dispatched` head, with no device/network command. Clean Bluetooth
selection and the next START remain to be accepted separately.
- `K1-P1-STOP-STABILITY`: STOP authority visibly oscillated before the operator
clicked. Not fixed in the checkpoint increment.
- `K1-P1-PENDING-FEEDBACK`: reconnect/search/select/provision transitions replace