Notion MCP preflight

Run before board sync when the operator may not have Notion wired.

Check availability

The agent has ground truth about its own tools. Notion MCP is available when tools such as notion-fetch, notion-create-pages, or notion-update-page (server name may vary) are present. If absent, follow the fallback below.

Only sync when the board is in use — user confirmed, or hoen.yaml sets work_tracking.backend: notion.

If Notion MCP is missing

1. Tell the teammate what completed without MCP (effort JSON validated, plan markdown refreshed, plan ## Tracking updated).
2. Encourage them to copy-paste a Progress block into the Notion page / ticket:

node library/skills/work-tracking/scripts/format-sync.mjs \
  --input path/to/plan.effort.json \
  --paste-md \
  --plan-doc path/to/plan.md

The block includes a Detailed plan link built from git remote get-url origin (GitHub / Azure DevOps / Bitbucket) — not a local path. Optionally also print --map notion JSON if they prefer filling database properties by hand. 3. Recommend installing Notion MCP for the IDE; restart / reload; confirm tools appear. 4. Do not block git-side work.

Agent behaviour without MCP

Step	Without MCP
Validate effort JSON	✅ Run scripts locally
Refresh plan 👀 / breakdown	✅ Paste script markdown
Update plan ## Tracking	✅ Plan ID, Board item, Work type
Create/update Notion card	⚠️ --paste-md into the page/ticket; teammate pastes
Set Plan synced at	⚠️ Note intended date in PR / plan doc