droboticflow/docs/verification/owned-source-exceptions-20261102.md

3.2 KiB

Owned source-validation exceptions

Base: codex/review-focus-layout-stability@a9f24732, continuing the unified local worktree. No release or production mutation.

Behavior

Owned work-buffer responses now include server-computed sourceValidationStatus in both full and summary formats. Automatic continuation skips failed, pending and unverified sources. Explicit selection remains available for inspecting the task and its existing source-error/recovery panel. The selector and recovery list label failed sources “源数据异常”; a buffer containing failed sources and no runnable task reports “源数据异常,待管理员处理。”

Ownership, drafts, versions, ledger slots and occupied capacity are retained. No automatic unassignment or return to the public pool occurs. Source repair remains an explicit administrator revalidation action; successful validation clears the live buffer status on its next read. This is presentation/continuation recovery for already-owned exceptions, not a source-file repair or historical migration.

Read and compatibility scope

Reuse the existing request-local admission batch reads (task identity/validation fields and index-job status by indexed ID). Each nonempty buffer adds two projected batch reads, not a full payload read per item. Summary projections retain source fingerprints and source-index flags internally; the response adds only a small status field. No additional polling interval, permission cache, media fetch, source rewrite or ledger write is introduced. Existing claim result equivalence is regression-tested, including legacy records. Older clients ignore the added field; older servers retain existing client fallback behavior.

Evidence

  • API recovery regression: full and summary buffer status transitions failed → pending → valid; task remains owned with unchanged version/content and occupied count.
  • Targeted buffer/API and source-admission tests pass.
  • Local Mongo: claim fence, batch-versus-legacy result equivalence, projected-buffer admission equivalence and stable read-only ledger polling pass.
  • Frontend buffer summary/reconciliation: 15 tests pass, including exclusion from automatic selection and preservation of legacy response status.
  • Browser replica: annotator source-error responsibility/refresh; owned work-page selector and explicit inspection; administrator confirmation, actual validator success and recovery; existing generation-recovery scenario. Four cases pass, no page errors, no annotation writes. First new work-page assertion stopped at the existing inactive-session gate; the test now explicitly opens the owned task before asserting the error panel.
  • Type/architecture check, formatting check and web build pass (existing large-chunk warning).
  • Inspected screenshot: local-data/test-results/source-validation-browser/owned-source-failed.png; normal/recovered and administrator states are captured by the same browser suite. Private logs: local-data/diagnostics/source-reclaim/.

No 120-person capacity test or production write test was run. The two additional small batch reads per buffer poll have not been capacity-accepted in production. Production exceptions remain untouched; deployment and any targeted reassignment/recovery require their separate approvals.