docs(repo): sync quality guardrail references

This commit is contained in:
2026-04-01 09:05:23 +02:00
parent 01e116ce99
commit 6c138964ca
3 changed files with 10 additions and 1 deletions
-1
View File
@@ -11,7 +11,6 @@
| Showcase quality backlog | [showcase-quality-backlog.md](/home/hartmut/Documents/Copilot/capakraken/docs/showcase-quality-backlog.md) | Consolidated working backlog for the current quality and maintainability north star |
| Parallel worktree hygiene | [parallel-worktree-hygiene.md](/home/hartmut/Documents/Copilot/capakraken/docs/parallel-worktree-hygiene.md) | Keep parallel worker slices isolated and the worktree reviewable |
| Target CI/CD architecture | [cicd-target-architecture.md](/home/hartmut/Documents/Copilot/capakraken/docs/cicd-target-architecture.md) | Canonical image-based build, deploy, and rollback flow |
| Parallel worktree hygiene | [parallel-worktree-hygiene.md](/home/hartmut/Documents/Copilot/capakraken/docs/parallel-worktree-hygiene.md) | Lightweight guardrail for shared dirty worktrees and parallel worker scopes |
| Active roadmap and open gaps | [product-roadmap.md](/home/hartmut/Documents/Copilot/capakraken/docs/product-roadmap.md) | Primary backlog and current delivery order |
| Estimating system design | [estimating-extension-design.md](/home/hartmut/Documents/Copilot/capakraken/docs/estimating-extension-design.md) | Workbook analysis, field mapping, and implementation plan |
| Dispo import implementation | [dispo-import-implementation.md](/home/hartmut/Documents/Copilot/capakraken/docs/dispo-import-implementation.md) | Clean-slate Dispo v2 import design, mapping rules, staging flow, and commit policy |
+8
View File
@@ -50,6 +50,14 @@ pnpm worktree:hygiene -- --fail-on-dirty
Use `--json` when another tool or agent should consume the output programmatically.
The helper is also covered by the repo-level script test suite:
```bash
pnpm test:scripts
```
That suite runs in CI before the architecture and import/export guardrails so hygiene regressions fail early.
## Parallel-Worker Rules
1. Pick an explicit ownership scope before editing files.
+2
View File
@@ -36,6 +36,8 @@ This backlog consolidates the still-relevant work from:
Already materially improved:
- SSE audience scoping is under CI guardrails.
- repo script guardrails are now test-backed in CI
- critical narrow ownership surfaces now have explicit `maxLines` architecture checks
- runtime secret handling is environment-first
- assistant-tool and several router monoliths were decomposed
- image-based CI/CD and deploy flow exists