jab put ignores the cwd/nav dir context — stages the WHOLE tree + every mounted subReported by gritzko 2026-07-11: a bare :put typed in a wiki-navigated pager view (footer put ///wiki) staged todo/README.mkd, all of wiki/* AND beagle/mark/* inside the beagle sub — the whole tracked-dirty set, sub banners and all.
jab put from shared/ staged root-level CMakeLists.txt + README.mkd and descended the test sub; the cwd never scoped anything.verbs/put/put.js putRun with no path args runs bareStage(repo,…) + bareStageSubs (PUT-004/SUBS-044) over the whole wt; be.ctxDir (BE-032) is never consulted; the loop's BE-048 block deliberately left mutations whole-scope — gritzko now extends the ruling: a DIR context scopes a bare mutation too (git parity: git add -u in a subdir is cwd-scoped).jab put <dir> already scopes correctly (verified) — regression-guard it.discover.ctxSub helper (exported by that fix).///path mutation arg0 rescopes to the OUTERMOST repo from a nested worktree (do NOT fix here).jab put from a subdir cwd (or a pager context nav'd into one) stages only the tracked-dirty set under that dir; from the wt root, unchanged whole-wt.bareStageSubs) descends only mounted subs AT/BELOW the scope dir.discover.ctxSub (the STATUS-006 mechanism), one shared shape — no per-verb reimplementation.ctxSub becomes the dir-form path arg (rooted /sub/), riding the EXISTING dir-stage path (stageArg dir + stageInSub for crossings) instead of bareStage — auto-pair moves under the scope dir need a check.put from a subdir stages only that subtree (root file + sub file stay unstaged)put from the wt root stays whole-wt + sub recursion (regression)put <dir> unchanged:put stages only that subtree