@dashai/cli 0.30.2 → 0.31.1

package/README.md

@@ -847,7 +847,7 @@ dashwise module ship my-module --workspace acme --bump patch
 dashwise module ship my-module --commit-sha <full-40-character-sha> --installation 156
 ```
 
-Before anything is queued it prints the revision it will release (`Releasing <sha> from main`, from the server's release plan) and names newer work on another branch that is not included. If the release is still building at `--timeout` (exit 4), it prints `dashwise module ship <slug> --build <id>`, which waits for that build and then installs it, without queueing another release. `--yes` skips the install question when nothing is lost; it never accepts data loss. A move that loses data is accepted only by answering in a terminal; without one, it is refused and the refusal prints the `module install --accept-data-loss <drift_hash>` re-run line. **Refused inside an AI agent session**: an agent may release (`module release`), but taking a module live is a person's act. Exit codes are `module release`'s while building (4: still building) and `module install`'s after.
+Before anything is queued it prints the revision it will release (`Releasing <sha> from main`, from the server's release plan) and names newer work on another branch that is not included. If the release is still building at `--timeout` (exit 4), it prints `dashwise module ship <slug> --build <id>`, which waits for that build and then installs it, without queueing another release. `--yes` skips the install question when nothing is lost; it never accepts data loss. A move that loses data is accepted only by answering in a terminal; without one, it is refused and the refusal prints the `module install --accept-data-loss <drift_hash>` re-run line. **A person takes it live** (DW-323): inside an AI agent session, or when Dashwise answers `GO_LIVE_NEEDS_PERSON` (its person gate refuses CLI tokens a direct go-live), the install half files a go-live request for the existing installation instead, prints the module's Live tab link and waits up to `--wait <seconds>` (default 900; 240 inside an AI agent session, under a coding agent's 10-minute tool-call limit) for a person to approve or decline it there. An approval that is still running the update counts as waiting, not as a failure. A module's first installation in a company is created by a person in Dashwise. Exit codes are `module release`'s while building (4: still building) and `module install`'s after; a proposal ends 0 (live), 3 (declined or replaced by a newer proposal), 1 (the update failed after the approval, or the request cannot be read) or 5 (still waiting; the proposal stays open). To wait longer than one tool call, use `--wait 0` and run the same command again to check: while the proposal is open it files nothing new and ends 5, and 0 once it is live. `--json` prints the proposal's outcome as one object (`go_live_request_id`, `status`, `outcome`, `approve_at`, `awaiting_person`). `module install` behaves the same.
 
 ### `dashwise module build-log [slug] <buildId>`