0-RTT scope for future revisions (§5.3)

[arkstack-dev]

v0.1 forbids 0-RTT entirely. §5.3 leaves the door open for narrowly scoped idempotent operations in future revisions.

What would those operations realistically be? Candidates I can think of:

• Re-establishing a session after migration where the auth state survives
• Read-only prepared statement execution against a previously authenticated
  session (requires session resumption semantics that v0.1 doesn't have)

I'd rather hear use cases than speculate.