docs: Align documentation with true microservices architecture

Transform all documentation from modular monolith to true microservices
architecture where core services are independently deployable.

Key Changes:
- Core Kernel: Infrastructure only (no business logic)
- Core Services: Auth, Identity, Authz, Audit as separate microservices
  - Each service has own entry point (cmd/{service}/)
  - Each service has own gRPC server and database schema
  - Services register with Consul for service discovery
- API Gateway: Moved from Epic 8 to Epic 1 as core infrastructure
  - Single entry point for all external traffic
  - Handles routing, JWT validation, rate limiting, CORS
- Service Discovery: Consul as primary mechanism (ADR-0033)
- Database Pattern: Per-service connections with schema isolation

Documentation Updates:
- Updated all 9 architecture documents
- Updated 4 ADRs and created 2 new ADRs (API Gateway, Service Discovery)
- Rewrote Epic 1: Core Kernel & Infrastructure (infrastructure only)
- Rewrote Epic 2: Core Services (Auth, Identity, Authz, Audit as services)
- Updated Epic 3-8 stories for service architecture
- Updated plan.md, playbook.md, requirements.md, index.md
- Updated all epic READMEs and story files

New ADRs:
- ADR-0032: API Gateway Strategy
- ADR-0033: Service Discovery Implementation (Consul)

New Stories:
- Epic 1.7: Service Client Interfaces
- Epic 1.8: API Gateway Implementation

docs/content/stories/COMPLETE_TASK_LIST.md

@@ -16,34 +16,35 @@ Tasks are organized by epic and section. Each task file follows the naming conve
 - [0.5 Dependency Injection and Application Bootstrap](./epic0/0.5-di-and-bootstrap.md)
 
 ## Epic 1: Core Kernel & Infrastructure
-- [1.1 Enhanced DI Container](./epic1/1.1-enhanced-di-container.md)
-- [1.2 Database Layer](./epic1/1.2-database-layer.md)
+- [1.1 Enhanced DI Container](./epic1/1.1-enhanced-di-container.md) - Core kernel services only
+- [1.2 Database Client Foundation](./epic1/1.2-database-layer.md) - Per-service database connections
 - [1.3 Health & Metrics System](./epic1/1.3-health-metrics-system.md)
 - [1.4 Error Handling](./epic1/1.4-error-handling.md)
-- [1.5 HTTP Server](./epic1/1.5-http-server.md)
-- [1.6 OpenTelemetry](./epic1/1.6-opentelemetry.md)
+- [1.5 HTTP/gRPC Server Foundation](./epic1/1.5-http-server.md) - Server foundations for services
+- [1.6 OpenTelemetry](./epic1/1.6-opentelemetry.md) - Distributed tracing across services
+- [1.7 Service Client Interfaces](./epic1/1.7-service-client-interfaces.md) - Service client interfaces
+- [1.8 API Gateway Implementation](./epic1/1.8-api-gateway.md) - API Gateway as core infrastructure
 - [Epic 1 Overview](./epic1/README.md)
 
-## Epic 2: Authentication & Authorization
-- [2.1 JWT Authentication System](./epic2/2.1-jwt-authentication.md)
-- [2.2 Identity Management System](./epic2/2.2-identity-management.md)
-- [2.3 RBAC System](./epic2/2.3-rbac-system.md)
-- [2.4 Role Management API](./epic2/2.4-role-management.md)
-- [2.5 Audit Logging System](./epic2/2.5-audit-logging.md)
-- [2.6 Database Seeding and Initialization](./epic2/2.6-database-seeding.md)
-- [2.7 Service Client Interfaces](./epic2/2.7-service-abstraction-layer.md)
+## Epic 2: Core Services (Authentication & Authorization)
+- [2.1 Auth Service - JWT Authentication](./epic2/2.1-jwt-authentication.md) - Independent Auth Service
+- [2.2 Identity Service - User Management](./epic2/2.2-identity-management.md) - Independent Identity Service
+- [2.3 Authz Service - Authorization & RBAC](./epic2/2.3-rbac-system.md) - Independent Authz Service
+- [2.4 Role Management (Part of Authz Service)](./epic2/2.4-role-management.md) - Role management gRPC endpoints
+- [2.5 Audit Service - Audit Logging](./epic2/2.5-audit-logging.md) - Independent Audit Service
+- [2.6 Database Seeding](./epic2/2.6-database-seeding.md) - Per-service seeding
 - [Epic 2 Overview](./epic2/README.md)
 
-## Epic 3: Module Framework
-- [3.1 Module System Interface](./epic3/3.1-module-system-interface.md)
+## Epic 3: Module Framework (Feature Services)
+- [3.1 Module System Interface](./epic3/3.1-module-system-interface.md) - Module interface for feature services
 - [3.2 Permission Code Generation](./epic3/3.2-permission-code-generation.md)
-- [3.3 Module Loader](./epic3/3.3-module-loader.md)
-- [3.4 Module CLI](./epic3/3.4-module-cli.md)
-- [3.5 Service Registry and Discovery](./epic3/3.5-service-registry.md)
+- [3.3 Service Loader](./epic3/3.3-module-loader.md) - Service initialization helpers
+- [3.4 Service Management CLI](./epic3/3.4-module-cli.md) - Service management CLI
+- [3.5 Service Registry Verification](./epic3/3.5-service-registry.md) - Verify Consul integration
 - [Epic 3 Overview](./epic3/README.md)
 
-## Epic 4: Sample Feature Module (Blog)
-- [4.1 Complete Blog Module](./epic4/4.1-blog-module.md)
+## Epic 4: Sample Feature Service (Blog Service)
+- [4.1 Complete Blog Service](./epic4/4.1-blog-module.md) - Blog Service as reference implementation
 - [Epic 4 Overview](./epic4/README.md)
 
 ## Epic 5: Infrastructure Adapters
@@ -53,7 +54,7 @@ Tasks are organized by epic and section. Each task file follows the naming conve
 - [5.4 Email Notification](./epic5/5.4-email-notification.md)
 - [5.5 Scheduler & Jobs](./epic5/5.5-scheduler-jobs.md)
 - [5.6 Secret Store](./epic5/5.6-secret-store.md)
-- [5.7 gRPC Service Definitions and Clients](./epic5/5.7-grpc-services.md)
+- [5.7 Advanced gRPC Features](./epic5/5.7-grpc-services.md) - Streaming, gRPC-Gateway (basic gRPC in Epic 1-2)
 - [Epic 5 Overview](./epic5/README.md)
 
 ## Epic 6: Observability & Production Readiness
@@ -75,10 +76,12 @@ Tasks are organized by epic and section. Each task file follows the naming conve
 ## Epic 8: Advanced Features & Polish
 - [8.1 OIDC Support](./epic8/8.1-oidc-support.md)
 - [8.2 GraphQL API](./epic8/8.2-graphql-api.md)
-- [8.3 Additional Modules](./epic8/8.3-additional-modules.md)
+- [8.3 Additional Sample Feature Services](./epic8/8.3-additional-modules.md) - Notification & Analytics Services
 - [8.4 Final Polish](./epic8/8.4-final-polish.md)
 - [Epic 8 Overview](./epic8/README.md)
 
+**Note:** API Gateway is now in Epic 1 (Story 1.8) as core infrastructure, not an advanced feature.
+
 ## Task Status Tracking
 
 To track task completion: