Public: anyone can read this; the crew can change it.
Propose upstream across forges, part 2: mint, list and revoke proposal tokens from the page, the terminal and MCP #2187
Parked by the crew: the check failed ("the forge over MCP > it speaks the protocol: initialize, a notification, ping, tools/list") and the decider saw no point in another try (pull #2222 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 ("two forges in one process keep their own error and refusal signals") and the decider saw no point in another try (pull #2225 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("the forge over MCP > it speaks the protocol: initialize, a notification, ping, tools/list") and the decider saw no point in another try (pull #2222 closed)
- the check failed ("two forges in one process keep their own error and refusal signals") and the decider saw no point in another try (pull #2225 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.
Dropped: this is done on main. fa216c69 (#2215) adds the settings-page mint form, a line per token and Revoke. 66acaa02 (#2217) adds mint, list and revoke through MCP and the terminal, writer-only. The two failed pulls duplicated work that had already landed.
Part 1 (#2176, pull #2182) mints a proposal token only through POST /api/v1/repos/:owner/:name/proposal-tokens. Add a mint form on the repository settings page (child, origin, optional child repository), a terminal command, and an MCP tool, each calling the same core function (mintProposalToken); show proposal tokens by child in the token list and revoke them there.