🔀 将已部署主线整合回 dev:标注复审、源索引切片与平台稳定性 #52

Merged
longtao.wu merged 332 commits from codex/dev-mainline-20261019 into dev 2026-10-22 12:57:15 +08:00
Collaborator

Summary

将近期分散在多个分支、已部署到 Fanyu 的改动统一合入 dev,使主线对应线上 963b530f。这是完整主线整合,包含 316 个提交、452 个文件;关联 #49、#51,并包含 #44、#45 的提交历史。

dev 03db2a28
  + 标注切片编辑、撤销/舍弃、自动保存、返工与复审交互
  + 连续作业、源索引切片、审核证据及兼容交付
  + 领取/列表性能、租约恢复、项目写锁及视频加载修复
  + 按领域拆分 API 路由,并用路由快照固定路径和权限
  + 源校验等待退避、媒体时钟、侧栏范围、缓存副本、分页计数与零 IMU 修复
  = 963b530f(2026-10-19 已部署)

最后一组修复使等待源校验的修订按 2s 起步、上限 1min 退避,最多等待 1h,超时保留编辑内容;使用候选标称帧率及整数媒体时间戳验证固定帧序,容忍时间单位量化而继续拒绝丢帧。源索引明确记录零 IMU 样本时,可完成仅含表头的 CSV 交付,仍校验实际计数,历史物理修订保持非空要求。

Evidence

  • Before: 待整合版本 8379b666 的真实媒体反例中,30fps / 1ms 时间单位的 121 帧视频被误拒;10fps 原生时间单位下的丢帧被放过;零 IMU 切片在完整打包入口再次校验时失败。
    After: 增加不同帧长、分数帧率和半 tick 精度边界回归;正常视频通过、丢帧拒绝。真实媒体交付、舍弃、part-index 和迁移相关 Python 回归 42 passed,0 skipped;源索引/时钟/等待和项目写锁的定向竞态检查通过。
  • npm run lint、npm run format:check、前端/Go 构建及算子生成副本一致性检查通过。test:go:gate、test:frontend:gate 均无新增失败;仍有 70 个 Go、13 个前端已知基线失败,不声明全量测试全绿。
  • 从该提交的干净 Git archive 构建 linux/amd64 镜像,核对 revision 标签、载荷 SHA-256 和不可变 registry manifest。API 候选镜像内执行源索引、时钟与恢复回归;打包候选镜像经真实 operator-runner 验证正常交付、零 IMU、计数不符拒绝、旧物理切片空 IMU 拒绝四个场景。
  • 2026-10-19 已按明确授权发布:API、切片处理器、源校验器、Worker、Coordinator 均为 963b530f,12 个 Pod 就绪;实际 Deployment 与批准的镜像/构建标记及源索引打包镜像变更一致。
  • 线上只读验收:标注员、质检、终审三类账号登录、任务读取及角色权限与发布前一致;匿名接口返回 401;页面及 7 个入口资源通过。刷新真实浏览器后原有 4 条个人任务仍在,版本栏显示 API / Worker ready · 963b530。
  • 未完成的生产验收: 管理员/供应商负责人角色、跨供应商完整矩阵、领取/保存/送检/审核提交等写流程、强制故障恢复、并发压测、视频首帧/缓冲/播放速度。本次没有在客户任务上执行写测试,发布记录保留为 deployed_pending_acceptance。

Merge Danger

Door: two-way(源码合并可撤回;运行版本回退有兼容条件)

已有源索引修订需要保留兼容的 API/Worker/打包读者;启用 striped 锁后,回退旧二进制前须按 ADR 0011 切回 barrier 并确认写入者和租约排空。不能将旧 dev 直接当作运行回退目标,也不能恢复整库覆盖客户新增数据。兼容范围见 ADR 0010、0011。

Blast Radius: platform

涵盖标注/返工/质检/终审、切片交付、API 路由及后台任务。合并范围较大,应按上述业务领域审阅;线上只读检查不代表完整生产业务验收或 100 人容量验收。CI 配置随 PR 提交,远端运行结果须另行核对。

