Fix Accepting a change set

Rex tab window:01a1b262-4e2b-723a-8cab-57bc8caf8004 was already closed.
Deleted branch cs/fix-accepting-a-change-set.
Deleted origin/cs/fix-accepting-a-change-set.
Updated main in /home/rhiza/code/rhiza.
rhiza: step close-out: pass
rhiza: step ship: entered, visit 1
go build -ldflags "-X main.version=223a9233" -o /home/rhiza/bin/rhiza ./cmd/rhiza
/home/rhiza/bin/rhiza rex install
Installed Rhiza's app actions and key mode in /home/rhiza/.config/rex/rhiza.lua (0 written, 2 unchanged); Rex reloaded.
Ran .rhiza/workflows/ship.sh.
rhiza: step ship: pass
rhiza: run 01M6RYM3KB9MPB5R6BY5FT1EBB succeeded
Run 01M6RYM3KB9MPB5R6BY5FT1EBB succeeded

- Workflow: ship-change
- Change set: 01M6RXNQFZX8YM80WFZJCXBRAJ: Fix Accepting a change set
- Worktree: /home/rhiza/code/rhiza.fix-accepting-a-change-set
- Autonomous: yes
- Started: 2026-11-06T17:31:11Z

## Steps

- build/build (visit 1): pass, then build/render: 1 of 1 leaves passed
- build/render (visit 1): pass, then build/check: exit 0
- build/check (visit 1): pass, then review/code: exit 0
- review/code (visit 1): pass, then review/review: exit 0
- review/review (visit 1): pass, then review/render: 5 of 5 checks passed
- review/render (visit 1): pass, then render-pr: exit 0
- render-pr (visit 1): pass, then open-pr: exit 0
- open-pr (visit 1): pass, then wait-pr: exit 0
- wait-pr (visit 1): pass, then pr-green: held after 12 checks
- pr-green (visit 1): pass, then signoff: exit 0
- signoff (visit 1): pass, then rebase: approved by rule autonomous
- rebase (visit 1): pass, then wait-rebased: exit 0
- wait-rebased (visit 1): pass, then rebased-green: held after 12 checks
- rebased-green (visit 1): pass, then land: exit 0
- land (visit 1): pass, then wait-landed: exit 0
- wait-landed (visit 1): pass, then landed-green: held after 12 checks
- landed-green (visit 1): pass, then rebase-merge: exit 0
- rebase-merge (visit 1): pass, then wait-rebased-merge: exit 0
- wait-rebased-merge (visit 1): pass, then rebased-merge-green: held after 1 checks
- rebased-merge-green (visit 1): pass, then merge: exit 0
- merge (visit 1): pass, then wait-main: exit 0
- wait-main (visit 1): pass, then main-green: held after 1 checks
- main-green (visit 1): pass, then close-out: exit 0
- close-out (visit 1): pass, then ship: exit 0
- ship (visit 1): pass, then end: exit 0

## Leaves

- run-worktree-carries-accept (step build/build): passed: attempt 2: verifier passed
  - attempt 1 builder, session e168054c-cd47-4757-829d-01a1b1ea31f1: pass (said done)
  - attempt 1 verifier, session aabc1cf7-9fca-46aa-a5ac-01a1b1f613a8: fail (verifier found 2 problem(s))
  - attempt 2 builder, session 43e68393-8fa4-46e8-8ade-01a1b20f2027: pass (said done)
  - attempt 2 verifier, session aa46bbcf-9e82-4cce-a8de-01a1b239ff7e: pass (Evidence written by the verifier)
  - attempt 1 finding f1: The acceptance requires the new testscript to show that `rhiza ship land` in the worktree commits the accept entry on the branch. cmd/rhiza/testdata/script/run-worktree-carries-accept.txtar never runs `rhiza ship land`; the only mention is in its header comment. It asserts only that the entry is untracked (`git status` shows `?? .rhiza/log/`) and that `change show` reports accepted. Nothing checks that the accept entry is committed on the run's branch after land. The script passes with `go test -trimpath ./cmd/rhiza -run TestScripts/run-worktree-carries-accept`, but that leaves this point of the acceptance unchecked. Fix: in the worktree, add a fake gh, a bare origin and a pushed branch (as in ship-land-branch-build.txtar), run `rhiza ship land --change <cs>`, then assert the accept entry file is tracked in the branch's HEAD (for example `git ls-files .rhiza/log/<cs>` lists it, or `git status --porcelain` no longer shows it).
  - attempt 1 finding f2: The acceptance says the testscript 'starts a run on it (a new worktree, and again with the worktree already existing on its branch)'. The script uses `rhiza session start` both times and never runs `rhiza run start`. The two commands share changeWorktree.open, so the code path is the same, but the run entry point the acceptance names is not exercised. Fix: start the second case (or both) with `rhiza run start` using the fake rex (or `--dry-run` where it sets up the worktree), and assert that the reused worktree then reports accepted.

