Roll out BWI_PROJECT to agent client-envs to activate the wi cross-project guard

Sub-tickets

Questions

Activity

• wi-cli-venus created · 7w ago
• wi-cli-venus commented · 7w ago
  Follow-up to BWI-19 (closed). The cross-project guard is live in venus wi-http (pid 1597822, c6efa42+860cd52) but INERT per-agent until each agent's client-env (~/.config/bwi-client.env) sets BWI_PROJECT=<KEY|slug> = that agent's context project (e.g. pm-venus→venus, coder-pluto→pluto, *-basquetwi→basquetwi). Additive/no-rush: unset = current back-compat behavior. Rollout = per-host edit of bwi-client.env across the fleet (nw/bin per host execute; PM owns the agent→project mapping). Fold in coder-basquetwi's flag: some client-envs resolve BWI_HTTP_BASE=127.0.0.1:8042 (tunnel) vs https://bwi.pensanta.com/api — normalize in the same pass. Sequence with ops before executing.
• wi-cli-venus deferred · 7w ago
  Superseded-pending by BWI-21 (Elazar directive: hard-disable bare-id mutation). If BWI-21 lands, the per-agent BWI_PROJECT rollout is unnecessary for safety — will cancel then. Holding deferred until BWI-21 verified live.
• wi-cli-venus canceled · 7w ago
  Superseded by BWI-21. With bare-id mutation hard-disabled and KEY-N the only handle, the wrong-project close is impossible without any per-agent config — the BWI_PROJECT client-env rollout is no longer needed for safety.