shoney.arickathil
464b61ba65
The manifest pinned `[build] runtime = "../../../runtime/wovm"`, a repo-only relative path that overrides woc's runtime resolution — so `woc <copied-dir>` failed off-repo (e.g. an installed toolchain on a test server) with "runtime binary not found". - Drop the [build] section: the project no longer hardcodes a machine path, so an installed `woc` self-locates `wovm` beside its own binary. - The module justfile's `build` recipe now sets WO_RUNTIME=<repo>/runtime/wovm so the in-repo build still uses the freshly built VM. - Acceptance is unaffected (it compiles via `woc --emit` + an explicit $WOVM, never the manifest [build] key). Verified: just log-watcher::build OK; just log-watcher 7/0; and building a copied tree with the installed-layout woc from an unrelated cwd self-locates the sibling wovm and produces a runnable binary. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| examples | ||
| plan | ||
| runtime | ||
| stories/language-runtime-database | ||
| superpowers | ||
| 00-code-review.md | ||
| 00-principles.md | ||
| 00-status.md | ||
| 01-problem.md | ||
| 08-project-structure.md | ||
| cm.md | ||