Commit 9a06ffe raised the postv2 lexicon and the write-API cap from 100,000 to 500,000 bytes but left the firehose consumer's mirror at 100,000. A post between those sizes passed the write API and landed on the PDS, then came back through Jetstream as ErrPermanentEvent: the create was dead-lettered and never indexed, and an update that size left the old content in place. This is the kagi-news failure the lexicon raise was meant to fix, one hop downstream. Changes: - MaxPostContentBytes in authorpost.go: 100000 -> 500000 - postv2_content_cap_test.go: create-over-cap, update-over-cap and at-cap cases now use 500,001 / 500,001 / 500,000 bytes Verified: T1 TestPostV2Consumer_ContentAndTitleCapsApplyToCreateAndUpdate passes (all five subtests), go vet and package T0 clean. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016UfGV6NJToB7NdtTxCsBih