fix-cargo-install — Workgraph live mirror

Metadata

Status	done
Assigned	`agent-2279`
Agent identity	`f51439356729d112a6c404803d88015d5b44832c6c584c62b96732b63c2b0c7e`
Model	`codex:gpt-5.5`
Created	2026-05-04T14:56:37.741416532+00:00
Started	2026-05-04T14:57:44.710033081+00:00
Completed	2026-05-04T15:17:30.107501953+00:00
Tags	`fix,dev,ux,workflow`, `eval-scheduled`
Eval score	0.89
└ blocking impact	0.95
└ completeness	0.95
└ coordination overhead	0.90
└ correctness	0.90
└ downstream usability	0.85
└ efficiency	0.85
└ intent fidelity	0.91
└ style adherence	0.90

Description

User's /home/erik/workgraph working directory periodically ends up checked out on an abandoned agent worktree branch (e.g., wg/agent-1398/fix-tui-perf). cargo install --path . from that state silently builds a binary missing all the recently-merged work on main. User then hits 'why isn't the fix working' bugs that are actually 'I built from the wrong branch.'

This has happened multiple times this week. Each time, the chat agent (me) initially missed it because I assumed cwd = main.

Fix

During cargo install --path . in the workgraph repo: detect non-main branch + warn
OR: a small wg dev-check command that checks 'are you on main, is your binary current with main HEAD' and warns if drift detected
Or: hook into wg quickstart to add this check as part of session-start orientation

Recommend option 2 (wg dev-check) so it's opt-in and doesn't fight with legitimate cases (developer is intentionally on a feature branch). Then quickstart mentions it.

Validation

wg dev-check (or whatever it's named) prints branch + binary mtime + main HEAD; warns if mismatched
Live smoke: from main, run check — green. From a non-main branch with stale binary, run — warns.
cargo build + cargo test pass
cargo install --path . was run before claiming done

## Description
User's `/home/erik/workgraph` working directory periodically ends up checked out on an abandoned agent worktree branch (e.g., `wg/agent-1398/fix-tui-perf`). `cargo install --path .` from that state silently builds a binary missing all the recently-merged work on main. User then hits 'why isn't the fix working' bugs that are actually 'I built from the wrong branch.'

This has happened multiple times this week. Each time, the chat agent (me) initially missed it because I assumed cwd = main.

## Fix
- During `cargo install --path .` in the workgraph repo: detect non-main branch + warn
- OR: a small `wg dev-check` command that checks 'are you on main, is your binary current with main HEAD' and warns if drift detected
- Or: hook into `wg quickstart` to add this check as part of session-start orientation

Recommend option 2 (`wg dev-check`) so it's opt-in and doesn't fight with legitimate cases (developer is intentionally on a feature branch). Then quickstart mentions it.

## Validation
- [ ] `wg dev-check` (or whatever it's named) prints branch + binary mtime + main HEAD; warns if mismatched
- [ ] Live smoke: from main, run check — green. From a non-main branch with stale binary, run — warns.
- [ ] cargo build + cargo test pass
- [ ] cargo install --path . was run before claiming done

Depends on

done .assign-fix-cargo-install

Required by

(none)

Log

2026-05-04T14:56:37.713043229+00:00 Task paused
2026-05-04T14:57:19.125792011+00:00 Task published
2026-05-04T14:57:41.675343717+00:00 Lightweight assignment: agent=Careful Programmer (f5143935), exec_mode=full, context_scope=task, reason=Careful Programmer matches a correctness-critical fix requiring live smoke testing on multiple branch states (main vs non-main) with high implementation fidelity.
2026-05-04T14:57:44.710037409+00:00 Spawned by coordinator --executor codex --model gpt-5.5
2026-05-04T14:58:02.810283345+00:00 Starting implementation; no unread messages, inspecting command structure and existing WIP
2026-05-04T14:59:06.742128472+00:00 FANOUT_DECISION: stay inline — small CLI diagnostic touching command wiring, one module, docs, and focused tests
2026-05-04T15:06:53.211105939+00:00 Implemented wg dev-check with branch/main/binary freshness output, quickstart mention, integration coverage, and owned smoke scenario
2026-05-04T15:11:14.637557979+00:00 Validated: cargo build passes; cargo test dev_check passes; owned smoke scenario passes. Full cargo test currently fails in existing integration_cycle_detection tests that call wg init with no route/model, unrelated to dev-check.
2026-05-04T15:16:10.078802898+00:00 Validated: cargo install --path . completed and installed wg from this worktree
2026-05-04T15:16:25.626808096+00:00 Validated: wg dev-check prints branch/main HEAD/binary mtime; installed binary warns on this non-main worktree; quickstart mentions dev-check
2026-05-04T15:17:15.501442999+00:00 Committed: c8bcac6b5 — pushed to origin/wg/agent-2279/fix-cargo-install
2026-05-04T15:17:30.107510779+00:00 Task pending eval (agent reported done; awaiting `.evaluate-*` to score)
2026-05-04T15:19:16.952013103+00:00 PendingEval → Done (evaluator passed; downstream unblocks)