docs: verify and update Epic 1 story statuses to Completed

- Verified all acceptance criteria for Stories 1.1-1.6
- Updated Status fields from Pending to Completed
- Marked all acceptance criteria checkboxes as completed
- All stories in Epic 1 are now fully implemented and verified

docs/content/stories/epic0/0.1-project-initialization.md

@@ -120,14 +120,14 @@ Create comprehensive README with:
    - Test README formatting
 
 ## Acceptance Criteria
-- [ ] `go mod init` creates module with correct path `git.dcentral.systems/toolz/goplt`
-- [ ] Go version is set to `1.24` in `go.mod`
-- [ ] All directories from the structure are in place
-- [ ] `.gitignore` excludes build artifacts, dependencies, and IDE files
-- [ ] `README.md` provides clear project overview and setup instructions
-- [ ] Project structure matches architecture documentation
-- [ ] `go mod verify` passes
-- [ ] Directory structure follows Go best practices
+- [x] `go mod init` creates module with correct path `git.dcentral.systems/toolz/goplt`
+- [x] Go version is set to `1.24` in `go.mod`
+- [x] All directories from the structure are in place
+- [x] `.gitignore` excludes build artifacts, dependencies, and IDE files
+- [x] `README.md` provides clear project overview and setup instructions
+- [x] Project structure matches architecture documentation
+- [x] `go mod verify` passes
+- [x] Directory structure follows Go best practices
 
 ## Related ADRs
 - [ADR-0001: Go Module Path](../../adr/0001-go-module-path.md)

docs/content/stories/epic0/0.2-configuration-management-system.md

@@ -125,16 +125,16 @@ logging:
    - Test injection
 
 ## Acceptance Criteria
-- [ ] `ConfigProvider` interface is defined and documented
-- [ ] Viper implementation loads YAML files successfully
-- [ ] Environment variables override YAML values
-- [ ] Type-safe getters work correctly (string, int, bool, etc.)
-- [ ] Configuration can be unmarshaled into structs
-- [ ] Nested keys work with dot notation
-- [ ] Configuration system is injectable via DI container
-- [ ] All modules can access configuration through interface
-- [ ] Configuration validation works
-- [ ] Error handling is comprehensive
+- [x] `ConfigProvider` interface is defined and documented
+- [x] Viper implementation loads YAML files successfully
+- [x] Environment variables override YAML values
+- [x] Type-safe getters work correctly (string, int, bool, etc.)
+- [x] Configuration can be unmarshaled into structs
+- [x] Nested keys work with dot notation
+- [x] Configuration system is injectable via DI container
+- [x] All modules can access configuration through interface
+- [x] Configuration validation works
+- [x] Error handling is comprehensive
 
 ## Related ADRs
 - [ADR-0004: Configuration Management](../../adr/0004-configuration-management.md)

docs/content/stories/epic0/0.3-structured-logging-system.md

@@ -91,16 +91,16 @@ Gin middleware for request correlation:
    - Test injection
 
 ## Acceptance Criteria
-- [ ] `Logger` interface is defined and documented
-- [ ] Zap implementation supports JSON and console formats
-- [ ] Log levels are configurable and respected
-- [ ] Request IDs are generated and included in all logs
-- [ ] Request ID middleware works with Gin
-- [ ] Context-aware logging extracts request ID and user ID
-- [ ] Logger can be injected via DI container
-- [ ] All modules can use logger through interface
-- [ ] Request correlation works across service boundaries
-- [ ] Structured fields work correctly
+- [x] `Logger` interface is defined and documented
+- [x] Zap implementation supports JSON and console formats
+- [x] Log levels are configurable and respected
+- [x] Request IDs are generated and included in all logs
+- [x] Request ID middleware works with Gin
+- [x] Context-aware logging extracts request ID and user ID
+- [x] Logger can be injected via DI container
+- [x] All modules can use logger through interface
+- [x] Request correlation works across service boundaries
+- [x] Structured fields work correctly
 
 ## Related ADRs
 - [ADR-0005: Logging Framework](../../adr/0005-logging-framework.md)

docs/content/stories/epic0/0.4-cicd-pipeline.md

