Picking the video type and being told the field is required. A `<select>`
whose `value` matches none of its options still displays the first one, so a
required field with no default showed "محاكاة تفاعلية" as though it had been
chosen while the form held nothing - and choosing it fired no change event,
because it was already what the browser had selected. The only way through
was to pick a different type and come back.
An unset required choice now gets a placeholder row, so what is displayed and
what is stored agree and the first real pick is a real change. It is disabled,
so it cannot be picked back once something has been. Optional fields keep
their "none" row and fields with a default still get neither.
`video_type` is the only required choice without a default on the platform,
and it arrived yesterday - the form had never been asked for one before.
The rule lives in `selectOptions.ts` rather than inline, because a `<select>`
showing something other than what the form holds is wo…
Ask motion video for six things, and each agent once
Three changes, all of them to what the platform wrapped around the notebook.
No prompt the notebook wrote is altered; what is added is appended and named.
The form asked for twenty-four fields to make a four-minute video. It now asks
for three: the type, the length, and the content - plus objectives, audience
and characters, each optional and each with a real default behind it. The
seventeen that left the form did not leave the pipeline: `full_input()`
expands the brief into the same `VideoInput` the notebook built, with the
notebook's own values. The content box opens at eighteen rows, because the
thing being pasted into it is a lesson.
Style checks report instead of refusing. Thirty-three of fifty-two checks used
to raise, and a raise costs the answer again - per scene, on a per-scene agent.
Three still refuse, the three without which a later step breaks rather than
disappoints: scene numbers sequential from one, the scripts covering exactly
the scenes that need one, and an interac…
Keep the author's header at the gate, and let the gate add and export
Four things wrong at the review gate, three of them one cause.
The structure was protected from the agent's edits and the header was not.
Every header field goes into the outline prompt and comes back out of it, and
`restore` returned `{**outline, "chapters": restored}` - so the title, the
audience, the description and the page count stayed whatever the agent sent
back. An audience written carefully by the designer returns paraphrased and
shorter; a page count typed into a form returns as the agent's number, and it
is the number every later stage divides its budget by. Restored now, with one
exception that is the rule rather than an exception to it: a field the author
left blank has no author's version to put back, and a description written for
a book that had none is the agent doing its job.
The fourth: `Chapter.outcome` is required in the schema with a floor of twelve
characters and the prompt prints it in the JSON it asks for, and on a real
two-chapter run both chapters came back …
The planner no longer receives the evidence it never reads, the quality
pass is off on its own measurements, the outline is held to the number of
مواضيع the page count pays for, a محور is written in one call instead of
one per موضوع, and the writer's model comes from settings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Group on the column, not on an expression holding a literal (part 2)