[RCmerci]

Integrity failures and stale Timeline reports need correlation across the authoritative preimage, Worker query snapshot, Runtime owner and App publication. Add bounded, allowlisted technical observations for those boundaries and Capture page creation. Values, titles, credentials and raw external errors are excluded; observers remain best effort, the Overlay observer runs outside commit locks, and existing commit/retry/validation/persistence behavior is retained.

Reconcile the diagnostics with the merged Timeline and presentation changes. Feed hooks now observe the current date catalog, Today probe, depth-zero roots, bounded child previews and actual completion flag. They preserve request UUID allocation, query arguments, cursors and owner fencing, with no extra graph read. The effective diff from current main remains five diagnostics files.

Validation:

• Complete original diagnostics diff and actual integration resolution independently reviewed using the repository review skill; no evidenced findings. The published head's tree exactly matches the reviewed candidate.
• Combined @all/native_embed build passes. Runtime175, App149, Worker50, Overlay98/86 and the remaining suites pass. The first parallel full run had one TLS peer-process teardown timeout after semantic assertions passed; the unchanged isolated case151 and then complete Sync333 pass. The original failed run is preserved.
• Controlled Runtime logs validate bounded JSON/8KiB, at-most16 identity samples, safe boundary fields and at-most3 preview requests. This is not live-graph coverage.
• Exact head CI: https://github.com/logseq/logseq_journal/actions/runs/40307046073 — completed success.
• Earlier 6709 Simulator/Web correlation controls apply to their earlier source only. A new signed iPhoneOS candidate builds, with experimental host-restamp/cross_abi_validated=false; no final-main native runtime or server E2E acceptance is claimed here.
• The edited decision validates; five unrelated historical document format failures remain.

This is diagnostic instrumentation and does not claim to resolve the reported Capture integrity failure.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-25T07:21:50.780178Z	015e056	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.