pluto-commons.md archive-trigger count: 23 measured as 24, and the literal count removed rather than incremented

DONE at aaaeb79 / v2.23.137. Own commit per pmmaster's instruction that a documentation number corrected inside a larger change is how the wrong figure survived in the first place. pluto-commons.md:78 said 'All 23 archive triggers RAISE when app.user_id is missing'. Measured against prod pg_catalog 2026-10-06: pg_proc.proname LIKE 'fn_archive%' -> 24 functions non-internal pg_trigger bound to those functions -> 24 distinct tgrelid armed by them -> 24 of those functions, prosrc naming RAISE AND app.user_id -> 24 So the UNIVERSALITY holds, which is the only part the rule rests on. THE FIGURE WAS NOT WRONG WHEN WRITTEN. 23 was correct through PLUTO-707 (2026-08-17); migration 131 added fn_archive_pacientes at 07:36Z on 2026-10-06 and made it 24. So this is not a measurement error being corrected - it is a literal per-table count in prose going stale on the next archive-table DDL while continuing to read authoritative. Incrementing 23 to 24 would have reproduced the defect on the next archive table. The line now states the universality, carries the measured figure with its date and the exact query, and tells the reader to RE-MEASURE rather than quote. pmmaster originally routed this to coder-venus-cc as commons backup maintainer, then corrected: the number lives in pluto/shared/md/pluto-commons.md (pluto's repo, not shared/), and measuring it needs a pluto DSN coder-venus-cc does not hold.