Verification
A portfolio that says “everything passes” and shows nothing is asking for an act of faith. This page publishes what runs before each release, against which commit, and with what result.
Last run
All green- Command
- npm run verificar
- Commit
- 2bd6f9b · 2bd6f9b5d27a208d766c717a1e5437d2ec116593
- Commit date
- September 5, 2026
- Result
- 368 tests, 0 failing · types clean · linter clean
Publishing stops if any of this fails: the script that builds the site runs these checks first and aborts with whatever went wrong.
Breakdown by file
Each tool tests its engine against the cases its package declares, plus the shared invariants: determinism, rejection of unknown fields, and traceability of every rule applied. That is why these numbers are higher than the package cases shown on each card: these are the automated tests that actually run.
19 files · 368 tests · 0 failing
See the breakdown by file
| File | tests | Failures |
|---|---|---|
| herramientas/L01/motor.test.ts | 23 | 0 |
| herramientas/P01/motor.test.ts | 34 | 0 |
| herramientas/P02/motor.test.ts | 24 | 0 |
| herramientas/P03/motor.test.ts | 19 | 0 |
| herramientas/P04/motor.test.ts | 17 | 0 |
| herramientas/P05/motor.test.ts | 22 | 0 |
| herramientas/P06/motor.test.ts | 20 | 0 |
| herramientas/P07/motor.test.ts | 23 | 0 |
| herramientas/P08/motor.test.ts | 30 | 0 |
| herramientas/P09/motor.test.ts | 25 | 0 |
| herramientas/P10/motor.test.ts | 30 | 0 |
| herramientas/P11/motor.test.ts | 18 | 0 |
| herramientas/P12/motor.test.ts | 18 | 0 |
| herramientas/P16/motor.test.ts | 18 | 0 |
| lib/motor/diagnostico.test.ts | 13 | 0 |
| lib/motor/paquete.test.ts | 8 | 0 |
| lib/motor/permanencia.test.ts | 14 | 0 |
| lib/motor/recomendador.test.ts | 9 | 0 |
| nucleo/sha256.test.ts | 3 | 0 |
| Total | 368 | 0 |
Overflow by screen width
A page that spills off the screen on a phone is noticed immediately and fixed late. All 17 pages are checked at four widths, looking for anything that forces horizontal scrolling.
- 320 px
0
of 17 pages overflow
- 375 px
0
of 17 pages overflow
- 768 px
0
of 17 pages overflow
- 1280 px
0
of 17 pages overflow
Measured by hand with a browser on August 26, 2026, not on every release. Overflow depends on layout and cannot be computed without a rendering engine; automating it needs a headless browser inside the integration pipeline, and until that exists I would rather say it is manual than present it as automatic.
How far this goes
This is what we run, not an independent check: the repository is private, so nobody outside can run the same command against the same commit and compare. The identifier is published so that anyone with repository access can do exactly that. An external auditor raised this very point, and was right to.