fix(auditlog): truncate over-width SiteCalls.LastError on the cached-telemetry dual-write and the reconciliation pull (review 2026-10-21 follow-up)

docs/requirements/Component-AuditLog.md

@@ -353,7 +353,11 @@ collapse first-write-wins before the statement is built, duplicates *across*
 packets are eliminated by the anti-semi-join, and any failure falls back to the
 per-row / per-entry path — so the documented invariant that one bad row cannot
 sink the rest of the batch still holds, it is simply no longer paid for on the
-healthy path.
+healthy path. A site `LastError` longer than the central `SiteCalls.LastError` column (1024
+characters) is truncated to the column width on both the dual-write and the
+reconciliation pull (`SiteCallColumnBounds`) — an over-width message used to fail the
+whole dual-write with SQL 8152, so the audit row came back Rejected and the
+`SiteCalls` row was never written by either path (review 2026-10-21 follow-up).
 
 The set-based path binds its string parameters at the VALUE's own length, never
 at the column width. Declaring the width makes the client TRUNCATE an over-long