Allow independent dates while ARR field reviews are pending

.project-docs/30-worklog/tasks/20261008-production-review-9e7b.md

@@ -74,3 +74,14 @@ Read: memory-index, project-positioning, current-state latest September sections
 2. Durable revisioned field review before handoff; required candidate gaps only; immutable derived source and audit; same-request continuation.
 3. Authenticated review UI and context-scoped recovery.
 4. Synthetic regression and saved real 10/7 validation; activate local service safely and leave actual unresolved business values for user.
+
+## Same-task Follow-up: Independent Report Dates
+
+- User asks whether unfinished10/7 prevents downloading9/17. Desired behavior: each report date retains its own pending field review; staff may start another date and return to earlier pending dates.
+- Concurrent gate resumed the same task/worktree successfully; registry confirms feature/planning/codex and no other owners. Existing project context above remains applicable; September restrictions are superseded only by later explicit authorization. This fix needs no new real Oracle query or business rule change.
+- Planning gate Passed: current backend already deduplicates by date, not globally. The frontend unconditionally redirects any new submission to the current field review. The service exposes only the latest task, so earlier pending field reviews also need a persistent return entry.
+- Plan: allow explicit submissions for a different selected date, expose pending field-review dates, retain per-date review/draft identity, test independent-day queues and UI switching, then refresh the local page without confirming actual business values.
+- Outcome: another selected date now starts its own download; selecting the current review date still opens its existing review without reacquisition. A server-backed pending-date list allows return to all earlier source reviews, including after reload and after another day's task finishes. Same-day deduplication remains unchanged. In-page unsaved drafts are isolated by request and cleared on source-context change; the documentation tells users to save before refreshing. Uncertain/active requests cannot be abandoned through the pending-date entry.
+- Verification:74 Python tests passed without skips (40 backend/config/local-wrapper tests and34 existing source-review/runtime tests, disposable local PostgreSQL enabled),31 JavaScript tests passed, node syntax and Git whitespace checks passed. Tests cover two pending days, same-day deduplication, queue restart, server list restoration, per-request drafts, lost new submission and reopening a completed review.
+- Local activation: gracefully restarted the existing private local service only after verifying zero active queued/downloading/processing tasks. No actual business value was changed and no new Oracle request was made. CUA verified choosing9/17 enables “下载并处理” while10/7 still shows0/26; the pending-date entry returns to10/7 unchanged. The page is left with9/17 selected for the user's explicit submission. Screenshot: private `production-validation-20261007/independent-report-dates-20261008.png`.
+- Promotion candidate: document independent report-date progress and the persistent pending-field-review entry in canonical product flow at integration. This preserves existing business rules and user-approved date interaction; no policy reversal is involved.