pierlog-tracker

Notes

• 2026-09-07 (entirely-api 9cf7ddb): branch scoping FIXED. The tracker compared portal_users.branch (an account ID) against a map keyed ‘baltimore’/‘manassas’, which never matched, so every branch scheduler/GOA saw every branch’s outstanding pier logs. Now: SUPERUSER_ROLES + triage see all; others see expand_branch_accounts(branch) (own account; corporate GOA = all client branches). Rows resolve via _pierlog_row_account: real branch account wins, triage/UPRO-parked rows resolve through config.derive_invoice_branch (invoice prefix then triage_originating_branch, mixed-case data tolerated). _ACCOUNT_BRANCH_DISPLAY = config.ACCOUNT_NAMES wholesale (VB/Roanoke/WV/Hooksett no longer blank); RFI scheduler map key renamed to ‘Groundworks North Haven’. Live after deploy: owner 53/18 waiting, Baltimore scheduler 11/1, Manassas GOA 40/15, VB read-only 1/1, North Haven GOA 1/1, Hooksett GOA (jcorso) 0. The sidebar pier-log badge (sidebar-nav-badges) now inherits this scoping.