genfile 0.6.0

CLI for genfile_core template archive management - create, manage, and materialize code generation templates.
Documentation
# Feature: Template Materialization

### Scope

- **Purpose**: Renders template archives into generated files at a target destination.
- **Responsibility**: Documents the `.materialize` and `.unpack` commands.
- **In Scope**: Parameter substitution via template engine, output file writing, mandatory parameter validation, dry-run mode.
- **Out of Scope**: Parameter value assignment (→ 004), archive serialization (→ 007).

### Design

Materialization validates that all mandatory parameters have values, then renders each template file by substituting parameter values via the template engine, writing outputs to the destination directory. Static files are copied verbatim. Unpack copies raw archive content without rendering, useful for inspecting or extracting archives without substitution. Both operations support dry-run mode for preview without writing.

### Invariants

| File | Relationship |
|------|--------------|
| [`invariant/003_error_handling.md`]../invariant/003_error_handling.md | Path validation constraint that materialization must enforce |
| [`invariant/004_security.md`]../invariant/004_security.md | Security constraint guarding output paths during generation |

### Sources

| File | Relationship |
|------|--------------|
| [`src/handlers/materialize.rs`]../../src/handlers/materialize.rs | Handler implementations for materialize/unpack commands |

### Tests

| File | Relationship |
|------|--------------|
| [`tests/materialization_test.rs`]../../tests/materialization_test.rs | Integration tests for materialize and unpack commands |