set_ui_review_scenario_cap
Set this web_app project's ui-review scenario budget, or reset it.
``scenario_cap`` is an integer from 6 through 32, or ``null`` to reset to
the platform default of 12. The screenshot cap derives from it and moves
with it, so the two can never starve each other.
Raising is always allowed, including from a completely full manifest.
LOWERING is refused when the default branch already declares more scenarios
or screenshots than the smaller budget allows, and is also refused when that
manifest cannot be read — both caps are enforced when keelen pushes and not
in your CI, so an over-cap manifest fails every push while CI stays green.
On a project with the retained evidence catalog (the response carries
``evidence_lifecycle: true``) the same parameter is a CAPTURE-RUN setting:
it limits how many scenarios and screenshots one capture run holds, a pull
request that needs more is split into capture batches, and the catalog
keeps every scenario whatever the value. The response then also reports
``catalog`` (the retained counts) separately from ``run_limits``, and a
lower is not refused for catalog size once the catalog is migrated.
Read ``project_status.ui_review`` first to see the live occupancy. Repeated
calls with the same value change nothing.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | ||
| scenario_cap | No |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |