feat: expand Caddy.Config.Global with 35+ typed fields and nested structs (#5)

Co-authored-by: Jonathan Gao <[email protected]>

Author: gsmlg

.specify/memory/constitution.md

@@ -1,18 +1,16 @@
 <!--
 Sync Impact Report
 ==================
-Version change: N/A → 1.0.0
+Version change: 1.0.1 → 1.1.0
+Modified principles: None
 Added sections:
-  - Core Principles (5 principles)
-  - Quality Standards
-  - Development Workflow
-  - Governance
-Modified principles: None (initial version)
-Removed sections: None (initial version)
+  - VI. Caddyfile Structure: Defines mandatory 3-part configuration architecture
+    (global config, additionals list, site configs list)
+Removed sections: None
 Templates requiring updates:
-  - .specify/templates/plan-template.md: ✅ Compatible (Constitution Check section exists)
-  - .specify/templates/spec-template.md: ✅ Compatible (Requirements align with principles)
-  - .specify/templates/tasks-template.md: ✅ Compatible (Test-first workflow supported)
+  - .specify/templates/plan-template.md: ✅ Compatible (no changes needed)
+  - .specify/templates/spec-template.md: ✅ Compatible (no changes needed)
+  - .specify/templates/tasks-template.md: ✅ Compatible (no changes needed)
 Follow-up TODOs: None
 -->
 
@@ -32,13 +30,20 @@ standardized interfaces that Elixir developers expect from production-grade libr
 
 ### II. Observability by Default
 
-Every significant operation MUST emit telemetry events. Logging MUST use telemetry-based
-emission rather than direct Logger calls. Events MUST include sufficient metadata for
-debugging and monitoring. The `Caddy.Telemetry` module serves as the single source of truth
-for all observable events.
+Every significant operation MUST emit telemetry events. The `Caddy.Telemetry` module serves
+as the single source of truth for all observable events.
 
-**Rationale**: Telemetry enables users to integrate Caddy operations into their existing
-monitoring infrastructure without coupling to specific logging implementations.
+**Logging Requirements**:
+- All logging MUST use `Caddy.Telemetry.log_*` functions (`log_debug/2`, `log_info/2`,
+  `log_warning/2`, `log_error/2`)
+- Direct usage of `Logger` module (Logger.debug, Logger.info, etc.) is PROHIBITED
+- The default telemetry handler forwards log events to Elixir's Logger automatically
+- Users MAY disable the default handler and attach custom handlers for their needs
+
+**Rationale**: Telemetry-based logging decouples the library from specific logging
+implementations. Users can integrate Caddy log events into their existing monitoring
+infrastructure, filter events, or route them to external services without modifying
+library code.
 
 ### III. Test-Driven Quality
 
@@ -69,13 +74,37 @@ dependencies MUST be isolated from production builds.
 **Rationale**: Fewer dependencies reduce security surface, simplify upgrades, and minimize
 conflicts with user applications.
 
+### VI. Caddyfile Structure
+
+The `Caddy.Config` module MUST organize Caddyfile configuration into three distinct parts:
+
+1. **Global Config**: Server-wide settings enclosed in `{ }` block at the top of Caddyfile
+   (e.g., `debug`, `auto_https off`, admin socket configuration)
+2. **Additionals Config**: A list of additional configuration blocks that are NOT site
+   definitions (e.g., named matchers, snippets, import statements). Each additional MUST
+   be stored and retrievable independently.
+3. **Site Configs**: A list of site definitions, where each site has a unique identifier,
+   address/matcher, and directive block. Sites MUST be independently addable, removable,
+   and modifiable via API.
+
+**Implementation Requirements**:
+- `Caddy.Config` MUST provide separate getter/setter functions for each configuration part
+- The generated Caddyfile MUST concatenate parts in order: global → additionals → sites
+- Each site MUST be identifiable by a user-provided key for targeted updates
+- Configuration changes MUST emit telemetry events per Principle II
+
+**Rationale**: Separating configuration into logical parts enables granular management of
+Caddy settings. Users can modify individual sites or global settings without regenerating
+the entire configuration, supporting dynamic proxy management in production environments.
+
 ## Quality Standards
 
 - **Static Analysis**: All code MUST pass `mix credo --strict` and `mix dialyzer`
 - **Formatting**: All code MUST pass `mix format --check-formatted`
 - **Documentation**: Public modules MUST have `@moduledoc`, public functions MUST have `@doc`
 - **Type Specs**: Public functions SHOULD have `@spec` annotations
 - **Test Coverage**: New features MUST include corresponding tests
+- **Logging**: All log statements MUST use `Caddy.Telemetry.log_*` functions
 
 ## Development Workflow
 
@@ -100,4 +129,4 @@ with these principles. Reviewers SHOULD reference specific principles when reque
 RECOMMENDED. Non-compliant code discovered should be addressed via dedicated refactoring
 tasks.
 
-**Version**: 1.0.0 | **Ratified**: 2025-12-15 | **Last Amended**: 2025-12-15
+**Version**: 1.1.0 | **Ratified**: 2025-12-15 | **Last Amended**: 2025-12-22

CLAUDE.md

@@ -178,4 +178,11 @@ A default handler (`Caddy.Logger.Handler`) automatically forwards log events to
 config :caddy, attach_default_handler: false
 ```
 
-Use `Caddy.Telemetry.list_events/0` to see all available events.
+Use `Caddy.Telemetry.list_events/0` to see all available events.
+
+## Active Technologies
+- Elixir ~> 1.18, OTP 27+ + Jason (JSON), Telemetry (observability), Mox (testing) (001-expand-global-config)
+- N/A (in-memory configuration structs) (001-expand-global-config)
+
+## Recent Changes
+- 001-expand-global-config: Added Elixir ~> 1.18, OTP 27+ + Jason (JSON), Telemetry (observability), Mox (testing)