docs: explain pending release-pack model choices and assessments
Documents optional configured-model choices and assessment limits for API #1288 / App #2266. The guide and response brief contained model_choices, but the actual create/update request briefs still duplicated an older strict schema and omitted it. Both write routes now reference the shared ReleasePackBrief; all other request-brief semantics are unchanged.
A focused regression resolves each actual route's request body, verifies optional strict seven-key choices with 1–200-character values, and confirms estimate/retry accept no replacement choices. It failed on both write routes before the fix (2 failed, 2 controls passed), then all four cases passed. The pending guide, original full-pack/retry intent, assessment-only limits and fresh-analysis restriction remain unchanged; this does not establish commercial permission or generation availability.
Compared the actual API 99613105855378502e1145ee5fa9e8dedfc36074 parser and both route adapters before editing. Its brief parser is byte-identical to the existing pinned API. This Docs-only correction preserves the existing API pin until Packs supplies its matching fixture successor; no API checkout/fixture was edited.
Validation at 609b7d70bb94640e66a9d256d54bc14671195d32:
- 168 tests / 50 suites, 11 docs checks, 38 response-producer tests, 2 inventory tests, types and lint passed.
- Production Webpack build passed. Exact-head normal CI test/build, CLI guide and Vercel build status passed; native rerun remains coordinator-owned.
- Remote original inventory check passed. The following shared-fixture check is RED until Packs adopts the new generated fixture; no checker was weakened.
- Only the two request-brief references, focused test and required hashes/derived text changed from
99bdde2.
Frozen Content SHA-256: 61b972a3cbd4821e349a4fdbc678f26839c866ae692982fe357b3d54dc8ea288.
Proposed API fixture SHA-256: a19c822fe2b0b2a42f5e4cd8cfe0329899ab7e352fe981d5bb362ebaa63dcc24.
Keep draft/unmerged for paired API fixture adoption, final pin/checks, independent review and the exact successor's native request expansion. No browser/login/provider/product API/spend/deployment operation was performed; the coordinator owns Docs-before-API release order.