Chinesezjc adba2e305a fix(code-runtime-python): make the wire-field binding exhaustive over interface keys ...

The array-based FrameFields<T> only checked that listed names were members of
the frame's keys, so a field added to a TS interface (e.g. LogMessage.seq?)
left the existing arrays a valid subset — typecheck passed, and since the
constant and Python both lacked the field the mirror test passed too. The
JSDoc's claim that runtime covered this was false.

Replace it with WIRE_FRAME_FIELD_ROLES, a per-frame map keyed by field name
(`Record<RequiredKeys<T>, 'required'> & Record<OptionalKeys<T>, 'optional'>`),
so every interface key MUST appear with a matching required/optional tag: an
added field, a removed field, a rename, or an optionality flip all fail
typecheck at the roles map (verified). WIRE_FRAME_FIELDS is projected from it
as the sorted arrays the mirror test still compares to the Python TypedDicts.

Also drop the `export` added to the promoted frame interfaces (Namespace,
ErrorClass, RunMessage, DoneErrorField, ReplyOk, ReplyErr) — nothing outside
protocol.ts imports them, so the barrel surface is unchanged and knip stays
clean.

2026-08-07 13:27:54 +08:00

..

index.ts

feat(code-runtime-python): add the fd-3 frame protocol

2026-08-07 13:27:54 +08:00

invariant.ts

feat(code-runtime-python): add the fd-3 frame protocol

2026-08-07 13:27:54 +08:00

protocol.ts

fix(code-runtime-python): make the wire-field binding exhaustive over interface keys

2026-08-07 13:27:54 +08:00