* feat: poll async document creation tasks
* feat: opt document creation into async promotion
* feat: surface log id on async document creation failures
A task that ends in "failed" arrives inside a successful HTTP envelope,
so the caller builds the error itself and dropped the x-tt-logid that
support escalations need. The create response's log id is carried in
too, covering a task that already failed before the first poll.
Co-Authored-By: Claude <noreply@anthropic.com>
* fix(doc): keep async document creation synchronous to callers
* feat(doc): add internal creation timing diagnostics
* test(docs): verify async polling before resource uploads
* refactor(docs): keep creation log IDs out of shared runtime
* test(docs): cover creation client and empty-response errors
* fix(docs): simplify async creation failure recovery
* fix(docs): shorten creation timeout guidance
* fix(docs): validate creation recovery command examples
* fix(docs): clarify async timeout recovery and cover unknown status
---------
Co-authored-by: Claude <noreply@anthropic.com>
SunPeiYang996