docs(blog): verify IPython fence parser follow-up

[TimeToBuildBob]

The parser article described the shell fence fix but lacked the IPython follow-up. Add a dated update showing how a triple-quoted Python string loses its embedded Markdown fences before proposed gptme/gptme#3773, with parent/head results for complete messages in both default and streaming extraction.

The update explicitly records two remaining failures from that PR’s review, reproduced at the same pinned head, and states that the fix remains open and unmerged. It updates the existing article and keeps its URL and share image.

Validation:

• Exact archived source: 90 codeblock tests pass at eb4ec3907; two of three triple-quote regressions fail against parent e905cf701.
• Both published review counterexamples return no parsed blocks at the tested head in both modes.
• Independent factual/privacy review, scoped source and website hooks, strict frontmatter validation, full CSS/Jekyll build, rendered example/table inspection, and existing OG card inspection.

[TimeToBuildBob]

🤖 AI code review

Safe to merge — no P0/P1 findings

Confidence 5/5

✅ No findings. The diff looks correct to me on this pass.

_{Reviewed 9dff04d0b5b7 · openrouter/deepseek/deepseek-v4-flash-0731 · llm (in-band) engine · 148s · about this reviewer}

_{Maintainer commands}

_{@TimeToBuildBob review (own line) — fresh review · @TimeToBuildBob fix — a worker acts on the findings. Once per comment; 👀 = received.}