When fnode is invoked from a cwd outside fivenode_go (e.g. a sibling
project like /Users/.../solmade), the legacy fallback
"../../fivedev/five" was resolved against the caller's cwd, pointing
fnode at /Users/fivedev/five which doesn't exist. go mod tidy then
failed with "open /Users/fivedev/five/go.mod: no such file".
New resolution order in fiveRoot():
1. walkUpForModule("five") — same as before, wins inside the
Five source tree.
2. fiveFromFnodeGoMod() — parse the `replace five => <path>`
line in fivenode_go's own go.mod (found via fnodeRoot()),
resolving relative paths against that root.
3. Hardcoded relative fallback (legacy).
Lets sibling apps run `fnode build app/foo.prg ...` from their own
directory without needing to cd into fivenode_go first.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Charles KWON OhJun
b19bb0c445