chore(release): version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

rn-dev-agent-cdp@0.45.3

Patch Changes

• a88d139: cdp_network_log no longer returns two entries per request (GH bug: cdp_network_log returns duplicate entries per request (CDP Network domain + injected hook both capture) #214).

  Root cause: setup sends Network.enable (mode cdp), then probeNetworkDomain fires a probe fetch and watches the buffer. On RN ≥ 0.83 the CDP Network domain does deliver events, but when they don't flush within the probe window — a false negative documented after platform switches / reloads (GH iOS testing friction — 9 observations from a live-verification session (native prompt, physical device, share sheet, MMKV, platform switching) #59 Auto-handle Expo Dev Client server picker before testing #9) — the probe returns none and setup injects the fetch/XHR hook without disabling the still-enabled Network domain. Both paths then capture every request (CDP numeric-id entries + hook UUID-id entries), and the existing exact-id dedup can't collapse them because the two id schemes never collide.

  Fix: when setup falls back to the hook, it now disables the CDP Network domain first, so the hook is the single capture source. This also makes cdp_status's networkDomain: false truthful instead of a label over a still-running domain — the "capability flag out of sync" symptom in the report was the same root cause. Read-time fuzzy dedup was deliberately rejected: it would collapse legitimately-identical rapid requests (a real double-mutation) and hide bugs — the opposite of what the reporter needed.

rn-dev-agent-plugin@0.54.3

Patch Changes

• a88d139: cdp_network_log no longer returns two entries per request (GH bug: cdp_network_log returns duplicate entries per request (CDP Network domain + injected hook both capture) #214).

  Root cause: setup sends Network.enable (mode cdp), then probeNetworkDomain fires a probe fetch and watches the buffer. On RN ≥ 0.83 the CDP Network domain does deliver events, but when they don't flush within the probe window — a false negative documented after platform switches / reloads (GH iOS testing friction — 9 observations from a live-verification session (native prompt, physical device, share sheet, MMKV, platform switching) #59 Auto-handle Expo Dev Client server picker before testing #9) — the probe returns none and setup injects the fetch/XHR hook without disabling the still-enabled Network domain. Both paths then capture every request (CDP numeric-id entries + hook UUID-id entries), and the existing exact-id dedup can't collapse them because the two id schemes never collide.

  Fix: when setup falls back to the hook, it now disables the CDP Network domain first, so the hook is the single capture source. This also makes cdp_status's networkDomain: false truthful instead of a label over a still-running domain — the "capability flag out of sync" symptom in the report was the same root cause. Read-time fuzzy dedup was deliberately rejected: it would collapse legitimately-identical rapid requests (a real double-mutation) and hide bugs — the opposite of what the reporter needed.