onenote-deploy-integration

# OneNote Deploy Integration ## Overview Deploying OneNote integrations into containers breaks local development assumptions: MSAL token caches vanish on restart, health checks must validate Graph API connectivity (not just HTTP 200), and graceful shutdown must flush token state. This skill provides production-ready Dockerfile, Docker Compose, and Kubernetes manifests with MSAL token persistence, health/readiness probes that verify actual Graph reachability, and SIGTERM handling. ## Prerequisites - Docker 24+ and Docker Compose v2 - Node.js 20 LTS or Python 3.11+ - Azure AD app registration with delegated permissions (`Notes.Read`, `Notes.ReadWrite`) - Redis (recommended for multi-replica) or persistent volume for token cache ## Instructions ### Dockerfile ```dockerfile FROM node:20-slim AS builder WORKDIR /app COPY package*.json ./ RUN npm ci COPY tsconfig.json src/ ./ RUN npm run build FROM node:20-slim WORKDIR /app RUN apt-get update && apt-get install -y --no-install-recommends curl && rm -rf /var/lib/apt/lists/* COPY --from=builder /app/dist ./dist COPY --from=builder /app/node_modules ./node_modules COPY --from=builder /app/package.json ./ RUN mkdir -p /app/.cache/msal && chown -R node:node /app/.cache USER node ENV NODE_ENV=production MSAL_CACHE_DIR=/app/.cache/msal HEALTHCHECK --interval=30s --timeout=10s --start-period=15s --retries=3 \ CMD curl -sf http://localhost:3000/health || exit 1 EXPOSE 3000 CMD ["node", "dist/index.js"] ``` ### MSAL Token Cache Pe...