## Summary 将近期分散在多个分支、已部署到 Fanyu 的改动统一合入 `dev`,使主线对应线上 `963b530f`。这是完整主线整合,包含 316 个提交、452 个文件;关联 #49、#51,并包含 #44、#45 的提交历史。 ```text dev 03db2a28 + 标注切片编辑、撤销/舍弃、自动保存、返工与复审交互 + 连续作业、源索引切片、审核证据及兼容交付 + 领取/列表性能、租约恢复、项目写锁及视频加载修复 + 按领域拆分 API 路由,并用路由快照固定路径和权限 + 源校验等待退避、媒体时钟、侧栏范围、缓存副本、分页计数与零 IMU 修复 = 963b530f(2026-10-19 已部署) ``` 最后一组修复使等待源校验的修订按 2s 起步、上限 1min 退避,最多等待 1h,超时保留编辑内容;使用候选标称帧率及整数媒体时间戳验证固定帧序,容忍时间单位量化而继续拒绝丢帧。源索引明确记录零 IMU 样本时,可完成仅含表头的 CSV 交付,仍校验实际计数,历史物理修订保持非空要求。 ## Evidence - **Before:** 待整合版本 `8379b666` 的真实媒体反例中,30fps / 1ms 时间单位的 121 帧视频被误拒;10fps 原生时间单位下的丢帧被放过;零 IMU 切片在完整打包入口再次校验时失败。 **After:** 增加不同帧长、分数帧率和半 tick 精度边界回归;正常视频通过、丢帧拒绝。真实媒体交付、舍弃、part-index 和迁移相关 Python 回归 **42 passed,0 skipped**;源索引/时钟/等待和项目写锁的定向竞态检查通过。 - `npm run lint`、`npm run format:check`、前端/Go 构建及算子生成副本一致性检查通过。`test:go:gate`、`test:frontend:gate` 均无新增失败;仍有 **70 个 Go、13 个前端已知基线失败**,不声明全量测试全绿。 - 从该提交的干净 Git archive 构建 linux/amd64 镜像,核对 revision 标签、载荷 SHA-256 和不可变 registry manifest。API 候选镜像内执行源索引、时钟与恢复回归;打包候选镜像经真实 operator-runner 验证正常交付、零 IMU、计数不符拒绝、旧物理切片空 IMU 拒绝四个场景。 - 2026-10-19 已按明确授权发布:API、切片处理器、源校验器、Worker、Coordinator 均为 `963b530f`,12 个 Pod 就绪;实际 Deployment 与批准的镜像/构建标记及源索引打包镜像变更一致。 - 线上只读验收:标注员、质检、终审三类账号登录、任务读取及角色权限与发布前一致;匿名接口返回 401;页面及 7 个入口资源通过。刷新真实浏览器后原有 4 条个人任务仍在,版本栏显示 `API / Worker ready · 963b530`。 - **未完成的生产验收:** 管理员/供应商负责人角色、跨供应商完整矩阵、领取/保存/送检/审核提交等写流程、强制故障恢复、并发压测、视频首帧/缓冲/播放速度。本次没有在客户任务上执行写测试,发布记录保留为 `deployed_pending_acceptance`。 ## Merge Danger **Door:** two-way(源码合并可撤回;运行版本回退有兼容条件) 已有源索引修订需要保留兼容的 API/Worker/打包读者;启用 striped 锁后,回退旧二进制前须按 ADR 0011 切回 barrier 并确认写入者和租约排空。不能将旧 `dev` 直接当作运行回退目标,也不能恢复整库覆盖客户新增数据。兼容范围见 ADR 0010、0011。 **Blast Radius:** platform 涵盖标注/返工/质检/终审、切片交付、API 路由及后台任务。合并范围较大,应按上述业务领域审阅;线上只读检查不代表完整生产业务验收或 100 人容量验收。CI 配置随 PR 提交,远端运行结果须另行核对。
zhanghongming added 316 commits 2026-10-19 00:45:38 +08:00
Wire the existing zero-call saveCombinedDraft endpoint into the Capture
annotation workbench per .scratch/autosave-workbench spec:

- D1 triggers: slice switch (new onSelectedSliceChange workbench prop),
  20s idle debounce after the last edit, and visibilitychange(hidden)/
  pagehide immediate keepalive flush.
- D4 payload merge: unconfirmed workbench description drafts with a
  complete start<end range join segments; mid-selection drafts stay in
  the editor until their range completes.
- D2 conflict handling: 409 with a foreign server draft raises an
  explicit banner (load server draft via reload / overwrite with local
  content using the authoritative version); 409 without a server draft
  (our own formal confirmation cleared it) silently resyncs the version.
- Single in-flight PUT, formal mutations take priority (isBlocked),
  validation 4xx does not retry identical payloads, network errors do
  not block editing; monotonic version guard on apply; non-blocking
  "草稿已自动保存 HH:mm" status line.

Verification: tsc clean; 7 new unit tests (fake-clock scheduler, draft
fingerprint, merge/filter); full frontend suite 656 tests with a failure
set byte-identical to the pre-change baseline (14 pre-existing); Go
internal/api failures unchanged (no Go files touched). Manual E2E
evidence on the local replica stack remains open in the ticket.
Record the approved catch-up work order outcome: Go lane suites and the
28-test Python suite pass at c8794dd7; the retained 20260927 seeded
database replays the five-role HTTP workflow on current binaries (sl-2
snapshot full pass through final acceptance; sl-3 stops at quality as
designed; BLF scratch needs a fresh batch per the documented boundary).
Note the colima 27019 forward workaround (lane-mongo-2 on 27020, same
volumes), the session-sandbox localhost-TCP gating requirement, the
part-index delivery shape addition to the delivery-packaging coverage
gap, and the still-open movi browser smoke.
- extract domain-neutral idle flush scheduler to src/lib/idle-flush-scheduler.js;
  annotation-autosave.js delegates and keeps its 20s default (A01 tests unchanged)
- new review-draft-autosave.js: 8s constant + collector with write-guards,
  empty-text/legacy/clear-intent never auto-executed
- useReviewDraft: touch on edit, autosave enqueue isomorphic with manual save
  (background+autosave), settle keeps editor open with refreshed baseline,
  conflicts reuse existing blocked handling (no auto-retry), cancel on leave;
  beforeunload stays dirty-only
- 10 new node tests; full-suite failure set identical to pre-change baseline
  (14 known pre-existing); tsc clean; fixes one pre-existing prettier violation
