Repair the ger40-lab fixture's dead worktree dependency paths #303
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Brummel/Aura#303
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
fieldtests/milestone-real-project-readiness/ger40-lab/Cargo.toml:11(and siblings) pin the aura crates by ABSOLUTE path into/home/brummel/dev/aura/.claude/worktrees/boss-real-project-readiness/...— a worktree that no longer exists (run worktrees are removed at their ratified merge). Any verb invoked from inside the fixture project failscargo metadatabefore reaching aura at all. Found orthogonally by the #300 fieldtest.Consequence
The milestone fieldtest for real-project-readiness would trip over its own fixture rather than the product. The fixture must reference the engine relative to the repository (or the primary checkout), never an ephemeral worktree path.
refs #300
Premise correction (owner review, 2026-07-21)
This issue's consequence paragraph is wrong: the "Real-project readiness" milestone is closed (0 open / 13 closed), so there is no future milestone fieldtest for this fixture to trip. The fieldtest corpora under
fieldtests/are not workspace members and run in no suite — they are frozen historical records (the ledger's own framing of the 0106 corpus). Repairing ger40-lab's paths so it runs again would keep a historical artifact alive against that convention.What survives of this issue is at most a hygiene rule for FUTURE fieldtest labs: committed fixtures must not reference the engine by absolute path into an ephemeral run worktree (the cycle-300 lab already complies — no worktree or absolute paths). Disposition — close as historical record, or re-scope to that forward-looking hygiene rule — is the owner's call, under discussion.
Closed as not load-bearing (owner decision, 2026-07-21): the milestone this fixture served is closed, the fieldtest corpora are frozen historical records outside the workspace (nothing executes them), and repairing the paths would keep a historical artifact artificially alive. The one forward-looking lesson — committed fixture labs must reference the engine relative to the repository, never via a run worktree's absolute path — is filed against the skills plugin (the fieldtester agent's conventions), where future labs are generated.