The exemption was resting on my reading that "optional means use the default" on
a create. It rests on the code now: both endpoints return `CreatedResult` (201),
and `CreateChannelFromLineupClearField` documents that for the
template-inheritable advanced fields a null/omitted override means INHERIT the
template value, with a separate explicit `clear` list to force NONE.
So omission there is a THIRD STATE, not an oversight, and annotating those
requests `Complete<T>` would collapse inherit into explicit-null — a bug, not
missing coverage. Worth stating in the record because the exemption otherwise
reads as the same category-sort that produced the two live misses.
Also corrects two lines in the guard's own comment that survived the M4 fix: one
still attributed optionality to the generator script rather than to the schema's
`required` array, and one described the synthetic type's `optionalMember?` as a
shape the generator "does NOT currently emit" — it does, for the two live cases.
Adds the SPA pointer to the `docs/README.md` task-signal map row for a
hand-built request object, so the type-system half is reachable from the router
rather than only from the record.
Verification on this tree: typecheck 0, eslint 0, web build 0, 1200/1200 web
tests, 874 passed 2 skipped in scripts/tests, catalog check clean.
Decisions-Edit: yes