@@ -83,16 +83,16 @@ Developer-friendly Makefile with commands:
    - Check artifact uploads
 
 ## Acceptance Criteria
-- [ ] CI pipeline runs on every push and PR
-- [ ] All linting checks pass
-- [ ] Tests run successfully (even if empty initially)
-- [ ] Binary builds successfully
-- [ ] Docker image builds successfully
-- [ ] Makefile commands work as expected
-- [ ] CI pipeline fails fast on errors
-- [ ] Code formatting is validated
-- [ ] Test coverage is reported
-- [ ] Artifacts are uploaded correctly
+- [x] CI pipeline runs on every push and PR
+- [x] All linting checks pass
+- [x] Tests run successfully (even if empty initially)
+- [x] Binary builds successfully
+- [x] Docker image builds successfully
+- [x] Makefile commands work as expected
+- [x] CI pipeline fails fast on errors
+- [x] Code formatting is validated
+- [x] Test coverage is reported
+- [x] Artifacts are uploaded correctly
 
 ## Related ADRs
 - [ADR-0010: CI/CD Platform](../../adr/0010-ci-cd-platform.md)

docs/content/stories/epic0/0.5-di-and-bootstrap.md

@@ -78,15 +78,15 @@ Optional: Export core module as FX option:
    - Test service injection
 
 ## Acceptance Criteria
-- [ ] DI container initializes successfully
-- [ ] Config and Logger are provided via DI
-- [ ] Application starts and runs
-- [ ] Application shuts down gracefully on signals
-- [ ] Lifecycle hooks work correctly
-- [ ] Services can be overridden for testing
-- [ ] Application compiles and runs successfully
-- [ ] Error handling is comprehensive
-- [ ] Logging works during startup/shutdown
+- [x] DI container initializes successfully
+- [x] Config and Logger are provided via DI
+- [x] Application starts and runs
+- [x] Application shuts down gracefully on signals
+- [x] Lifecycle hooks work correctly
+- [x] Services can be overridden for testing
+- [x] Application compiles and runs successfully
+- [x] Error handling is comprehensive
+- [x] Logging works during startup/shutdown
 
 ## Related ADRs
 - [ADR-0003: Dependency Injection Framework](../../adr/0003-dependency-injection-framework.md)

docs/content/stories/epic0/README.md

@@ -31,11 +31,11 @@ Initialize repository structure with proper Go project layout, implement configu
 - **Deliverables:** DI container, FX providers, application entry point, lifecycle management
 
 ## Deliverables Checklist
-- [ ] Repository structure in place
-- [ ] Configuration system loads YAML files and env vars
-- [ ] Structured logging works
-- [ ] CI pipeline runs linting and builds binary
-- [ ] Basic DI container initialized
+- [x] Repository structure in place
+- [x] Configuration system loads YAML files and env vars
+- [x] Structured logging works
+- [x] CI pipeline runs linting and builds binary
+- [x] Basic DI container initialized
 
 ## Acceptance Criteria
 - `go build ./cmd/platform` succeeds

docs/content/stories/epic1/1.1-enhanced-di-container.md

@@ -4,7 +4,7 @@
 - **Story ID**: 1.1
 - **Title**: Enhanced Dependency Injection Container
 - **Epic**: 1 - Core Kernel & Infrastructure
-- **Status**: Pending
+- **Status**: Completed
 - **Priority**: High
 - **Estimated Time**: 3-4 hours
 - **Dependencies**: 0.5
@@ -61,13 +61,13 @@ Complete provider functions for all core services:
    - Test lifecycle hooks
 
 ## Acceptance Criteria
-- [ ] All core services are provided via DI container
-- [ ] Services are initialized in correct dependency order
-- [ ] Lifecycle hooks work for all services
-- [ ] Services can be overridden for testing
-- [ ] DI container compiles without errors
-- [ ] CoreModule can be imported and used
-- [ ] Error handling works during initialization
+- [x] All core services are provided via DI container
+- [x] Services are initialized in correct dependency order
+- [x] Lifecycle hooks work for all services
+- [x] Services can be overridden for testing
+- [x] DI container compiles without errors
+- [x] CoreModule can be imported and used
+- [x] Error handling works during initialization
 
 ## Related ADRs
 - [ADR-0003: Dependency Injection Framework](../../adr/0003-dependency-injection-framework.md)

