pj 52ee0ad424 ci(examples): one dispatch workflow for every example ...

folio.yml and replay-ui.yml ran the same operation: build sanderling for
a platform, bring a target up, run a spec against it, classify the trace,
upload the run. They are now one matrix over four examples, each naming
its own runner.

The job is named for what it fuzzes. 'dogfood' named why we run it, not
what runs, the same error as a diagnostic that reports a motivation
instead of an observation.

The matrix is computed by a plan job because jobs.<id>.if cannot read the
matrix context, so a static matrix has no way to leave a leg out. Seeds,
budgets, timeouts, runners and artifact names are unchanged.

2026-08-16 01:22:32 +05:30

..

actions

ci(examples): add the replay-ui fixture action

2026-08-16 01:22:25 +05:30

scripts

test(ci): cover the folio classifier's verdicts

2026-08-16 01:08:45 +05:30

workflows

ci(examples): one dispatch workflow for every example

2026-08-16 01:22:32 +05:30