Data

{
  "owner": "mirendev",
  "repo": "runtime",
  "number": 1432,
  "verdict": "ready",
  "event": "comment",
  "summary": "This does what MIR-2199 asks. `miren detective --help` now describes Workbench as a public beta and no longer says it has to be enabled for each organization. The regenerated `docs/docs/command/detective.md` matches the new `workbenchDescription` constant in `cli/commands/workbench.go` line for line. Nothing else in `cli/` or `docs/` still describes Workbench as a Labs feature or needing Discord access. The remaining \"Ask Workbench\" strings at `workbench.go:185` and `workbench_ui.go:429` are just the chat banner, and they still read correctly.\n\nThe code is ready. I'm not recommending approval because of when it should merge, which is your call. You noted that Cloud still gates access behind a flag that's off by default, and its 403 still sends people to Discord. If this lands first, a user in an org without the flag will see \"available to all Miren Cloud users\" in `--help` and then get the old denial message. A human should decide whether to hold this until the Cloud change ships, or merge now and accept a short window where the CLI and Cloud disagree.",
  "posted_to_pr": true,
  "draft": true,
  "head_sha": "f091f80ef56237c1f20f1409e975f4aa74d8624f"
}