docs(protocol): §3.9 activity — recent terminal outcomes (proto 2, pairs core#93)#14
Merged
Merged
Conversation
…ore PR 3/3) §3.9 reserved -> full: wire format, per-state field table (tx_hash only on executed, reason only on failed — absent, not null), relative age_secs with the backdated-expiry semantics, newest-first ordering, and the 100-outcome cap with its reason (the console's 64 KiB response mirror vs a lockout avalanche). §2 session line + family paragraph: activity joins context/positions as an auth-gated read-op — the family is complete, the 'future read-ops' sentence retires. §6 proto-2 row += activity. §3.11 unchanged on purpose: activity never answers wallet_locked (fixed in §3.9). No anchor moved — §3.9 was reserved by PR2 exactly for this.
…lete Gate-2 delta: §3.9 ordering wording now matches the store — chronological on the raw resolve instant (age_secs truncated after ordering; equal ages do not imply arbitrary order), id fallback only for truly simultaneous resolutions. §3.11: unauthorized and protocol_error rows now enumerate positions (stale since PR2) and activity.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Companion canon PR for rustok-org/core#93 (Console v2 Phase 2, core PR 3/3). Merge order: core first.
tx_hashonly on executed,reasononly on failed — absent, not null), relativeage_secswith backdated-expiry semantics, ordering by the raw resolve instant (newest first; equal ages do NOT imply arbitrary order — Gate-2 wording), the 100-outcome cap with its reason (the console's 64 KiB response mirror vs a lockout avalanche), and the explicit "nowallet_lockedhere". No anchor moved — §3.9 was reserved by PR2 exactly for this (heading-grep before/after identical apart from §3.9's own title).| activity; the auth-gated family paragraph now lists all three read-ops — the "Future read-ops…" sentence retires (family complete).activity(§3.9), both columns; preamble likewise.unauthorizedandprotocol_errorrows now enumeratepositions(stale since PR2) andactivity. Thewallet_lockedrow deliberately stayscontext, positions.