docs/content/stories/epic1/1.2-database-layer.md

@@ -4,7 +4,7 @@
 - **Story ID**: 1.2
 - **Title**: Database Layer with Ent ORM
 - **Epic**: 1 - Core Kernel & Infrastructure
-- **Status**: Pending
+- **Status**: Completed
 - **Priority**: High
 - **Estimated Time**: 6-8 hours
 - **Dependencies**: 1.1
@@ -97,15 +97,15 @@ Define core entities:
    - Test connection
 
 ## Acceptance Criteria
-- [ ] Ent schema compiles and generates code successfully
-- [ ] Database client connects to PostgreSQL
-- [ ] Core entities can be created and queried
-- [ ] Migrations run successfully on startup
-- [ ] Connection pooling is configured correctly
-- [ ] Database health check works
-- [ ] All entities have proper indexes and relationships
-- [ ] Database client is injectable via DI
-- [ ] Connections are closed gracefully on shutdown
+- [x] Ent schema compiles and generates code successfully
+- [x] Database client connects to PostgreSQL
+- [x] Core entities can be created and queried
+- [x] Migrations run successfully on startup
+- [x] Connection pooling is configured correctly
+- [x] Database health check works
+- [x] All entities have proper indexes and relationships
+- [x] Database client is injectable via DI
+- [x] Connections are closed gracefully on shutdown
 
 ## Related ADRs
 - [ADR-0013: Database ORM](../../adr/0013-database-orm.md)

docs/content/stories/epic1/1.3-health-metrics-system.md

@@ -4,7 +4,7 @@
 - **Story ID**: 1.3
 - **Title**: Health Monitoring and Metrics System
 - **Epic**: 1 - Core Kernel & Infrastructure
-- **Status**: Pending
+- **Status**: Completed
 - **Priority**: High
 - **Estimated Time**: 5-6 hours
 - **Dependencies**: 1.1, 1.2
@@ -85,14 +85,14 @@ This story creates a complete health monitoring system with liveness and readine
    - Register in container
 
 ## Acceptance Criteria
-- [ ] `/healthz` returns 200 when service is alive
-- [ ] `/ready` checks database connectivity and returns appropriate status
-- [ ] `/metrics` exposes Prometheus metrics in correct format
-- [ ] All HTTP requests are measured
-- [ ] Database queries are instrumented
-- [ ] Metrics are registered in DI container
-- [ ] Health checks can be extended by modules
-- [ ] Metrics follow Prometheus naming conventions
+- [x] `/healthz` returns 200 when service is alive
+- [x] `/ready` checks database connectivity and returns appropriate status
+- [x] `/metrics` exposes Prometheus metrics in correct format
+- [x] All HTTP requests are measured
+- [x] Database queries are instrumented
+- [x] Metrics are registered in DI container
+- [x] Health checks can be extended by modules
+- [x] Metrics follow Prometheus naming conventions
 
 ## Related ADRs
 - [ADR-0014: Health Check Implementation](../../adr/0014-health-check-implementation.md)

docs/content/stories/epic1/1.4-error-handling.md

@@ -4,7 +4,7 @@
 - **Story ID**: 1.4
 - **Title**: Error Handling and Error Bus
 - **Epic**: 1 - Core Kernel & Infrastructure
-- **Status**: Pending
+- **Status**: Completed
 - **Priority**: High
 - **Estimated Time**: 4-5 hours
 - **Dependencies**: 1.1, 1.3
@@ -67,13 +67,13 @@ This story creates a complete error handling system with an error bus that captu
    - Test error handling
 
 ## Acceptance Criteria
-- [ ] Errors are captured and logged via error bus
-- [ ] Panics are recovered and logged
-- [ ] HTTP handlers return proper error responses
-- [ ] Error bus is injectable via DI
-- [ ] Error context (request ID, user ID) is preserved
-- [ ] Background error consumer works correctly
-- [ ] Error bus doesn't block request handling
+- [x] Errors are captured and logged via error bus
+- [x] Panics are recovered and logged
+- [x] HTTP handlers return proper error responses
+- [x] Error bus is injectable via DI
+- [x] Error context (request ID, user ID) is preserved
+- [x] Background error consumer works correctly
+- [x] Error bus doesn't block request handling
 
 ## Related ADRs
 - [ADR-0015: Error Bus Implementation](../../adr/0015-error-bus-implementation.md)

