docs: record September 17 optional field reanalysis

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

@@ -38,7 +38,7 @@
 
 ## Follow-ups
 
-- The user explicitly deferred API/XML population alignment. That issue remains separate and must not block fixing normal optional omission or be represented as resolved by this change. The user has now explicitly approved cancellation exclusion, so300007418 no longer requires a room.10/7 awaits only two existing manual-price keys (LIAN TAI/WHO1/Opera0 and QBD/GRPA3/Opera0); each affects one record/three nights. Do not choose a price, equate an Oracle0 with the processed price, or claim final daily/monthly acceptance. Source population/text alignment remains separately deferred.9/17 has received saved-status evidence but its old optional-source gaps were not reinterpreted this turn;30 active source decisions remain.
+- The user explicitly deferred API/XML population alignment. That issue remains separate and must not block fixing normal optional omission or be represented as resolved by this change. The user has now explicitly approved cancellation exclusion, so300007418 no longer requires a room.10/7 awaits only two existing manual-price keys (LIAN TAI/WHO1/Opera0 and QBD/GRPA3/Opera0); each affects one record/three nights. Do not choose a price, equate an Oracle0 with the processed price, or claim final daily/monthly acceptance. Source population/text alignment remains separately deferred.9/17 now has saved-status evidence and the corroborated optional-source interpretation:0 active field decisions, editing revision3, ready for explicit continuation. It has not been processed or finalized; subsequent existing price review may still apply.
 - Integration owner should promote the accepted behavior and production compatibility evidence, then integrate this branch into the primary project. Keep this checkout while the local service runs from it. It is manually created, not eligible for automatic skill-managed retirement.
 - Production deployment/configuration and remote publishing are separate follow-ups. This turn only activated the local instance against the existing production read service.
 
@@ -189,3 +189,13 @@ Read: memory-index, project-positioning, current-state latest September sections
 - Actual9/17 maintenance result:18 raw cancellations excluded from review; active decisions38→30, original unchanged, revision2. Its prior optional source omissions remain a separate pending follow-up, and this date was not submitted/processed or refetched.
 - Private evidence: cold backup `/Users/chillishark/Library/Application Support/ARR2.0/policy43-service-backup-20261008-121313`; live `policy43-upgrade-intent.json`, `policy43-upgrade-completed.json`, `policy43-activation.json`; dry run `production-validation-20261007/policy43-dryrun-da8e24ea`; private executable `upgrade_cancelled_scope.py`. Browser screenshots `cancelled-scope-no-room-review-20261008.png` and `cancelled-scope-price-review-20261008.png`. The authenticated result tab is retained. No credential/environment/grant change, Oracle business read, production deployment, remote push or primary-checkout integration occurred.
 - Promotion candidate: update canonical source-selection/business-rules/current-state with user-approved cancellation exclusion and processor4.3/020 requirements, retaining the deferred broad population alignment. Human confirmation for the cancellation policy is satisfied by this conversation; integration ownership is still required for canonical writes.
+
+## Same-task Follow-up: September17 Optional-field Prompts
+
+- User asks what filling the verified team code means for9/17. Concurrent gate resumed the same task/feature/codex/owned checkout with no peers; retained project context applies. Planning gate Passed. Authenticated read-only review is revision2/editing,30 unresolved items:25 optional BLOCK_CODE and5 optional PRODUCTS;18 cancellations already excluded and no saved staff decisions. Original XML rules permit these optional associations to be empty.
+- The prior10/7 optional-association interpretation was not applied to this older9/17 capture. Plan: replay the complete immutable9/17 responses offline under the already accepted narrow omission policy; prove that only corroborated missing block/package observations become explicit empty and all original bytes/fields/context/order remain unchanged; dry-run on a private review copy and append the validated interpretation to the live editing review with revision protection. Do not query Oracle, change rule identity, overwrite staff decisions, finalize9/17 or alter the pending10/7 price review. Keep any genuinely unresolved association evidence for staff.
+- Outcome: all25 BLOCK_CODE and5 PRODUCTS active review items are corroborated normal empty associations, not newly mandatory fields or failed interface reads. Replayed all320 recorded attempts for106 source rows:319 successful HTTP responses and1 original transport failure followed by its recorded successful retry. Initial rehearsal did not handle that failure-only metadata and stopped without live changes; the corrected offline transport faithfully replays it as ConnectionError with no wait/network. Across the complete source48 block observations and11 package observations become empty; strict whole-object projection permits no other field/context/order/source change. Newly collected statuses were checked against all106 existing saved-status evidence entries, then omitted from the optional-only projection where absent in the original source; the independent status overlay remains unchanged.
+- Verification: checked every byte length/SHA/file-set entry of both immutable original and replay captures (original962 files), strict optional-only projection, copied-review rehearsal, idempotent replay, unchanged manual decisions and status receipt, and independent read-only agent audit of all59 changed associations directly from the successful saved search/detail responses. Current Packages fetchInstructions and search/detail status/version agreement are established. No core code change or new unit-test run was needed for this previously tested internal maintenance operation.
+- Local activation: backed up only the editing9/17 review, then used the existing internal append-only reanalysis operation with expected revision2. Authenticated API now reports editing revision3/pending0/total0/can_finalize=true,18 cancellations excluded, no job and no finalize intent. Original data SHA remains `b9e115470f3ce4d1a31fde03308c18f0854c9daef5a8beb71d8ca5b997cdc831`; original manifest SHA remains `8efb54d2737d15d837295ffa7f5e5bd1ff0d467d89fb1e956de6b1055a8c076f`.10/7 remains finalized source revision4 and its existing price-review job, unchanged. No Oracle call, service restart, policy-pin change, Finance write, real daily/monthly generation, remote push or primary-checkout edit.
+- UI verification: preserved the original10/7 price panel and opened a separate local result tab. The pending-date button was initially disabled after restoration; choosing9/17 refreshed its enabled state, then opening the existing pending task made no new download. Page visibly shows9/17,0/0 confirmed,18 excluded cancellations, “没有待完善字段”, and an enabled “确认并生成日报”. Did not click generation. Both result and existing price tabs are retained. Private screenshot: `/Users/chillishark/Library/Application Support/ARR2.0/production-validation-20261007/sept17-optional-review-cleared-20261008.png`.
+- Private audit: `production-validation-20261007/sept17-optional-reanalysis-dccb6cbb03c4/{receipt,activation}.json`; replay manifest `7e4ec018d8898864c4fabacc4e2fba8be8e917704b95bc4e6fc7467d8c635783`; optional-only projected data `8afddb5d08bbc0c8814c1036db6b0be91aa45cb25676bc25731e642b8581ad9f`; pre-append backup `ohip-production-57106-20261008/sept17-source-reanalysis-backup-20261008-123341`. Raw guest data stays outside Git. Promotion candidate: explain old pending captures require explicit source-policy interpretation rather than blanket staff confirmation; retain current optional/required distinction. Broader report-scope alignment remains deferred.