Skip to content

feat(dx): define repository config boundary - #232

Merged
DecisionNerd merged 3 commits into
mainfrom
feat/225-repository-config-boundary
Jul 30, 2026
Merged

DecisionNerd merged 3 commits into
mainfrom
feat/225-repository-config-boundary

Conversation

@DecisionNerd

@DecisionNerd DecisionNerd commented Jul 30, 2026 •

Copy link
Copy Markdown
Contributor

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


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Note

Define .graphforge/ repository configuration boundary with versioned JSON Schema contracts

Macroscope summarized 62e09be.

@coderabbitai

coderabbitai Bot commented Jul 30, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 98dfcab9-2ffe-4ede-b8d2-8b2592e82dcc

📥 Commits

Reviewing files that changed from the base of the PR and between 6aacbb8 and 62e09be.

⛔ Files ignored due to path filters (12)
  • CHANGELOG.md is excluded by !**/*.md
  • docs/adr/0016-repository-integration-and-deployment-configuration.md is excluded by !**/*.md, !**/docs/**
  • docs/adr/README.md is excluded by !**/*.md, !**/docs/**
  • docs/book/architecture/overview.md is excluded by !**/*.md, !**/docs/**
  • docs/contracts/examples/graphforge-resolved-v1.json is excluded by !**/docs/**, !**/examples/**
  • docs/contracts/examples/graphforge-v1.yaml is excluded by !**/docs/**, !**/examples/**
  • docs/contracts/graphforge-project-config-v1.schema.json is excluded by !**/docs/**
  • docs/contracts/graphforge-resolved-config-v1.schema.json is excluded by !**/docs/**
  • docs/engineering/ARCHITECTURE.md is excluded by !**/*.md, !**/docs/**
  • docs/engineering/adrs/README.md is excluded by !**/*.md, !**/docs/**
  • docs/reference/changelog.md is excluded by !**/*.md, !**/docs/**
  • uv.lock is excluded by !**/*.lock, !**/*.lock
📒 Files selected for processing (4)
  • docs-site/astro.config.mjs
  • docs-site/scripts/sync-content.mjs
  • pyproject.toml
  • tests/unit/test_graphforge_config_contract.py

Comment @coderabbitai help to get the list of available commands.

@github-actions github-actions Bot added testing Test coverage and testing infrastructure documentation Improvements or additions to documentation labels Jul 30, 2026
@DecisionNerd
DecisionNerd merged commit f6a0860 into main Jul 30, 2026
18 checks passed
@DecisionNerd
DecisionNerd deleted the feat/225-repository-config-boundary branch August 13, 2026 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation testing Test coverage and testing infrastructure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(architecture): define repository and deployment configuration boundary

1 participant