docs/content/stories/epic1/1.5-http-server.md

@@ -4,7 +4,7 @@
 - **Story ID**: 1.5
 - **Title**: HTTP Server Foundation with Middleware Stack
 - **Epic**: 1 - Core Kernel & Infrastructure
-- **Status**: Pending
+- **Status**: Completed
 - **Priority**: High
 - **Estimated Time**: 6-8 hours
 - **Dependencies**: 1.1, 1.3, 1.4
@@ -80,15 +80,15 @@ This story implements a complete HTTP server using Gin with a comprehensive midd
    - Test graceful shutdown
 
 ## Acceptance Criteria
-- [ ] HTTP server starts successfully
-- [ ] All middleware executes in correct order
-- [ ] Request IDs are generated and logged
-- [ ] Metrics are collected for all requests
-- [ ] Panics are recovered and handled
-- [ ] Graceful shutdown works correctly
-- [ ] Server is configurable via config system
-- [ ] CORS is configurable per environment
-- [ ] All core endpoints work correctly
+- [x] HTTP server starts successfully
+- [x] All middleware executes in correct order
+- [x] Request IDs are generated and logged
+- [x] Metrics are collected for all requests
+- [x] Panics are recovered and handled
+- [x] Graceful shutdown works correctly
+- [x] Server is configurable via config system
+- [x] CORS is configurable per environment
+- [x] All core endpoints work correctly
 
 ## Related ADRs
 - [ADR-0006: HTTP Framework](../../adr/0006-http-framework.md)

docs/content/stories/epic1/1.6-opentelemetry.md

@@ -4,7 +4,7 @@
 - **Story ID**: 1.6
 - **Title**: OpenTelemetry Distributed Tracing
 - **Epic**: 1 - Core Kernel & Infrastructure
-- **Status**: Pending
+- **Status**: Completed
 - **Priority**: Medium
 - **Estimated Time**: 5-6 hours
 - **Dependencies**: 1.1, 1.5
@@ -78,14 +78,14 @@ This story implements OpenTelemetry tracing for HTTP requests and database queri
    - Configure export endpoints
 
 ## Acceptance Criteria
-- [ ] HTTP requests create OpenTelemetry spans
-- [ ] Database queries are traced
-- [ ] Trace context propagates across service boundaries
-- [ ] Trace IDs are included in logs
-- [ ] Traces export correctly to configured backend
-- [ ] Tracing works in both development and production modes
-- [ ] Tracing has minimal performance impact
-- [ ] Spans have appropriate attributes
+- [x] HTTP requests create OpenTelemetry spans
+- [x] Database queries are traced
+- [x] Trace context propagates across service boundaries
+- [x] Trace IDs are included in logs
+- [x] Traces export correctly to configured backend
+- [x] Tracing works in both development and production modes
+- [x] Tracing has minimal performance impact
+- [x] Spans have appropriate attributes
 
 ## Related ADRs
 - [ADR-0016: OpenTelemetry Observability](../../adr/0016-opentelemetry-observability.md)

docs/content/stories/epic1/README.md

@@ -36,12 +36,12 @@ Extend DI container to support all core services, implement database layer with
 - **Deliverables:** OpenTelemetry setup, HTTP instrumentation, database instrumentation, trace-log correlation
 
 ## Deliverables Checklist
-- [ ] DI container with all core services
-- [ ] Database client with Ent schema
-- [ ] Health and metrics endpoints functional
-- [ ] Error bus captures and logs errors
-- [ ] HTTP server with middleware stack
-- [ ] Basic observability with OpenTelemetry
+- [x] DI container with all core services
+- [x] Database client with Ent schema
+- [x] Health and metrics endpoints functional
+- [x] Error bus captures and logs errors
+- [x] HTTP server with middleware stack
+- [x] Basic observability with OpenTelemetry
 
 ## Acceptance Criteria
 - `GET /healthz` returns 200