fix(bphtb): restore SPPT lookup after sequential numbering ## Changes Imported SPPTs now use sequential letter numbers, but BPHTB synchronization and its payment table still required the old NOP-based letter format. Remove that obsolete condition from both lookups while retaining the linked NOP and tax-object checks. Add regression coverage for sequential and legacy numbering, latest eligible NJOP selection, object and NOP isolation, payment-table filtering and pagination, and access checks. Closes #1887 ## Release impact Patch. Restore the intended behavior of existing BPHTB SPPT synchronization and payment listings. ## Migration notes No schema migration, configuration change, or data repair is required. ## Validation - TypeScript syntax checks, regression-file syntax checks, and git diff --check passed. - Build, tests, and dev were not run, per the user's instructions. - React Doctor could not start because this worktree has no installed dependencies. Runtime behavior and the new regression tests remain unverified. fix(feedback): prevent new reports starving in GitHub sync New bug reports and suggestions can stay at GitHub "Menunggu" indefinitely because PostgreSQL sorts NULL scheduled times after dated polling work. Recurring polls and repository-wide PR webhook wakeups keep that dated backlog ahead of reports that have never been attempted. Select eligible NULL scheduled times first, retaining the ID tie-breaker, retry delays and active leases. Add regression coverage for both report kinds with a polling backlog larger than the batch, an active lease and a future retry. ## Validation - Read-only production queue comparison reproduced the old ordering skipping reports 71 and 73 and the corrected ordering selecting both. - TypeScript syntax, Prettier and git diff checks pass. Independent diff review found no actionable issues. - Regression tests added but not run. Build, tests and dev commands were not run, per the user's instructions. ## Recovery and rollout Requeued production reports 71 and 73 through the existing worker. Their issues are #1886 and #1887. Both saved synced revision 1, matching their report revision, with no sync error. Production had zero unlinked bugs or suggestions after recovery. The queue ordering fix still needs release through the normal production flow. No migration or configuration change is required. ## Release impact Patch. Restore the existing GitHub feedback synchronization behavior.