[eosobande]

Clarify how applications use the existing result APIs. This is a documentation-only change: runtime behavior and public signatures are unchanged.

• Explain that restoring navigation does not restore an in-memory pending result, and that the app chooses missing-result recovery before dependent work starts.
• Show abandoned-request cleanup with the existing consume(key) overload, including nullable values, unrelated keys and late producer callbacks.
• Clarify same-key publication inside a callback, including equal payloads and the lack of automatic redelivery.
• Add a reading path through the existing API contracts.

The diff contains only README and KDoc changes in ResultStore, ResultConsumer and ResultEffect. Existing CI/CD, Gradle files and tests are unchanged. No Python tooling or publication-verification fixtures remain.

Validation: the existing 33 library and 4 sample Android JVM tests passed, with no failures or skips.

This PR remains a draft.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
🔒 Security Review	🔄 Running since 2026-10-26T21:09:22.107910Z	82ae769	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[atunwo]

This documentation-only change clarifies transient result lifetime, abandoned-request cleanup, callback republishing limitations, and the API reading path without changing runtime code or public signatures. No blocking issues found; the added guidance is consistent with the inspected store, consumer, effect, and state-helper implementations. Supplied CI reports all five checks successful. I did not independently run builds or tests, and callback republishing is not directly covered by the inspected test cases.