Current canonical ownership
Draft PR #160 / branch fix/blob-size-preflight-20260811 is the sole active Inkspan writer for this converter MIME-override resource boundary. Do not treat exact head/check snapshots in this issue as lifecycle authority; refetch PR #160, protected main, formal reviews/threads, live governance, and every applicable exact-head workflow immediately before any action. Active-PR source/tests and the PR body are higher-authority than this planning issue; protected main remains shipped truth until integration.
Acceptance contract
An explicit mimeType must be a string no longer than 1,024 UTF-16 code units. A 1,025-code-unit override fails closed before payload conversion or output interpolation; the exact 1,024 boundary remains accepted and emitted unchanged. The ceiling is Inkspan-local resource policy, not an IANA/HTTP limit. Omitted MIME behavior, sniffing/fallback semantics, accepted in-bound parameter text, maxBytes behavior, payload preflights, Node/browser parity, package behavior, and standalone no-service operation remain intact. Rejected MIME values are not trimmed, normalized, parsed, inferred, reflected, or coerced.
The canonical #160 regression corpus must machine-check this boundary, including rejection before Blob payload reads. No network, persistence, authorization, tenancy, credentials, model/provider, deployment, migration, retention, or durable-audit authority moves into Inkspan.
Evidence rule
Predecessor workflow/review results are historical only. Pending, queued, skipped, cancelled, absent, stale, predecessor, status-only, or model-only evidence is non-passing. Exact-current-head technical success does not substitute for qualifying independent approval or then-live governance.
Integration boundary
Keep this issue open until #160 integrates under then-live governance. Keep #160 Draft/unmerged while #118 owns the frozen protected v0.6.0 publication/provenance boundary and exact-current-head gates plus qualifying independent approval remain incomplete. Do not create a competing converter writer, transfer predecessor evidence, self-approve, weaken gates, force-push/destructively rebase, move protected main, or fabricate release identity.
Current canonical ownership
Draft PR #160 / branch
fix/blob-size-preflight-20260811is the sole active Inkspan writer for this converter MIME-override resource boundary. Do not treat exact head/check snapshots in this issue as lifecycle authority; refetch PR #160, protectedmain, formal reviews/threads, live governance, and every applicable exact-head workflow immediately before any action. Active-PR source/tests and the PR body are higher-authority than this planning issue; protected main remains shipped truth until integration.Acceptance contract
An explicit
mimeTypemust be a string no longer than 1,024 UTF-16 code units. A 1,025-code-unit override fails closed before payload conversion or output interpolation; the exact 1,024 boundary remains accepted and emitted unchanged. The ceiling is Inkspan-local resource policy, not an IANA/HTTP limit. Omitted MIME behavior, sniffing/fallback semantics, accepted in-bound parameter text,maxBytesbehavior, payload preflights, Node/browser parity, package behavior, and standalone no-service operation remain intact. Rejected MIME values are not trimmed, normalized, parsed, inferred, reflected, or coerced.The canonical #160 regression corpus must machine-check this boundary, including rejection before Blob payload reads. No network, persistence, authorization, tenancy, credentials, model/provider, deployment, migration, retention, or durable-audit authority moves into Inkspan.
Evidence rule
Predecessor workflow/review results are historical only. Pending, queued, skipped, cancelled, absent, stale, predecessor, status-only, or model-only evidence is non-passing. Exact-current-head technical success does not substitute for qualifying independent approval or then-live governance.
Integration boundary
Keep this issue open until #160 integrates under then-live governance. Keep #160 Draft/unmerged while #118 owns the frozen protected
v0.6.0publication/provenance boundary and exact-current-head gates plus qualifying independent approval remain incomplete. Do not create a competing converter writer, transfer predecessor evidence, self-approve, weaken gates, force-push/destructively rebase, move protected main, or fabricate release identity.