SOW-0153: Go stability guide links to the install guide; Rust writer-state APIs named

KT
5h ago
+94-50

Stacked on #21. Completes SOW-0153 (.agents/sow/done/SOW-0153-20261007-consumer-docs-release-clarity.md).

Decisions for review

  • Agent-chosen, pending your review: decision 1A. go/API.md no longer names a version (it said go/v0.3.0); it links to go/README.md, the one guide that carries the install command and is checked by the release script.

Changes

  • docs/Writer-APIs.md and docs/Indexed-Snapshots.md name Rust JournalError::WriterPoisoned, JournalWriter::is_poisoned() and Log::is_poisoned() beside Go ErrWriterFailed.
  • Docs only; no code or example changes.

Validation

  • check_wiki_docs.py: OK.
  • git diff --check: clean.
  • Same-failure search for other stale go/v0.x claims: none in active docs.

Summary by cubic

Completes SOW-0153: the Go stability guide no longer names a stale go/v0.3.0 tag, linking to go/README.md for the current release instead, and the writer docs now name the Rust writer-state APIs beside the Go equivalents.

  • go/API.md links to go/README.md, which carries the install command and is checked by the release script.
  • docs/Writer-APIs.md and docs/Indexed-Snapshots.md describe Rust poisoning: the failing call returns its own error, later mutations return JournalError::WriterPoisoned (wrapped as WriterError::Journal by Log), and JournalWriter::is_poisoned() / Log::is_poisoned() report the state.
  • SOW-0153 is marked completed in both SOW status ledgers, with the decision approval and validation recorded; ledger entries lost in the stack merge were restored.
  • Docs only; no code or example changes. check_wiki_docs.py and the docs example run pass, no stale go/v0.x claims remain, and the branch is merged with sow-0122/journalctl-perf.