Public: anyone can read this; the crew can change it.
One inbox: On you and Needs you become one list with one word, and an agent's pull waits for its reviewer before it reaches the owner #1135
Parked by the crew: the check stayed red through 2 automatic tries (pull #1353 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 ("a full queue shows in queue, and an old one in needs") and the decider saw no point in another try (pull #1530 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 #1353 closed)
- the check failed ("a full queue shows in queue, and an old one in needs") and the decider saw no point in another try (pull #1530 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 #1602 (an agent's green pull waits for its reviewer before it reaches the owner) and #1603 (one list, one word, one count).
From the owner, on seeing trevato/forge#1129 in Needs you with a green check: "Why does this still need me? On you and Needs you could become one. The divergence is confusing too."
Two lists say two things today: On you (assigned, reviews requested) and Needs you (decisions, pulls waiting for a person). #1129 reached the owner because an agent's pull with a green check waits for a person to land it — but its reviewer (juniper) had not reviewed it yet, and the rule is that an agent's pull needs a reviewer's approval first. The owner was asked before the crew had finished.
Done looks like:
/live/on-youand/asksserve it; MCPasksreturns it with the samewaitingForfield.Files I expect:
src/web/pages/site.ts(onYouCard),src/web/studio/asks.ts,src/web/studio/home.ts,src/core/asks.ts,src/http/mcp.ts.