docs: Feed survive track PoC learnings back to the map #136

Context

The 3 survive PoCs are the engineering spine of Q2. Their findings — benchmarks, threat models, failure modes — are exactly the hard-to-reproduce insights that make the map defensible. v0.4.0 should capture these learnings.

Survive PoCs

• ethereum/iptf-pm#164
• ethereum/iptf-pm#165
• ethereum/iptf-pm#166

Scope

• For each completed survive PoC, review findings and identify which patterns/approaches need updating
• Add concrete data (benchmarks, measured trade-offs) to replace hypothetical CROPS reasoning in relevant patterns
• Create new patterns if a survive PoC surfaces a primitive not yet in the map
• Update approaches with survive PoC validation data (proven vs speculative)

Done when

All 3 survive PoCs have corresponding map updates — pattern enrichment, new patterns, or approach validation data.