Stars for a flash dump: a programmer or TFTP dump earns what an ipctool backup earns #458

From the user group, 2026-10-11, a maintainer:

Ценность загруженного файлом дампа, снятого программатором или с консолью и TFTP примерно 25% от той, которую делает ipctool. Об этом уже говорилось.
(A dump uploaded as a file, read with a programmer or through the console and TFTP, is worth about 25% of one ipctool makes. This has been said before.)

What the code does
reports.Points (service/internal/reports/club.go) gives a backup StarsPerDump (10★) whenever its bytes are new to the catalogue, and 0 when an earlier published report or a board artifact has the same sha256. It doesn't consider how the dump was taken. ipctool's report earns StarsPerItem (1★) on its own line in potential, so an ipctool upload is 10 + 1, and a bare programmer dump is 10. The site says the same on the send forms and in "How stars work" (STARS.dump in frontend/apps/site/src/lib/club.ts; club.rules_dump, club.new_dump_hint in data/locales/boards.*.yml).

Why the difference matters (as I read the remark; please correct)
An ipctool backup comes with the camera's own description of itself: chip, sensor, flash ID, partitions, read on the running camera. A file from a programmer or TFTP is bytes alone, and its read can't be checked the same way.

To decide

• What a dump earns without ipctool's report beside it, in the same report or joined to it with a club code: 25% would be 2–3★ against 10.
• Whether a dump that gets its ipctool report later, joined by a code, earns the difference when that is published.
• The wording: "How stars work" and the dump hints on the send and new-camera forms, en/ru/zh.
• Already-awarded stars stay as they are; a decision only changes what is paid from then on.

Related: #456 (adding a dump to a report already sent).