apple-notes-ci-integration

# Apple Notes CI Integration ## Overview Apple Notes automation is macOS-only because it depends on the Apple Events subsystem and Notes.app. CI pipelines must use GitHub Actions macOS runners (`macos-latest` or `macos-14`). However, macOS CI runners have restricted TCC (Transparency, Consent, and Control) permissions, which means direct Notes.app automation via `osascript` will fail in CI. The standard pattern is to run unit tests against a mock JXA client in CI, and reserve real Notes.app integration tests for local macOS machines or self-hosted runners with pre-granted automation permissions. ## GitHub Actions Workflow ```yaml # .github/workflows/notes-ci.yml name: Notes Automation CI on: push: branches: [main] pull_request: branches: [main] jobs: unit-tests: runs-on: macos-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: { node-version: "20", cache: "npm" } - run: npm ci - name: Verify macOS version run: sw_vers - name: Lint JXA scripts run: | # Validate JavaScript syntax in all .jxa files for f in scripts/*.jxa; do node --check "$f" 2>/dev/null || echo "WARN: $f is osascript-only" done - name: Unit tests (mocked Notes client) run: npm test - name: Validate JXA templates run: | # Ensure osascript can parse (but not execute) JXA scripts for f in scripts/*.jxa; do o...