Per-product Known issues / Troubleshooting sections — pick a format #5

Context

PR #2 adds a generic symptom → cause troubleshooting guide. But product-specific failures have no home today — e.g. for the TigerScale alone: PN532 transport flashed ≠ transport wired, wrong screen variant selected at flash time, load-cell drift before warm-up, negative weight from swapped bridge wires.

Checked on Sept 5: no "troubleshooting" or "known issues" content anywhere on the site outside PR #2.

The question to settle

Two formats are possible, and it's better to pick one before content accumulates:

1. A "Known issues / Troubleshooting" section in each product page — Symptom | Cause | Fix table, close to the specs it relates to;
2. Centralized guides — one troubleshooting guide per product family under guides/.

Offer

I'll demo option 1 on TigerScale first (that's where I have the most verified material), you judge the format on the real thing, then we generalize — or switch to option 2.