Session CONV-5

Summary

Short diagnostic session. The user asked to check the Notion integration. Discovered that NOTION_OFFPLAN_TOKEN was not exported to the shell environment at MCP server startup, so the notion-offplan MCP server tools were unavailable. Worked around by sourcing .env directly and calling the Notion REST API via curl. Confirmed Notion is fully operational: Sessions DB has CONV-3 and CONV-4, Plans DB has one draft plan ("Launch Plan v2"), Workstreams DB is empty (0 rows), Learnings DB has 3 entries. No files were modified.

Changes

None — session was purely diagnostic/exploratory.

Decisions

Used curl + REST API fallback rather than the MCP server. The MCP server requires NOTION_OFFPLAN_TOKEN to be in the environment before Claude Code starts — sourcing .env mid-session does not inject it into the already-running MCP process. The fix is to ensure the var is exported at shell startup (e.g. via .zshrc or direnv).

Next Steps

1. Fix NOTION_OFFPLAN_TOKEN persistence — add to ~/.zshrc or set up direnv in ~/code/offplan-online/os/.envrc so the var is always exported before Claude Code starts
2. Verify notion-offplan MCP tools load correctly on next session start
3. Create first workstream in Notion (Workstreams DB is empty — no active work is tracked yet)
4. Ratify the "Launch Plan v2" draft and spin up the first product workstream

Open Questions

• Should NOTION_OFFPLAN_TOKEN go in ~/.zshrc (global) or via direnv (project-scoped)?
• Is the Launch Plan v2 HTML file ready to be ratified, or does it need more review?

Context for next session

The notion-offplan MCP tools will only appear if NOTION_OFFPLAN_TOKEN is in the environment at startup. Until that is fixed, the curl fallback works fine for all Notion operations. No workstreams exist yet in Notion.