- opinionCardScopes: three cards (slice/action/timestamp), same visual spec
(role=option + aria-selected highlight, click enters target editing)
- timestamp card entries = timestamp opinions owned by the current action,
atSeconds ascending; current action resolved from the same position data
as the D5 target model (new reviewPositionAction in review-navigation.js,
range reported with ReviewPosition by the viewing surface)
- timestampProblemsOfAction pure helper in review-opinions.ts, table-driven
tests; slice identity guards cross-slice leakage in slice-seconds basis
- remove the all-task flat timestamp list from ReviewProblemPanel (G-jump
and timeline markers keep the full-task set from the hook)
- entry click keeps selectProblem anchoring; J/K focus emphasis preserved on
in-card entries; anchored-target entry stays emphasized
- names: timestamp -> 当前时间点意见 (no task revival)
- 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
D1: single-slice tasks open the slice-edit panel on E (panel supports
adding boundaries); the slice-edit-unavailable toast branch is deleted
outright (key table context, notice state, dispatch and UI).
D6: J/K landing on slice problems auto-opens/switches the panel target
(reworkLocatePlan now carries a sliceEdit intent on jump plans); landing
on action/timestamp problems collapses the panel with pendingSlices
stashed and restored on reopen while the workspace is unchanged; Esc
remains the explicit full discard. Panel-open J/K passes through to the
rework navigator instead of locking; conflict-list J/K stays locked and
mouse-path locks are untouched (jump selects bypass the click lock via
an explicit flag only).
- mergeDegenerateProducts: straddle pieces within EPS merge into a
same-status neighbour (coverage unchanged) so degenerate boundary
structures can no longer persist invisible zero-width segments that
intervalStyle renders as display:none
- scanSliceEditConflicts now returns autoFollows (silently-following
edge-glued invalid actions) + conflictAutoFollowHint derivation for
the collapsed conflict-list hint row (panel and drag quick paths)
- invalid track blocks get a min-width visibility marker so needle-width
invalid intervals stay visible on the track
- 5 new engine tests (guard x3, autoFollows, hint); workbench source
guards updated to pin the corrected wiring; repro record updated with
post-fix matrix
D7 layout fixes, zero interaction changes: a panel-scoped rule
neutralizes the shared inset:0 dictionary base (it covered boundary
rows and every panel button because the panel root is the nearest
positioned ancestor), the panel header and Enter-apply footer become
sticky within the panel's own scroll container, and the compact
disposition dialog ends 138px above the viewport bottom so it clears
the 126px submit rail instead of overlapping its top. Pin tests guard
the scoped rule, the sticky edges, the unchanged Esc/Ctrl+Enter key
contract, and the compact dialog offset.
User: 「shift 左右能改变切片或标注动作的边界…这个也没有做」. The global map
returned null for every shift+arrow outside the panel (line ~68), and in
continuousActions mode the early adjust-boundary return fired regardless of
whether an action editor was open — startBoundaryHold then silently no-oped
without editingAnnotation, so the key looked dead in both shapes.
- annotation-shortcuts: shift+arrows in annotate phase now resolve to
coarse-nudge-boundary unless (continuousActions && actionEditor) keeps the I3
action-boundary binding; slice-phase behaviour unchanged either way; repeats
consume; modifiers still fall through natively.
- workbench dispatch: coarseNudgeSliceBoundary nudges the selected slice's
boundary 0.5s (selectedBoundary if one was clicked/dragged, else the panel's
default-focus rule: selected slice end, last slice falls back to start) and
commits through onSliceBoundaryChange — the same committed pipeline the slice
phase uses (clean → immediate apply, conflict → the ticket 04 list,
Esc = nudge never happened).
- help table: new annotate row for the slice-boundary nudge; the continuous
context relabels it to the dual semantics; the old continuous extra row is now
slice-phase only.
- keyboard guide: the committed-nudge paragraph and the panel prerequisites
(drafts no longer block opening; apply still requires them) updated.
Tests: annotation-shortcuts (new dispatch matrix incl. no cross-talk with the
panel table, editable inert, modifiers) + continuous-shortcuts pins updated to
the actionEditor-aware contract.
User: E almost never opened (「E 老是按不出来,操作暂时没有完成」). Two defects:
1) openSliceEditPanel hard-blocked on outstandingDrafts — but parked drafts are
the normal state during continuous annotation, so E was almost always dead.
The blocked notice also never reached the user: it starts with 请, and
userErrorMessage's instructive-copy rule replaces such messages with the
generic 「操作暂时未完成」 fallback.
Design change (ticket 04): OPEN despite parked drafts. New
onSliceEditSessionChange channel tells the page when the panel session is
open; the page extends the autosave isBlocked gate (panel session OR any
conflict list) so drafts stay in workbench state and the structure snapshot
reference stays stable, then flushes once immediately on release
(slice-edit-close edge via sliceEditSessionFlushEdge). Guards kept:
slices<2, and the non-continuous active-editor block with unchanged copy.
The apply-time drafts guard stays (applying structure edits while draft
intervals reference the pre-apply layout can orphan content); the docs now
spell out that split.
2) The E-panel sanity walk exposed a pre-existing dead Enter: the
applySliceEditPanel workspace-drift guard compared prop references against
panel.snapshot.slices/actions, but snapshotSliceEditWorkspace deep-copies, so
Enter was ALWAYS rejected with 「面板期间工作区发生了其它修改」. The guard now
compares by value (same sorted-JSON convention as the preview-equality check
below it); genuine external changes still fail the check.
Verified live (probe-e-walk): E open → ←/→ nudge (red block) → Shift coarse →
Enter → conflict list → 1+Enter applied → E reopen → Esc; task A structure
round-trips byte-identically.
Removed with no feature flags: sliceEditActive state + auto-exit effect,
enter/exit/nudge/switch boundary helpers, the sliceEditShortcut dispatch
branch + key table + help rows, the slice-edit-mode-banner render, and the
in-mode highlighted-boundary overlay. E opens the 04 reconfig panel only
(toggle-slice-edit / slice-edit-unavailable dispatch unchanged); the batch-0
constant slot stays and still hosts the single-slice E notice and the
panel lock notice with zero layout shift.
Keymap finalized per ticket 04's judgments, pinned by tests: panel-internal
E = cancel; panel keys C/G/arrows/Enter/Esc; list keys up/down/1/2/3/Enter/
Esc; outside-mode keys unchanged incl. Shift+arrow action boundary (I3).
Grep evidence: src/ tests/ scripts/ have zero sliceEditActive /
sliceEditShortcut / slice-edit-mode-banner / enterSliceEditMode /
nudgeSliceEditBoundary / slice-edit-highlighted-boundary references outside
the anti-resurrection guard test and one explanatory comment.
Gates: tsc exit 0; frontend 774/760/14 — failure set identical to the
pre-change baseline by name (14 known upstream debts).
Removed with no feature flags: SliceTriageCard.tsx, slice-triage-card.js,
slice-triage-card-types.ts, slice-boundary-triage.js, the sliceTriage page
state + applySliceTriage/choose/dismiss, workbench card render + key-swallow
dispatch + props, triageCardShortcut/Help key tables, and the .slice-triage-*
CSS block. Commit-style boundary moves (slice-phase </>arrows and Shift+arrows)
now route through planSliceEditDragRelease into the 04 conflict list — the
same single disposition entry as drag release / hover+split / trash merge.
Grep evidence: src/ tests/ scripts/ have zero slice-boundary-triage /
slice-triage-card / SliceTriageCard / triageCardShortcut / triageCardAnchor /
sliceTriage / applySliceTriage / classifyBoundaryMove / applyBoundaryMove /
slice-triage references outside the new anti-resurrection guard test.
Dead helpers commitSliceBoundaryDraft / stepSliceBoundaryByFrame (unreferenced
since the numeric-draft sidebar was removed) deleted with their state.
Gates: tsc exit 0; frontend 775/760/15 — failure set identical to baseline by
name except the intentionally-red ticket-06 guard (old E-mode still present,
next commit).