feat(parser-react): portals & toasts (A9) — Gate 2 complete, Phase 2 done

[officialCodeWork]

Summary

TRACKER Step 2.5 — failure mode A9, and the close of Phase 2 (Gate 2).

What's in it

• Portal components flagged — createPortal users get flags: ["portal"]: a screenshot of the dialog shows nothing from its trigger's DOM subtree, and agents should know the DOM position won't match the render tree. Matching already surfaces both sides: the modal's text → ConfirmDialog, whose instance list points at the OrdersToolbar trigger site.
• Toast text belongs to the caller — toast("Order deleted") (react-hot-toast, notistack enqueueSnackbar, antd message.*): the string exists only as a call argument, rendered by a <Toaster/> mounted elsewhere. It now becomes a renderedText entry with source: "portal" on the calling component — a screenshot of the toast matches its trigger.
• Prop-flow correction the fixture forced — function-valued props (onConfirm={handleConfirm}) and on[A-Z] attributes are callbacks, not data: the fetch inside the callback no longer emits provides-data. The DELETE still reaches the dialog's lineage the right way — through the 2.3 handler chain (onClick:onConfirm --triggers--> DELETE /api/orders/selected). Data-in vs. effect-out stays distinguishable in the graph.

Gate 2 (from docs/testing-strategy.md)

Instance attribution accuracy = 1.0 on C1 fixtures; B1 handler resolution ≥ 0.85 at ≤ 4 levels; C6 store-writer linking green

Passed — plus A9: scorecard 137 pass / 0 fail / 0 xfail · precision 1.000 · recall 1.000 · match accuracy 1.000.

Test plan

• 88 unit tests green (3 new: portal flag, modal→trigger surfacing, toast provenance)
• pnpm eval gate OK; schema regenerated (portal text source), drift gate green

Documentation

• TRACKER.md — 2.5 done, Gate 2 recorded, Status → Phase 3 (journey graph), step 3.1

🤖 Generated with Claude Code