chore: fix docs after fences fix

This commit is contained in:
Jesús Pérez 2026-01-14 05:01:36 +00:00
parent 784bc0ef71
commit 2d442bcbde
Signed by: jesus
GPG Key ID: 9F243E355E0BC939
22 changed files with 22 additions and 22 deletions

View File

@ -179,4 +179,4 @@ Functions that call the bash wrappers:
---
**Last Updated**: 2025-01-09
**Structure Version**: 2.0 (Multi-subsystem organization)
**Structure Version**: 2.0 (Multi-subsystem organization)

View File

@ -325,4 +325,4 @@ enable_pre_commit = false
For detailed documentation, see:
- $env.TOOLS_PATH/dev-system/ci/docs/configuration-guide.md
- $env.TOOLS_PATH/dev-system/ci/docs/installation-guide.md
- $env.TOOLS_PATH/dev-system/ci/docs/installation-guide.md

View File

@ -387,4 +387,4 @@ To add a new configuration field:
---
**Version**: 1.0.0
**Last Updated**: 2025-01-05
**Last Updated**: 2025-01-05

View File

@ -331,4 +331,4 @@ grep "nickel_path" forms/fragments/*.toml | sort
---
**Version**: 1.0.0
**Last Updated**: 2025-01-05
**Last Updated**: 2025-01-05

View File

@ -222,4 +222,4 @@ When TypeDialog processes forms:
- `provisioning/.typedialog/provisioning/platform/constraints/constraints.toml` - Constraint definitions
- `constraint_update_status.md` - Progress tracking for constraint interpolation updates
- `provisioning/.typedialog/provisioning/platform/templates/*.j2` - Jinja2 templates for code generation
- `provisioning/schemas/` - Nickel schemas (use same ranges as constraints)
- `provisioning/schemas/` - Nickel schemas (use same ranges as constraints)

View File

@ -295,4 +295,4 @@ Ready to proceed with implementation:
---
**To contribute**: Pick any unchecked fragment above and follow the pattern in `constraint_interpolation_guide.md`. Each constraint update takes ~5 minutes per fragment.
**To contribute**: Pick any unchecked fragment above and follow the pattern in `constraint_interpolation_guide.md`. Each constraint update takes ~5 minutes per fragment.

View File

@ -95,4 +95,4 @@ nu scripts/install-services.nu all enterprise --kubernetes --namespace productio
- TypeDialog CLI
- yq v4.50.1+
- Docker (optional)
- kubectl (optional)
- kubectl (optional)

View File

@ -252,4 +252,4 @@ grep -r "try\|panic\|todo" scripts/ # Should be empty
**Version**: 1.0.0
**Last Updated**: 2025-01-05
**Guideline**: @.claude/guidelines/nushell.md (NuShell 0.109+)
**Guideline**: @.claude/guidelines/nushell.md (NuShell 0.109+)

View File

@ -76,4 +76,4 @@ git push origin main
| Caching | ✅ Built-in | ⚠️ Server-side** |
\* Multi-OS builds require multiple Woodpecker agents
\*\* Configure in Woodpecker server settings
\*\* Configure in Woodpecker server settings

View File

@ -128,4 +128,4 @@ nickel eval --format json <your-config.ncl> | jq '.'
**Status**: Nickel migration complete. System is production-ready.
**Date**: 2026-01-08
**Branch**: nickel
**Branch**: nickel

View File

@ -127,4 +127,4 @@ Maintainers handle releases following semantic versioning:
- Ask in discussions or open an issue
- Join our community channels
Thank you for contributing!
Thank you for contributing!

View File

@ -1122,4 +1122,4 @@ PROVIDER_AWS_SOURCE="https://github.com/aws/aws-cli/releases"
- Automatic provider discovery from `extensions/providers/*/nickel/version.ncl`
- Direct Nickel file parsing with JSON export
- Zero dependency on environment variables or legacy systems
- 100% bash/shell compatible for deployment scripts
- 100% bash/shell compatible for deployment scripts

View File

@ -243,4 +243,4 @@ A: Yes. It's simpler and more robust than the old Rust installer.
---
**Status**: ✅ Ready for use
**Last Updated**: 2025-01-02
**Last Updated**: 2025-01-02

View File

@ -388,4 +388,4 @@ docker-compose -f provisioning/platform/infrastructure/docker/docker-compose.cic
**Version**: 1.0.0
**Last Updated**: 2026-01-05
**Script Reference**: `provisioning/scripts/setup-platform-config.sh`
**Script Reference**: `provisioning/scripts/setup-platform-config.sh`

View File

@ -491,4 +491,4 @@ cargo run -p orchestrator
**Version**: 1.0.0
**Last Updated**: 2026-01-05
**Status**: Ready to use
**Status**: Ready to use

View File

@ -507,4 +507,4 @@ tail -f tmp/k8s-deployment/kubernetes-*.log
4. **Configure ingress**: Set up ingress controllers
5. **Implement GitOps**: Configure ArgoCD or Flux
This example demonstrates the complete workflow from workspace creation to production Kubernetes cluster deployment using the new package-based system.
This example demonstrates the complete workflow from workspace creation to production Kubernetes cluster deployment using the new package-based system.

View File

@ -537,4 +537,4 @@ For issues or questions:
- `workspace.ncl`: Infrastructure definition (Nickel)
- `config.toml`: Provider credentials and settings
- `deploy.nu`: Deployment orchestration (Nushell)
- `README.md`: This file
- `README.md`: This file

View File

@ -410,4 +410,4 @@ For issues or questions:
- `workspace.ncl`: Infrastructure definition (Nickel)
- `config.toml`: Provider credentials and settings
- `deploy.nu`: Deployment automation script (Nushell)
- `README.md`: This file
- `README.md`: This file

View File

@ -726,4 +726,4 @@ For issues or questions:
- `workspace.ncl`: Global infrastructure definition (Nickel)
- `config.toml`: Provider credentials and regional settings
- `deploy.nu`: Multi-region deployment orchestration (Nushell)
- `README.md`: This file
- `README.md`: This file

View File

@ -342,4 +342,4 @@ When new forms or help sections are added:
**Status**: ✅ Complete
**Phases Completed**: 1, 2, 3, 4A, 4B, 4C, 4D
**Ready for**: Production deployment, further language additions, testing
**Ready for**: Production deployment, further language additions, testing

View File

@ -399,4 +399,4 @@ ORCHESTRATOR_MODE=solo cargo run -p orchestrator
**Version**: 1.0.0
**Created**: 2026-01-05
**Last Updated**: 2026-01-05
**Last Updated**: 2026-01-05

View File

@ -270,4 +270,4 @@ config = ovr.layer_resolution.infra_conditional(
- **Migration Tools**: Use `tools/migrate-infra.nu` for infrastructure conversion
- **Registry System**: Explore `registry/` for template metadata and imports
This system provides the perfect balance of flexibility, reusability, and maintainability while preserving the core provisioning system's integrity.
This system provides the perfect balance of flexibility, reusability, and maintainability while preserving the core provisioning system's integrity.