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.