docs(noema): converge #673 private-reporting cancellation authority

CHANGELOG.md

@@ -3,6 +3,7 @@
 - Add a Noema-owned exact-claim evidence receipt contract whose execution and research producers serialize one canonical artifact that binds every receipt semantic field, including command/result/isolation/network or source revision/excerpt/retrieval policy. Admission accepts only a receipt ID from untrusted model output. The owner API first verifies the exact authenticated OpenCode-handoff manifest digest, canonical envelope bytes, reviewed producer-to-kind policy, and repository/head/workflow/run/attempt identity before it can construct an immutable typed index; admission then reconstructs each canonical artifact and verifies time/claim/artifact identity. The version-2 manifest now binds a separate producer-authenticated `ClaimEvidenceRequirement` containing the exact claim, independently required evidence kind, and `context` or `finding` publication authority. Raw current-head source lines are context only: they are withheld from finding-reference prompts and cannot publish a finding or `request_changes`; an explicitly producer-authorized source finding remains usable and retains exact path/line checks. Finding-free model `request_changes` and `blocked` verdicts cannot bypass receipt admission to publish a vacuous blocking review. Requirement/receipt kind mismatch, fixed-artifact semantic substitution, caller-supplied receipt dictionaries, model self-classification, stale identities, cross-kind receipts, marker-only sandbox output, noncanonical artifact bytes, and expired receipts fail closed before the GitHub publisher. This remains the owner prerequisite for ContextualWisdomLab/.github#1641 and issue #555. The reviewed `sandboxed_verify` adapter exists in owner source, but its actual central stdout/stderr/marker-to-manifest wiring and the trusted research producer are not yet integrated; exact-head hosted GREEN, immutable release, and the verified central consumer bump remain required.
 
 ## Unreleased
+- Protected #673의 read-only private-vulnerability-reporting bounded JSON response audit는 기존 16 KiB byte ceiling과 media-type gate, fatal UTF-8·duplicate-key·JSON admission을 유지하면서 streamed oversize가 이미 결정된 뒤 `reader.cancel()`이 동기적으로 throw해도 안정적인 size-limit failure를 대체하지 않도록 한다. Asynchronous cancellation rejection은 best-effort cleanup으로 유지되고 consumed reader lock은 terminal path에서 독립적으로 해제된다. Private-vulnerability-reporting setting authority, GitHub identity, provider routing, outbound policy, quarantine/security 또는 foreign domain authority를 Noema로 이전하지 않으며 이 protected source는 immutable release, deployment 또는 production outcome evidence를 대신하지 않는다. PR #673.
 - Protected #670의 contextual-orchestrator `/healthz` bounded response consumer는 advertised `Content-Length` 또는 streamed bytes가 65,536-byte ceiling을 넘은 뒤 cancellation completion을 기다리지 않고 안정적인 oversized-response 실패를 반환한다. Stalled/rejected 및 synchronously throwing cleanup은 원래 classification을 지연·대체하지 않으며 consumed reader lock 해제와 분리된다. 기존 HTTPS gateway identity, fixed retained buffer, explicit caller deadline, fatal UTF-8·duplicate-key·JSON admission을 유지하고 contextual-orchestrator service, provider/model routing, credential, outbound, quarantine/security 또는 foreign domain authority를 Noema로 이전하지 않는다. 이 protected source는 immutable release나 deployed availability/p95 evidence를 대신하지 않는다. PR #670.
 - Protected #668의 external OIDC discovery/JWKS·GitHub API bounded JSON response reader는 65,536-byte ceiling을 넘는 chunk를 확인한 뒤 `reader.cancel()` completion을 기다리지 않고 안정적인 실패를 반환한다. Stalled/rejected cancellation cleanup은 거부 classification을 지연·대체하지 않으며 terminal reader-lock 해제와 분리된다. 기존 fixed retained buffer, 10-second absolute deadline, fatal UTF-8·duplicate-key·JSON admission과 OIDC/GitHub identity·credential authority는 유지한다. 이 protected source는 immutable release나 deployed heap/p95 evidence를 대신하지 않는다. PR #668.
 - Protected #665의 Cloudflare production control-plane deploy/status/recovery bounded response reader는 기존 1 MiB byte ceiling과 fixed retained buffer, oversize-before-copy 실패-폐쇄 및 terminal reader-lock 해제를 유지하면서 byte-ceiling decision 이후 `reader.cancel()` completion을 기다리지 않고 best-effort cleanup으로 분리한다. Cancellation completion은 best-effort cleanup이므로 stalled/rejected cleanup은 안정적인 oversized-response 거부를 지연·대체하지 않는다. Cloudflare/provider authority, destination/outbound policy, credential authority, quarantine/security authority 또는 foreign domain truth를 Noema로 이전하지 않으며 immutable release, controlled production recovery rehearsal 또는 deployed p95/heap evidence를 대신하지 않는다. PR #665.