Forms: document date / time fields (#944)
Forms.md — nine question types, a "Date and time fields" section covering the
three modes and why it is one type with a setting rather than three types, the
is_after / is_before row on the operator table plus a note that the menu narrows
per trigger type, and the timezone warning.
Dev guide — new §3b on date fields: the mode, the stored formats, why these are
NAIVE values and must not be converted, why the operators compare as strings
(ISO-8601 lexical order is chronological order), and opsFor() narrowing the menu
without narrowing the API. Also: config must be MERGED not replaced (an earlier
buildRulesForSave dropped date_mode), the system prompt is part of the feature
and drifts silently (section was whitelisted in #940 but never described to the
model, so it was never emitted), and adding datetime was the first real test of
the deliberate three-renderers decision.
Every app file named verified to exist; every wiki link resolves.
Forms: document sections, conditional logic and field identity (#940-943)
Forms.md — nine types (section added), a Sections section, a Conditional
questions section with the operator table and the three deliberate behaviours
(hidden is not required; hidden answers are not stored; conditions look
backwards only), and what "removed" means on a submissions column.
New Form-Sections-and-Conditional-Logic-Developer-Guide.md — the colour-keyed
file table, why field identity had to be fixed first (with the old positional
sync quoted), the three identity spaces (id / "idx:N" / _key), why a section is
a row rather than a table, the backwards-only rule as the thing that makes
cycles impossible by construction, the two evaluators and the one case table
that keeps them honest, soft delete, version-fork remapping, why the three
renderers were deliberately NOT merged, the AI-apply trap, and the upgrade note
for REST clients.
Every app file named verified to exist; every wiki link resolves.