refs chakra-ui#10204

CHANGES
- Fix HTTP mode CMD path from dist/http.js to api/index.js
- Add non-root mcpuser for container security
- Copy missing api/ directory from build stage
- Update Docker.md with local development examples

IMPACT
- HTTP mode now works correctly alongside stdio mode
- Enhanced container security with non-root execution
- Both modes tested and verified with secure setup

TECHNICAL NOTES
- Part 1/2 of Docker/GHCR implementation foundation
- Maintains feature parity with npx version

CHANGES
- Add multi-arch Docker workflow for GHCR publishing
- Implement manual dispatch testing without disrupting auto releases
- Create comprehensive workflows documentation system
- Fix Docker.md version tag alignment (remove "v" prefix)

IMPACT
- MCP maintainers get automated Docker publishing on releases
- Contributors can dry-run test Docker builds before merging
- New developers have clear CI/CD system documentation

TECHNICAL NOTES
- Multi-platform builds: linux/amd64, linux/arm64
- Triggered by @chakra-ui/react-mcp@* tags + workflow_dispatch
- SHOULD_PUSH env var controls push vs dry-run behavior
- Complete system architecture in workflows README
- Completes 2/2 Docker implementation (pending testing)

CHANGES
- Fix stdio mode to use Docker args (-e) instead of NPM env field
- Correct HTTP mode header name from CHAKRA_PRO_API_KEY to x-api-key
- Add explicit CHAKRA_PRO_API_KEY environment variable to Dockerfile
- Update documentation for both deployment modes

IMPACT
- Chakra UI Pro features now properly accessible in Docker deployments
- Consistent API key handling across stdio and HTTP transport modes
- Clear separation between host process (NPM) and container environment (Docker)

TECHNICAL NOTES
- Docker containers require -e flags for internal environment variables
- NPM env field sets host process environment, not container environment
- HTTP mode uses standard x-api-key header following REST conventions
- Explicit ENV declaration improves Dockerfile transparency

CHANGES
- Add comprehensive Docker Image Publishing section to workflows README
- Document step-by-step manual workflow instructions with GitHub Actions links
- Clarify Docker tag independence from internal @chakra-ui/react-mcp version
- Reference apps/mcp/package.json for version info instead of hard-coding
- Improve workflow input descriptions for manual dispatch clarity

IMPACT
- Core maintainers can confidently publish Docker images automatically or manually
- Clear operational guidance for first release and testing scenarios
- Eliminates confusion between Docker tags and internal package versions
- Reduces maintenance burden with dynamic version references

CHANGES
- Merge Docker.md content into README.md following DRY principles
- Fix GHCR image name alignment across all documentation files
- Replace hardcoded version with package.json import in http.ts
- Add GitHub source links to tool documentation
- Remove dead Docker.md references from workflows README
- Add GHCR README copying step to mcp-docker.yml workflow

IMPACT
- Single source of truth for MCP Docker documentation
- Consistent GHCR image references across all files
- Dynamic versioning eliminates manual updates
- Enhanced tool discoverability with direct source links

TECHNICAL NOTES
- Applied KISS principle: simplified version handling with JSON import
- Applied DRY principle: eliminated duplicate Docker documentation
- Corrected ghcr.io/chakra-ui/chakra-ui/react-mcp → ghcr.io/chakra-ui/react-mcp
- Workflow now copies apps/mcp/README.md to root for GHCR display

CHANGES
- Streamline MCP README description and features for clarity
- Remove hard-coded repository restrictions from Docker workflow
- Add OCI image metadata labels for proper GHCR presentation
- Make image naming dynamic using repository_owner variable

IMPACT
- Workflow now works seamlessly in any fork without configuration
- Container images display proper metadata on GHCR package pages
- Documentation provides clearer value proposition for users

TECHNICAL NOTES
- Eliminated need to edit hard-coded values when testing in forks
- Added org.opencontainers.image labels for description, source, and license

CHANGES
- Implement dynamic container labels using GITHUB_REPOSITORY build arg
- Add comprehensive Dockerfile documentation with stage organization
- Enhance README with API key security guidance and usage clarity
- Fix grammar and improve example consistency throughout docs

IMPACT
- Contributors can build fork-friendly images with correct metadata
- End users gain clearer setup instructions and security best practices
- Enhanced trust through GHCR-compliant container labeling
- Improved maintainability with well-documented Docker stages

TECHNICAL NOTES
- Follows official GitHub Container Registry metadata standards
- Dynamic labels replace hardcoded repository references
- Multi-stage Dockerfile with clear separation of concerns
- Enhanced security documentation for API key handling