ContractSpec docs

OSS-first docs

These docs teach the open system first: contracts, generated surfaces, runtimes, governance, and incremental adoption. Studio shows up as the operating layer on top, not as the source of truth.

Request changes on a review

Push the review back to changes-requested with a structured list of change requests.

field.key.label
Request changes on a review
field.version.label
field.type.label
field.title.label
Request changes on a review
field.description.label

Push the review back to changes-requested with a structured list of change requests.

field.tags.label
review,request-changes,mutation
field.owners.label
field.stability.label
public

Transitions the review record to `changes-requested` with a structured list of `changeRequests` (field-scoped). Non-terminal: when the upstream subject is updated, the review system fires an internal `review.resubmit` event (not a public op) that returns the review to `pending`.

Per SEAMS §1.3 (S-11), emits exactly one `audit.event.append` with kind `review.changes-requested`.

Capability: `review.act`. Idempotency: required.