- 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
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.