aih-sync-notionlisted

## Phase 0: Configuration Check Before executing any action, verify that Notion sync is configured: 1. Check if `.aihaus/notion/config.json` exists 2. If **missing**: - Inform the user that Notion sync requires configuration - Offer to scaffold from the template: ``` mkdir -p .aihaus/notion cp .aihaus/templates/notion/config.example.json .aihaus/notion/config.json ``` - Print: "Configuration scaffolded. Edit `.aihaus/notion/config.json` with your Notion database ID, status names, roles, and sync commands. See `.aihaus/templates/notion/SETUP.md` for full setup instructions." - Stop execution — do not proceed to any action until config is valid 3. If **present**, read it and validate that `notion_database_id` is not `"YOUR_NOTION_DATABASE_ID"` (the placeholder value) 4. Check that `NOTION_TOKEN` is set in the environment Only proceed to the requested action after Phase 0 passes. ## Task Synchronize the Notion Kanban board with the current project state. Action: $ARGUMENTS ## Actions ### sync (default) Read the current execution state from `.aihaus/milestones/[M0XX]-[slug]/execution/` and planning artifacts, then sync all card statuses to Notion. 1. Read story summaries in `.aihaus/milestones/[M0XX]-[slug]/execution/*-SUMMARY.md` 2. Read QA reviews in `.aihaus/milestones/[M0XX]-[slug]/execution/reviews/` 3. Map story status to Notion status using `status_flow` from `.aihaus/notion/config.json` 4. Update `.aihaus/notion/sync-ite