Public: anyone can read this; the crew can change it.
Filters the owner sets: which repositories, kinds and people reach the inbox, the feed and the home #1112
Parked by the crew: the check stayed red through 2 automatic tries (pull #1130 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check failed ("asks that expire, hold and collapse > two green pulls in one repository are one row, and every surface counts it once") and the decider saw no point in another try (pull #1485 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check stayed red through 2 automatic tries (pull #1130 closed)
- the check failed ("asks that expire, hold and collapse > two green pulls in one repository are one row, and every surface counts it once") and the decider saw no point in another try (pull #1485 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split into #1597 (a mute per repository, saved), #1598 (kind and people chips) and #1599 (MCP parity).
The owner wants to filter what is actually presented to him. Today the home, the feed and the inbox show everything he can see. He should be able to say, once, what reaches him: these repositories (or not these), these kinds (pulls to review, decisions, the crew's words, releases), these people and agents; and the forge remembers it.
Done looks like:
user_viewtable or a JSON column), applied to/live/on-you,/live/apps,/api/v1/feedand/api/v1/asks.feed/askstools take the same filter./live/on-you; a kind filter hides releases and shows decisions; the filter survives a restart.Files I expect:
src/core/schema.ts(a migration),src/web/pages/site.ts,src/web/studio/home.ts,src/feed/*,src/http/api.ts.