[brianstrauch]

Builds on the standalone-package migration in #384. Adds a Deep Agents sample whose activity-backed read_file tool returns 6 MiB of text. Native Temporal External Storage offloads the tool result and the following model input through the SDK's S3 driver, while the workflow returns a small byte count, SHA-256, and final answer.

The sample passes a DataConverter with External Storage to the standalone Deep Agents plugin, which composes its LangChain converter with that configuration. It uses the default 256 KiB threshold, so the workflow input, first model input, and final result stay inline. It reuses the existing local mock S3 service and scripts model replies, so it needs no AWS or LLM credentials. Includes setup documentation and a sample-index entry.

Validation:

• The integration test passes with a local Temporal server and verifies the full 6 MiB result and SHA-256, native references at both large activity boundaries, inline small payloads, and replay through a fresh S3 client after worker shutdown.
• The sample files pass Ruff import/format checks and mypy.

[DABH]

One functional/design issue needs attention: the worker-wide scripted-response cursor makes concurrent executions interfere with one another; see the inline P2.

The storage configuration itself is well scoped: the S3 client lives through payload access, the plugin composes the converter, and the test checks both large activity boundaries, inline small payloads, full-content integrity, and replay through a fresh storage client.

Local validation:

• The new integration test passed on Python 3.13.
• Ruff import/format checks and scoped mypy passed.
• A separate two-workflow probe on one worker reproduced stalled workflow tasks and execution timeouts with the current provider. Selecting scripted replies from each request's message history made both workflows complete with the expected 6 MiB size and SHA-256.

[DABH]

No actionable findings in the updated PR after reviewing correctness, design, functionality, test quality, and maintainability.

The earlier P2 is addressed by queue isolation. Each demo constructs its own client/plugin and now uses its unique workflow ID as the task queue for both the worker and workflow start. Model and tool activities inherit that queue, keeping each scripted-response cursor confined to its demo. This keeps the fix appropriately scoped to a self-contained External Storage example.

The new regression test runs two real main() invocations concurrently, checks both final answers and the size/SHA-256 assertions inside the driver, and verifies distinct workflow-specific queues. The existing test still checks both large activity boundaries, inline small payloads, complete content, forced replay, and replay through a fresh S3 client.

Validation at 1b09931 on Python 3.13:

• Both targeted tests passed against a local Temporal server.
• Both targeted tests passed against the time-skipping server.
• Scoped Ruff import/format checks and mypy passed.