[moetemp]

This PR merges Brook #41 into the Jetty crate and removes the auto close from the native Store. It also fixes the native findings of an independent review.

Jetty's crate is Brook's crate plus a native Store, which calls the Stream service of the Temporal server. The SDK review dropped auto close at every layer, and the server dropped it in moetemp/temporal#102.

What changed?

• The merge adds [Brook] Removed the auto close from the Stores, the service and the protos. #41, with the auto close removal and the crate review fixes. Examples are the close owner check, filtered reads past the scan cap, and the Redis ACL docs.
• The native Store no longer reads auto_close or sends it to the server, and its Store::auto_close is gone. A Workflow create still sends close_with_run.
• The proto copy equals [Jetty] Reserved auto_close in CreateStreamRequest and DescribeStreamResponse. api#31 byte for byte.

Review fixes on native.

• A FAILED_PRECONDITION with no Stream details or reason prefix maps to Storage. Every Stream error of the server has details, so only framework errors get this mapping.
• Native create, append and close send a 5 s deadline, the default of the Redis Store, in place of the connection's 30 s.
• A create conflict returns the server's stream_already_exists error, which names the stored Retention, not the requested one.
• The service refuses a sequence past 2^53 - 1 on native too. The server stores the sequence as an exact i64, so it would accept it.
• A test of no-wait filtered reads accepts the match in the first page. The server scans an empty filtered page to the end, which the contract allows.

The PR also pins the Jetty Core, moetemp/sdk-rust#210, at 2de24aef.

Please note that the native Store still doesn't send defer_withdrawal or a close's withdraw_run.

Why?

The review found that native writes used the connection's deadline, and that a conflict named the wrong Retention. It also found that framework errors could map to a Stream reason. The merge of #41 applies the Brook crate fixes to Jetty.

How did you test it?

On abd8955b, cargo test --workspace passes on memory, on Redis 8.10.1 standalone and as a cluster, and on native against a server built from moetemp/temporal#103. tests/native_calls.rs checks the deadline and the create conflict on a fake server. cargo fmt --check and clippy with -D warnings pass. The two commits after it, a merge of the comment pass of #41 and this PR's comment pass, change only comments and docs. They pass the same suites on memory and Redis. The sdk-streams fork CI passes on the head. It has no native lane.

The superproject branch temporalio/internal-ai-prototypes 2026/10/ai198-streams pins abd8955b, the tested commit.

• Unit Tests
• Staging
• End to End Tests