Beagle SCM

JS-109: gitParseCommit leaks a JSStringRef on empty-tree and default-body paths

Proposed by the 2026-07-07 jab multi-agent review; confirmed by both skeptic verifiers. Two call sites create a JSStringRef and never release it — masked only because the LSan suppression covers all of libjavascriptcoregtk.

Input

Context

• JABCSet(ctx, o, "tree", JSValueMakeString(ctx, JSStringCreateWithUTF8CString(""))) (jab pack.hpp:370) and the default-body JSValueRef body = JSValueMakeString(ctx, JSStringCreateWithUTF8CString("")) (pack.hpp:378) never JSStringRelease the +1 ref; JSValueMakeString retains its own.
• Every parsed commit leaks one OpaqueJSString (two without a tree header); every other call site in the repo releases.
• The leak hides behind main.cpp's blanket leak:libjavascriptcoregtk suppression (JS-064) — exactly the class that suppression was not meant to cover.

Goals

• Create-once + JSStringRelease after JSValueMakeString (or a shared JSOfCString("")); git.js parse test stays green.

Constraints

• Two-line fix; do not touch the LSan suppression setup.

WIP

TODOs

• release the two refs; eyeball pack.hpp for further unreleased creates