Why one issue, not N

Single user-visible doc gap: PR #510 is in the v0.9.2…v0.9.3 commit delta but absent from the release notes. Filing on its own (rather than batching with bug fixes) so it lands as a documentation patch and does not get held behind code review for unrelated fixes.

Sub-item C1: v0.9.3 missing changelog entry for #510

• Repro hypothesis: Read v0.9.3 changelog. PR fix: apply ingest protections during bootstrap import #510 is not credited. Compare with git log v0.9.2..v0.9.3 — fix: apply ingest protections during bootstrap import #510's commit is in the delta. Most likely a missing changeset file in the PR.
• Evidence:
  • fix: apply ingest protections during bootstrap import #510 changes user-visible bootstrap behavior: oversized files, images, and tool results in transcripts are now externalized on first import; the raw transcript hash is now used as a reconciliation anchor; the bulk insert path is replaced by a per-message ingest path.
  • fix: apply ingest protections during bootstrap import #510 is a peer of fix: externalize oversized raw payloads #511 and fix: externalize native user image blocks #521 — both of which ARE in the changelog — for closing Large raw payloads are stored/reassembled as normal messages and can dominate LCM context #492.
  • Unlike fix: add overflow assembly diagnostics #512 (diagnostics-only, defensible omission), fix: apply ingest protections during bootstrap import #510 is user-visible and deserves credit.
• Suggested fix: Append a 0.9.3 patch entry crediting jalehman. One-line entry covering: oversized content externalized on first bootstrap import, raw-transcript hash now used for reconcile anchor.

Suggested PR scope

Single-file PR adding the missing changeset entry to the v0.9.3 section. No code touched. If the project uses a changesets-style workflow, add the missing changeset file and regenerate the rendered changelog; otherwise edit the rendered changelog directly. PR description should reference this issue and the original #510 so reviewers can confirm wording matches the PR's user-visible behavior.

Cross-links

• Large raw payloads are stored/reassembled as normal messages and can dominate LCM context #492 — the bug closed by the fix: apply ingest protections during bootstrap import #510/fix: externalize oversized raw payloads #511/fix: externalize native user image blocks #521 trio.
• fix: apply ingest protections during bootstrap import #510 — the PR missing from the changelog.
• fix: externalize oversized raw payloads #511 — peer PR (in changelog).
• fix: externalize native user image blocks #521 — peer PR (in changelog).