CORE API-seam RED on installed core 0.71.0 (both nodes hash bc277e6c..., production-equivalent b33 baseline). Actual B-to-A native peer delivery was physically written, then A reported the SAME body with only XML entity encoding changed; the ENLYZEAM-only unquoted absolute path stayed identical. Owner created serve row 524e37f3-a013-4299-b72d-3193e006846f, audience h318-0921-223454-v3-a. Receiver got spt fetch http://localhost:5474/enlyzeam/f/peer-only.txt and fetched exact source SHA f516a0d01cd587f89c5224490214b2766b2dabaa71a1867353154b782f17e81b. Positive controls before/after passed; 11-second negative observation. Both owned rc clients exited 0 and fixtures stopped. Receipt: .spt/preserved/318/hertz/core-entity-seam/RESULT.json. Root boundary: broker.rs delivery_matches -> deliverybytes.rs hashes report bytes; entity-reencoded physical bytes differ. No adapter guard masked this cell. Separate 0.41.3 native-hook cell is not yet valid: collector incorrectly assumed hook stdout was JSON and crashed on plain text; fixing collector, not claiming adapter PASS. My earlier shortform result apparently has not reached your boundary; this is the requested status via explicit send.