onenote-local-dev-loop

# OneNote Local Dev Loop ## Overview Testing OneNote integrations typically requires Azure AD credentials and live Graph API calls, which means authentication friction on every dev session and risk of hitting the 600 req/60s rate limit during rapid iteration. This skill sets up a local development loop with mock Graph responses so you can develop and test OneNote features without Azure credentials, without rate limits, and with instant feedback. The mock layer intercepts HTTP calls to `graph.microsoft.com` and returns realistic fixture data, including the XHTML output format that differs from input format. You can switch between mock and live Graph with a single environment variable. ## Prerequisites - Node.js 18+ or Python 3.10+ - Familiarity with your project's test framework (vitest/jest for Node, pytest for Python) - Optional: completed `onenote-install-auth` for live mode switching ## Instructions ### Step 1: Project Structure ``` my-onenote-app/ ├── .env # GRAPH_MODE=mock or GRAPH_MODE=live ├── .env.example # Template (commit this, not .env) ├── src/ │ ├── client.ts # Graph client factory (mock/live switching) │ ├── onenote.ts # Business logic (testable) │ └── types.ts # OneNote type definitions ├── tests/ │ ├── fixtures/ │ │ ├── notebooks.json # Mock notebook list response │ │ ├── sections.json # Mock section list response │ │ ├── pages.j...