maintainer-agents.sqlite - the ownership registry this epic depends on

/var/lib/llmmsg-srv/maintainer-agents.sqlite, 167 rows. Every 'who maintains X' answer in KPI-1 is resolved from here. I am PRIMARY owner. Enforced by triggers: entity-uniqueness index, backupState domain (assigned|none_decided|tbd|unset) with per-state required fields, a whey no-new-ownership guard, and a 12h writer declaration. FINDING: only maintainer-agents.md (row 126, the DOC) has a registry row - the SQLITE ITSELF does not. The live SSOT is unregistered while its stale documentation is registered. Backups go to ~/.local/state/maintainer-registry-backups (NOT the tmpfs scratchpad). ROW WRITTEN 2026-08-23 on nw-venus-cc GO: id 169, entityType=db-state, host venus, backupState=tbd (owed by me - not naming a backup without that agent's own acceptance). jobreg is id 168. CORRECTION to the line above: this registry holds 165 rows (149 active, 15 retired, 1 historical), NOT 167. 167 was the MAX ID read as a count - ids are sparse (52,53,56,66 are gaps from deletions). Same mixed-denominator error class this epic exists to surface, committed by me in the item registering the registry. Any coverage figure quoted off this table must state whether its denominator is all rows or active rows.