feat: 返工与复审工作流 + 自动保存(A/B 块全量) #44

Closed
zhanghongming wants to merge 0 commits from feature/bigupdate-1 into dev
Collaborator

Summary

A 块 自动保存                     B 块 返工与复审
├─ A01 标注工作台 20s/换片/隐藏    ├─ B01 时间点意见闭环(F 菜单/G 键/规范帧唯一)
├─ A02 审查草稿 8s 空闲           │      + 定向归还 & FANYU_REWORK_RETURN 回退开关
├─ A03 崩溃兜底(裁定 wontfix)    ├─ B02 退回基线冻结 + 处理反馈 + D7 确认冻结
└─ A04 统一验证(50 人压测)       ├─ B03 融合返工(返工优先领取/上下对比/D2 拆段)
                                  ├─ B04 终审批次复验(来源投影/待完成点名)
                                  ├─ B05 终验 + 中文手册 + 兼容证据
                                  └─ B06 评估(保留/媒体复用/容量 → spec §11)

关键行为变更(有意):质检退回定向归还原标注员(回退开关 FANYU_REWORK_RETURN=pool 恢复公共池);时间点意见/核对结论编辑需新前端(旧后端拒收防静默丢失)。

Evidence

  • Before: 退回任务回公共池随机领取;审查意见仅整体/切片/动作三档;无退回基线;复审无正式核对判定。
    After: 五角色复现栈全链路演示(退回→反馈→再提交→复审核对→通过,D7 确认冻结进 Review 记录);时间点 60.05s 存取/排他末帧拒绝/汇总带点位标签;50 人压测 350/350 PUT 全 200(p50 65ms/p99 1.1s/零慢查询)。
  • 回归:internal/api 65=基线 65、前端 14=基线 14(逐名一致零新增);tsc/生产构建绿;场景矩阵 13/13 @1413×615。
  • code-review 双轴已完成并整改(3 真缺陷修复:返工优先窗口/跨来源轴混排/弱校验;记录见 .scratch B05 票面)。
  • 手册:docs/rework-review-manual.zh-CN.md。

Merge Danger

Door: two-way

回退=回滚旧镜像(无迁移/无配置变更/新增字段全 optional,兼容性结论见 B05 Answer §4);行为开关可现场切回公共池。

Blast Radius: 标注/质检/终审三角色工作台与领取路由

返工定向归还改变领取分布(开关可回退);旧镜像可继续读写既有数据;时间点意见编辑需新前端。

## Summary ```text A 块 自动保存 B 块 返工与复审 ├─ A01 标注工作台 20s/换片/隐藏 ├─ B01 时间点意见闭环(F 菜单/G 键/规范帧唯一) ├─ A02 审查草稿 8s 空闲 │ + 定向归还 & FANYU_REWORK_RETURN 回退开关 ├─ A03 崩溃兜底(裁定 wontfix) ├─ B02 退回基线冻结 + 处理反馈 + D7 确认冻结 └─ A04 统一验证(50 人压测) ├─ B03 融合返工(返工优先领取/上下对比/D2 拆段) ├─ B04 终审批次复验(来源投影/待完成点名) ├─ B05 终验 + 中文手册 + 兼容证据 └─ B06 评估(保留/媒体复用/容量 → spec §11) ``` 关键行为变更(有意):质检退回**定向归还原标注员**(回退开关 `FANYU_REWORK_RETURN=pool` 恢复公共池);时间点意见/核对结论编辑需新前端(旧后端拒收防静默丢失)。 ## Evidence - **Before:** 退回任务回公共池随机领取;审查意见仅整体/切片/动作三档;无退回基线;复审无正式核对判定。 **After:** 五角色复现栈全链路演示(退回→反馈→再提交→复审核对→通过,D7 确认冻结进 Review 记录);时间点 60.05s 存取/排他末帧拒绝/汇总带点位标签;50 人压测 350/350 PUT 全 200(p50 65ms/p99 1.1s/零慢查询)。 - 回归:internal/api 65=基线 65、前端 14=基线 14(逐名一致零新增);tsc/生产构建绿;场景矩阵 13/13 @1413×615。 - code-review 双轴已完成并整改(3 真缺陷修复:返工优先窗口/跨来源轴混排/弱校验;记录见 .scratch B05 票面)。 - 手册:docs/rework-review-manual.zh-CN.md。 ## Merge Danger **Door:** two-way 回退=回滚旧镜像(无迁移/无配置变更/新增字段全 optional,兼容性结论见 B05 Answer §4);行为开关可现场切回公共池。 **Blast Radius:** 标注/质检/终审三角色工作台与领取路由 返工定向归还改变领取分布(开关可回退);旧镜像可继续读写既有数据;时间点意见编辑需新前端。
zhanghongming added 34 commits 2026-10-13 08:52:56 +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
zhanghongming added 1 commit 2026-10-13 09:18:32 +08:00
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.
zhanghongming added 3 commits 2026-10-13 10:10:06 +08:00
- 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
Owner

