[aryanorastar]

Customer failure and change

An official page can be cited correctly while its guidance is outdated or inapplicable. Preserve reliable publisher dates and explicit scope through the existing ingestion → parent-page storage → chunks → ranking → answer/review pipeline. Prefer newer dates only within equivalent authority/topic/scope/relevance slots; keep complementary facts, stronger matches, unknown dates and safety details. Fetch time is never a publisher date. No extra model stage or increased page/evidence budget.

Final integration and decision

Merged current main a461f86 (#91) into this branch with a merge commit. Retain both SOURCE_DATE_POLICY and #91's transient first-filter audit/reviewer/single-second-look boundaries. Provenance/ranking/schema code matches the previously reviewed implementation; no new prompt repair was added during integration.

The adopted relative gate requires no candidate-only material final-answer failure, no protected-handoff regression and no lower pass count. Aryan’s specific #90 disposition additionally permits independently reviewed integration when a finding is shared or clearly unrelated to provenance/date behavior; the observed staff-claim acceptance gap is now blocked on both current main and integrated #90. Frozen original results remain 21/24 candidate vs 19/24 old main, not a newly measured integrated score:

Frozen candidate failure	Old-main final counterpart	Decision
No-loss assurance q06-r1-B	Custody assurance q03-r1-B	Same broader retention/no-loss family; not an identical same-scenario guarantee
Unsupported cloud/UI state q06-r2-A	q06-r1-A	Same family
Completed staff flag q07-r2-A	Absent from all24 old-main finals	Candidate-only wording in this sample; identical undated evidence, no date-order mechanism established

Fresh offline injection of that exact unsafe review through both normal and compact paths shows old main/frozen #90 accept it, while current main/integrated #90 remove/audit it, invalidate approval and invoke the existing second look. Repeated unsafe responses remain rejected/escalated. Independent review identifies a pre-existing acceptance gap now blocked for the observed defect and recommends merge after final gates. This is not proof that the extra policy had no stochastic influence or a regenerated quality measurement. Shared custody/state/applicability weaknesses remain #83.

The conditional max96-request run is not activated; zero paid requests during this integration. Original grades and outputs remain unchanged.

Verification

• Full 1,258/1,258, no-model 8/8, progress guards 4/4.
• Independent integration review: 240 focused checks, provenance/source identity, Preserve safe context through answer review #91 audit/handler/selection parity, schema and normal/compact saved-response replay PASS. Final corrected docs/head review PASS at ca59fe0.
• Exact-head Node20/24 and real PostgreSQL CI run 40712936315 PASS. The first integration docs head failed a plan guard because an explicit memory-enablement condition was omitted; the condition was restored and current checks pass. No failed check was waived.
• Existing real persistence/search/evidence round trip, undated-refresh clearing, additive/idempotent migration, six parallel page-fetch cap/10-second timeout/eight-chunk/9000-character bounds remain exercised.
• Prior synthetic generated path excludes live docs/full gateway/staff delivery and is not whole-product accuracy. No customer/protected inputs or optional enablement.

Release status

#91 merged a461f86; its rollout c42efc65 passed startup/how-to but failed source applicability in the broken-device smoke: Limitless-only guidance for unidentified hardware. Context/private delivery passed. The approved rollback is verified healthy at a9c9508 / a6ef6b22. Third smoke and further deployment are held; #90 was absent from the failed image and is not deployed. Its provenance foundation does not itself resolve source applicability. Continue #83 offline with general red-before tests and independent review before another rollout; no new paid run without permission.

Master/architecture/roadmap/runbook reflect the rollback and hold. Implementation64/100, delivery56/100 and full acceptance2/21 remain unchanged. #83/#62/#65 remain open. This merge does not grant a deployment, customer resolution, memory/context/fix-inbox enablement or branch deletion.

[aryanorastar]

Scoped code re-review PASS at42619cfc9b3140e1ccd016fb71ba7693948b101c. The independent P2 generic-heading collision was reproduced before repair. Ranking now requires the same article title AND section, explicit scope, comparable date kind and equivalent relevance/corroboration; dates cannot displace a stronger match, unrelated article or broader query support. Independent69/69 affected checks and all four original reproduction assertions pass. Unchanged persistence/schema SQL evidence remains valid.

Local full1216/no-model8 and isolated SQL pass; exact-head hosted Node20/24/real PostgreSQL are green in run40299305309. Fourteen new synthetic tests include full-cap topic separation, query coverage and unchanged six parallel fetches/10-second deadlines/evidence bounds.

Keep draft. Necessary generated-answer/accuracy verification is still unperformed and needs Aryan's explicit quota authorization. Code/transport tests do not establish semantic conflict resolution, customer-version applicability or a global accuracy percentage. No paid/provider/customer/protected run, merge, deployment, assignment or optional-feature change occurred in this review.