diff --git a/docs/api/async-logger-state-new.md b/docs/api/async-logger-state-new.md
index b3afd5c..4f5fce1 100644
--- a/docs/api/async-logger-state-new.md
+++ b/docs/api/async-logger-state-new.md
@@ -54,6 +54,7 @@ Detailed rules explaining key parameters and behaviors
 - `AsyncLogger::state()` is the higher-level API that reads these values from a concrete logger.
 - It also does not validate whether the supplied fields represent a combination that could come from one real logger instant.
 - The constructed value matches the same public shape used by async logger serializers.
+- Because `AsyncLoggerState` is only a data snapshot type, this constructor is mainly useful for tests, adapters, and synthetic diagnostics rather than ordinary logger inspection.
 
 ### How to Use
 
diff --git a/docs/api/async-logger-state-type.md b/docs/api/async-logger-state-type.md
index 5ab70ac..06d9c13 100644
--- a/docs/api/async-logger-state-type.md
+++ b/docs/api/async-logger-state-type.md
@@ -34,6 +34,7 @@ Detailed rules explaining key parameters and behaviors
 - The remaining fields capture queue counts, lifecycle status, failure state, last error text, and active flush policy.
 - `AsyncLogger::state()` returns this type directly, while `async_logger_state_to_json(...)` and `stringify_async_logger_state(...)` export the same data shape for diagnostics.
 - `AsyncLogger::state()` currently builds this snapshot from `async_runtime_state()` plus the logger's current counters, lifecycle flags, last error, and flush policy.
+- `AsyncLoggerState::new(...)` can also construct this type manually, but manual construction is synthetic snapshot data and does not read one live logger instant by itself.
 
 ### How to Use
 
diff --git a/docs/api/async-runtime-state-new.md b/docs/api/async-runtime-state-new.md
index 602e453..ed8c6ed 100644
--- a/docs/api/async-runtime-state-new.md
+++ b/docs/api/async-runtime-state-new.md
@@ -42,6 +42,7 @@ Detailed rules explaining key parameters and behaviors
 - `async_runtime_state()` is the higher-level API that reads these values from the live runtime environment.
 - It also does not validate whether the supplied pair matches the current backend contract.
 - The constructed value matches the same public shape used by async runtime serializers.
+- Because `AsyncRuntimeState` is only a data snapshot type, this constructor is mainly useful for tests, adapters, and synthetic diagnostics rather than ordinary runtime probing.
 
 ### How to Use
 
diff --git a/docs/api/async-runtime-state-type.md b/docs/api/async-runtime-state-type.md
index 42d5ca4..3560852 100644
--- a/docs/api/async-runtime-state-type.md
+++ b/docs/api/async-runtime-state-type.md
@@ -34,6 +34,7 @@ Detailed rules explaining key parameters and behaviors
 - `async_runtime_state()` returns this type directly as an environment-level snapshot.
 - `async_runtime_state()` currently builds that snapshot from `async_runtime_mode()` and `async_runtime_supports_background_worker()`.
 - `async_runtime_state_to_json(...)` and `stringify_async_runtime_state(...)` serialize the same snapshot shape for diagnostics.
+- `AsyncRuntimeState::new(...)` can also construct this type manually, but manual construction is synthetic data and does not probe the current backend by itself.
 
 ### How to Use