46de088423182a14d15acd3c35747fba588421db
The previous fix still used MAX(actualMax, counterVal) which meant a stale counter (from entries deleted before the fix was deployed) would override the actual entry count. Changed to use ONLY actualMax + 1. The RegistrySequence counter is now just a cache that gets synced — it never overrides the actual entries count. Also added /api/registratura/debug-sequences endpoint: - GET: shows all counters vs actual entry max (for diagnostics) - POST: resets all counters to match actual entries (one-time fix) After deploy, call POST /api/registratura/debug-sequences to reset the stale counters, then delete the BTG-2026-OUT-00004 entry and recreate it — it will get 00001. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
pre-launch hardening: Address Book type sort, Hot Desk proportions, TVA calculator, ROADMAP Phase 4B
Description
No description provided
Languages
TypeScript
98.7%
PLpgSQL
0.4%
Shell
0.3%
Dockerfile
0.2%
CSS
0.2%
Other
0.1%