clock property
What clock.now() reads in everything this project renders — previews,
scenario steps, store shots — or null for flutterware's own
pinnedClockOrigin.
Not a plugin, for the same reason changes and identity are not: four plugins render a screen that can show a date, and a date that differs between them is a project with four answers. It is one setting because the thing it buys — two renders of the same code producing the same picture — is only true if everything renders at the same instant.
There is deliberately no "the wall clock, always" here. That is the
default this replaced: it makes every capture differ from itself daily,
and previews and store shots have no per-run override to climb back out
with. A single scenario run that wants today's date says --clock now.
It reaches whatever flutterware itself starts. A bare flutter test reads
no manifest, so a suite run that way stays on pinnedClockOrigin unless
the host says otherwise — FW_CLOCK, or the fw.clock dart-define,
which is that lane's spelling of this same setting and deliberately the
same name.
Implementation
final DateTime? clock;