- resolve autosave-workbench issue 02; fold browser E2E evidence into ticket 04
- A02 review autosave browser E2E 10/10: exactly one PUT after 8s idle, editor
  kept open, status text, reload restores opinion verbatim, no decision
  auto-submit, idle zero traffic
- A01 workbench E2E 4/5: claim/continue/render/idle-clean pass; typing->PUT->
  reload deferred to online verification (slice generation needs k8s worker
  runtime; company kubeconfig refused by policy)
- 50-user write-rate load test PASS: 350/350 draft PUTs 200 (4 cadence rounds
  at 20s + 3 synchronized bursts), p50 65ms / p99 1.1s, 0 failures, 0 5xx,
  0 Mongo slow ops (profiler slowms=100)
- regression: frontend failure set identical to baseline (14 known); Go 70
  failing subtests all pre-existing families, zero Go files changed
- fixture/loadtest/e2e tooling documented in local-data/verification/
  autosave-replica/ (untracked, referenced from ticket)
- server: timestamp scope in canonicalReviewProblems (identity = source +
  canonical frame, discard-slice/out-of-range/exclusive-end rejections with
  explicit messages, zero duration, dual basis conversion; fixes input
  timeBasis being clobbered by the shared branch) and reviewOpinionKey
  (microsecond frame identity); comment summary gains per-point labels;
  slice-id statistics cover timestamp problems
- rework routing: FANYU_REWORK_RETURN=directed|pool rollback switch applied
  at both decision entries (v5.8 plan + legacy /reviews); directed branch
  already existed (22ca5cd8) with 7-scenario matrix; new pool-branch test
  asserts public-pool restore + admin reassignment channel stays available
- frontend (D5): timestamp option in the F scope menu (three-card navigation
  untouched via opinionCardScopes), timestamp opinion list in the review
  panel with click-to-locate, independent G key jump command wired through
  quality + acceptance workbenches; scope type widened
- tests: 4 new Go tests (canonicalization, 6-case rejection table, per-frame
  uniqueness, pool switch) green; api suite failures identical to baseline
  (65); frontend failures subset of baseline 14, zero new; replica-stack
  live demo: save at 60.05s -> exclusive-end rejected -> formal rejection ->
  directed return to original annotator with labeled timestamp comment
- resolve review-rework-workflow issue 01; interactive rework-side point
  positioning handed to issue 02 (return-baseline view)
- ReworkBaselineRecord: frozen at formal quality rejection via a new decision
  effect (idempotent apply); embeds original opinions, reject comment, and the
  reviewed revision's slice/action summaries - self-contained by design so
  revision pruning can never orphan it and no customer data is deleted
- ReworkFeedbackRecord + GET/PUT /api/human-items/{id}/rework-feedback:
  writer restricted to the directed owner (incl. admin-reassigned owner) or
  manager; entries must reference baseline opinions; CAS version conflicts;
  readable by the reviewer; missing-baseline rounds return a graceful conflict
- GET /rework-baseline returns null baseline for legacy rounds (degraded read,
  never blocks the flow)
- ReviewDraft.Confirmations (D7): canonical validation against the current
  round's baseline (unknown/duplicate opinions rejected; unresolved requires
  note or a current-round opinion; no-baseline rounds must stay empty);
  frozen into AnnotationReviewRecord at the formal decision, matching the
  irreversible-verdict principle
- tests: baseline freeze+embedded evidence, feedback contract (403/400/CAS/
  reviewer-read), confirmation validation+freeze, graceful-missing - all
  green; internal/api failures identical to baseline (65), zero new
- rework API client (baseline/feedback GET + CAS save)
- useReworkReviewData: fetches current-round baseline + feedback when
  reviewRound >= 1, degrades to null on missing/legacy data
- ReviewProblemPanel: read-only original-opinion section with per-opinion
  annotator feedback, D7 confirmation controls (已解决 / 仍有问题+note) that
  upsert into the review draft confirmations and ride the existing 8s
  autosave + formal-decision freeze
- frontend failure set identical to baseline (14), tsc clean
- ReworkFeedbackEditor: read-only original opinions from the frozen
  baseline, per-opinion feedback textarea, 8s idle autosave via the shared
  scheduler, CAS conflict banner preserving local text, mounted above the
  annotate workbench for rework rounds
- replica-stack five-role demo (fresh binary after killing a stale go-run
  child that still held :3001): quality timestamp-opinion rejection ->
  baseline frozen (1 problem, 4 embedded slices, labeled comment) ->
  directed return -> admin reassignment -> annotator reads baseline +
  saves feedback (stale replay 409) -> resubmit -> reviewer reads feedback,
  D7 confirmation draft, formal approval, confirmations frozen in the
  review record
- resolve review-rework-workflow issue 02; frontend failures identical to
  baseline (14), tsc clean
- retention: baselines/feedback kept forever (<=0.3MB per task lifetime,
  no cleanup jobs); materialized slices keep K=2 generations, older-gen
  cleanup registered as a known-gap for the C-block maintenance track
- comparison media: zero new video files - metadataOnly materialization
  references source run artifacts, manifestSha256 content-addressed reuse
  (existing code branch cited), playback over the existing presigned/direct
  pipeline
