forked from longtao.wu/droboticflow
- server: handleSliceResetCreate splits on submission history using the established isRework signals (task revision fence, rework status, human annotation revision via fanyuV5CombinedSubmissionIsRework); first pass runs the original reset write path with sliceResetHistory audit, history keeps 409 slice_reset_disabled with in-place guidance (spec D1 revised) - table tests pin both classes incl. the system-suggestion edge; the four retired-contract test files flip to split-flow assertions - frontend: restore the reslice button, warning dialog with both reset modes, and authoritative reconciliation from f980696f~1; entry is gated client-side by the same signals (resliceEligible), normal and focused layouts share the restored footer entry; E-mode changes untouched - dev preview regains the entry; two retirement-era nail assertions flip back with the gate asserted in their place