Merge branch 'feat/serverless-worker-prerelease' of https://github.com/temporalio/documentation into feat/serverless-worker-prerelease

Author: lennessyy

docs/develop/plugins-guide.mdx

@@ -976,6 +976,9 @@ worker = Temporalio::Worker.new(
   </SdkTabs.Ruby>
 </SdkTabs>
 
-Check for duplicate side effects or other types of failures.
+Inside this replay regime, you should test for duplicate side effects or other types of failures. When testing for duplicate side effects, it may not be sufficient to simply have a counter that increments once per effect, as activities may be retried. Instead, consider these patterns:
+
+- count `ActivityTaskScheduled` events of the expected activity type in workflow history (one per intended call, independent of retries), 
+- or accumulate activity IDs in a concurrency-safe set and assert on its size (different scheduled activities get different IDs; retries of the same scheduled activity share one).
 
 It's harder to test against side effects to global variables, so this practice is best avoided entirely.

docs/develop/python/index.mdx

@@ -40,6 +40,8 @@ From there, you can dive deeper into any of the Temporal primitives to start bui
 - [Message passing](/develop/python/workflows/message-passing)
 - [Schedules](/develop/python/workflows/schedules)
 - [Timers](/develop/python/workflows/timers)
+- [Versioning](/develop/python/workflows/versioning)
+- [Workflow Streams](/develop/python/workflows/workflow-streams)
 
 ## [Activities](/develop/python/activities)
 

docs/develop/python/workflows/index.mdx

@@ -26,3 +26,4 @@ import * as Components from '@site/src/components';
 - [Schedules](/develop/python/workflows/schedules)
 - [Timers](/develop/python/workflows/timers)
 - [Versioning](/develop/python/workflows/versioning)
+- [Workflow Streams](/develop/python/workflows/workflow-streams)