Beagle SCM

BE-036: pager word spells expand shell-style globs (put/delete multi-file args)

On the CLI the user's SHELL expands globs before be sees argv, so be put *.c works; in the pager the typed spell goes to the verb VERBATIM, so put *.c / delete src/* hands the literal pattern as a filename (FILENONE / bogus row). The pager already owns confined FS enumeration for Tab-completion (_fsCompletions, BRO-013, wt-confined via resolveInTree/wtJoin per BE-027); glob expansion is the same machinery driven by a pattern instead of a prefix. The pager plays the shell here: it multiplies WORDS, it does not resolve them — verbs still resolve each arg via resolve(context,base,rel) (BE-030, BE-032) and put/delete rest args stay RAW wt-relative (authorityRepo strips arg0 only).

Input

Context

• views/bro/pager.js _runSpell/_applySpell hand the typed word spell to driveSpell → cli(); core/loop.js:327 splits/scalar()s the words — no expansion point anywhere, patterns reach the verb literally.
• Tab-completion resolves a ./ stem against the VIEW dir and a bare stem against the wt root, enumerates via io.readdir, and CONFINES to the wt (resolveInTree throws NAVESCAPE → no candidates) — exactly the enumeration a glob expander needs (BE-027, pager.js:604).
• Requested by gritzko 2026-07-09: "commands like put, delete in the pager may benefit from expanding globs shell-style. may do along the same lines as autocompletion."

Goals

• A word spell typed in the pager expands *, ?, [...] in its arg words shell-style before dispatch: put *.c stages every matching wt file, delete src/*.tmp removes the matches.
• Expansion reuses the Tab-completion enumeration + confinement (one FS walker, one NAVESCAPE law); matches outside the wt are impossible by construction.
• Expanded words keep the typed stem's shape — a ./ stem yields view-relative ./x words, a bare stem yields wt-relative words (same token shape as _compTok) — so verbs resolve them exactly as if the user had typed each one.

Constraints

• Pager-only (the pager IS the shell); verbs stay glob-unaware, CLI keeps relying on the user's shell.
• Word-spell arg positions only — never rewrite schemed URI spells, ?ref/#frag slot edits, or the verb word itself.
• No pre-merging with the context URI: expansion multiplies raw relative words, resolution stays in the verbs (BE-030 law).
• Repro-first: a pager-driven put *.c failing today, expanding after.

WIP

Design decisions

• Alphabet: *, ?, [...] per segment; ** out of scope for the first cut.
• No-match policy RULED failglob (gritzko 2026-07-09): message in the addr bar, spell NOT dispatched — bash's silent pass-through would feed the literal pattern to a destructive delete.
• Dotfiles: skipped unless the pattern segment itself starts with . (shell convention); expansion output sorted. NOTE: io.readdir hides dotfiles entirely (same as Tab-completion), so the dotted-pattern branch is unreachable today — kept as a guard should readdir ever change.
• Expansion point: on the split words of a word spell at spell-apply time (before the driveSpell reentry), gated on the word actually containing a glob metachar.
• As built (wt BE-036): _globToRe (one segment → anchored RegExp), _isGlobWord (skips ?ref/#frag/-flag/scheme: words), _glob (segment-wise frontier walk, literals via resolveInTree, glob segs via wtJoin+readdir, output via _compTok), _globSpell (argline.shellSplit, verb peeled, quoted words inert, failglob → null), called from _applySpell before _composeCall.
• A leading-? glob word (?.c) is NOT expanded — leading ? is the ref-slot-edit syntax; the slot grammar wins over the shell alphabet.

TODOs

• Repro: pager put *.c today hands the literal *.c to put (RED), test/bro/glob/glob.js unit-drive like navescape.js.
• Segment-wise glob matcher + expander over the _fsCompletions-style confined readdir walk.
• Wire into the word-spell path (all word-spell arg words, put/delete included); failglob on no match.
• Suite: baseline 162/161 pass/1 fail → after 163/162/1; the lone red is the pre-existing be-js-bro-view readdir-order golden (BE-027-documented). Orchestrator re-ran repro + bro subset 2026-07-09: same.

Blockers and bummers

• Fresh-clone bootstrap race hit during worktree setup (store trunk 2dcfc392): jab get file:…?/beagle-ext checks out the project's own be -> . symlink over the bootstrap locator, then the test submodule gate requires shared/gitmodules.js/core/discover.js BEFORE those subtrees exist → "require: cannot find". Worked around with per-subtree jab get shared|core|view|views|verbs first. Root-caused 2026-07-09 under GET-041 (open umbrella): jab's pinBeStack pins symlink paths verbatim + explicit ./ requires bypass it; exposed by the a763a86a checkout-order change.

Outcome

• (open — fix staged in wt /home/gritzko/src/BE-036, uncommitted: views/bro/pager.js + test/bro/glob/{glob.js,run.sh}; pending user review + land)