request_review: true when creating or updating an Erdo page to check its layout,
forms and compliance copy with the page’s judge lenses. The save returns a review
object containing id, page_id, and status: "running" before browser capture,
Lighthouse and the judges finish. The page is already saved.
Use the CLI for a material edit to a live page:
--no-wait. Read the result later without running another review:
erdo pages deploy also accepts --request-review and --no-wait. Each explicit
request gets its own ID, including another request for unchanged content. Re-reading
an existing ID does not run the judges again.
REST and MCP
Create withPOST /v1/pages or update with PUT /v1/pages/:pageID, including
request_review: true. Read the latest explicit review using:
erdo_deploy_page, erdo_update_page, and
erdo_get_page_content_review. The reader takes page_id and an optional review_id.
Reads require access to the page in its owning organization. A review ID belonging
to another page or organization is not returned.
The review moves from running to ready or failed. A ready review contains
result, with the full issues, summary, judges and available lighthouse
measurements. A page without applicable lenses returns result.reviewed: false
with a reason. A failed review contains error and completed_at. Reviews
interrupted by a server restart become readable failures after twenty minutes;
request a new review to try again. The CLI exits unsuccessfully when a review fails.
The in-chat builder and edit tools continue to receive findings inline so they can
repair the page in the same turn. Reviews requested through page saves use the
same judges and do not open a separate Activity item.
For reviews of external URLs, use Page reviews.
