The org-sys operator person is inserted by the upgrade SQL, so unlike every identity the dashboard creates it has no identity_aliases row and no identity_events create row, and the shared-token path acts as it without checking its lifecycle. Decide whether the upgrade should write the alias/create event and whether requestPrincipal should refuse a suspended or retired operator.
Imported from beads archie-core-lgw8 · GitHub #1498 · type bug · priority P3 · created 2026-10-05
The org-sys operator person is inserted by the upgrade SQL, so unlike every identity the dashboard creates it has no identity_aliases row and no identity_events create row, and the shared-token path acts as it without checking its lifecycle. Decide whether the upgrade should write the alias/create event and whether requestPrincipal should refuse a suspended or retired operator.
---
_Imported from beads `archie-core-lgw8` · GitHub #1498 · type bug · priority P3 · created 2026-10-05_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The org-sys operator person is inserted by the upgrade SQL, so unlike every identity the dashboard creates it has no identity_aliases row and no identity_events create row, and the shared-token path acts as it without checking its lifecycle. Decide whether the upgrade should write the alias/create event and whether requestPrincipal should refuse a suspended or retired operator.
Imported from beads
archie-core-lgw8· GitHub #1498 · type bug · priority P3 · created 2026-10-05