- capacity at 50 users: sequential two-stream comparison <=2x single path
  (~250Mbps peak), consistent with the C-block 50-user criteria; no new
  storage/bandwidth budget items for B03
- resolve issue 06; unblocks issue 03
- random-claims: my directed rework item is returned as-is (no version bump)
  before any random draw, and keeps priority on repeat claims until the
  rework is submitted; other annotators never receive someone else's
  directed item (assigned filter unchanged)
- quality pool rows gain a 返工复查 badge + detail line for round>0 items;
  workbench header shows the same state; DetailedTaskStatus widened
- pool list stable-sorts rework items to the top (先清自己的错再领新)
- tests: rework-first claim matrix (priority, idempotent resume, priority
  release after submit, invisible to others) green; api suite failures
  identical to baseline (65); frontend failures identical (14); tsc clean
- ReworkFeedbackEditor: 定位 button per timestamp opinion, seeking the
  annotate workbench player via the existing seekRequest channel
  (revision-deduped), same capture-seconds timeline; B03 全局导航 for the
  rework side without touching workbench internals
- tsc clean; frontend failures identical to baseline (14)
- adjustSlice: actions crossed by a moved slice boundary split into two
  source-positioned halves (deterministic :split: ids) marked status
  needs-check; touching boundaries still stretch; untouched actions kept
  verbatim (D2 ruling 2026-10-12)
- action list renders 待核对(边界拆分) with amber emphasis for
  needs-check segments
- ReworkComparisonPanel: structural baseline-vs-workspace diff (slice
  boundaries/names/dispositions, action text/boundaries, additions and
  removals, split detection) per spec §5.1/§5.3 + §11.2 zero-new-media
  conclusion; collapsible details region above the workbench
- tsc clean; frontend failures identical to baseline (14)
The 1d1c9f50 editor patch called s.replace() without reassigning the
variable, so the 定位 button never landed despite the commit message;
this adds it for real (verified: browser shows 定位钮 on the rework
feedback section, seek wired via seekRequest). Also recorded: Vite's
module cache served stale transforms until restart, and the app-level
project scope defaulted to review-focused (no rework rows there) —
both cost one debug cycle each.
- GET /api/human-items/{id}/source-opinions: per-source projection of
  rework baselines (round, frozen problems incl. timestamps, comment) and
  formal quality reviews (round, decision, reviewer, frozen D7
  confirmations); aggregate items only
- multi-source coordination detail: requireAcceptanceSourceReady and the
  decision gate now name the pending sources (itemKey + stage + status)
  instead of a generic message
- AcceptanceSourceOpinions panel in the final-acceptance workspace:
  collapsible per-source history labelled who/which-round
- rework_review badge extends to prepackage_acceptance rounds
- tests: pending-gate names source then approves after ready; projection
  carries baselines/reviews/confirmations and rejects non-aggregate items;
  api failures identical to baseline (65), frontend zero new, tsc clean
- B05 matrix (1413x615): five work modes incl. rework folding, dual-camera,
  legacy replay, keyboard-focus guard - 13/13 with two explicit deployment-
  time exemptions (D2 interactive drag, aggregate acceptance demo) routed to
  the established online-verification list
- known-gap table terminal: materialization cleanup -> formal backlog
  ticket; no silent downgrades outstanding
- docs/rework-review-manual.zh-CN.md: three-role manual (annotator rework /
  quality reject+recheck / acceptance batch recheck) aligned with CONTEXT.md
- compat evidence: optional-field read compat, rollback switch, legacy
  payload writes; asymmetry documented (timestamp/confirmation editing
  needs the new frontend by design)
- perf evidence: A04 50-user load + B06 capacity conclusions
- resolve issues 03 and 05; roadmap moves to the deployment phase
- rework_baseline: drop hand-rolled itoa for strconv.Itoa (P6 reuse)
- AcceptanceSourceOpinions goes through reworkApi.sourceOpinions instead
  of a direct apiRequest (API-wrapper layering)
- shared opinionScopeLabel in review-opinions.ts replaces the triplicated
  scope→label cascades
- rework-first scan limit named and justified in place
- feedback editor tracks conflict via state flag instead of matching
  human-readable error text
- kept: reworkReturnMode os.Getenv follows the 24-precedent api-package
  flag style (auth.go DROBOTICFLOW_ENABLE_LEGACY_ORGANIZATION_ADMIN);
  baseline double-fetch note (useReworkReviewData is review-stage gated,
  annotate mode needs its own fetch)
- c3 rework-first: drop the Limit-20 newest-first window that could bury an
  old returned task under newer claims (review finding: silent priority
  loss); full personal-item scan is the documented correct behavior
- c4 timestamp jump: per-source ordering (current source first, cycle
  within source before moving on) - never interleaves seconds from
  different sources on one axis (spec §4.3)
- c5 unresolved confirmation now requires an explicit note (spec §5.3
  明确引用; the any-opinion loophole closed)
- a1 D1 downgrade: opinions with saved handling feedback render amber
  有修改,待复核 instead of full red; unhandled keep the strong alert
- a2 reviewer-side structural comparison: ReworkComparisonPanel now also
  mounts beside the review panel for re-review rounds (§5.3)
