For a SECOND verb set — publication scripts in html/be, run from html/ —
jab <verb> must find that shard's verbs while core/shared still load from the
parent be/. Today verb discovery anchors on ONE root, so a nested shard is
invisible. Prereq for the mark publication verb (MARK, step (b)).
be/ = rev-ctrl (beagle-ext); a new html/be/ = publication verbs, jab-run from html/.loop.js:_isVerb(w, _here) probes <_here>/verbs|views/<w>/<w>.js; _here = dirname(argv[1]) = the resolved main.js. registry.build([verb], require) (loop.js:319) resolves the handler via loop.js's own require.html/ (no html/be/main.js), resolveBe("main.js") climbs to journal/be/main.js → _here = journal/be; both the probe and require land in journal/be, never html/be → a cwd-nearest html/be/verbs/mark/ is never seen.verbFile(w, startDir?): be-climb from cwd (default) for <dir>/be/verbs|views/<w>/<w>.js, ceiling $HOME, first hit wins — mirrors jab's own resolveBe.be/ shard supplies its own verbs; verbs absent there INHERIT from the parent be/ up-tree; core/shared stay anchored on _here.registry.convention; keep _isVerb's signature.registry.verbFile), core/shared keep _here — so a nested shard adds verbs without duplicating the loop/kernel.registry.verbFile + registry.resolveVerb (own the climb + contract in ONE module, unit-testable without loop.js's _here bootstrap).mark found from cwd, get inherited up, no down-leak, resolveVerb → args handler (be/test/be029.js).registry.verbFile / registry.resolveVerb (cwd-climb + convention).loop.js: _isVerb via verbFile; dispatch via resolveVerb.jab head regression OK, nested ping shard dispatches PONG.journal/be (gates the live jab mark); then MARK step (b).$HOME/be is the locator (do NOT plant be in the worktree); jab get 'file:/home/gritzko/.be?/beagle-ext' from the empty dir then completes.