feat(architecture): define repository and deployment configuration boundary

[DecisionNerd]

Objective

Define and freeze GraphForge's repository-integration and deployment-configuration boundary before implementation.

Acceptance criteria

1. The next-numbered ADR selects one .graphforge/ namespace, with tracked definitions and ignored state/, imports/, exports/, materialized seeds, snapshots, and actual data.
2. A closed graphforge.yaml JSON Schema and canonical secret-free resolved JSON contract cover local and named deployment targets.
3. The ADR records Rust/core, binding/CLI, skill-package, Git, IaC, secret, worktree, and ownership boundaries and compares every alternative required by feat(dx): add repository-local GraphForge lifecycle CLIs and project skills #219.
4. Both ADR indexes, architecture/configuration documentation, contract tests, and [Unreleased] are updated.
5. The accepted contract composes with ADRs 0013, 0014, and 0015 without creating another persistence authority.

Relationships

• Parent and close gate: feat(dx): add repository-local GraphForge lifecycle CLIs and project skills #219
• Blocks all other feat(dx): add repository-local GraphForge lifecycle CLIs and project skills #219 implementation slices.

Non-goals

• Implementing lifecycle commands, bindings, skills, portable interchange, or IaC resources.

[coderabbitai]

🔗 Related PRs

#217 - feat(api): add embedded write modes [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!