Dockerfiles bake DROBOTICFLOW_IMAGE_BUILD_COMMIT from a build-arg that
defaults to 'unknown', and the API prefers it over the deployment stamp, so
release images built without the arg reported buildCommit 'unknown'.
Add scripts/release-build-api-image.sh for release.py builds: it refuses
uncommitted tracked changes, passes the checkout commit and UTC build time,
pushes, and prints the digest reference for prepare --image. The general
build-and-push script now passes both args too. Document the step in the
release README.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One branch per task from origin/dev with a task card, agents push their own
task branches freely, PR creation needs the user's approval, deploy only
commits in dev. scripts/agent_status.py lists every branch against dev and
the newest deployed release across all worktree ledgers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Same-project saves queued behind one project lock. Add default-off record stripes while deletion, authorization and claim operations retain exclusive protection across all stripes. Require a complete barrier rollout before striped activation. Verify local Mongo deletion, revocation, crash recovery and two 100-user HTTP runs with save p95 below 400ms.
Acceptance finding (ticket 09 scope 5): the QC review view showed no action rail —
and neither did the annotator side. Root cause was NOT a review-phase render gate:
continuousActionsForItem derives task.continuousActions from
batch.processingProfile === raw_human + the three-role stage list, and the seeded
ise-demo(-b) batches never set the profile, so the workbench gate
continuousActions && phase === annotate was false everywhere.
- seed: perCapture.batch now carries processingProfile: raw_human (stages already
matched IsFanyuV58ThreeRoleHumanLoop).
- new static test pins the demo-data contract (ise-demo-seed.test.mjs).
- live stack patched in-place (db.humanBatches updateMany on ise-demo-batch /
ise-demo-b-batch) so the user's in-flight acceptance progress is preserved.
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).
Default proxy.golang.org is unreachable from some networks; the env value
now flows into the Dockerfile ARG (goproxy.cn mirror used for this
release build). No behavior change when GOPROXY is unset.
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)
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.