notion-domain-contextlisted

# Notion Domain Context Search only through the runtime-specific hard boundary below and return a cited Evidence Packet. Do not return a fixed status when live read tools are available. Route installation and OAuth requests to the `vulpora-installer` skill. Read [principles](reference/principles.md) first. Read only the relevant topic from the [KB index](reference/kb/INDEX.md). ## Choose the executable runtime path ### Codex or OMX Use the parent session's `vulpora-notion` MCP tools directly. Do not require, spawn, or substitute a named custom agent; current Codex/OMX collaboration surfaces may not expose an `agent_type` selector. Before the first call, inspect the current tool inventory: - Accept only tools whose server provenance is exactly `vulpora-notion`. If endpoint metadata is available, it must also equal `https://mcp.notion.com/mcp`; the endpoint alone never proves that Vulpora's server-level allowlist applies. - Accept only `notion-search`, `notion-fetch`, and the OpenAI client aliases `search`, `fetch`. - If any mutation, user-listing, comment, database, or other Notion tool from that server is callable, return `status: error` with `unknowns: [unsafe_tool_profile]`. Do not call the server. - If the allowed search/fetch tools are absent before any Notion content is read, follow [Start deferred authentication on first use](#start-deferred-authentication-on-first-use). Do not assume that an absent inventory means an absent MCP config: an installed but