JAB-035: embed a default jsrc/ pack in the binary — the permanent floor of the jsrc stack

Now
OPEN
Sev
MED
Ask
gritzko
Rep
///jab

A prebuilt jab binary is useless alone: every bareword dies with "cannot find jsrc/main.js" until the user clones a jsrc/ checkout — the install is a two-step. Let the binary CARRY a default pack of .js files and append it as the LAST entry of the frozen jsrc stack, so it backfills per-file under any user jsrc/. That both collapses the install to "download, run" and makes incremental extension the norm: a user's jsrc/ holding a single verbs/foo.js overrides that one file, every other bareword falls through to the pack.

Input

Context

require.cpp resolves barewords by the once-frozen upward climb (pinJsrcStack, GET-041); resolveJsrc already falls through the stack PER SPEC, so overlay semantics come for free — the floor just has to be on the stack.

Goals

A release jab that runs be status out of the box with no checkout, while any jsrc/ up the chain overlays it file-by-file.

Constraints

WIP

Design decisions

Always-append, per-file fallthrough — overlay is the extension mechanism, not a hazard.

TODOs

Blockers and bummers

Outcome

Implemented in //JAB-035 (base ///jab/#c7c0c495), 16 files staged, NOT committed.