- a3 D4 counters: reviewer header shows 待处理 N / 待复核 M (non-blocking)
- a5 confirmation-only autosave: idle flush now carries confirmation
  changes via an in-place opinion re-save; zero-opinion drafts degrade to
  an explicit message instead of silence (§5.4-8)
- a4 axis markers: backlog ticket maintenance-backlog#02 (visual
  enhancement; discovery already covered by list + G + locate)
- regressions: api 65=65 zero new; frontend 14=14 zero new; tsc clean
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.
- worker maintenance job (hourly, batch of 3 tasks/tick): terminal-only
  (accepted/rejected) tasks keep the newest K=2 materialized generations,
  older generation directories are reclaimed from disk
- ownership filter by artifact ID marker prevents cross-task deletion;
  path traversal rejected at identifier level (Join-cleaning-proof) plus
  reconstructed-path prefix containment
- source video artifacts, rework baselines (embedded data), and formal
  records are never touched; artifact records stay as tombstones per
  spec §7 graceful-degradation semantics; rescans are idempotent no-ops
- tests: K=2 retention + source/other-task isolation, non-terminal and
  shallow-history skips, traversal rejection - all green
- thin marker strip atop the review slice timeline: orange dots at
  capture-seconds positions; near-neighbours (<0.8% track width) cluster
  into a count badge; single marker click seeks via reviewController,
  cluster click expands a popover listing each opinion (time + text)
- parent slices are never painted red (markers live on their own strip,
  visually distinct from the playhead)
- data flows through the new reviewTimestampOpinions prop mapped from
  reviewDraft.timestampProblems (same source as G-jump and locate)
- browser-verified on the replica stack: two nearby opinions (0.09s/
  0.14s) cluster into one '2 条' marker, expansion lists both; frontend
  regressions identical to baseline (14), tsc clean
- delete ReworkFeedback concept (editor, domain, API, store) per user decision
- add /rework-handling API: one-click skip ('no change') with CAS + trace for re-review
- add rework-emphasis pure lib: baseline-vs-workspace diff auto-clears red,
  merge reattach, multi-round (latest red, older dimmed), J/K jump order
- workbench: red slice blocks + count badges, red/gray action blocks,
  red timestamp markers, per-slice opinion cards, summary strip above track,
  soft submit gate, help entries, one-line notice pointer
- QC ripple: skipped chips replace feedback read in ReviewProblemPanel
- docs: CONTEXT.md glossary (意见处理状态), ADR 0006, manual rewrite
- 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
- remove the two annotate-phase stage locks in canonicalSliceDispositionState:
  boundary moves of discarded slices and explicit merges are now edited in
  place, first pass and rework share one server path (spec §3.4, R2-Q7:a)
- keep the bottom line untouched: every action must fall fully inside exactly
  one slice and carry a whitelisted status (annotation_operations.go /
  annotation_contiguous.go), pinned by new table-driven cases incl. half
  actions and the three triage products
- retire the reslice write endpoint: POST /slice-reset now answers 409
  slice_reset_disabled pointing at in-place editing and never writes;
  sliceResetHistory evidence and reads stay intact (R3-2:a)
- reset-family tests flipped to the disabled contract; historical post-reset
  invariants still covered via a legacy-state fixture helper
# Conflicts:
#	src/components/CaptureAnnotationWorkbench.tsx
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).
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
# Conflicts:
#	src/components/CaptureAnnotationWorkbench.tsx
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).
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).
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.
User reported the two timeline tracks nearly overlapping in the QC review view at
narrower viewports. Reproduced in the review-focused layout (reviewFocus=1): the
workbench grid pinned row 4 (slice timeline editor) at 66px and row 5 (action
timeline) at 90px — both smaller than their content (slider + heading + 46px slice
track ≈ 104px; action timeline min-h-40 = 160px). Flex children with min-height:0
were crushed (heading ≈ 4px, banner slot 32→18px, slice track 46→42px) and the
slice blocks overflowed onto the action blocks: 24px container gap, ~6px block
overlap at every viewport ≥1413. Same family as ticket 01's focused-mode
regression (fixed-height rows + absolutely positioned tracks + a dead slot).

- rows 4/5 now content-driven (auto); the video row (1fr) absorbs the difference.
- the slice-edit banner slot is display:none under [data-review-focused]: both
  notices are unreachable in review (E and the panel are gated by the review
  keymap), so the slot is dead weight there; annotator-side constant-slot
  semantics in capture-workspace.css are untouched.
