forked from longtao.wu/droboticflow
📝 Record supplier priority local handoff
This commit is contained in:
parent
433a3b6a63
commit
ac1eddccbd
@ -6,7 +6,7 @@ Goal: finish an exiting supplier's existing acceptance work for settlement; supp
|
||||
|
||||
Owned files: new acceptance_priority domain/store/API files and tests; Store interface/MemoryStore field; human loop routes/review continuation; review-claim-candidates helper/human-loop service; Users admin insertion and new SupplierAcceptancePriorityPanel. Existing AGENTS/docs/admin pool test edits are unrelated, preserved and excluded from staging/check selection.
|
||||
|
||||
Status: local implementation and scoped verification complete; awaiting local commit/handoff. Source supplier resolution is request-local through SourceBatchID and source human items/task ownership; missing/conflicting evidence stays unknown, visible only as admin “归属待核对” count. No customer record backfill. New collection acceptancePriorities is created only when an administrator first saves locally/after approved deployment. No startup migration/index build.
|
||||
Status: local implementation complete and committed as 433a3b6a; scoped verification passed; ready for decision gate 2. No push/deployment authorization exercised. Source supplier resolution is request-local through SourceBatchID and source human items/task ownership; missing/conflicting evidence stays unknown, visible only as admin “归属待核对” count. No customer record backfill. New collection acceptancePriorities is created only when an administrator first saves locally/after approved deployment. No startup migration/index build.
|
||||
|
||||
Implemented: immutable versioned per-supplier configuration in acceptancePriorities; admin-only read/write routes and supplier account-management panel; request-local batch source ownership resolution through identity-only bulk queries; priority-before-normal admission in random/continuous paths; existing own-task precedence, permission checks, final store CAS and totals preserved. Unknown/conflicting source ownership is shown only in the admin unresolved count. No startup migrations or task backfill. Candidate-only metadata read mode avoids annotation hydration and serializes an explicit anonymous whitelist. Source lookup failure does not silently fall back to ordinary admission.
|
||||
|
||||
@ -20,3 +20,5 @@ Verification:
|
||||
- Earlier development failures are retained in temporary diagnostic logs; corrected MemoryStore private-field cloning and browser fixture routing/auth/reload assumptions. UI startup imports an existing synthetic legacy task once, so browser count assertions compare with the live fixture API rather than assume a fixed backlog size. The separate API before/after count equality and exact source ownership/count assertions remain in place.
|
||||
|
||||
Compatibility/activation: see docs/acceptance-supplier-priority.md. Production activation and business acceptance remain gate 2/explicit deployment authorization. Production supplier/project/expiry selection is not yet made; no production policy was created. No pushes, PRs, cluster/BOS writes, or customer-data writes. Production-size latency/capacity and full release gates have not been claimed.
|
||||
|
||||
Local handoff: implementation commit 433a3b6a. Pre-commit TypeScript/architecture/Go formatting checks passed. Existing protected user edits remain outside the task commit. Remote dev has not been changed by this task. Release preparation must first synchronize the authorized release tip and use the documented release process; deployment authorization is not inferred from decision gate 1.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user