Sven laptop
635a130f0b
### Summary of Changes
1. Documentation Consolidation:
• Relocated the docs/ folder and all repository .md files (README.md, DEPLOYMENT.md, DOCKER_README.md,
DOMAINS_README.md, GETTING_STARTED.md, CI_CD_PORTAINER_GUIDE.md, ADMIN_DEPLOYMENT_SUMMARY.md,
SECURITY_PRIVATE_FILES.md, handoff.md, azure-project-plan.md, plus service-specific READMEs) into .
• Updated document links in README.md.
2. AI Agent Project Map:
• Created PROJECT_MAP.md in the project root containing complete architecture diagrams, service specs, ports, DB
schemas, environment variables, and developer workflows.
• Added PROJECT_MAP.md to .gitignore.
3. Monitoring UI & Infrastructure Integration:
• Added monitoring_ui service to docker-compose.yml (port 5175).
• Configured Gitea workflow docker-build.yml for monitoring_ui builds.
• Added CORS middleware headers in index.js.
• Added nginx.conf copy step in Dockerfile.
──────
### Recommended Commit Message
docs: consolidate project documentation into monitoring_ui and add agent project map
- Move all markdown documentation files and docs/ folder into monitoring_ui/docs/
- Update documentation hub index (monitoring_ui/docs/README.md) with relative paths
- Generate comprehensive AI agent reference map (PROJECT_MAP.md) in repository root
- Add PROJECT_MAP.md and monitoring_ui build output/env overrides to .gitignore
- Integrate monitoring_ui service into docker-compose.yml and Gitea CI workflow
- Configure CORS handling in employee_api for monitoring dashboard access
──────
### Alternative Short Commit Message
refactor(docs): move docs to monitoring_ui and create AI agent PROJECT_MAP.md
4.3 KiB
Important: This skill provides guidance and recommended instructions to assist the AI system. Outputs are not guaranteed to be complete, correct, secure, or applicable to every scenario. Results should be reviewed and validated by a human before being applied. The AI model may choose not to follow all instructions exactly, and additional verification may be required.
SKU Selection Matrix
Select SKU based on context.json.intent.budget. Cross-reference with intent.scale for right-sizing.
Budget Tiers
⛔ Free/shared tiers (App Service F1/D1, Static Web Apps Free) are NOT offered. Every app requires a managed identity for Azure resource auth, and the free-tier MI sidecar OOMs on Linux; free SWA also lacks CORS/custom-auth config these apps need. The compute floor is B1 (App Service) / Standard (Static Web Apps). Never emit F1, D1, or Free.
| Service | cost-optimized | balanced | performance |
|---|---|---|---|
| Container Apps | Consumption (scale-to-zero) | Consumption | Dedicated |
| App Service | B1 (Basic) | B1 / S1 | P1v3 |
| Azure SQL | Basic (5 DTU) | Standard (S0) | Premium / Serverless |
| Cosmos DB | Serverless | Provisioned (400 RU) | Provisioned (autoscale) |
| Storage | Standard_LRS | Standard_GRS | Premium_LRS |
| Static Web Apps | Standard | Standard | Standard |
| Service Bus | Basic | Standard | Premium |
| Redis Cache | Basic C0 | Standard C1 | Premium P1 |
| Functions | Flex Consumption | Flex Consumption | Premium EP1 |
| Log Analytics | PerGB2018 | PerGB2018 | PerGB2018 (dedicated cluster) |
⚠️ Log Analytics
FreeSKU is deprecated. ARM rejects it with some API versions and retention settings. Always usePerGB2018— first 5 GB/month is free anyway.
⛔ Functions floor is Flex Consumption — NOT Consumption or Elastic Premium. The Consumption and Elastic Premium plans back
AzureWebJobsStoragewith Azure Files, which does not support managed-identity connections and therefore requiresallowSharedKeyAccesson the storage account — banned by the managed-identity-only rule (and the KV workaround for the Files connection string is also banned). Flex Consumption supports identity-basedAzureWebJobsStorage(AzureWebJobsStorage__accountName+AzureWebJobsStorage__credential=managedidentity), so it is the only Functions plan compatible withallowSharedKeyAccess: false. Never select Consumption/Elastic Premium — this is the same floor-raise as App Service F1→B1.
Modifier Rules
intent.scale = "Large"(100K+ users) → bump minimum one tier above cost-optimizedintent.budget = "performance"+intent.scale = "Small"→ don't over-provision; use balanced tier- Policy denies a SKU → fall back to next available tier (never below the B1 / SWA Standard floor), add to
assumptions[] - Cosmos DB Serverless: max 1K RU/s burst, no geo-replication — only for intermittent/dev workloads. Sustained read-heavy → Provisioned.
Default Behavior
- Single-component app + cost-optimized → cheapest viable SKU at or above the floor (App Service B1, Static Web Apps Standard)
- Simple web app with no DB → ~$13–$20/month (B1 minimum — no $0 tier)
- Always output exact SKU codes: "App Service B1 (Basic)" not "cheapest tier"
Auto-Cheapest for Fast-Track
⛔ If prereq-output.json.fastTrackEligible == true AND context.json.intent.budget is unset, treat as cost-optimized. Fast-track means single-component + no DB + no auth + no Dockerfile. Pick App Service B1 (Basic) for dynamic apps that need a runtime (Node.js/Python starter templates), or Static Web Apps Standard for pure static HTML/JS/CSS with no server-side runtime. The user still sees the SKU + monthly cost in the scaffold approval gate — they can override via "Edit plan". Do NOT ask the user about budget unless they mention cost first (per intent-gathering.md).
⛔ There is no free promise — fast-track starts at the B1 / SWA Standard floor. If the chosen floor SKU is unavailable during deploy prep (no B1 quota — see sku-quota-validation.md § After Checking), fall back to the cheapest AVAILABLE tier at or above the floor. Record an assumptions[] note stating WHY the SKU differs, so the approval gate presents the resulting cost.