- measured gap after: 44px at 1680/1440/1366/1280 (focused), 173px unfocused;
  evidence under .scratch/slice-edit-ux-rework/probe-out/fix-afterB-*.json
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.
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.
The captions-visibility static guard pinned '((isQualityReview || captionsViewable)'
byte-for-byte. Prettier's paren wrapping for that expression depends on the
surrounding line-width context; after the acceptance-fix edits it now emits the
single-paren form (both are valid prettier output — HEAD's double-paren form was
also clean). The assertion now pins the condition composition, not the paren
shape. No behavior change.
✅ ticket 11: close slice-edit UX feature — user acceptance rounds + online deployment verified
Some checks failed
web-ci / checks (push) Waiting to run
web-ci / checks (pull_request) Has been cancelled
04f28c4fce
🛡️ retro F2: release check --local refuses images without a linux/amd64 manifest entry (arm64-only wedge prevention)
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
4fdecd8e07
✨ Add dictionary CSV export, bulk import and batch remove to labels panel
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
5bba40e9e0
Clicking an unclaimed row in the claimable pool wrote its id into the URL,
which an effect misread as ownership and flipped the list to My Tasks; the
selection sync then dropped the previewed task entirely. Gate the flip on
confirmed assignment (pools.mine / task detail), and start review
workspaces on the claimable pool for URL arrivals, so owned deep links
still land in My Tasks via the ownership effect. Claim-without-preview
keeps preserving the current list view.
🐛 Keep returned annotations visible to annotators when import waves bury their tasks
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
90d5c0c5a2
A quality rejection reassigns the ORIGINAL annotation task, whose
createdAt keeps the original import date. The task list pages
org-wide newest-first and then role-filters each window, so once newer
import waves fill the window with unreadable foreign tasks the
annotator's own returned task can no longer be fetched: each page
filtered to empty, and the filtered-empty response dropped the
continuation cursor so paging stopped for good (production incident
2026-10-14: reviewer saw the return, annotator saw nothing).

- server: authorization-empty pages now carry the store window's
  nextCursor/hasMore (taskPageCursor helper shared with the success
  path) so limited consumers can always continue paging
- client: non-manager workspaces (annotators included, previously
  review-only) fetch tasks by pool legacyTaskIds via the existing
  ids= join instead of the newest-first window, mirroring the
  任务关联数据缺失 fix
- tests: Go windowed-paging contract test (empty page keeps cursor,
  page 2 returns the rework task, ids join reaches it directly) and a
  frontend source pin for the ids-join condition
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.
- 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
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).
Server: reject NEW task-scope problems on draft PUT (409
review_task_scope_deprecated, ID-matched against stored entries;
existing entries round-trip unchanged, full-replace semantics kept);
formal-rejection flattening no longer emits 整体任务 lines or
expands ProblemSliceIDs; rework-baseline reads hide task problems
(read-only narrowing); workforce stats stop counting task scope.

Frontend: remove task from composer scope lists and card cycle;
hide stored task opinions in rework banner/soft reminder/rail,
QC panel groups and history, acceptance source projection, stats
panel rows, frozen-comment displays (stripTaskOpinionLines);
submit/approve gates count visible problems only; stats panel
documents the 2026-10-14 scope switch.

Data untouched: no migration, no deletion, audit trail intact.
- 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
- 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)
Reviewed-on: #48
🎨 Normalize existing formatting for PR CI
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
3472c021de
🐛 Fix discard confirmation focus and reset restored action tracks
Some checks failed
web-ci / checks (push) Has been cancelled
52dcb53a8c
🐛 Allow legacy editable tasks to undo persisted slice changes
Some checks failed
web-ci / checks (push) Has been cancelled
89164601af
🐳 Include hook bootstrap in API dependency build layer
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
45981287be
🎨 Give focused task controls a separate header row
Some checks failed
web-ci / checks (push) Has been cancelled
470b171355
🐛 Recover annotation saves and separate pending task views
Some checks are pending
web-ci / checks (push) Waiting to run
9289a95d04
⚡ Parallelize project saves while fencing scope mutations
Some checks are pending
web-ci / checks (push) Waiting to run
94a840c2ad
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.
🛡️ Honor read-only database bootstrap in coordinator releases
Some checks are pending
web-ci / checks (push) Waiting to run
3a4e4d308a
🛡️ Bound source validation to explicit current requests
Some checks are pending
web-ci / checks (push) Waiting to run
ba6c46cffa
Reviewed-on: #50
⚡ Preserve selective annotation bounds on Mongo 8.0.17
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
ad47b733e2
Walks the chi router and records, per method+pattern, the middleware chain
above the global middlewares, the endpoint function, and an access matrix
(anon, API token, super admin, and each business role) produced by running
the route's real middleware chain in front of a stub endpoint. Closure names
drop Go's "func" prefix, which flips with inlining. Guards the upcoming split
of route registration out of server.go: any route, handler, or permission
change shows up as a golden diff.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pure move: NewHandlerWithConfig now only assembles the server and returns
server.routes(). Route snapshot unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
routes.go keeps only the global middleware chain, the shared business-role
sets, and one mount call per domain: system, dashboard, acceptance, human
loop, annotation, projects, organization, workflows, runs, delivery, data
platform, and object sync. Role-only groups become withRoles/With on the
routes they guard, so each route's permission sits next to it instead of in
a role-shaped group far from the rest of its domain.

