──────
Build and Push Docker Images / detect-changes (push) Successful in 11s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m2s
Build and Push Docker Images / build-transit-api (push) Successful in 1m1s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m5s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m13s
Build and Push Docker Images / build-monitoring-ui (push) Successful in 1m15s
Build and Push Docker Images / deploy-test-node (push) Successful in 3s

### 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
This commit is contained in:
Sven laptop
2026-09-20 23:33:55 +02:00
parent f935bbeb8c
commit 635a130f0b
195 changed files with 28309 additions and 957 deletions
@@ -0,0 +1,87 @@
/*---------------------------------------------------------------------------------------------
* Copyright (c) Microsoft Corporation. All rights reserved.
* Licensed under the MIT License. See LICENSE.md in the project root for license information.
*--------------------------------------------------------------------------------------------*/
/**
* Prereq-phase TypeScript interfaces for prereq-output.json.
*
* Standalone schema for azure-app-onboard-prereq — this agent can run independently.
*
* Shared types used across phases (AppOnboardComponent, PostDeployRecommendation,
* DetectedService, AppOnboardContext) are defined in:
* session-schemas.ts (local copy in this phase's references/)
*
* Context schema (AppOnboardContext, AppOnboardIntent) is defined in:
* session-schemas.ts (local copy in this phase's references/)
*/
// ─── prereq-output.json ──────────────────────────────────────────────────────
export interface BuildRequirements {
hasNativeModules: boolean;
hasDockerfile: boolean;
/** @deprecated F1/D1/Free are never offered (managed identity is mandatory and the
* free-tier MI sidecar OOMs). Retained for back-compat; treat as always false.
* The compute floor is always B1. */
f1Viable: boolean;
/** True when Dockerfile uses BuildKit-only syntax (--mount, # syntax=docker/dockerfile:1) */
hasBuildKitSyntax?: boolean;
/** Port from EXPOSE directive — used for Container Apps targetPort */
exposedPort?: number;
/** Estimated native module compilation time in seconds (typically 30–300s;
* larger compiled dependencies like scipy may take 600+s).
* Used by deploy phase to set WEBSITES_CONTAINER_START_TIME_LIMIT. */
estimatedInstallTime?: number;
/** @deprecated F1 is never selected. Retained as a "size up from B1" signal.
* Examples: "native modules (node-gyp)", "large dependency tree (27 pinned deps)",
* "build-time compilation (TypeScript tsc)", "major migration (Flask 0.12→2.3)" */
f1BlockReason?: string;
}
/** Structured warning from prereq evaluation */
export interface PrereqWarning {
id: string;
component: string;
axis: "build" | "completeness" | "deployability";
summary: string;
detail: string;
/** What to do about this warning — actionable fix instruction.
* Examples: "Set PGSSLMODE=require env var in IaC", "Add trust proxy setting to Express app" */
fix: string;
/** When the fix should be applied in the pipeline.
* "prereq" = prereq can fix this NOW with user approval (code/config changes that prevent deploy failures).
* "scaffold" = handled in generated IaC only (env var override, probe config). NEVER modifies user code.
* "deploy-gate" = surface at deploy approval gate for user awareness. No code changes.
* "post-deploy" = informational — add to postDeployRecommendations[], no action during pipeline. */
fixPhase: "prereq" | "scaffold" | "deploy-gate" | "post-deploy";
}
export interface PrereqOutput {
// AppOnboardComponent[] — see session-schemas.ts
components: unknown[];
/** Structured warnings — see prereq-artifacts.md for write rules */
warnings: PrereqWarning[];
detectedStack: string;
/** Prereq-only: auto-approves readiness gate + simplifies prepare alt analysis.
* Does NOT skip any phase, gate, reference read, or validation. */
fastTrackEligible: boolean;
overallHealth?: "ready" | "readyWithCaveats" | "blocked";
/** Build-time requirements detected from manifests and lockfiles */
buildRequirements?: BuildRequirements;
/** Detected health endpoint path (e.g., "/health", "/api/v1/health/").
* Used by scaffold for Azure health probe config and deploy for curl health check.
* null if no health endpoint found (triggers W-HEALTH warning). */
healthEndpoint?: string | null;
/** Application entry point detected from manifest (e.g., "index.js", "main.py", "cmd/main.go").
* Used by prepare/deploy-strategy.md for startupCommand generation. */
entryPoint?: string;
/** Structured recommendations derived from WARN findings.
* Merged into prepare-plan.json.postDeployRecommendations[] by the prepare phase.
* PostDeployRecommendation type — see session-schemas.ts */
postDeployRecommendations?: unknown[];
/** First-run init commands (DB migrations, seed data) detected from
* framework signals + migrations/ dir. Prepare prepends required entries
* to deployStrategy.startupCommand. See dependency-compatibility.md § First-Run. */
initCommands?: { type: string; framework: string; command: string; required: boolean }[];
}