docs: the portability report fails only with --strict

developing.md said findings never fail the portability report. Since the report gained --strict, that's true only by default: --strict exits 1 when it finds any. The workflow still runs it without --strict.
2026-11-13 18:49:34 -10:00 · 2026-11-14 00:44:20 +00:00
1 changed files with 1 additions and 1 deletions
@@ -33,7 +33,7 @@ suite. Both sets are readable in the root `package.json` scripts.

 | Lane | Command | Meaning |
 |---|---|---|
-| Portability report | `node scripts/portability-report.mjs` | lists added lines with machine-specific values; findings never fail it (`.github/workflows/portability-report.yml`) |
+| Portability report | `node scripts/portability-report.mjs` | lists added lines with machine-specific values; findings don't fail it by default, and `--strict` exits 1 when it finds any. The workflow (`.github/workflows/portability-report.yml`) runs it without `--strict`. |

 ## The norm (web-UI freeze at 0.5.0)