1.5 KiB
Complete visual audit exports without duplicate inline payloads
Run34 visit3 retained a complete, untruncated native session (71 messages,
4,196,297 decoded native bytes), but the HTML audit exceeded the8MiB render cap.
The readable tool projection printed47 inline data: attachment URIs as text,
duplicating3,752,634 bytes already stored in complete native message records.
The renderer now summarizes an inline attachment in the readable projection ONLY when its exact URI bytes also occur in that message's retained native record. The complete native JSON remains unchanged and HTML-escaped. If the native record is absent or does not contain the payload, the original full projection is kept; there is no evidence loss or fabricated completeness.
No source/render/artifact bound is raised. All remain at their existing limits, and genuinely oversized exports still report partial/truncated. No HTML is executed from the attachment; MIME labels and native data stay escaped.
Read-only scratch export of the exact original visual-review session now
produces4,676,544 bytes,71 messages, truncated:false. Production originals and
checkpoints were not overwritten by this proof.
Regressions cover a4MiB inline payload retained exactly once, fallback when no native copy exists, and escaped/unescaped hostile native JSON/MIME values. The full Go suite passes with the unrelated notification-test URL env isolated. Installation remains deferred until a quiescent service window; no active run may be interrupted just to activate this correction.