manage-phabricator-tasklisted

# Manage Phabricator Task ## When to use - User asks to create, file, open, or submit a Phabricator task or ticket. - User asks to update, edit, reassign, close, reopen, or change the status/priority of an existing Phabricator task. - Do NOT use for just reading existing tasks. Use the `read-phabricator-task` skill for that. ## Authentication Use the official Phabricator MCP server only. Phabricator holds files, shared passwords, and secrets far beyond task content, so a manually managed credential is real exposure. - Discover the available tools with `ToolSearch` (query `"phabricator"` or `"maniphest"`), exact tool names depend on how the server was registered locally, do not hardcode a guess. - One-time setup, if the tools aren't found: resolve the server URL exactly as described in the `read-phabricator-task` skill's Authentication section, `$PHABRICATOR_MCP_URL`, then `~/.arcrc`-derived, then ask the user, don't re-derive it a different way here. - No token is required. The first call opens a browser tab for login/authorize. Tokens are ephemeral and periodically expire, a re-authorize prompt mid-session is expected behavior, not a failure. - Never fall back to a stored Conduit token, a raw `curl` call to `$PHAB/api/...`, or a different Phabricator MCP server. If the official MCP misbehaves, loop in the platform team instead. ## Known limitations Verified live against this MCP server, don't try to work around these: - No user directory search. `pha_user_search` ret