feat: Upgrade fluent-asserts to v2.0 with major architectural changes

- Refactor evaluation logic to use structs for better performance and memory management.
- Transition from GC-based string serialization to HeapString for @nogc compatibility.
- Update import paths for operations and serializers to reflect new module structure.
- Enhance custom operation and serializer registration processes.
- Introduce new features including centralized configuration, multiple output formats, and context data for assertions.
- Improve assertion failure messages and statistics tracking.
- Add migration guide for users upgrading from v1.x to v2.0.

Author: gedaiu

docs/astro.config.mjs

@@ -19,13 +19,17 @@ export default defineConfig({
           label: 'Guide',
           items: [
             { label: 'Introduction', link: '/guide/introduction/' },
+            { label: 'Philosophy', link: '/guide/philosophy/' },
             { label: 'Installation', link: '/guide/installation/' },
-            { label: 'Assertion Styles', link: '/guide/assertion-styles/' },
             { label: 'Core Concepts', link: '/guide/core-concepts/' },
+            { label: 'Assertion Styles', link: '/guide/assertion-styles/' },
+            { label: 'Configuration', link: '/guide/configuration/' },
+            { label: 'Context Data', link: '/guide/context-data/' },
+            { label: 'Assertion Statistics', link: '/guide/statistics/' },
             { label: 'Memory Management', link: '/guide/memory-management/' },
             { label: 'Extending', link: '/guide/extending/' },
-            { label: 'Philosophy', link: '/guide/philosophy/' },
             { label: 'Contributing', link: '/guide/contributing/' },
+            { label: 'Upgrading to v2', link: '/guide/upgrading-v2/' },
           ],
         },
         {

docs/src/content/docs/guide/configuration.mdx

@@ -7,11 +7,11 @@ fluent-asserts provides configurable output formats for assertion failure messag
 
 ## Output Formats
 
-Three output formats are available:
+Three output formats are available, each designed for a specific audience:
 
 ### Verbose (Default)
 
-The verbose format provides detailed, human-readable output with full context:
+The **human-friendly** format. Provides detailed, readable output with full context including source code snippets. Perfect for local development and debugging when you need to understand exactly what went wrong.
 
 ```
 ASSERTION FAILED: 5 should equal 3.
@@ -24,17 +24,9 @@ source/mytest.d:42
 >  42:    expect(5).to.equal(3);
 ```
 
-### Compact
-
-A single-line format optimized for minimal token usage, useful for AI-assisted development:
-
-```
-FAIL: 5 should equal 3. | actual=5 expected=3 | source/mytest.d:42
-```
-
 ### TAP (Test Anything Protocol)
 
-Standard TAP format for integration with CI/CD tools and test harnesses:
+The **universal machine-readable** format. [TAP](https://testanything.org/) is a standard protocol understood by CI/CD systems, test harnesses, and reporting tools worldwide. Use this when integrating with automated pipelines or generating test reports.
 
 ```
 not ok - 5 should equal 3.
@@ -45,6 +37,14 @@ not ok - 5 should equal 3.
   ...
 ```
 
+### Compact
+
+The **token-optimized** format for AI-assisted development. Delivers all essential information in a single line, minimizing token usage when working with AI coding assistants like Claude Code. Every character counts when you're paying per token.
+
+```
+FAIL: 5 should equal 3. | actual=5 expected=3 | source/mytest.d:42
+```
+
 ## Setting the Output Format
 
 ### Environment Variable
@@ -93,11 +93,11 @@ unittest {
 
 ## Format Comparison
 
-| Format | Use Case | Output Size |
-|--------|----------|-------------|
-| `verbose` | Development, debugging | Large |
-| `compact` | AI tools, log aggregation | Small |
-| `tap` | CI/CD, test harnesses | Medium |
+| Format | Audience | Use Case | Output Size |
+|--------|----------|----------|-------------|
+| `verbose` | Humans | Local development, debugging | Large |
+| `tap` | Machines | CI/CD pipelines, test harnesses, reporting tools | Medium |
+| `compact` | AI assistants | Claude Code, token-limited contexts | Small |
 
 ## Example Outputs
 

docs/src/content/docs/guide/context-data.mdx

@@ -173,9 +173,10 @@ void validateOrder(Order order) {
 
 ## Limits
 
-- Context is limited to 8 key-value pairs per assertion
+- Context is limited to 8 key-value pairs per assertion (defined by `MAX_CONTEXT_ENTRIES`)
 - Keys and values are converted to strings using `std.conv.to!string`
 - Context is cleared between assertions
+- If you exceed 8 context entries, a warning is displayed in the output indicating that additional entries were dropped
 
 ## Next Steps