@zhanghongming 审查基线:dev=03db2a28,PR head=21127800。结论:发现阻断问题,暂缓合入 dev。

Standards

  1. [P1] 自动保存未隔离任务/用户会话。src/hooks/useAnnotationAutosave.ts:98-109 在请求返回后直接调用旧 onApplied;src/pages/AnnotationOperations.tsx:2493-2507 只比较版本号,就把返回的 humanItem 和基线写到当前任务。A 自动保存未完成时确认切换到 B,A 的版本不低于 B 即可污染 B 的上下文;409 回读分支也缺同类隔离。请让成功、冲突、重同步、错误及 finally 都受 task/user generation 或已有 mutation context 保护。
  2. [P2] 旧物化目录清理会饿死后续任务。internal/worker/materialization_cleanup.go:113-134 每个有效 task/run 都消耗 cleaned 预算,包括没有旧目录、已经清过的任务;每轮固定从头扫,前三个任务可永久占满预算。请加入跨轮游标/公平推进,并补充多任务、多状态及多组织回归。

Spec

P1 同时违反自动保存规格 D2 的“不静默覆盖”和返工规格 §8 对“迟到响应”的验证要求。已用本 PR 实际 hook 加最小隔离 harness 复现:延迟 A 响应,在 B 上下文接收后得到 {task:B,humanItem:item-A};并非仅凭推测报告。

验证边界:后续整合候选的 TypeScript、25 项相关前端测试及 API/store/worker 定向测试通过,但现有测试没有覆盖上述切任务竞态。本次没有部署或修改客户数据。两项问题仍存在于 #45,不能通过合并后续 PR 绕过。

@zhanghongming 审查基线:dev=03db2a28,PR head=21127800。结论:发现阻断问题,暂缓合入 dev。 ## Standards 1. [P1] 自动保存未隔离任务/用户会话。src/hooks/useAnnotationAutosave.ts:98-109 在请求返回后直接调用旧 onApplied;src/pages/AnnotationOperations.tsx:2493-2507 只比较版本号,就把返回的 humanItem 和基线写到当前任务。A 自动保存未完成时确认切换到 B,A 的版本不低于 B 即可污染 B 的上下文;409 回读分支也缺同类隔离。请让成功、冲突、重同步、错误及 finally 都受 task/user generation 或已有 mutation context 保护。 2. [P2] 旧物化目录清理会饿死后续任务。internal/worker/materialization_cleanup.go:113-134 每个有效 task/run 都消耗 cleaned 预算,包括没有旧目录、已经清过的任务;每轮固定从头扫,前三个任务可永久占满预算。请加入跨轮游标/公平推进,并补充多任务、多状态及多组织回归。 ## Spec P1 同时违反自动保存规格 D2 的“不静默覆盖”和返工规格 §8 对“迟到响应”的验证要求。已用本 PR 实际 hook 加最小隔离 harness 复现:延迟 A 响应,在 B 上下文接收后得到 {task:B,humanItem:item-A};并非仅凭推测报告。 验证边界:后续整合候选的 TypeScript、25 项相关前端测试及 API/store/worker 定向测试通过,但现有测试没有覆盖上述切任务竞态。本次没有部署或修改客户数据。两项问题仍存在于 #45,不能通过合并后续 PR 绕过。
Owner

