Summary

Add a project-level setting that limits the maximum number of workspaces that may run at the same time within a project and its entire tree of child projects.

Goal

Within any given project, an administrator can define a maximum number of concurrently running workspaces. The limit applies to the project itself plus all descendant projects (children, grandchildren, …), counted together as one pool.

Requirements

• Provide a project-level configuration to set the max number of concurrently running workspaces.
• The consumed count is the sum of running workspaces for the project itself and every descendant project in its subtree.
• The cap is enforced against that combined subtree count (i.e. a busy child project consumes headroom for the whole subtree).
• Applies recursively: a project that has child projects also contributes those children's running workspaces to the total.

Acceptance criteria

•  A project can be configured with a max concurrent running-workspace value.
•  The running-workspace count used for enforcement includes the project and all of its descendant projects.
•  Once the combined subtree count reaches the configured maximum, further workspace starts within that subtree are prevented according to the agreed behavior.
•  The setting, the current subtree count, and the limit are observable/verifiable.

Notes / open points

• Enforcement behavior when the limit is reached (reject vs. queue) and precedence when both a parent and a nested child define limits — to be confirmed in the design.
• Configuration surface (UI / API) to be specified during implementation.