Summary

Consolidated 5+ scattered deployment-related top-level directories into a single organized deployment/ directory to simplify the repository structure.

Problem

Recent PRs added multiple deployment directories at the top level, creating a cluttered repository structure:

• deploy/ - Azure deployment files
• helm/ - Helm charts
• k8s/ - Kubernetes manifests
• scripts/ - Deployment and validation scripts
• Dockerfile and docker-compose.yml - Docker files at root

Solution

Before: 10 top-level items (5 deployment-related scattered around)

NLWebNet/
├── src/, samples/, tests/, doc/     # Core application
├── deploy/, helm/, k8s/, scripts/   # Deployment (scattered)
├── Dockerfile, docker-compose.yml   # Docker files at root
└── ...

After: 5 clean top-level directories with logical grouping

NLWebNet/
├── src/                    # Core library
├── samples/                # Demo applications  
├── tests/                  # Unit tests
├── doc/                    # Documentation
└── deployment/             # ALL deployment infrastructure
    ├── azure/              # Azure deployment (Bicep templates)
    ├── kubernetes/         
    │   ├── helm/           # Helm charts
    │   └── manifests/      # K8s manifests
    ├── docker/             # Docker & Docker Compose files
    └── scripts/            # Deployment & validation scripts

Changes Made

• Moved files: Reorganized all deployment files into logical subdirectories under deployment/
• Updated documentation: Fixed all path references in README.md, deployment guide, and validation docs
• Fixed scripts: Updated relative paths in validation and deployment scripts to work from new locations
• Preserved functionality: All deployment features continue to work as before

Benefits

• ✅ Cleaner top-level: Reduced from 10 to 5 top-level directories
• ✅ Logical organization: Related files grouped together
• ✅ Industry standard: Follows common monorepo structure patterns
• ✅ Easier navigation: Clear separation between application code and deployment infrastructure
• ✅ Maintained compatibility: All existing deployment workflows preserved

Fixes #18.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.