@zhanghongming 本轮再次检查:当前 head 仍为 21127800,dev 为 03db2a28;上一轮评论后没有新增修复提交或回复。仍暂缓合并。

请先修复已报告的两项问题:

  • P1 自动保存跨任务迟到响应:在成功、409 回读、错误和在途状态收尾前校验 task/user generation。回归应延迟 A 的响应后切换 B,并验证 B 的任务身份、编辑基线与保存提示保持不变。该问题上一轮已离线复现。
  • P2 物化清理推进:不能让每轮固定前三个 task/run(包括无旧目录或已清理任务)永久消耗全部预算。增加游标或公平轮转,验证多任务、多状态、多组织都能最终被扫描和清理。

这两项也被 #45 继承,需同步到后续功能分支。Git 显示可合并仅说明没有文本冲突,不代表问题已修复。本次无代码增量,未重复运行上一轮测试,也未合入 dev 或部署。

@zhanghongming 本轮再次检查:当前 head 仍为 21127800,dev 为 03db2a28;上一轮评论后没有新增修复提交或回复。仍暂缓合并。 请先修复已报告的两项问题: - P1 自动保存跨任务迟到响应:在成功、409 回读、错误和在途状态收尾前校验 task/user generation。回归应延迟 A 的响应后切换 B,并验证 B 的任务身份、编辑基线与保存提示保持不变。该问题上一轮已离线复现。 - P2 物化清理推进:不能让每轮固定前三个 task/run(包括无旧目录或已清理任务)永久消耗全部预算。增加游标或公平轮转,验证多任务、多状态、多组织都能最终被扫描和清理。 这两项也被 #45 继承,需同步到后续功能分支。Git 显示可合并仅说明没有文本冲突,不代表问题已修复。本次无代码增量,未重复运行上一轮测试,也未合入 dev 或部署。
Owner

@zhanghongming 10月17日复核:本 PR head 仍为21127800,原阻断修复未回到此分支,因此不单独合入 dev。新的整合 PR #49 已包含本 PR,并保留自动保存会话隔离及物化清理公平推进修复;这两项在整合版本的代码层已确认。#49 仍有返工处理状态写权限问题,已用真实 HTTP handler 隔离复现并评论(#49 / issuecomment-24040)。#50 已合入 #49 的功能分支,合并提交10b0dddd。后续建议在整合分支补齐权限修复后统一重审,不通过先合旧 PR 绕过阻断。本次保留本 PR 开放,不自动关闭或合并。

@zhanghongming 10月17日复核:本 PR head 仍为21127800,原阻断修复未回到此分支,因此不单独合入 dev。新的整合 PR #49 已包含本 PR,并保留自动保存会话隔离及物化清理公平推进修复;这两项在整合版本的代码层已确认。#49 仍有返工处理状态写权限问题,已用真实 HTTP handler 隔离复现并评论(#49 / issuecomment-24040)。#50 已合入 #49 的功能分支,合并提交10b0dddd。后续建议在整合分支补齐权限修复后统一重审,不通过先合旧 PR 绕过阻断。本次保留本 PR 开放,不自动关闭或合并。
Owner

@zhanghongming 本 PR 的21127800已是 dev=1aad4029 的祖先,全部功能及后续修复已通过 #52 整合进入主线。原自动保存跨任务响应和清理公平性问题在整合版本中已修正,返工处理权限也由 #53 补齐并通过本轮15场景回归。此PR按“已由 #52 覆盖”关闭,不重复合并旧状态,源分支保留。本次只完成代码整合与PR收尾,不表示新增上线或完整生产验收。

@zhanghongming 本 PR 的21127800已是 dev=1aad4029 的祖先,全部功能及后续修复已通过 #52 整合进入主线。原自动保存跨任务响应和清理公平性问题在整合版本中已修正,返工处理权限也由 #53 补齐并通过本轮15场景回归。此PR按“已由 #52 覆盖”关闭,不重复合并旧状态,源分支保留。本次只完成代码整合与PR收尾,不表示新增上线或完整生产验收。
longtao.wu closed this pull request 2026-10-22 13:01:54 +08:00

Pull request closed

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#44
No description provided.