docs: keep ADRs in the main repository
This commit is contained in:
@@ -91,6 +91,13 @@ Concise but detailed reference for contributors working across the `moeru-ai/air
|
|||||||
|
|
||||||
## Before You Start
|
## Before You Start
|
||||||
|
|
||||||
|
## Architecture decisions
|
||||||
|
|
||||||
|
- Put project-wide and client ADRs directly in `docs/ai/`.
|
||||||
|
- Put hosted backend ADRs directly in `server/docs/ai/`.
|
||||||
|
- Both paths are relative to the repository root.
|
||||||
|
- Keep ADRs in this repository and include them in the related commits and pull requests.
|
||||||
|
|
||||||
## Enforced Repository Skills
|
## Enforced Repository Skills
|
||||||
|
|
||||||
- For testing, Vitest, regression reproduction, mocks, or test import-boundary work, always use [`enforce-rules-for-vitest` skill](.agents/skills/enforce-rules-for-vitest/SKILL.md).
|
- For testing, Vitest, regression reproduction, mocks, or test import-boundary work, always use [`enforce-rules-for-vitest` skill](.agents/skills/enforce-rules-for-vitest/SKILL.md).
|
||||||
|
|||||||
+2
-3
@@ -12,9 +12,8 @@
|
|||||||
|
|
||||||
## Architecture decisions
|
## Architecture decisions
|
||||||
|
|
||||||
- Put server ADRs in `../airi-docs/adr/`.
|
- Put server ADRs directly in `server/docs/ai/`, relative to the repository root.
|
||||||
- For an ADR task, write or update the ADR only. Do not stage, commit, push, or open a PR for ADR files.
|
- Include ADRs in the related commits and pull requests in this repository.
|
||||||
- The user owns ADR commits and pushes.
|
|
||||||
- Create or update the ADR before you change a server boundary.
|
- Create or update the ADR before you change a server boundary.
|
||||||
- A server boundary includes an HTTP contract, provider contract, persistence model, or cross-module lifecycle.
|
- A server boundary includes an HTTP contract, provider contract, persistence model, or cross-module lifecycle.
|
||||||
- Add a module dependency graph, an affected-file tree, and a sequence diagram to every implementation ADR.
|
- Add a module dependency graph, an affected-file tree, and a sequence diagram to every implementation ADR.
|
||||||
|
|||||||
Reference in New Issue
Block a user