Beagle SCM

JS-015 LOW: script args dropped — no process.argv / args global

A JABC script cannot read its own command-line parameters: main() takes the first non-flag token as the script path and breaks, never exposing the trailing argv to JS. Method: Issues.

Input

Context

• js/main.cpp:120-123 — once argv[i] is taken as script_file, the

  arg loop breaks; every token after it is ignored.

• No process.argv / scriptArgs / args global is installed, so a

  script has no way to see its parameters (verified: grep argv in js/).

• Blocks any parameterized utility, e.g. jabc tool.js status ~/repo

  (the surfaced gap from the be status JABC-coverage review).

Goals

• The argv tail (tokens after the script path) reaches JS as an array.

Constraints

• Pure main.cpp + glue; no abc change. --eval / --version intact.
• JS-owned strings; no held refs beyond bootstrap (JABC rule #4).

WIP

Design decisions

• (open) Collect the tail into a JS array set as a global — args, and

  optionally a Node-ish process.argv = ["jabc", script, …tail].

TODOs

• Repro-first: jabc tool.js a b → args deep-equals ["a","b"]

  (C++/e2e assert, red before).

• Build the array in main() after module install, before the run.

Blockers

• None.

Outcome

• LANDED 800c57a3 (2026-06-21): main() records the argv tail; new

  JABCInstallArgv sets global args + Node-ish process.argv (["jabc", script, …tail]) after module install. New js/test/run-015.sh ctest JABCargv red-before/green-after; ctest -R JABC 18/18, ASAN/LSan clean. Posted past a benign POSTCFLCT (doc string in INDEX.md → POST-006).

• Pre-existing, not changed: --eval CODE x still treats x as a script

  path (the no-trailing-script --eval case works, args=[]).