fieldtester: committed fixture labs must not reference the engine via the run worktree's absolute path #33

New Issue

2026-07-21T14:16:41+02:00

claude commented

2026-07-21 14:16:41 +02:00

Motivation

The aura #300 fieldtest found fieldtests/milestone-real-project-readiness/ger40-lab/Cargo.toml pinning engine crates by ABSOLUTE path into a run worktree (/home/.../.claude/worktrees/boss-real-project-readiness/...) — dead the moment that run's worktree was removed at its ratified merge. The committed lab is a frozen historical record, so nothing broke operationally, but any future project-as-crate fixture generated the same way ships broken references into history. aura closed the repair issue (#303) as not load-bearing; the durable fix belongs here.

Problem

agents/fieldtester.md does not constrain how a generated fixture lab references the project under test. A fieldtester running inside a run worktree naturally writes that worktree's absolute path into the lab's manifest — correct at generation time, dead after merge-and-cleanup.

Wanted

One line in the fieldtester conventions: a committed fixture lab must reference the project under test relative to the repository root (or not at all, for data-only labs), never via an absolute path and never via the run worktree.

## Motivation The aura #300 fieldtest found `fieldtests/milestone-real-project-readiness/ger40-lab/Cargo.toml` pinning engine crates by ABSOLUTE path into a run worktree (`/home/.../.claude/worktrees/boss-real-project-readiness/...`) — dead the moment that run's worktree was removed at its ratified merge. The committed lab is a frozen historical record, so nothing broke operationally, but any future project-as-crate fixture generated the same way ships broken references into history. aura closed the repair issue (#303) as not load-bearing; the durable fix belongs here. ## Problem `agents/fieldtester.md` does not constrain how a generated fixture lab references the project under test. A fieldtester running inside a run worktree naturally writes that worktree's absolute path into the lab's manifest — correct at generation time, dead after merge-and-cleanup. ## Wanted One line in the fieldtester conventions: a committed fixture lab must reference the project under test relative to the repository root (or not at all, for data-only labs), never via an absolute path and never via the run worktree.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Brummel/Skills#33