A direct source-code check against beautiful-mermaid's current upstream tree, not a rendered-output comparison, confirms eleven fixed parsing and rendering bugs are unchanged four months on.
Read the postThe real daily merge-count histogram behind two weeks of reviving a dead fork — not the rounder number the tracking issue guessed — and what it does and doesn't tell you about agent-driven maintenance.
Read moreNine accessibility issues, filed and fixed over four days, ended with a written conformance statement and an automated test that fails the build if a future diagram type ships without an accessible name. Here's the arc from bug report to guarantee, and the regression that got caught eight hours after the guarantee shipped.
Read moreOn 2026-08-25, one evening of deliberate, format-by-format testing turned "upstream looks stalled" into fifteen numbered, reproducible rendering bugs. That list is the actual case for continuing the fork.
Read moreInstead of one "improve test coverage" ticket, this repo filed nineteen — one per file, all in a 25-second burst — and closed all nineteen in under four minutes each. The backlog shape did more work than any individual fix did.
Read moreBefore a single Mermaid rendering bug got fixed in this fork, roughly twenty hours went into package managers, lint, coverage gates, and security scanning. Here's the verified timeline and the case for why that ordering wasn't optional.
Read moreOn 2026-08-27 this repo extracted five shared seams out of code that had been drifting for two days — not because it looked messy, but because the same missing abstraction had already produced the same bug twice, and would go on to produce it twice more.
Read moreThe unglamorous last mile between a patched fork and an npm-installable package — deploy target, attribution, branding, and the release itself — verified against the actual issues, PRs, and tags, not the plan.
Read moreA demo page that renders real before/after diffs became a build-time guarantee, then a habit, then a hard requirement about what counts as proof. The four issues that got it there, verified against their own PRs.
Read moreThe hardest recurring bug in zombie-mermaid's ASCII renderer wasn't diagram layout, it was column-width math, and it came back four times in a week wearing a different costume each time.
Read moreA weekly job has an LLM compare this repo's ASCII rendering against real mermaid.js and files issues for what doesn't match. A second bot turns PR review comments into tracked issues. Neither fixes anything — that part is still humans.
Read moreA same-input comparison against mermaid-ascii 1.5.0 — where the two renderers match character for character, where they diverge, and what each does better.
Read more