Combine report field and price checks into one review workspace

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

@@ -289,3 +289,13 @@ Read: memory-index, project-positioning, current-state latest September sections
 - Confirmed actual acquisition, not a demonstrated frozen page: authenticated local API and read-only queue show new9/15 request6430210d593fc4754dcb8bc292d6c6e3 downloading, started2026-10-08T14:55:58Z. Saved search has85 reservations and hasMore=false. Capture responses advanced from135 at15:01:21Z to157 at15:02:20Z to175 at15:03:04Z; at15:03:06Z completed58 reservation details,58 rate queries and58 profile reads plus initial search, all175 upstream200, no transport failures. Median response2.17s and latest20 mean2.43s; collection is sequential with final source recheck, explaining minutes of sustained download. No source result/final handoff yet. Queue updated_at records the phase start rather than a progress heartbeat, so its unchanged value is not evidence of a stall.
 - Read-only frontend audit: successful task GET returning downloading correctly preserves that message. A separate unresolved-fetch weakness can hold loading forever (no API timeout); agent reproduced it with an isolated memory-only harness, but it is not the demonstrated cause here because saved acquisition is actively advancing. Record as a future resilience candidate, not a fix claim. Chrome computer-control surface is unavailable, so no claim of directly inspecting the user's Chrome page or its network requests. Backend acquisition evidence is independent of browser.
 - Outcome/boundaries: explain85 reservations and sequential supplemental reads, with observed progress rather than claiming success or exact completion time. Existing active task left running without restart, retry, new Oracle request initiated by this investigation, cancellation, price/report mutation or code changes. No automated follow-up scheduled. No regression suite needed for a read-only investigation; project-document boundary/structure and whitespace checks apply. Promotion candidate for integration-owned product follow-up: expose completed/total acquisition progress and bound local status-query waits; no business-rule change or new authorization is implied.
+
+## Same-task Follow-up: Unified Manual Check Layout
+
+- User requests moving pending dates below the former field-completion heading, renaming that date area “需处理日期”, and combining field completion/price review under “人工核对”. Concurrent Task Gate Passed for same task/feature/codex/owned checkout/branch/base, no peers and no unknown edits. Project Context Loaded: retained required project memory, ADR004/006/007, architecture/domain/evidence/reflection/commitments/stale context; refreshed active task and planning entry/gate. Goal: one date selector area and one manual-check workspace while preserving independent date requests and original field/price rules. Modules: static index/styles/app/i18n and existing JS/UI checks. Constraints: no Oracle acquisition or business value changes, no resets/finalization of real tasks, preserve source drafts and unsaved-price safeguards. Design skill loaded; preserve the existing design, adapting only grouping/labels, responsive spacing and focus. Planning Gate Passed.
+- Plan: remove pending-date controls from the download card and create a dedicated “需处理日期” section preceding a shared “人工核对” workspace. Retain field and price content as distinct conditional bodies inside that workspace with explicit subtype guidance, one visible parent heading, existing controls/API/IDs and audited state. Validate source↔price switching, existing guards and empty/terminal states, then verify actual local page and screenshot without entering real prices or confirming generation. Static assets can activate without restarting a service or disturbing active acquisition.
+- Outcome: independent “需处理日期” card now occupies the former field-review position below the overview. One “人工核对” parent contains mutually exclusive field-completion and price-review bodies, with current date/type guidance and one visible primary heading. Existing field/price IDs, save/confirm/cancel/pagination and audited endpoints remain. Opening either kind scrolls to the unified heading; cached field→history price→same field correctly restores the field body. Context switches clear the shared mode and cached price display, and late price reads cannot repopulate the old context. No source/pricing/Finance business rule or input value changed.
+- Verification:74 related JavaScript cases passed, including4 new shared-workspace cases and strengthened existing cross-month assertions; independent read-only audit reran47 field/review JS cases and found no new blocker.12 existing static UI cases passed, including a new hierarchy check proving the dates sit outside the download form/conditional bodies and both review bodies share the parent. Final root rerun of those12 passed after the CSS correction; node syntax, whitespace and documentation gates passed. Meaningful state checks cover history entry, cached return, terminal hiding while other dates remain, source-context recovery and unsaved0 protection. Existing same-page price redraw/language-change draft limitations are not claimed resolved by this layout change.
+- Actual local UI: reloaded only the independent verification tab, then selected9/17 fields→history9/16 prices→same cached9/17 fields→9/15 fields→9/16 prices. At each step the date/type matched and only one review body was visible.9/15 retains its1 missing-room item,9/16 retains its one blank price key0/1,9/17 retains0 active field items; no save, cancellation or generation was triggered. All3 complete review objects match the pre-layout authenticated baseline exactly. Private before/after JSON evidence and screenshots are in `production-validation-20261007/unified-manual-check-{before,after}-20261008.json` and `unified-manual-check-layout-20261008.png`; raw material stays outside Git.
+- Responsive result: observed CSS widths375/767/1024/1440 verified. Initial767 check found7px page overflow from the absolute screen-reader label inside the price table; setting the new parent to position:relative bounds that label, and final375/767 checks now have scrollWidth equal clientWidth. Wide tables retain their existing contained scrolling. Temporary viewport overrides were reset. The preserved visual palette/typography was preferred over the design search's unrelated liquid-glass/marketing recommendations. Existing user tabs were not reloaded; result tab retained. Static changes are served by the running8875 instance, without a service restart, new acquisition, hotel write, real review mutation, report generation or remote push.
+- Promotion candidate: integration-owned product/data-flow docs should describe independent “需处理日期” navigation followed by a single “人工核对” workspace, keeping source completeness and price decisions as distinct business stages. No conflict with ADR006/007 or additional business-policy confirmation. Remaining action for users is refreshing an existing page to load the new layout, then continuing original pending tasks.