Register loopover_mark_notifications_read as a local stdio MCP tool

[JSONbored]

Context

loopover_mark_notifications_read is registered as a remote MCP tool (src/mcp/server.ts:2268) and has a CLI mirror (notifications-read, packages/loopover-mcp/bin/loopover-mcp.ts:4156) — but no local stdio MCP tool registration exists for it in packages/loopover-mcp/bin/loopover-mcp.ts. This is the same gap class as the one fixed by PR #6382 (which registered loopover_list_pending_actions, loopover_decide_pending_action, loopover_set_agent_paused, loopover_set_action_autonomy, and loopover_get_gate_precision as local stdio tools, all in the same maintain-adjacent family). #6745 added the REST route + CLI subcommand for this specific tool but never added the matching stdio-tool registration, so it fell outside that batch.

Requirements

⚠️ Required pattern — mirror the existing registerStdioTool blocks at packages/loopover-mcp/bin/loopover-mcp.ts:2533-2600 exactly (the five siblings PR #6382 added). Do not invent a new registration shape, a different input-schema convention, or a different result-formatting helper.

• Add a registerStdioTool("loopover_mark_notifications_read", { description: stdioToolDescription("loopover_mark_notifications_read"), inputSchema: ... }, async (...) => toolResult(...)) block to packages/loopover-mcp/bin/loopover-mcp.ts, placed near its sibling tools in the same family.
• The tool must call the same underlying REST endpoint the existing CLI command notifications-read already calls (loopover-mcp.ts:4156) — reuse that call, don't duplicate the HTTP logic.
• Add the tool's description via the same stdioToolDescription-style lookup the sibling tools use — do not hardcode a description inline if the codebase's existing pattern centralizes it.

Deliverables

• loopover_mark_notifications_read registered as a local stdio MCP tool in packages/loopover-mcp/bin/loopover-mcp.ts, following the exact pattern of its five siblings from PR feat(mcp): register the maintain REST surface as local stdio tools #6382.
• The new tool calls the same REST endpoint the existing notifications-read CLI command already uses — no duplicated HTTP logic.

Test Coverage Requirements

Match whatever test coverage convention packages/loopover-mcp's existing stdio-tool registrations already have (check for an existing test file covering the sibling tools from PR #6382 and follow its shape) — confirm this package's coverage.include scoping before assuming the top-level 99% patch gate applies exactly as src/** does.

Expected Outcome

loopover_mark_notifications_read is available as a local stdio MCP tool, matching its existing REST route and CLI command — a self-host operator using the local MCP server (not just the CLI or remote MCP) can call this tool directly.

Links & Resources

• src/mcp/server.ts:2268 (the remote tool this mirrors)
• packages/loopover-mcp/bin/loopover-mcp.ts:4156 (the existing CLI command calling the same endpoint)
• packages/loopover-mcp/bin/loopover-mcp.ts:2533-2600 (the pattern to mirror, from PR feat(mcp): register the maintain REST surface as local stdio tools #6382)
• REST + CLI mirror for contributor notifications (list + mark-read) #6745 (added the REST route + CLI mirror, but not this stdio tool)

[linear-code]

JSO-5446