libDir/_here) duplicated across 5 modulesThe be-relative require workaround (resolve a module's own dir so it can
require siblings by absolute path under the resident loop, where argv[1]
is loop.js not the module) is reinvented in five modules with subtly
different fallbacks — "." vs argv[1] vs __dirname. Several sites do
the require LAZILY in a function body, defeating the registry warm-cache
and hiding the dependency graph. Method: Issues.
libDir(){ return __dirname || "." } then
subs.js:53 lazy require(libDir()+"/../core/discover.js") in
classifyMount's body — a per-call require, not a top import.libDir(){ __dirname || "." }.libDir(){ __dirname || "." }._here = argv[1].slice(0,
lastIndexOf("/")) — argv[1]-based, not __dirname.require(__dirname+"/../../core/…")
inline, no helper.shared/util/here.js exporting a base-dir + a sibling
require helper; the 5 sites consume it (one resolution rule).__dirname (require.cpp injects it),
drop the "."/argv[1] fallbacks once verified present.__dirname-relative (the require.cpp contract);
the "." fallback is dead under the real loader — assert + drop.libDir(){ __dirname||"." } duplicated in shared/subs.js:52,
shared/classify.js:579, verbs/post/fold-decide.js:227; core/loop.js:16-17 uses the
_self=process.argv[1]/_here idiom; no shared/util/here.js exists.