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.
R1-Q8/R2-Q7 (spec slice-edit-ux-rework, seam ②):
- planQualityReviewDecision now builds the next rework baseline as
unresolved prior opinions (same entry IDs, QC still-problem notes
merged into the original text) followed by this round's new opinions;
resolved opinions never enter the new baseline
- rework-baseline reads (any round) and the acceptance source-opinions
baseline projection narrow to unresolved-only via the frozen round's
review confirmations; frozen records stay untouched (B02)
- legacy fallback: missing confirmations mean unresolved and opinions
keep carrying (documented + tested); missing prior baseline keeps the
first-round fresh-only behavior
- ADR 0008 records the decision, consequences and the rejected
collapsed-display alternative
One command now rebuilds TWO tasks sharing the org/accounts: task A
(unchanged, round-1 rework returned to the annotator) and new task B
on a second ise-demo-b-* capture driven through the full loop — first
submit, QC 8 opinions, reject, partial rework via real endpoints
(split S1 @15s, discard S3 via dictionary reason, act-07 description,
act-13 invalid), resubmit ending round-2 submitted awaiting QC
re-review with structureChangeSummary split=1/discarded=1. Deliberately
unresolved act-17, both timepoints and the overall opinion keep the QC
receive view red/gray mixed out of the box. Walkthrough §0 becomes a
two-task table and case-2 points at task B directly (manual path via A
kept as an optional note).
- new ReworkOpinionRail: all opinions in a scrollable right-column mini window
(focused/compact layout only), grouped red → skipped → gray → old, click to locate
- jumpOrder extended from red-only to full navigation order with per-entry state;
J/K walk the full list in both layouts (red first), gate dialog filters red
- focused layout: per-slice cards under the slice track removed (no stacking),
summary strip slimmed to one line pointing at the rail
- docs: manual + ADR 0006 wording updated for the new J/K semantics
Six follow-ups from the round8-12 hotfix retrospective:
- web-ci.yml: lint + Go/frontend tests on every push and PR (nothing ran
app checks before; the round10 dev-mode regression shipped green)
- tests/known-failures.json + check-test-baseline.mjs: gate by exact
failing-test id instead of hand-counted failure totals (14 frontend,
70 Go upstream debts recorded from the dev tip)
- devboot.test.mjs: boots the real Vite dev server and pins the movi
loader contract that broke round10 (query-less DEV url, /vendor stays
off the module pipeline)
- scripts/local/smoke-workbench.mjs: pre-release smoke covering the
seven recurring acceptance points (login/pool/claim/play-while-loading/
captions/4x/playhead), 3x green against the local replica
- docs/CODING_STANDARDS.md + AGENTS pointer: eligibility flags are
server-shipped, the UI renders them (rounds 9+12 lesson)
- vendor README host-element quirks section, HANDOFF gate pointers and
movi-path verification rule, perf-audit report pinned with the
post-round12 production 500 observation
- husky pre-commit: lint-staged (repo prettier scope) + tsc + gofmt
- gofmt: restore lint:go green on the dev tip (drift shipped silently
in the perf merge and round12 because nothing gated it)
Resolve server.go and production_stats.go conflicts by combining both
sides' intents:
- routes: keep dev's /api/dashboard/workforce and wrap the production
dashboard in the response cache
- dashboard loading: dev's parallel errgroup fetches, but the runs
goroutine keeps the C4 cursor-paginated summary page (limit 50 +
aggregates) instead of the unbounded list
- enrichDashboardHumanWork: keep the C4 aggregation-counter fast path;
the legacy fallback (stores without the counting interface) now
fetches items/packages in parallel like dev
- production_stats.go imports: our superset (time/sort/strings + cache)
Record how to verify the part-index delivery in the local replica: the three
test layers, the real-media boundary check that keeps review media while the
index references none, the reversible replica fixture, and the dry-run
migration command. Also note that the snapshot super admin cannot log in locally
because legacy organization-admin access is off, so the organization admin
account and its phone identifier are the working path.
Add scripts/part_index_migration.py, which produces the missing part.json for a
part that was delivered in the directory form. It reuses the package operator's
own builder by loading the operator source the way the runner does, so a
migrated index is structurally identical to an online package and
byte-identical to what the same evidence would have produced, apart from a
lineage.migratedFrom marker. A test compares both routes on one evidence set to
keep the two from forking.
The tool never writes object storage: publication has to go through the
API/Worker path so the owner marker, conditional create and no-overwrite
guarantees stay in effect. It refuses to run when the delivery directory lacks a
completion manifest, when a slice has an unknown disposition, when the revision
has no per-slice disposition evidence, and when the part already has a part.json
with different bytes.
Also fix a leak found while building this: the index wrote the operator's
absolute workspace path into calibration[].path. It now records the logical
delivery-relative path, matching the directory form's packages-manifest, and
keeps the local location out of customer-facing output.
Verification: 19 operator and migration tests pass. tests/backend failure set is
identical to the HEAD baseline (25 failed, 829 subtests passed, 516 vs 525
passing), so no regression.
Add a PART_INDEX_DELIVERY mode to the package operator (default off): a part
delivers a single part.json carrying both split levels, the task-level slice
boundaries and the action-level segments, plus a classification for every
reviewed interval. Kept intervals land in slices[], discarded intervals in
discardedSlices[] with their discard evidence, which deliberately makes the
discard reason part of the customer deliverable. Media, PTS, IMU, pose and
calibration bytes are no longer published; downstream packaging resolves them
from the pinned materialization revision.
The worker publishes the index through the same frozen-destination path as the
directory form. Extract prepareDeliveryTarget so single-file and directory
publication share one owner marker, overlap guards, delegated-scope check,
conditional create, sha256 verification, idempotent retry and the refusal to
overwrite another delivery. A part index also refuses to adopt a destination
that holds files without an owner marker, so additive migration cannot claim a
legacy directory by accident.
The API and download control plane recognise the new schema, project the split
classification for the browser, and treat a part index as a first-class final
delivery. Cross-language contract tests read the operator's own schema and
field literals so a one-sided rename fails a test.
Verification: 10 operator tests, 8 worker tests and 3 API tests for the new
behaviour pass. Failure sets match the HEAD baseline name-for-name for
internal/api (75), internal/worker (4), tests/backend and the frontend suite;
no regression. The end-to-end local replica stack was not exercised: it needs
image builds and the opt-in Go materialization fixture, so the Go to operator
handoff is covered by the contract tests instead.