docs: align task authentication schemas and requirements
Programs reading the task API contract do not get an explicit create-task authentication requirement, and its four 401 responses describe a numeric error the server does not send. Declare API-key or Bearer authentication for create-task, import the API-owned authentication error union, and provide examples showing text in either error or message. Existing human cURL generation already includes an API-key header.
The shared producer freezes four selected response schemas plus credential alternatives/examples. Real-route regression tests exercise missing/conflicting credentials and rejected header/Bearer keys with synthetic storage/credential leaves. Only the four task document bodies change in the complete AI reference; all 240 documents, 215 operation identities and 237 JSON blocks remain. Other request/status/success definitions, the earlier task-validation correction and runtime behavior are unchanged. The separate original #291 cleanup remains outside this documentation change. Related: recoupable/mono#318, recoupable/mono#328 and recoupable/mono#360.
API fixture companion #1103 must be accepted first; refresh this inventory pin to its actual merge. Retained Docs publication follows the actual Marketing merge through normal provenance sync. Source/fixture checks do not verify OAuth lifecycle, organization access or a real task/customer journey.
Validation: 247 API contract tests, 28 producer tests, 506 website tests, 11 docs tests, generation/reference/inventory/both-fixture checks and lint pass (Marketing: 0 errors, 39 existing warnings). API whole-project TypeScript retains the same 211 inherited diagnostics. The required normal production build passed before this candidate was committed.
API #1103 is refreshed onto actual released main 7512ee94. This website candidate remains unchanged; its preparatory API pin must be replaced by the accepted actual API merge before release.
Summary by cubic
Documents the task API authentication contract so clients reading the specification see explicit security requirements and correct 401 response shapes.
- The four
/api/tasksoperations now declare API-key or Bearer authentication. - 401 responses use the new
TaskAuthenticationErrorResponseschema, which accepts a texterrorormessagefield with examples for missing/conflicting headers and invalid credentials. - A new
build_task_authentication_contract.pyfreezes the contract, and regression tests cover the credential scenarios.
The apiSourceCommit pin is already refreshed to the released API, so no follow-up is needed for that dependency.