feat(dx): define repository config boundary - #232
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 43 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (12)
📒 Files selected for processing (4)
Comment |
…onfig-boundary # Conflicts: # CHANGELOG.md
Closes #225\n\nDefines proposed ADR 0016 plus the closed project and resolved configuration schemas that gate the remaining #219 slices. The contract keeps actual GraphForge/source data out of code Git, preserves Rust ownership, and separates portable intent from Pulumi/Terraform provider inputs.\n\nValidation:\n- uv run --extra dev pytest -q tests/unit/test_graphforge_config_contract.py\n- uv run --extra dev ruff check tests/unit/test_graphforge_config_contract.py\n- pnpm docs:build\n- pnpm docs:check-links\n- git diff --check
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Note
Define
.graphforge/repository configuration boundary with versioned JSON Schema contracts.graphforge/directory as the boundary for repository integration and deployment configuration.graphforge-project-config-v1.schema.jsonfor project config andgraphforge-resolved-config-v1.schema.jsonfor resolved (secret-free) IaC output.tests/unit/test_graphforge_config_contract.py, enforcing closed object schemas, secret-free resolved output, and canonical serialization.jsonschema>=4.23to thedevoptional dependencies inpyproject.tomlto support schema validation in tests.Macroscope summarized 62e09be.