feat: modernize application — source, platform artifacts, CI/CD (#3)

docs/migration-plan.md

@@ -0,0 +1,44 @@
+# Modernization Plan for pclinic-andrej-demo1
+
+## Application Type
+Java Application
+
+## Selected Modernization Strategy
+- **Migration Approach**: containerize-optimize
+- **Target Platform**: orchestrator
+- **Observability**: ENABLED (Prometheus metrics, health checks, tracing)
+- **Security Scanning**: ENABLED (Trivy vulnerability scanning)
+
+## Discovery Summary
+### Discovery Report
+
+#### Application Overview
+The application is a Java-based project using the Spring Boot framework. It supports both Maven and Gradle as build tools, with dependencies defined in `pom.xml` and `build.gradle`. The application appears to be a web application, likely a pet clinic or similar system, based on the dependencies and API endpoints.
+
+---
+
+#### Technology Stack
+- **Programming Language**: Java
+- **Framework**: Spring Boot
+- **Build Tools**: Maven and Gradle
+- **Databas...
+
+## Generated Artifacts
+1. **Dockerfile**: Optimized with health checks and metrics endpoints
+2. **score.yaml**: Platform intent with service ports and DNS resource
+3. **CI Workflow**: Automated build/push to ACR with Trivy security scanning
+
+## Next Steps
+1. Review and customize generated artifacts
+2. Test container build and run
+3. Deploy to development environment using score.yaml
+4. Validate application functionality
+5. Promote to staging/production via Humanitec
+
+## Migration Strategy Details
+
+### Containerize Optimize
+Add cloud-native patterns: health checks, metrics, optimized base images.
+
+### Platform: orchestrator
+score.yaml optimized for Azure Container Apps with managed scaling and Azure-specific configuration.