docs(telemetry): state the crash-repair export semantics for resumed streams

Review finding: synthetic turn closers written by SessionPersistence .load() at crash-resume sit below firstLiveSeq and are never exported, leaving the remote turn unbalanced. Kept deliberately — exporting a synthetic closer cannot complete a turn whose real tail records died in the crashed process's queue; it can only make an incomplete turn look closed. The OTel README now states the receiver rule (a never-closed turn on a resumed stream marks the previous process dying inside it; a later clean shutdown marker attests only to the resumed process's exit), and the revival Agent Note records why the repair suffix stays local.
2026-07-27 19:49:19 +08:00
parent 6adb14b56d
commit a72436105b
6 changed files with 8 additions and 8 deletions
@@ -2,5 +2,5 @@
 # side as of the last confirmed-consistent state. Both languages carry equal authority;
 # after editing either side, bring the other along and re-record with:
 #   pnpm run verify-translation-pairing --write
-README.md: 8dd2c4f6535d6d3ea772f7669185f62c4694ca43
-README.zh.md: 42bc9b7ddbbf6d9cb104de35d9489e6e583e1df7
+README.md: 6ead0ec7b7053551676b482dd4c905c8cd7cc1fe
+README.zh.md: 852242bfc4ac719660f31935167d2f4fa0f58f2e