## Checks

- compliance (step review/review): passed after 1 cycle
  - cycle 1: passed, check session 737ea8c9-e283-41c8-b508-01a1b260c2ac pass (said done)
  - round 1 (cycle 1): 1 finding, 0 confirmed
    - f1 nit at cmd/rhiza/testdata/script/run-worktree-carries-accept.txtar:76 on run-worktree-carries-accept: The acceptance says the run starts on the change set 'again with the worktree already existing on its branch'. The script covers the reused-worktree case with a second change set (Carry again), since the first one has already landed by then. This meets the acceptance's intent: a worktree set up while the change set was proposed picks up the main clone's later accept, and ship land commits it. The 'entry is there' check at that point only matches '?? .rhiza/log/' and does not name the change set's directory, although the pushed-tree check after ship land does pin the exact untracked entry.
- quality (step review/review): passed after 1 cycle
  - cycle 1: passed, check session 24b06b7c-aebc-4c33-839f-01a1b2611109 pass (said done)
  - round 1 (cycle 1): 2 findings, 0 confirmed
    - f1 nit at internal/api/session.go:607 on run-worktree-carries-accept: worktreeWorkspace's doc comment still says it copies entries only so the log has change set cs ('a change set opened since HEAD's commit is not checked out'); it now also copies main-clone entries of a change set the worktree already has (an untracked accept). Only the inline comment says so.
    - f2 nit at internal/api/session.go:630: Whenever the main clone has the change set's log dir, the worktree workspace is opened (and folded) a second time even if copyChangeSetLog copied nothing; copyChangeSetLog could report whether it copied anything so the reopen is skipped on the common path.
- qa (step review/review): passed after 1 cycle
  - cycle 1: passed, check session 9bc184a1-1ee5-4504-8846-01a1b2615b31 pass (said done)
  - round 1 (cycle 1): no findings
- scope (step review/review): passed after 1 cycle
  - cycle 1: passed, check session 64724d64-34cf-4457-bb7d-01a1b261ab28 pass (said done)
  - round 1 (cycle 1): no findings
- model (step review/review): passed after 1 cycle
  - cycle 1: passed, check session 49d07cf4-6796-4963-879d-01a1b26213cb pass (said done)
  - round 1 (cycle 1): no findings

## Code checks

- step review/code: pass

## Sign-offs

- signoff (visit 1): approved by rule autonomous

## Sessions

- build/build, session e168054c-cd47-4757-829d-01a1b1ea31f1: tokens input 36, output 5847, cache creation 42405, cache read 1099169; helper tokens input 0, output 0, cache creation 0, cache read 0
- build/build, session aabc1cf7-9fca-46aa-a5ac-01a1b1f613a8: tokens input 34, output 5193, cache creation 41303, cache read 926981; helper tokens input 0, output 0, cache creation 0, cache read 0
- build/build, session 43e68393-8fa4-46e8-8ade-01a1b20f2027: tokens input 52, output 11587, cache creation 50486, cache read 1764932; helper tokens input 0, output 0, cache creation 0, cache read 0
- build/build, session aa46bbcf-9e82-4cce-a8de-01a1b239ff7e: tokens input 68, output 10235, cache creation 50538, cache read 1935699; helper tokens input 0, output 0, cache creation 0, cache read 0
- review/review, session 737ea8c9-e283-41c8-b508-01a1b260c2ac: tokens input 28, output 4209, cache creation 40962, cache read 787177; helper tokens input 0, output 0, cache creation 0, cache read 0
- review/review, session 24b06b7c-aebc-4c33-839f-01a1b2611109: tokens input 38, output 4034, cache creation 42020, cache read 985787; helper tokens input 0, output 0, cache creation 0, cache read 0
- review/review, session 9bc184a1-1ee5-4504-8846-01a1b2615b31: tokens input 26, output 7820, cache creation 41071, cache read 780968; helper tokens input 0, output 0, cache creation 0, cache read 0
- review/review, session 64724d64-34cf-4457-bb7d-01a1b261ab28: tokens input 12, output 1692, cache creation 30998, cache read 303823; helper tokens input 0, output 0, cache creation 0, cache read 0
- review/review, session 49d07cf4-6796-4963-879d-01a1b26213cb: tokens input 16, output 1791, cache creation 33350, cache read 435638; helper tokens input 0, output 0, cache creation 0, cache read 0

Totals: tokens input 310, output 52408, cache creation 373133, cache read 9020174; helper tokens input 0, output 0, cache creation 0, cache read 0