FlashForge Creator 5 / 5 Pro: no connection tutorial #19

The FlashForge Creator 5 and Creator 5 Pro are fully supported everywhere except the
connection tutorial. Both share ONE tutorial — a single new series covering the two models.

Current state

Already done, nothing to change:

• data/printers/ffg_printer_models.json — Creator 5 is id 5, Creator 5 Pro is id 6.
• assets/img/ffg_printers/creator_5.png + creator_5_pro.png — both present.
• renderer/printers/flashforge/probe.js — ffgModelIdFromMachineModel() resolves both
  (the "Pro" test runs first, since creator 5 pro contains creator 5).
• Tool-changer (T1…Tn), the imposed CFS colour palette (gated on model ids 5/6), and the
  UDP serial discovery are all implemented and verified against a real Creator 5 Pro (fw 1.9.2).

Missing: any entry in renderer/printers/flashforge/tutorial.json.

Why it matters — the failure is worse than "no tutorial"

FlashForge declares several models, so an unmatched one does not fall through quietly: it opens
the model picker (_ptShowModelPicker in renderer/inventory.js). A Creator 5 owner tapping
"Connection tutorial" today gets a grid of four Adventurer machines, none of which is theirs, and
has to pick one at random.

What to do

1. Add a new series to renderer/printers/flashforge/tutorial.json with the Creator 5's own
   screenshots (steps go in assets/img/tutorials/flashforge/<series-id>/), and two models
   entries — creator5 and creator5pro — BOTH pointing at that one series.
2. Add the step bodies as i18n keys in all 9 locales via npm run i18n:add
   (existing naming: tutoFlashforgeAd5xStepN).
3. Copy assets/img/ffg_printers/creator_5{,_pro}.png into
   assets/img/tutorials/flashforge/models/ — the picker reads from that folder, which is
   separate from ffg_printers/.
4. Check the resolution end to end: the hint is the catalogue name ("Creator 5",
   "Creator 5 Pro") and openPrinterTutorial matches it against the tutorial model id and
   label. "Creator 5" is a prefix of "Creator 5 Pro" — verify the Pro does not resolve to
   the plain model, or vice versa, by running both catalogue names through the resolver.

Blocked on

The Creator 5's own screen captures. The existing AD5X walkthrough shows a different machine's
screen (Basic Info bottom-right → Serial No. + IP → gear → Network Mode → Printer ID), and
the Creator 5 is known to differ at the network level — it answers
{"code":1,"message":"SN is ..."} where an AD5X reports its model, and add-flow.js already
carries a branch for a candidate that "carries no model/serial", citing it. A screenshot of the
wrong machine during setup is exactly where a mistake costs the most, so the AD5X steps must not
simply be reused.