No route, handler, or access change: testdata/routes.golden (generated from
the pre-split router) is byte-identical, the Go known-failure gate passes,
and a live API smoke against a throwaway DB matched the access matrix for
every parameter-free GET route across six identities.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
In barrier/striped mode an ordinary write to a guarded collection outside
the striped set (annotationRevisions, worklog events, stage attempts, ...)
fell through to the exclusive path and took the gate plus all 32 stripes:
33 lock round-trips per write, and it stalled every striped writer in the
project. Such records never share a stripe, so take just the gate, which
every exclusive operation also takes first. Nested striped writes still take
their stripe (without re-taking the held gate in barrier mode); taking the
gate while holding a stripe, or upgrading from it, is rejected to keep the
gate-then-stripes order.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The index heartbeat cancelled the job on any TouchAnnotationIndex error, so
a Mongo failover or timeout during a long source validation aborted it and
burned one of its five attempts; five blips marked a healthy source as
failed. Cancel only when the lease is provably lost, or when renewal errors
persist until the claimed lease is within a safety margin of lapsing, so
another processor never reclaims a job that is still running. Renewal
starts from the lease the claim actually stored.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The readiness poll re-ran seekTrack on every pending target, and seekTrack
reloads errored media. A track whose error event never reached onError (it
fired before dispatch, or onError filtered it) was therefore reloaded five
times a second with no limit, e.g. a pinned source answering 409. The poll
now sends an errored track through the same bounded recovery as onError
(failTrack: at most two delayed retries per camera, then pause) and never
reloads media itself.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A revision waiting for source validation was requeued every 2s with no limit,
re-reading the task and run and recomputing the source fingerprint each time;
with no validation-role process it spun forever. Wait with exponential
backoff (2s doubling to 1m) and fail the job, edits kept, after one hour of
waiting. Waiting still does not consume a crash retry. The two new job fields
are optional and absent on existing records.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The fixed-rate check allowed only 0.1ms between each frame time and
n*duration/count, so a constant 30fps camera muxed with a 1/1000 track
timescale (frame times 0, 0.033, 0.067, ...) was rejected as variable-rate
at frame 1. Allow half a time-base tick, never less than 0.1ms: fine time
bases (all local captures: 1/10240, 1/15360) are checked exactly as before,
and a genuinely dropped frame is still rejected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first "my tasks" sidebar page was read with only project and view, while
"load more" continued from its cursor with the URL's workflow/run added. With
a workflow or run in the URL, page 1 listed every workflow and later pages
only the requested one, so other workflows' tasks past page 1 were
unreachable. Pass the same workflow/run scope to the first page; requests
without one are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
annotationReadCache handed the same *HumanItemRecord to every lookup in a
request, and write handlers mutate the item they load (version, status,
assignment, payload keys) before the versioned write. After a failed or
conflicting write, later lookups in that request would see unsaved state.
Keep the single store read per request but return a copy per lookup, with
the payload, assignment and processing-job input maps cloned.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 我的任务 count for annotators (active and 已送检 views) is the number of
items loaded so far; with more pages it read as an exact total, e.g. 500 of
800. Show "500+" while another sidebar page exists, matching the load-more
label. A true total needs a server count for this view.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The physical source-index export failed the whole delivery for any kept slice
with zero exported IMU rows, even when its certificate's sampleCount was also
0 (a short slice or an IMU gap). Compare counts only, and write a
header-only imu.csv so every kept slice keeps the same file layout. A real
count mismatch is still rejected. operator-repos copy regenerated; the
package operator image must be rebuilt for this to reach deliveries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🐛 Fix source clock validation and zero-IMU delivery
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
963b530f84
Owner

@zhanghongming 10月19日审查:固定 head=963b530f,目标 dev=03db2a28;核对完整整合树及 ad47b733 之后的增量。结论:仍有已复现的 P2 权限阻断,暂缓合并。

Standards

internal/api/rework_handling.go:50-53、69-74 仍只按当前 AssignedUserID/管理员判断 PUT 权限,且允许 query 改轮次,未限制标注角色、返工阶段、当前轮次。已在本 PR 精确快照用真实 HTTP handler + 隔离内存数据复现:当前第2轮、quality_review阶段、当前领取人为质检员,PUT 当前轮及 ?round=1 均返回200并写入 skippedOpinionIds/version=1。路由拆分没有消除该缺口。请补角色/可编辑阶段/当前轮次门禁及质检、历史轮写入拒绝测试,管理员例外须明确约束。
另有非阻断文档差异:supplier_project_stripes.go 非分区集合写入现为 gate-only,ADR0011 第11条仍写 exclusive,建议同步升级/回退契约。

Spec

ADR0007 与返工规格规定“不改了”属于标注员处理记录,复审员仅核对;上述写入违反职责边界。源索引时钟、零IMU、等待退避和租约增量检查未发现新的确定性需求阻断。不能因 PR 已部署说明而忽略权限问题。

本轮验证:TypeScript、35项相关前端测试通过;源索引/媒体时钟/等待及 Worker 定向 Go 用例通过,Mongo锁/负载用例因未启用隔离库跳过。Python交付回归23通过、7跳过(缺导出媒体fixture),不是42项真实媒体全验收。TestRouteSnapshot 本地失败:242条差异的路径/方法/角色矩阵相同,差异来自编译器闭包符号,未发现由此造成的权限路由变化;需稳定化快照比较。未宣称全套门禁通过,未部署或写客户数据。

