docs: update dead links

docs/content/adr/0006-http-framework.md

@@ -27,7 +27,7 @@ Use **gin-gonic/gin** (v1.9.1+) as the HTTP framework.
 - Easy route grouping (useful for modules)
 - Good OpenTelemetry integration support
 - Widely used and well-documented
-- Recommended in playbook-golang.md
+- Recommended in playbook.md
 
 ## Consequences
 

docs/content/adr/0010-ci-cd-platform.md

@@ -26,7 +26,7 @@ Use **GitHub Actions** for CI/CD pipeline.
 - Rich ecosystem of actions
 - Easy to configure with YAML
 - Good documentation and community support
-- Recommended in playbook-golang.md
+- Recommended in playbook.md
 
 ## Consequences
 

docs/content/adr/0013-database-orm.md

@@ -27,7 +27,7 @@ Use **entgo.io/ent** as the primary ORM for the platform.
 - Strong relationship modeling
 - Good performance (no reflection at runtime)
 - Active development and good documentation
-- Recommended in playbook-golang.md
+- Recommended in playbook.md
 - Easy to integrate with OpenTelemetry
 
 ## Consequences

docs/content/adr/0016-opentelemetry-observability.md

@@ -29,7 +29,7 @@ Use **OpenTelemetry (OTEL)** for all observability:
 - Excellent Go SDK support
 - Integrates with major observability tools
 - Supports metrics, traces, and logs
-- Recommended in playbook-golang.md
+- Recommended in playbook.md
 - Future-proof (not locked to specific vendor)
 
 ## Consequences