- 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
- remove the two annotate-phase stage locks in canonicalSliceDispositionState:
boundary moves of discarded slices and explicit merges are now edited in
place, first pass and rework share one server path (spec §3.4, R2-Q7:a)
- keep the bottom line untouched: every action must fall fully inside exactly
one slice and carry a whitelisted status (annotation_operations.go /
annotation_contiguous.go), pinned by new table-driven cases incl. half
actions and the three triage products
- retire the reslice write endpoint: POST /slice-reset now answers 409
slice_reset_disabled pointing at in-place editing and never writes;
sliceResetHistory evidence and reads stay intact (R3-2:a)
- reset-family tests flipped to the disabled contract; historical post-reset
invariants still covered via a legacy-state fixture helper