The OpenAPI document describes labels made and removed, a commit's check, and a file read by path

Intent: a harness can manage labels and read a commit's verdict through OpenAPI alone.

Done:

[ ] Rows for POST ${REPO}/labels, DELETE ${REPO}/labels/{id}, GET ${REPO}/commits/{oid}/check and GET ${REPO}/contents/{path}, each with auth, body/query fields as its handler reads them, success status when not 200, and refusals by stable error code; summaries say the answer's shape as answered today
[ ] Placed as one block directly after the ${REPO}/tags row, changing no other row
[ ] test/openapi.test.ts still passes, and a new test asserts each new path and method is in the served document

Files: src/contract/openapi.ts, one test. #4846 adds the GET labels and commits rows elsewhere; do not add those here.

The OpenAPI document describes labels made and removed, a commit's check, and a file read by path #5113