### 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
5.5 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.
Subagent Template — Deploy Preflight & Checklist Generation
Read deploy reference files and distill deployment-specific rules into deploy-checklist.md. This is the main agent's ONLY source of deploy rules.
Critical Rules
- ⛔ Do NOT invoke any agents, run
azcommands, or modify IaC/app code. Read-only sub-agent. - ⛔ Do NOT read
deploy-schemas.tsorerror-classification.md— main agent reads those on-demand.
Input (provided by caller)
| Field | Source |
|---|---|
prepare-plan.json content |
services[], naming, region, costEstimate, deploymentVariables |
scaffold-manifest.json content |
deployCommand, validationResult, files[] |
context.json content |
azure.subscriptionId, subscriptionName, resourceGroup, sessionId, intent |
prereq-output.json content |
buildRequirements, warnings[], components[] |
| Session folder path + working directory | Required |
Output
| Artifact | Location |
|---|---|
deploy-checklist.md |
Session folder |
deploy-result.json skeleton (if missing) |
Session folder |
| Summary (≤300 tokens) | Return to caller |
Workflow
Step 1 — Read session artifacts + write skeleton
Read all 4 session artifacts. Extract: services[], naming, costEstimate, deployCommand, validationResult, deploymentVariables, subscriptionId, sessionId, buildRequirements, warnings[], quotaValidation.
If deploy-result.json missing, write skeleton with these EXACT field names (do NOT rename): { sessionId, subscriptionId, resourceGroupName, deploymentNames: ["app-onboard-deploy-{first 8 of sessionId}"], status: "in-progress", startedUtc, resourceIds: [], endpoints: [], healthStatus: "unknown", resourceResults: [], healingAttempts: [] }.
Step 2 — Read safety + blocked patterns refs
Read deploy-safety.md and blocked-patterns.md. Bake into checklist sections: deploy-result.json rules, blocked commands table, shell rules (sync shells, secrets persistence, no --track-status, az rest headers on Windows), 403 scope fallback (4-step procedure with real values), post-deploy tag verification, deployment operation polling (conditional: >5 resources), re-approval gates, antipatterns, artifact reconciliation.
Step 3 — Read preflight + approval gate refs
Read preflight-checks.md and approval-gate-template.md.
Bake preflight into checklist: auth token check, resource name availability (real names), RBAC scope pre-check, ⛔ MANDATORY what-if command (pre-filled with real deploymentName, region, subscriptionId), RG existence check, offer restriction check (conditional: if offerRestrictionsVerified false AND DB services in plan).
Bake approval gate VERBATIM with real values: subscription, RG, region, service table, cost table, validation status, files list, response handlers with exact CLI commands. If F1/D1 detected, append warning.
Step 4 — Read code-deployment + health refs
Read ONLY the code-deployment ref(s) matching the compute types in prepare-plan.json.services[]. Do NOT read references for compute types absent from the plan:
- If
App ServiceorFunctionsin plan → read code-deployment-appservice.md - If
Container Appsin plan → read code-deployment-container-apps.md - If
Static Web Appsin plan → read code-deployment-swa.md
Bake per-service-type ## Code deploy sections (one per compute service — do NOT merge).
Read health-check-patterns.md. Bake health check section: HTTP checks (timeout 30s, 3 retries), status interpretation, Azure default page detection strings, non-HTTP resource checks, functional verification (conditional).
Step 5 — Read conditional refs + handoff + write checklist
Database (conditional): If DB services in plan → read database-post-deploy.md. Bake migration discovery, execution commands, PG-specific checks.
Read ../../references/handoff-protocol.md. Bake cleanup commands (with real rg, sessionId), orphan listing, healing summary, post-deploy recommendations, agent-based next steps, auth-aware handoff.
Write deploy-checklist.md to session folder. If it already exists, replace all content via edit; if not, use create:
# Deploy Checklist for {appName}
# RG: {rgName} | Sub: {subscriptionId} | Session: {sessionId}
# ⚠️ If compaction recently occurred: re-read deploy/instructions.md Steps 6-8
Delete inapplicable sections (e.g., remove App Service section for Container Apps deploys).
⛔ Copy
## Before handoff (Step 8)and## Artifact verification (Step 8 — MANDATORY)from the template VERBATIM. Do NOT paraphrase, merge, or weaken⛔markers. These sections are the compaction-safe finalization anchor — diluting them causes artifact writes to be skipped after compaction.
Step 6 — Return summary
Return ≤300 tokens: preflight warnings, deploy command, service types, confirmation of checklist write, database migration note if applicable.