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
1.9 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.
Multi-Service Orchestration
Runs when
classify.mdfinds 2+ service roots, before inventory scanning begins.
Service ID Assignment
Derive a short kebab-case ID per service root. Use project manifest name if available, otherwise fall back to directory name.
| Runtime | Manifest Source | Field |
|---|---|---|
node-ts, node-js |
package.json |
"name" |
dotnet |
*.csproj |
<AssemblyName> or filename |
| Other | Service directory name | Fallback when no manifest name exists |
If two IDs collide, append the project type (e.g. payments-api becomes payments-api-functions).
Emulator Deduplication
Collect emulator lists from all services. Each emulator appears once in the plan's Emulators table — multiple services may depend on the same emulator.
Partial Configuration
Check each service root for existing debug config before planning.
| State | Plan Action |
|---|---|
| Fully configured | Skip |
| Partially configured | Generate only missing artifacts |
| Unconfigured | Full generation |
Compound Debug Configuration
Required when 2+ service roots are detected (including Frontend SPAs).
Startup Dependencies
If a frontend SPA has a proxy pointing to a local backend (detected via project-types.md § Backend Proxy Dependencies), record the proxyTarget service ID on that service entry. The compound config uses this to order startup (backends before frontends) that depend on them.