Reviews

The Reviews destination in the Repair group inspects retained commit reviews: what the model reviewer of review-commit read and answered before a commit was created. A push retains nothing to inspect; review-push reads the attestation each commit carries, shown under Install → Carried attestations. The screen has the same local control authorization boundary as the other Repair screens. It does not run a model, retry a commit or change credentials.

#Read an exchange

1. Choose Reviews, then Refresh. The initial screen says the records have not been read; loading and failure are distinct states.
2. The table lists retained IDs and their recorded outcome, or Unreadable result. An empty inspected directory is different from a missing or unreadable directory, which is an error.
3. Select a row. The detail pane re-reads that exact record and displays its ID, retained directory, outcome and full cause. Refresh clears the old selection; a failed request cannot leave a prior result presented as current.

#Interpret the result

Passed means the reviewer passed that exchange, not that Git created the commit. Source finding names a grounded finding to repair. Review unavailable names the failed review operation or dependency; it does not ask you to amend source merely because a provider failed.

Unreadable records keep their exact filesystem or JSON cause. A missing result is not guessed to be a pass, an unfinished exchange or a legacy record. The directory identifies the retained envelope and answer for further inspection.

#Shared command

The screen uses reviews/list and reviews/show, one tama request process per operation. These call the same reader as tama reviews list and show. Native request failures are shown and reported under tama.reviews.list or tama.reviews.show. The screen offers no publication or provider-repair mutation.

#Stage session-owned changes

The Session-owned staging panel above the retained reviews accepts a session identity and repository checkout. Inspect changes computes a candidate without publishing the index; Stage session changes publishes the recorded deltas atomically. Both show the changed paths, successful receipt calls and candidate tree. A conflict, missing receipt or failed Git operation displays its full cause and reports it under tama.stage.

The panel uses the typed stage native request and the same implementation as tama stage --session. It never invokes a shell staging command, compiler or installer. Working files remain untouched, unrelated staged entries remain in the index, and a candidate tree is not a qualification verdict.

#Harsh review rounds

The Harsh review rounds panel below staging takes a checkout path and Read rounds lists the rounds of harsh review recorded for the commit it is making: each round's reviewer (a session, the declared judge or the operator), the staged tree it covered and its findings, and each finding recorded as an Oko defect. review-commit lets that commit through only once a round by a reviewer other than its author, over the exact staged tree and message, found nothing. The panel uses the reviews/harsh native request, the same reader as tama reviews harsh show; an unreadable register is shown as the failure it is and reported under tama.reviews.harsh.