Distillation

Date: Jul 30, 2026

• 🟡 (21:21) Agent verified zstd in Node.js was added in v22.15.0 via commit 94647bbdb2 (PR #56599 — no, that was crypto/macOS). The actual zlib commit is 4991e5d826 — (SEMVER-MINOR) zlib: add zstd support (Jan Martin) #52100. This was the v22.15.0 entry, dated 2025-04-23 'Jod' (LTS), prepared by @RafaelGSS.
• 🟡 (21:21) Confirmed bspatch.ts code uses createZstdDecompress and zstdDecompressSync from node:zlib, both requiring v22.15.0+. Min Node version must be >=22.15.0, not >=22.5.
• 🟡 (21:21) Agent read architecture-flow.svg — current SVG uses currentColor for fills/strokes, rendered via Markdown <img> tag which can't inherit currentColor from host page (invisible on dark mode). Need Mermaid replacement.
• 🟡 (21:21) Architecture page referenced architecture-flow.svg via Markdown image. Size-comparison.svg is a chart (not flow) so stays as SVG.
• 🟡 (21:21) Apply page (apply.md) contains dubious performance numbers: Naive byte loop = 883ms, Uint32Array SWAR = 221ms, BigUint64Array = WRONG, claimed on "2021 M1 MacBook Pro". User flagged these as "completely made up" — need real benchmarks.
• 🟡 (21:21) FAQ.md "Is binpatch production-ready?" claims "powering self-updates for shipped binaries in production for years — including getsentry/cli". User wants this toned down to "months" since the new CLI is recent.
• 🟡 (21:21) FAQ.md "How is the project released?" section mentions Craft but doesn't link to https://craft.sentry.dev. Need to add link.
• 🟡 (21:22) Contributing.md has email security@withlore.ai for security disclosures — Lore reference that user wants dropped. Also says "Node 22.5+ is required (matches the project's minimum)" — wrong, must be 22.15.0.
• 🔴 (21:21) User's three asserted directives (carry-over context):
  • applyPatch() always returns the SHA-256 inline — design rule, no separate verify step.
  • "never trust a fix without seeing it fail" — quoted in contributing.md as the project's mutation-verify discipline (write fix, write failing test, revert fix to confirm test fails, restore fix, then PR).
  • SHA 94647bbdb2 referenced by user — corresponds to crypto/macOS cert support (PR #56599, Tim Jacomb), NOT zstd. User's SHA reference was likely for context but it's NOT the zstd-introducing commit; the actual zstd commit is 4991e5d826.
• 🔴 (21:22) User's three explicit directives (high-priority, MUST override prior state):
  • "always returns the SHA-256 inline" — reaffirmed in contributing.md coding conventions as a hard rule for applyPatch().
  • "never trust a fix without seeing it fail" — the project's testing principle (treat every fix as a hypothesis to falsify before opening PR).
  • Reference to commit 94647bbdb2 in context of recent Node changelog work.
• 🟡 (21:22) Agent launched background task (id ses_04b17e988ffepzhUZFP863yCkG) to run real performance benchmarks while doing other edits in parallel. Instruction: do NOT sleep, poll, or duplicate the task's work.
• 🟡 (21:22) Two edits applied successfully (likely the install.md and FAQ.md edits), plus the package.json engines.node field currently still reads >=22.5 — needs update to >=22.15.0.