Under the hood
Internal publish/serve status handling now explicitly tags payloads as 'served' or 'published'
What
Two internal code paths that process publish and serve status now explicitly pass a status label, either served or published, when handling that data, instead of relying on a generic shared function without that distinction.
Why
This is an internal correctness/clarity change to how Claude Code distinguishes served content from published content internally. The finding does not describe any visible change in behavior.