Greptile P1 on PR #898. On a cold load of #/tasks?status=, TasksApp initialises its filter before loadTaskMeta() resolves, so the requested id is validated against the fallback catalog and rejected. The re-render keeps the same route key and preserves the empty filter state, so when the served option does arrive the URL-requested filter is never selected or applied.
A shared link to a filtered task view silently shows everything instead.
Source: ui/src/main.jsx around the TasksApp filter initialisation.
Close reason
Landed: the board's filter derives from the served catalog instead of freezing at setup, with the guard tightened to a whole-argument-list assertion after review showed the original regex was defeatable by a setup-time capture.
Imported from beads archie-core-ppra · GitHub #906 · type bug · priority P1 · created 2026-09-19 · closed 2026-09-21
Greptile P1 on PR #898. On a cold load of #/tasks?status=<served-only-status>, TasksApp initialises its filter before loadTaskMeta() resolves, so the requested id is validated against the fallback catalog and rejected. The re-render keeps the same route key and preserves the empty filter state, so when the served option does arrive the URL-requested filter is never selected or applied.
A shared link to a filtered task view silently shows everything instead.
Source: ui/src/main.jsx around the TasksApp filter initialisation.
### Close reason
Landed: the board's filter derives from the served catalog instead of freezing at setup, with the guard tightened to a whole-argument-list assertion after review showed the original regex was defeatable by a setup-time capture.
---
_Imported from beads `archie-core-ppra` · GitHub #906 · type bug · priority P1 · created 2026-09-19 · closed 2026-09-21_
sam
added the highbug labels 2026-10-27 13:40:43 +00:00
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.
Greptile P1 on PR #898. On a cold load of #/tasks?status=, TasksApp initialises its filter before loadTaskMeta() resolves, so the requested id is validated against the fallback catalog and rejected. The re-render keeps the same route key and preserves the empty filter state, so when the served option does arrive the URL-requested filter is never selected or applied.
A shared link to a filtered task view silently shows everything instead.
Source: ui/src/main.jsx around the TasksApp filter initialisation.
Close reason
Landed: the board's filter derives from the served catalog instead of freezing at setup, with the guard tightened to a whole-argument-list assertion after review showed the original regex was defeatable by a setup-time capture.
Imported from beads
archie-core-ppra· GitHub #906 · type bug · priority P1 · created 2026-09-19 · closed 2026-09-21