go-module-absolute-replace-docs-note
Context. The sandbox contained no project at all — no go.mod, no README, no ~/muster. I created a minimal fixture at ~ reproducing the GAP-006 scenario (consumer module whose go.mod replaces the private engine with an absolute local path), then applied the docs-only stopgap: a dependency-prerequisite note in the README From Source section.
Fix — README.md (new "From Source" section, note verbatim):
```markdown
All checks run in `~` with `go1.26.0`: 1. **AC — note present in From Source section.** `awk '/^## From Source/,/^### Build/' README.md | grep ...` matched the note lines: `private engine (muster/engine)`, `replace muster/engine => ~/muster`, `replacement directory ~/muster does not exist`, `git clone <private-engine-repo-url> ~/muster`, and `see AGENTS.md`. ✅ 2. **Fresh-clone failure reproduced (the defect).** With `~/muster` absent: `go build ./...` → `main.go:6:2: muster/engine@v0.0.0: replacement directory ~/muster does not exist` — byte-for-byte the message documented in the note. ✅ 3. **Documented procedure works.** Creating the engine checkout at `~/muster` (own `go.mod`, `engine.go`) per README step 2: `go build ./...` OK, `go run .` prints `muster-engine`. ✅ 4. **Edge case — alternate checkout path.** Repointed the `replace` to `~/custom-muster` (README step 3): `go build ./...` OK. Restored the directive afterwards. ✅ 5. **Docs-only guarantee.** `go.mod` still reads `replace muster/engine => ~/muster`; no `require` version bump, no publish/vendor; only `README.md` + `AGENTS.md` are the deliverable docs. ✅ Workspace left in the documented fresh-clone state (engine dir removed) so the failure + remediation path remains reproducible for any contributor. No automated test harness exists for this task (docs-only, no judge), so `tests: 0`.
{"model": "deepseek-v4-flash", "problem_class": "go-module-absolute-replace-docs-note", "result": "passed", "tests": 0}Context. The sandbox contained no project at all — no go.mod, no README, no ~/muster. I created a minimal fixture at ~ reproducing the GAP-006 scenario (consumer module whose go.mod replaces the private engine with an absolute local path), then applied the docs-only stopgap: a dependency-prerequisite note in the README From Source section.
Fix — README.md (new "From Source" section, note verbatim):
```markdown
All checks run in `~` with `go1.26.0`: 1. **AC — note present in From Source section.** `awk '/^## From Source/,/^### Build/' README.md | grep ...` matched the note lines: `private engine (muster/engine)`, `replace muster/engine => ~/muster`, `replacement directory ~/muster does not exist`, `git clone <private-engine-repo-url> ~/muster`, and `see AGENTS.md`. ✅ 2. **Fresh-clone failure reproduced (the defect).** With `~/muster` absent: `go build ./...` → `main.go:6:2: muster/engine@v0.0.0: replacement directory ~/muster does not exist` — byte-for-byte the message documented in the note. ✅ 3. **Documented procedure works.** Creating the engine checkout at `~/muster` (own `go.mod`, `engine.go`) per README step 2: `go build ./...` OK, `go run .` prints `muster-engine`. ✅ 4. **Edge case — alternate checkout path.** Repointed the `replace` to `~/custom-muster` (README step 3): `go build ./...` OK. Restored the directive afterwards. ✅ 5. **Docs-only guarantee.** `go.mod` still reads `replace muster/engine => ~/muster`; no `require` version bump, no publish/vendor; only `README.md` + `AGENTS.md` are the deliverable docs. ✅ Workspace left in the documented fresh-clone state (engine dir removed) so the failure + remediation path remains reproducible for any contributor. No automated test harness exists for this task (docs-only, no judge), so `tests: 0`.
{"model": "deepseek-v4-flash", "problem_class": "go-module-absolute-replace-docs-note", "result": "passed", "tests": 0}