Port coded toast and friction instrumentation from Pluto

Elazar direct request 2026-08-30, split from TERRA-124 after coder02-terra-cc plan review. PURPOSE: complete the nonvisual toast and friction instrumentation originally bundled into TERRA-124 without allowing it to delay or block the visible practica-form control correction. CURRENT STATE: Terra already has friction-actions, friction-client and friction-codes, but no src/lib/toast.ts wrapper. The root layout does not yet carry the full Pluto-equivalent reporter bootstrap and NativeValidationCapture coverage described by TERRA-124. SCOPE: 1. Port and adapt the coded toast wrapper so each warning or error mechanism records reportFriction with a registered stable code before or with display. 2. Mount the required reporter bootstrap and NativeValidationCapture in the appropriate Terra root layout. 3. Adapt the friction-toast coverage test to reject uncoded warning/error calls and literal codes absent from the Terra registry, with an explicit narrow allowlist if any exception is real. 4. Preserve Terra code registry semantics and do not import unrelated Pluto domain behavior. ACCEPTANCE: - Source shows coded toast calls paired with reportFriction and registered codes. - Coverage test has must-pass and must-fail arms for uncoded calls and unknown codes. - Typecheck and relevant tests pass. - Deployed SHA/build is identified and the warning/error path is exercised in the authenticated app; source or deployment alone is not closure evidence. SEQUENCING: child starts only after the visible TERRA-124 control conversion, validation, deployment and rendered review are complete or independently accepted. It must not hold the visible fix hostage.