landing-report

You can view version slot allocations by generating a landing report, which provides a read-only snapshot of which VERSION slots are currently claimed by open PRs and what work is in progress across Conductor workspaces.

Yes, checking workspace status without mutating state is the core function of the landing report. It surfaces read-only visibility into workspace activity and version queue allocations to help you plan releases safely.

A landing report is used for version queue management to audit current activity and the planned release cadence. It shows which Conductor workspaces have work in progress so you can decide what to work on next.

Yes, you need a workspace with GStack to generate a version queue and ship plan dashboard. The skill requires access to version and PR data to render the read-only dashboard for review.

Workspace-state awareness surfaces where work is blocked by providing a snapshot of the upcoming ship plan and current activity across Conductor workspaces. This read-only visibility helps teams identify accelerating or stalled work without altering data.

The limitation of this read-only dashboard is that it cannot mutate state. It is designed strictly for reviewing the version queue and workspace status, meaning you cannot claim version slots or modify PRs directly through the landing report.