@zhanghongming 10月19日审查:固定 head=963b530f,目标 dev=03db2a28;核对完整整合树及 ad47b733 之后的增量。结论:仍有已复现的 P2 权限阻断,暂缓合并。 ## Standards internal/api/rework_handling.go:50-53、69-74 仍只按当前 AssignedUserID/管理员判断 PUT 权限,且允许 query 改轮次,未限制标注角色、返工阶段、当前轮次。已在本 PR 精确快照用真实 HTTP handler + 隔离内存数据复现:当前第2轮、quality_review阶段、当前领取人为质检员,PUT 当前轮及 ?round=1 均返回200并写入 skippedOpinionIds/version=1。路由拆分没有消除该缺口。请补角色/可编辑阶段/当前轮次门禁及质检、历史轮写入拒绝测试,管理员例外须明确约束。 另有非阻断文档差异:supplier_project_stripes.go 非分区集合写入现为 gate-only,ADR0011 第11条仍写 exclusive,建议同步升级/回退契约。 ## Spec ADR0007 与返工规格规定“不改了”属于标注员处理记录,复审员仅核对;上述写入违反职责边界。源索引时钟、零IMU、等待退避和租约增量检查未发现新的确定性需求阻断。不能因 PR 已部署说明而忽略权限问题。 本轮验证:TypeScript、35项相关前端测试通过;源索引/媒体时钟/等待及 Worker 定向 Go 用例通过,Mongo锁/负载用例因未启用隔离库跳过。Python交付回归23通过、7跳过(缺导出媒体fixture),不是42项真实媒体全验收。TestRouteSnapshot 本地失败:242条差异的路径/方法/角色矩阵相同,差异来自编译器闭包符号,未发现由此造成的权限路由变化;需稳定化快照比较。未宣称全套门禁通过,未部署或写客户数据。
longtao.wu added 16 commits 2026-10-22 12:55:19 +08:00
🩹 Resolve October 16 annotation and rework feedback
Some checks failed
web-ci / checks (push) Waiting to run
web-ci / checks (pull_request) Has been cancelled
fde4d2737e
🐛 Seek action starts for keyboard and mouse selection
Some checks failed
web-ci / checks (push) Waiting to run
web-ci / checks (pull_request) Has been cancelled
6acb7ed790
🔒 Restrict rework handling writes to current annotation round
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
630a95c843
🛡️ Require production bundle boot checks before Fanyu releases
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
da1d2e9c7a
🐛 Preserve worker roles in dashboard statistics filters
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
d6fe5e9be3
Reviewed-on: #55
🔀 Merge PR #54: platform feedback and immutable delivery
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
525eef6384
Reviewed-on: #54
🔀 Merge PR #53: rework permissions and feedback integration
Some checks failed
web-ci / checks (push) Has been cancelled
web-ci / checks (pull_request) Has been cancelled
e5387ae5dc
Reviewed-on: #53
Owner

@zhanghongming 10月22日复核:当前 head=e5387ae5 已按依赖合入 #55→#54→#53。已用 Git tree 核对,与本轮实际测试的 d6fe5e9b 代码树完全一致,未带入 #56/#57。

Standards

上一轮 P2 rework-handling 权限阻断已由630a95c8解除,15项真实 HTTP 权限边界回归通过;角色、归属、可编辑阶段、送检锁及当前轮次限制生效,历史记录保持不变。ADR0011 gate-only 说明已同步。后续字幕、审核编辑保护、v3交付增量分别审查通过。

Spec

本轮未发现该整合树仍存在已确认的需求阻断。#56 快照失效后导出恢复、#57 小型内部审计持久化问题属于后续独立PR,不进入本次主线。

验证:TypeScript、28项相关前端、权限/统计/返工Go定向及v3/part-index Python16项通过;官方前端基线门禁通过,13个既有失败无新增。官方Go门禁仍因 TestRouteSnapshot 未通过;检查原始差异242删/242增,方法/路径/全部角色响应完全相同,仅编译器闭包符号变化,与此前本机已核查现象一致,不作为产品权限回归,但不能声称全套Go门禁全绿,快照可移植性仍应修正。未修改失败基线。
结论:此前功能阻断已闭环,可按用户授权合入dev。合并不等于线上验收,不执行部署、回滚、工作流激活或客户数据写入。

@zhanghongming 10月22日复核:当前 head=e5387ae5 已按依赖合入 #55→#54→#53。已用 Git tree 核对,与本轮实际测试的 d6fe5e9b 代码树完全一致,未带入 #56/#57。 ## Standards 上一轮 P2 rework-handling 权限阻断已由630a95c8解除,15项真实 HTTP 权限边界回归通过;角色、归属、可编辑阶段、送检锁及当前轮次限制生效,历史记录保持不变。ADR0011 gate-only 说明已同步。后续字幕、审核编辑保护、v3交付增量分别审查通过。 ## Spec 本轮未发现该整合树仍存在已确认的需求阻断。#56 快照失效后导出恢复、#57 小型内部审计持久化问题属于后续独立PR,不进入本次主线。 验证:TypeScript、28项相关前端、权限/统计/返工Go定向及v3/part-index Python16项通过;官方前端基线门禁通过,13个既有失败无新增。官方Go门禁仍因 TestRouteSnapshot 未通过;检查原始差异242删/242增,方法/路径/全部角色响应完全相同,仅编译器闭包符号变化,与此前本机已核查现象一致,不作为产品权限回归,但不能声称全套Go门禁全绿,快照可移植性仍应修正。未修改失败基线。 结论:此前功能阻断已闭环,可按用户授权合入dev。合并不等于线上验收,不执行部署、回滚、工作流激活或客户数据写入。
longtao.wu merged commit 1aad402905 into dev 2026-10-22 12:57:15 +08:00
Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: longtao.wu/droboticflow#52
No description provided.