wi mutators: echo resolved ref+title and warn/refuse on cross-project target

Sub-tickets

Questions

Activity

• wi-cli-venus created · 7w ago
• wi-cli-venus commented · 7w ago
  Reported by pm-venus-cc (Elazar-flagged). Mutators (close/status/cancel/assign/block/rename/set-parent) accept a BARE number resolving to the GLOBAL id, while 'wi ls <project>' shows per-project refs (VENUS-57=global 1393; global 57=a Pluto CR). 'wi close 35/50/57' silently mutated 7 already-done PLUTO CRs (dup completed events + refreshed closedAt) while intended venus items stayed open — command echoed success. 'wi show VENUS-NN' (ref form) resolves correctly => defect is mutator asymmetry + silent output. Repro: cli-scripts/wi ~lines 280-308 status/assign/block/rename discard the API resp and echo bare 'ok'; HTTP resp already carries the resolved item. Fix spec (PM call): (1) ALL mutators echo what they touched: 'closed VENUS-57 <title>' (ref+projectSlug+title) from API response, never silent/ok. (2) Cross-project guard: bare-number handle resolving to project != caller-context project must refuse or require --force; ref-form (KEY-N) passes through. (3) Server wi-http-server resolveId: return resolved {ref,projectSlug,title} on every mutator response so CLI echoes without an extra GET. Out of scope: scrubbing the 7 stray completed events on Pluto CRs (global 35/36/37/38/46/50/57) — separate pm-venus/pm-pluto call; done-state already correct.
• wi-cli-venus statusChanged · 7w ago
  coder-basquetwi-cc working part 1 (echo)
• wi-cli-venus statusChanged · 7w ago
  verify exit code
• wi-cli-venus assigned · 7w ago
  coder-basquetwi / coder
• wi-cli-venus commented · 7w ago
  Part 1 (echo) shipped: commit c6efa42 — every mutator echoes 'verb REF [slug] title', exit 0. Part 2 (BWI_PROJECT + server expectProject guard) held pending llmmsg-srv maintainer rotation ack. Side incident during part-1 push: gitpush swept 4 .llmmsg-env (LLMMSG_HUB_BEARER) into c6efa42 → private repo ElazarPimentel/basquetWi main; remediated in 7033299 (.gitignore + rm --cached, 0 tracked now); history-purge deferred to Elazar, rotation to llmmsg-srv maintainers.
• wi-cli-venus commented · 7w ago
  Code-complete, both parts on main: part1 echo c6efa42, part2 cross-project guard 860cd52 (reviewed by PM, T1-T10 matrix incl. incident repro T4). NOT closing — guard is inert until (a) wi-http redeployed [db/bin-venus lane; stale whey:8042 flagged] and (b) BWI_PROJECT lands in agent client-envs [PM+ops rollout]. Open follow-ups: bearer rotation (llmmsg-srv maintainers) + c6efa42 history-purge (Elazar).
• wi-cli-venus statusChanged · 7w ago
  code-complete; awaiting wi-http redeploy + BWI_PROJECT client-env rollout
• wi-cli-venus statusChanged · 7w ago
  live: bypass + still working part-followups
• wi-cli-venus completed · 7w ago
  Shipped + production-verified on canonical venus wi-http (restarted ~14:14 UTC). Part1 echo c6efa42, part2 cross-project guard 860cd52. Verified live: 409 cross-project refusal (BWI_PROJECT=venus wi status 1398), KEY-N bypass + echo. whey:8042 BWI-16 leftover confirmed fully drained (nw-whey). Guard now inert-until per-agent BWI_PROJECT rollout → tracked as follow-up. Open side-items (not blockers): bearer rotation (llmmsg-srv maintainers), c6efa42 history-purge (Elazar).