✅ cover async retry reset behavior

docs/api/async-logger-has-failed.md

@@ -36,7 +36,7 @@ Detailed rules explaining key parameters and behaviors
 - `run()` clears previous failure state at startup.
 - `run()` also clears the stored `last_error()` string at startup before drain work begins.
 - If the worker loop raises an error, the logger records that failure and exposes it through this flag.
-- Once set by a failed run, the flag stays `true` until a later `run()` start resets it.
+- Once set by a failed run, the flag stays `true` until a later `run()` invocation actually starts and resets it.
 - This helper is intentionally compact and should usually be paired with `last_error()` for details.
 - Failure state is about runtime drain execution, not whether records were dropped due to overflow policy.
 
@@ -73,7 +73,7 @@ e.g.:
 
 - If `has_failed()` is `true`, callers should inspect `last_error()` or `state()` for more context.
 
-- `close()` or `shutdown()` do not clear this flag by themselves; only a later `run()` start resets it.
+- `close()` or `shutdown()` do not clear this flag by themselves; only a later `run()` that has already started resets it.
 
 ### Notes
 

docs/api/async-logger-last-error.md

@@ -36,7 +36,7 @@ Detailed rules explaining key parameters and behaviors
 - `run()` resets the stored error string when the worker starts.
 - If the worker loop fails, the error text is captured from the raised exception.
 - An empty string normally means no failure has been recorded.
-- Once a failure string is recorded, it stays in place until a later `run()` start clears it.
+- Once a failure string is recorded, it stays in place until a later `run()` invocation actually starts and clears it.
 - This helper reports worker execution errors, not ordinary overflow or backpressure conditions.
 - A new successful `run()` attempt clears any previously stored error text before drain work begins again.
 
@@ -73,7 +73,7 @@ e.g.:
 
 - If callers need broader context than just the error text, they should use `state()`.
 
-- `close()` or `shutdown()` do not clear a previously recorded error string by themselves.
+- `close()` or `shutdown()` do not clear a previously recorded error string by themselves; the reset happens when a later `run()` has already started.
 
 ### Notes
 

docs/api/async-logger-run.md

@@ -34,7 +34,7 @@ pub async fn[S : @bitlogger.Sink] AsyncLogger::run(self : AsyncLogger[S]) -> Uni
 Detailed rules explaining key parameters and behaviors
 
 - `run()` sets `is_running` to `true` before worker execution begins.
-- Every invocation clears previous failure state first by setting `has_failed=false` and `last_error()` to an empty string.
+- Every invocation clears previous failure state first by setting `has_failed=false` and `last_error()` to an empty string once that `run()` call has actually started executing.
 - The method then keeps draining records until `queue.get()` stops with `AsyncLoggerClosed` or a worker error escapes.
 - On a normal queue-close exit, `run()` clears `is_running` and returns normally.
 - On failure, the logger records `has_failed=true`, stores the error text in `last_error`, clears `is_running`, and then raises the error back out of `run()`.