com.wallstop-studios.dxmessaging 2.1.4 → 2.1.6

package/README.md

@@ -1,17 +1,32 @@
-# DxMessaging for Unity — The Modern Event System
+# DxMessaging for Unity
+
+<p align="center">
+  <img src="docs/images/DxMessaging-banner.svg" alt="DxMessaging Banner" width="800"/>
+</p>
+
+<p align="center">
+  <a href="https://wallstop.github.io/DxMessaging/">
+    <img src="https://img.shields.io/badge/📖_Full_Documentation-Visit_the_Docs_Site-2ea44f?style=for-the-badge" alt="Full Documentation" />
+  </a>
+</p>
 
 [![Unity](https://img.shields.io/badge/Unity-2021.3+-black.svg)](https://unity.com/releases/editor)<br/>
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE.md)<br/>
+[![openupm](https://img.shields.io/npm/v/com.wallstop-studios.dxmessaging?label=openupm&registry_uri=https://package.openupm.com)](https://openupm.com/packages/com.wallstop-studios.dxmessaging/)<br/>
 [![Version](https://img.shields.io/npm/v/com.wallstop-studios.dxmessaging.svg)](https://www.npmjs.com/package/com.wallstop-studios.dxmessaging)<br/>
-[![Performance: OS-Specific Benchmarks](https://img.shields.io/badge/Performance-OS--specific-blueviolet.svg)](Docs/Performance.md)<br/>
+[![Performance: OS-Specific Benchmarks](https://img.shields.io/badge/Performance-OS--specific-blueviolet.svg)](docs/architecture/performance.md)<br/>
 [![Markdown Link Validity](https://github.com/wallstop/DxMessaging/actions/workflows/markdown-link-validity.yml/badge.svg)](https://github.com/wallstop/DxMessaging/actions/workflows/markdown-link-validity.yml)<br/>
 [![Markdown Link Text Check](https://github.com/wallstop/DxMessaging/actions/workflows/markdown-link-text-check.yml/badge.svg)](https://github.com/wallstop/DxMessaging/actions/workflows/markdown-link-text-check.yml)
 
-**DxMessaging is a high‑performance, type‑safe messaging system** that replaces sprawling C# events, brittle UnityEvents, and global static event buses with a clean, observable, and predictable communication pattern.
+> **🤖 AI Assistance Disclosure:**
+>
+> This project has been actively developed and maintained by human authors for over a decade. Recent versions have utilized AI assistance for documentation, test coverage, and performance optimizations.
+
+**DxMessaging is a type-safe messaging system** that replaces sprawling C# events, brittle UnityEvents, and global static event buses with an observable and lifecycle-managed communication pattern.
 
-Think of it as **the event system Unity should have built-in** — one that actually scales.
+Think of it as: A messaging system designed for decoupled game systems.
 
-Need install instructions for Git URLs, scoped registries, or tarballs? Jump to the [Install Guide](Docs/Install.md).
+Need install instructions? Try [OpenUPM](https://openupm.com/packages/com.wallstop-studios.dxmessaging/) (recommended) or see the [Install Guide](docs/getting-started/install.md) for Git URLs, scoped registries, and more.
 
 ## Table of Contents
 
@@ -19,7 +34,7 @@ Need install instructions for Git URLs, scoped registries, or tarballs? Jump to
 - [Quick Start (5 Minutes)](#quick-start-5-minutes)
 - [Is DxMessaging Right for You?](#is-dxmessaging-right-for-you)
 - [Why DxMessaging?](#why-dxmessaging)
-- [Killer Features](#killer-features)
+- [Key Features](#key-features)
 - [The DxMessaging Solution](#the-dxmessaging-solution)
 - [Real-World Examples](#real-world-examples)
 - [Performance](#performance)
@@ -41,9 +56,9 @@ Need install instructions for Git URLs, scoped registries, or tarballs? Jump to
 - Wondered "which event fired when?" with no way to see message flow
 - Copy-pasted event boilerplate dozens of times
 
-#### Then DxMessaging solves your problems
+#### Then DxMessaging can help address these challenges
 
-- **Zero memory leaks** - automatic lifecycle management, no manual unsubscribe
+- **Automatic lifecycle management** - manages subscription lifecycle automatically, no manual unsubscribe
 - **Zero coupling** - systems communicate without knowing each other exist
 - **Full visibility** - see every message in the Inspector with timestamps and payloads
 - **Complete control** - priority-based ordering, validation, and interception
@@ -54,24 +69,30 @@ Need install instructions for Git URLs, scoped registries, or tarballs? Jump to
 1. **Targeted** - "Tell Player to heal" (commands to specific entities)
 1. **Broadcast** - "I took damage" (things that happen to _you_ that others can observe)
 
-**One line:** It's the event system Unity should have shipped with - type-safe, leak-proof, and actually debuggable. 🚀
+**One line:** It's a type-safe messaging system with automatic lifecycle management and built-in inspection tools.
 
 ---
 
 ## Quick Start (5 Minutes)
 
-**New to messaging?** Start with the [Visual Guide](Docs/VisualGuide.md) (5 min) for a beginner-friendly introduction!
+**New to messaging?** Start with the [Visual Guide](docs/getting-started/visual-guide.md) (5 min) for a beginner-friendly introduction!
 
 ### 1. Install
 
-Via Unity Package Manager → Add package from git URL (see the [Install Guide](Docs/Install.md) for scoped registry, tarball, and offline options):
+#### Via OpenUPM (Recommended)
+
+```bash
+openupm add com.wallstop-studios.dxmessaging
+```
+
+##### Or via Git URL
 
 ```bash
 # Unity Package Manager > Add package from git URL...
 https://github.com/wallstop/DxMessaging.git
 ```
 
-Prefer OpenUPM, scoped registries, or local tarballs? The [Install Guide](Docs/Install.md) covers every path in detail.
+See the [Install Guide](docs/getting-started/install.md) for all options including NPM scoped registries and local tarballs.
 
 ### 2. Define Your First Message
 
@@ -112,9 +133,9 @@ var msg = new OpenChest(chestId: 42);
 msg.EmitComponentTargeted(chestComponent);
 ```
 
-**Done!** No manual unsubscribe, no leaks, full type safety.
+No manual unsubscribe needed. Subscriptions are type-safe and lifecycle-managed.
 
-**Stuck?** See [Troubleshooting](Docs/Troubleshooting.md) or [FAQ](Docs/FAQ.md)
+**Stuck?** See [Troubleshooting](docs/reference/troubleshooting.md) or [FAQ](docs/reference/faq.md)
 
 ---
 
@@ -146,30 +167,30 @@ public class PlayerService : IInitializable, IDisposable
 
 - **DI for construction** — Inject services, repositories, managers via constructors
 - **Messaging for events** — Reactive, decoupled communication for gameplay events
-- **Best of both worlds** — Clean architecture with testable, isolated buses
+- **Combined approach** — Clean architecture with testable, isolated buses
 
 #### Automatic integration for
 
 - ✅ **Zenject/Extenject** — Full-featured DI with extensive Unity support
 - ✅ **VContainer** — Lightweight, high-performance DI with scoped lifetimes
-- ✅ **Reflex** — Minimal API, blazing-fast dependency injection
+- ✅ **Reflex** — Minimal API, high-performance dependency injection
 
 ##### Get started
 
-- [Zenject Integration Guide](Docs/Integrations/Zenject.md) — Complete setup with examples
-- [VContainer Integration Guide](Docs/Integrations/VContainer.md) — Scoped buses for scene isolation
-- [Reflex Integration Guide](Docs/Integrations/Reflex.md) — Minimal, lightweight patterns
+- [Zenject Integration Guide](docs/integrations/zenject.md) — Complete setup with examples
+- [VContainer Integration Guide](docs/integrations/vcontainer.md) — Scoped buses for scene isolation
+- [Reflex Integration Guide](docs/integrations/reflex.md) — Minimal, lightweight patterns
 
 ##### Core DI concepts
 
-- [Runtime Configuration](Docs/RuntimeConfiguration.md) — Setting message buses at runtime, re-binding registrations
-- [Message Bus Providers](Docs/MessageBusProviders.md) — Provider system for design-time and runtime bus configuration
+- [Runtime Configuration](docs/advanced/runtime-configuration.md) — Setting message buses at runtime, re-binding registrations
+- [Message Bus Providers](docs/advanced/message-bus-providers.md) — Provider system for design-time and runtime bus configuration
 
-**Not using DI?** No problem! DxMessaging works perfectly standalone with zero dependencies.
+**Not using DI?** No problem. DxMessaging works standalone with zero dependencies.
 
 ---
 
-## Is DxMessaging Right for You
+## Is DxMessaging Right for You?
 
 ### ✅ Use DxMessaging When
 
@@ -178,8 +199,8 @@ public class PlayerService : IInitializable, IDisposable
 - **Memory leaks are a concern** - You've been bitten by forgotten event unsubscribes before
 - **You value observability** - Need to debug "what fired when?" or track message flow
 - **Teams/long-term maintenance** - Multiple developers, or you'll maintain this code for years
-- **You want decoupling** - Hate when UI classes need references to 15 different game systems
-- **You're using DI frameworks** - Seamless integration with Zenject/VContainer/Reflex (see [DI Compatible](#-dependency-injection-di-compatible))
+- **You want decoupling** - When UI classes need references to many game systems
+- **You're using DI frameworks** - Compatible with Zenject/VContainer/Reflex (see [DI Compatible](#-dependency-injection-di-compatible))
 
 ### ❌ Don't Use DxMessaging When
 
@@ -191,31 +212,32 @@ public class PlayerService : IInitializable, IDisposable
 
 ### ⚠️ Maybe Use DxMessaging (Start Small)
 
-- **Existing large codebase** - Migrate incrementally: start with new features, refactor old code gradually (see [Migration Guide](Docs/MigrationGuide.md))
+- **Existing large codebase** - Migrate incrementally: start with new features, refactor old code gradually (see [Migration Guide](docs/guides/migration-guide.md))
 - **Small team learning** - Try it for one system (e.g., achievements) before going all-in
 - **Mid-size projects (5-20k lines)** - Evaluate after trying it for one complex interaction (e.g., combat or scene transitions)
 
 ### Decision Flow
 
-```text
-Does your project have 3+ systems that need to talk to each other?
-  NO → Stick with C# events or direct references
-  YES ↓
-
-Are you okay with a small upfront learning investment?
-  NO → Stick with what you know
-  YES ↓
-
-Do you need observable, decoupled, lifecycle-safe messaging?
-  YES → ✅ Use DxMessaging
-  NO → ❌ Keep it simple
+```mermaid
+flowchart TD
+    Q1{Does your project have 3+<br/>systems that need to talk to each other?}
+    Q1 -->|NO| A1[Stick with C# events or direct references]
+    Q1 -->|YES| Q2
+
+    Q2{Are you okay with a small<br/>upfront learning investment?}
+    Q2 -->|NO| A2[Stick with what you know]
+    Q2 -->|YES| Q3
+
+    Q3{Do you need observable, decoupled,<br/>lifecycle-safe messaging?}
+    Q3 -->|YES| A3["✅ Use DxMessaging"]
+    Q3 -->|NO| A4["❌ Keep it simple"]
 ```
 
-**Rule of thumb:** If you're reading this README and thinking "wow, this would solve SO many problems," then DxMessaging is for you. If you're thinking "this seems complicated," start with the [Visual Guide](Docs/VisualGuide.md) or stick with simpler patterns.
+**Rule of thumb:** If you're reading this README and thinking "this could address several challenges I'm facing," then DxMessaging may be a good fit. If you're thinking "this seems complicated," start with the [Visual Guide](docs/getting-started/visual-guide.md) or stick with simpler patterns.
 
-**New to messaging?** Start with the [Visual Guide](Docs/VisualGuide.md) (5 min) for a beginner-friendly introduction!
+**New to messaging?** Start with the [Visual Guide](docs/getting-started/visual-guide.md) (5 min) for a beginner-friendly introduction!
 
-Looking for hard numbers? See OS-specific [Performance Benchmarks](Docs/Performance.md).
+Looking for hard numbers? See OS-specific [Performance Benchmarks](docs/architecture/performance.md).
 
 ## Why DxMessaging
 
@@ -257,7 +279,7 @@ public class GameUI : MonoBehaviour {
 }
 ```
 
-**Your UI now depends on EVERYTHING.** Good luck refactoring that.
+**Your UI now depends on many systems.** Refactoring becomes more difficult.
 
 ###### Scenario 3: The Debugging Black Hole
 
@@ -267,17 +289,19 @@ You think: "Okay, which of the 47 events touching health failed? And in what ord
 
 **30 minutes later:** Still setting breakpoints everywhere...
 
-### Common Problems
+### Common Challenges
 
-- ❌ **Memory leaks** from forgotten unsubscribes (every Unity dev's nightmare)
-- ❌ **Tight coupling** making refactoring terrifying ("change one thing, break five others")
-- ❌ **No execution order control** ("why does the UI update before the player takes damage?")
-- ❌ **Impossible to debug** ("what fired when?" has no answer)
-- ❌ **Boilerplate overload** (write 50 lines for 3 events)
+Some developers encounter these challenges when working with traditional event systems:
+
+- **Memory leaks** from forgotten unsubscribes
+- **Tight coupling** making refactoring difficult
+- **No execution order control** leading to unpredictable behavior
+- **Limited debugging visibility** for tracking message flow
+- **Boilerplate code** when managing many event subscriptions
 
 ### The DxMessaging Solution
 
-#### Same scenarios, zero pain
+#### Same scenarios, simplified handling
 
 ##### Scenario 1: No More Memory Leaks
 
@@ -287,12 +311,12 @@ public class GameUI : MessageAwareComponent {
         base.RegisterMessageHandlers();
         _ = Token.RegisterUntargeted<ScoreChanged>(UpdateScore);
     }
-    // That's it! No manual cleanup needed.
+    // No manual cleanup needed.
     // Token automatically handles OnEnable/OnDisable/OnDestroy
 }
 ```
 
-**Automatic lifecycle = impossible to leak.** 🎉
+###### Automatic lifecycle = leaks are prevented by default
 
 ###### Scenario 2: No More Coupling
 
@@ -310,7 +334,7 @@ public class GameUI : MessageAwareComponent {
 }
 ```
 
-**Your UI is now independent.** Swap systems freely without breaking anything.
+**Your UI is now independent.** Swapping systems no longer requires updating UI references.
 
 ###### Scenario 3: Debugging is Built In
 
@@ -332,12 +356,12 @@ Active Registrations:
 ### How It Transforms Your Code
 
 ```csharp
-// 1. Define messages (clean, typed, discoverable)
+// 1. Define messages (typed, discoverable)
 [DxTargetedMessage]
 [DxAutoConstructor]
 public readonly partial struct Heal { public readonly int amount; }
 
-// 2. Listen (automatic lifecycle - zero leaks)
+// 2. Listen (automatic lifecycle - prevents leaks)
 public class Player : MessageAwareComponent {
     protected override void RegisterMessageHandlers() {
         base.RegisterMessageHandlers();
@@ -357,7 +381,7 @@ heal.EmitComponentTargeted(playerComponent);
 
 #### What you get
 
-- ✅ **Zero memory leaks** - tokens clean up automatically when components are destroyed
+- ✅ **Automatic cleanup** - tokens clean up when components are destroyed
 - ✅ **Zero coupling** - no SerializeFields, no GetComponent, no direct references
 - ✅ **Full visibility** - see message flow in Inspector with timestamps and payloads
 - ✅ **Predictable order** - priority-based execution (no more mystery race conditions)
@@ -365,11 +389,11 @@ heal.EmitComponentTargeted(playerComponent);
 - ✅ **Intercept & validate** - enforce rules before handlers run (clamp damage, block invalid input)
 - ✅ **Extension points everywhere** - interceptors, handlers, post-processors with priorities
 
-## Killer Features
+## Key Features
 
-Why DxMessaging is different:
+What DxMessaging offers:
 
-### 🚀 Performance: Zero-Allocation, Zero-Leak Design
+### Performance: Zero-Allocation Design
 
 **The problem with normal events:** Boxing allocations, GC spikes, memory leaks from forgotten unsubscribes.
 
@@ -379,12 +403,12 @@ Why DxMessaging is different:
 void OnDamage(ref TookDamage msg) {  // Pass by ref = zero allocations
     health -= msg.amount;            // No boxing, no GC pressure
 }
-// Automatic cleanup = zero leaks, guaranteed
+// Automatic cleanup prevents common leak patterns
 ```
 
-**Real-world impact:** A game emitting 1000 messages/second uses **zero GC** with DxMessaging vs. 40KB/sec with boxed events.
+**Note:** Struct messages passed by ref avoid GC allocations, which is standard behavior for value types in C#.
 
-### 🎯 Three Message Types That Actually Make Sense
+### Three Message Types
 
 Most event systems force you into one pattern. DxMessaging gives you the right tool for each job:
 
@@ -407,7 +431,7 @@ public struct TookDamage { public int amount; }
 
 **Why this matters:** You're not forcing everything through one generic "Event<T>" pattern. Each message type has clear semantics.
 
-### 🔄 The Message Pipeline
+### The Message Pipeline
 
 Every message flows through 3 stages with priority control:
 
@@ -416,16 +440,13 @@ flowchart LR
     P[Producer] --> I[Interceptors<br/>validate/mutate]
     I --> H[Handlers<br/>main logic]
     H --> PP[Post-Processors<br/>analytics/logging]
-    style I fill:#ffe7ba,stroke:#d48806,stroke-width:2px,color:#000
-    style H fill:#91d5ff,stroke:#096dd9,stroke-width:2px,color:#000
-    style PP fill:#b7eb8f,stroke:#389e0d,stroke-width:2px,color:#000
 ```
 
-### 🎭 Global Observers: Listen to EVERYTHING (Unique Feature!)
+### Global Observers: Listen to All Events
 
 **The problem with normal events:** To track all player damage, enemy damage, and NPC damage, you need 3 separate event subscriptions.
 
-**DxMessaging's superpower:** Subscribe ONCE to a message type, receive ALL instances with source information:
+**DxMessaging approach:** Subscribe once to a message type, receive all instances with source information:
 
 ```csharp
 // Track ALL damage from ANY source (players, enemies, NPCs, environment)
@@ -445,9 +466,9 @@ _ = token.RegisterBroadcastWithoutSource<TookDamage>(
 - **Analytics:** Aggregate stats from all entities without knowing about them upfront
 - **Debug tools:** Watch ALL messages in the Inspector without instrumenting code
 
-**Why this is revolutionary:** Traditional event buses require you to know entity types upfront. DxMessaging lets you observe dynamically.
+**How this differs:** Some event bus patterns require subscribing to each entity type separately. DxMessaging allows observing all instances of a message type in one registration.
 
-### 🛡️ Interceptors: Validate Before Execution (Safety Built In)
+### Interceptors: Validate Before Execution
 
 **The problem with normal events:** Validation logic duplicated in every handler, or bugs when you forget.
 
@@ -482,7 +503,7 @@ void OnDamage(ref TookDamage msg) {
 - Block messages during cutscenes
 - Log/audit sensitive actions
 
-### 🔍 Built-in Inspector Diagnostics (Actually Debuggable!)
+### Built-in Inspector Diagnostics
 
 **The problem with normal events:** "Which event fired? When? Who handled it? In what order?" = 🤷
 
@@ -514,9 +535,9 @@ void OnDamage(ref TookDamage msg) {
 
 **No more:** Setting 50 breakpoints and stepping through code for 30 minutes.
 
-### 🏝️ Local Bus Islands for Testing (Actually Testable!)
+### Local Bus Islands for Testing
 
-**The problem with normal events:** Global static events contaminate tests. Mock hell. Flaky tests.
+**The problem with normal events:** Global static events contaminate tests. Mock complexity. Flaky tests.
 
 **DxMessaging solution:** Each test gets its own isolated message bus:
 
@@ -544,29 +565,33 @@ public void TestAchievementSystem() {
 - Tests don't interfere with each other
 - No "arrange/act/cleanup" boilerplate
 - No mocking frameworks needed
-- Parallel test execution works perfectly
+- Parallel test execution is supported
 
 ## Documentation
 
+- **[📖 Documentation Site](https://wallstop.github.io/DxMessaging/)** - Full searchable documentation
+- **[📚 Wiki](https://github.com/wallstop/DxMessaging/wiki)** - Quick reference wiki
+- **[📋 Changelog](CHANGELOG.md)** - Version history
+
 ### 🎓 Learn
 
-- **New here?** Start with [Getting Started Guide](Docs/GettingStarted.md) (10 min read)
-- **Want patterns?** See [Common Patterns](Docs/Patterns.md)
-- **Deep dive?** Read [Design & Architecture](Docs/DesignAndArchitecture.md)
+- **New here?** Start with [Getting Started Guide](docs/getting-started/getting-started.md) (10 min read)
+- **Want patterns?** See [Common Patterns](docs/guides/patterns.md)
+- **Deep dive?** Read [Design & Architecture](docs/architecture/design-and-architecture.md)
 
 ### 📚 Core Concepts
 
-- [Overview](Docs/Overview.md) — What and why
-- [Quick Start](Docs/QuickStart.md) — First message in 5 minutes
-- [Message Types](Docs/MessageTypes.md) — When to use Untargeted/Targeted/Broadcast
-- [Interceptors & Ordering](Docs/InterceptorsAndOrdering.md) — Control execution flow
-- [Listening Patterns](Docs/ListeningPatterns.md) — All the ways to receive messages
+- [Overview](docs/getting-started/overview.md) — What and why
+- [Quick Start](docs/getting-started/quick-start.md) — First message in 5 minutes
+- [Message Types](docs/concepts/message-types.md) — When to use Untargeted/Targeted/Broadcast
+- [Interceptors & Ordering](docs/concepts/interceptors-and-ordering.md) — Control execution flow
+- [Listening Patterns](docs/concepts/listening-patterns.md) — All the ways to receive messages
 
 ### 🔧 Unity Integration
 
-- [Unity Integration](Docs/UnityIntegration.md) — MessagingComponent deep dive
-- [Targeting & Context](Docs/TargetingAndContext.md) — GameObject vs Component
-- [Diagnostics](Docs/Diagnostics.md) — Inspector tools and debugging
+- [Unity Integration](docs/guides/unity-integration.md) — MessagingComponent deep dive
+- [Targeting & Context](docs/concepts/targeting-and-context.md) — GameObject vs Component
+- [Diagnostics](docs/guides/diagnostics.md) — Inspector tools and debugging
 
 Important: Inheritance with MessageAwareComponent
 
@@ -580,14 +605,14 @@ Important: Inheritance with MessageAwareComponent
 
 DxMessaging works standalone (zero dependencies) or with any major DI framework. For detailed setup guides and code examples:
 
-- **[Zenject Integration Guide](Docs/Integrations/Zenject.md)** — Full-featured DI with extensive Unity support
-- **[VContainer Integration Guide](Docs/Integrations/VContainer.md)** — Lightweight DI with scoped lifetimes for scene isolation
-- **[Reflex Integration Guide](Docs/Integrations/Reflex.md)** — Minimal API, blazing-fast performance
+- **[Zenject Integration Guide](docs/integrations/zenject.md)** — Full-featured DI with extensive Unity support
+- **[VContainer Integration Guide](docs/integrations/vcontainer.md)** — Lightweight DI with scoped lifetimes for scene isolation
+- **[Reflex Integration Guide](docs/integrations/reflex.md)** — Minimal API, high-performance DI
 
 #### Core DI concepts
 
-- **[Runtime Configuration](Docs/RuntimeConfiguration.md)** — Setting and overriding message buses at runtime, re-binding registrations
-- **[Message Bus Providers](Docs/MessageBusProviders.md)** — Provider system and MessageBusProviderHandle for flexible bus configuration
+- **[Runtime Configuration](docs/advanced/runtime-configuration.md)** — Setting and overriding message buses at runtime, re-binding registrations
+- **[Message Bus Providers](docs/advanced/message-bus-providers.md)** — Provider system and MessageBusProviderHandle for flexible bus configuration
 
 Each guide includes:
 
@@ -600,8 +625,8 @@ See the [🔧 DI Compatible section](#-dependency-injection-di-compatible) above
 
 ### 🆚 Comparisons
 
-- [Compare with Other Unity Messaging Frameworks](Docs/Comparisons.md) — In-depth comparison with UniRx, MessagePipe, Zenject Signals, C# events, UnityEvents, and more
-- [Scriptable Object Architecture (SOA) Compatibility](Docs/Patterns.md#14-compatibility-with-scriptable-object-architecture-soa) — Migration patterns and interoperability with SOA
+- [Compare with Other Unity Messaging Frameworks](docs/architecture/comparisons.md) — In-depth comparison with UniRx, MessagePipe, Zenject Signals, C# events, UnityEvents, and more
+- [Scriptable Object Architecture (SOA) Compatibility](docs/guides/patterns.md#14-compatibility-with-scriptable-object-architecture-soa) — Migration patterns and interoperability with SOA
 
 #### Quick Framework Comparison
 
@@ -616,7 +641,7 @@ See the [🔧 DI Compatible section](#-dependency-injection-di-compatible) above
 ##### Choose DxMessaging when you want
 
 - Unity-first design with GameObject/Component targeting
-- Automatic lifecycle management (zero memory leaks)
+- Automatic lifecycle management (prevents common memory leaks)
 - Inspector debugging to see message flow and history
 - Execution order control (priority-based handlers)
 - Message validation/interception pipeline
@@ -624,11 +649,11 @@ See the [🔧 DI Compatible section](#-dependency-injection-di-compatible) above
 - Post-processing stage (analytics, logging after handlers)
 - No dependencies, plug-and-play setup
 
-See [full comparison](Docs/Comparisons.md) for detailed analysis with code examples, performance benchmarks, and decision guides.
+See [full comparison](docs/architecture/comparisons.md) for detailed analysis with code examples, performance benchmarks, and decision guides.
 
 > **📦 Using Scriptable Object Architecture (SOA)?**
 >
-> DxMessaging can work alongside or replace SOA patterns. See [SOA Compatibility Guide](Docs/Patterns.md#14-compatibility-with-scriptable-object-architecture-soa) for:
+> DxMessaging can work alongside or replace SOA patterns. See [SOA Compatibility Guide](docs/guides/patterns.md#14-compatibility-with-scriptable-object-architecture-soa) for:
 >
 > - Fair comparison of SOA vs. DxMessaging
 > - Migration patterns from GameEvent/FloatVariable to DxMessaging
@@ -637,17 +662,17 @@ See [full comparison](Docs/Comparisons.md) for detailed analysis with code examp
 
 ### 📖 Reference
 
-- [Install Guide](Docs/Install.md) — All install options (Git URL, scoped registry, tarball, manual copy)
-- [Glossary](Docs/Glossary.md) — All terms explained in plain English
-- [Quick Reference](Docs/QuickReference.md) — Cheat sheet
-- [API Reference](Docs/Reference.md) — Complete API
-- [Helpers](Docs/Helpers.md) — Source generators and utilities
-- [FAQ](Docs/FAQ.md) — Common questions
-- [Troubleshooting](Docs/Troubleshooting.md)
+- [Install Guide](docs/getting-started/install.md) — All install options (OpenUPM, Git URL, scoped registry, tarball)
+- [Glossary](docs/reference/glossary.md) — All terms explained in plain English
+- [Quick Reference](docs/reference/quick-reference.md) — Cheat sheet
+- [API Reference](docs/reference/reference.md) — Complete API
+- [Helpers](docs/reference/helpers.md) — Source generators and utilities
+- [FAQ](docs/reference/faq.md) — Common questions
+- [Troubleshooting](docs/reference/troubleshooting.md)
 
 ### 📦 Full Documentation
 
-Browse all docs: [Documentation Hub](Docs/Index.md)
+Browse all docs: [Documentation Hub](docs/getting-started/index.md)
 
 ## Real-World Examples
 
@@ -686,9 +711,9 @@ public class AchievementTracker : MessageAwareComponent {
     protected override void RegisterMessageHandlers() {
         base.RegisterMessageHandlers();
         _ = Token.RegisterGlobalAcceptAll(
-            onUntargeted: (ref IUntargetedMessage m) => Check(m),
-            onTargeted: (ref InstanceId t, ref ITargetedMessage m) => Check(m),
-            onBroadcast: (ref InstanceId s, ref IBroadcastMessage m) => Check(m)
+            acceptAllUntargeted: m => Check(m),
+            acceptAllTargeted: (t, m) => Check(m),
+            acceptAllBroadcast: (s, m) => Check(m)
         );
     }
 }
@@ -701,9 +726,9 @@ public class AchievementTracker : MessageAwareComponent {
 - **Type-indexed caching** for O(1) lookups
 - **Optimized for hot paths** with aggressive inlining
 
-See [Design & Architecture](Docs/DesignAndArchitecture.md#performance-optimizations) for details.
+See [Design & Architecture](docs/architecture/design-and-architecture.md#performance-optimizations) for details.
 
-For OS-specific benchmark tables generated by PlayMode tests, see [Performance Benchmarks](Docs/Performance.md).
+For OS-specific benchmark tables generated by PlayMode tests, see [Performance Benchmarks](docs/architecture/performance.md).
 
 ## Comparison Table
 
@@ -722,7 +747,7 @@ For OS-specific benchmark tables generated by PlayMode tests, see [Performance B
 | **Interceptors**         | ✅ Pipeline        | ❌ No              | ⚠️ Filters         | ❌ No              |
 | **Post-Processing**      | ✅ Dedicated       | ❌ No              | ⚠️ Filters         | ❌ No              |
 | **Stream Operators**     | ❌ No              | ✅ Extensive       | ❌ No              | ⚠️ With UniRx      |
-| **Performance**          | ✅ Good (14M)      | ✅ Good (18M)      | ✅ Best (97M)      | ⚠️ Moderate (2.5M) |
+| **Performance**          | ✅ Good (14M)      | ✅ Good (18M)      | ✅ High (97M)      | ⚠️ Moderate (2.5M) |
 | **Dependencies**         | ✅ None            | ⚠️ UniTask         | ✅ None            | ⚠️ Zenject         |
 
 ### Comparison with Traditional Approaches
@@ -751,7 +776,7 @@ Import samples from Package Manager:
 - .NET Standard 2.1
 - Works with all render pipelines (URP, HDRP, Built-in)
 
-See [Compatibility](Docs/Compatibility.md) for details.
+See [Compatibility](docs/reference/compatibility.md) for details.
 
 ## Contributing
 
@@ -769,8 +794,7 @@ Created and maintained by [wallstop studios](https://wallstopstudios.com)
 
 - 📦 [Package on GitHub](https://github.com/wallstop/DxMessaging)
 - 🐛 [Report Issues](https://github.com/wallstop/DxMessaging/issues)
-- 📘 [Full Documentation](Docs/Index.md)
+- 📖 [Documentation Site](https://wallstop.github.io/DxMessaging/)
+- 📚 [Wiki](https://github.com/wallstop/DxMessaging/wiki)
 
 ---
-
-**Stop fighting events. Start messaging.** 🚀

package/Runtime/Core/MessageBus/IMessageBus.cs

@@ -56,10 +56,29 @@ namespace DxMessaging.Core.MessageBus
 
         long EmissionId { get; }
 
+        /// <summary>
+        /// Default buffer size for message emission history.
+        /// </summary>
+        /// <remarks>
+        /// This constant is used as the default value for <see cref="GlobalMessageBufferSize"/>
+        /// and should be referenced by any settings classes to avoid configuration drift.
+        /// </remarks>
+        const int DefaultMessageBufferSize = 100;
+
         /// <summary>
         /// Default ring buffer size for emission history when diagnostics are enabled.
         /// </summary>
-        static int GlobalMessageBufferSize { get; set; }
+        /// <remarks>
+        /// <para>
+        /// Controls the maximum number of <see cref="Diagnostics.MessageEmissionData"/> records retained
+        /// per <see cref="MessageBus"/> instance when <see cref="DiagnosticsMode"/> is active.
+        /// </para>
+        /// <para>
+        /// The default value is <see cref="DefaultMessageBufferSize"/> (100). Setting this to 0 will
+        /// cause emissions to be silently discarded (no history is retained).
+        /// </para>
+        /// </remarks>
+        static int GlobalMessageBufferSize { get; set; } = DefaultMessageBufferSize;
 
         internal static int GlobalSequentialIndex = -1;