update nexus guides (#3821)

* update nexus guides

Signed-off-by: Phil Prasek <prasek@gmail.com>

* Update temporal-nexus.mdx

Fixing a couple of bad links

---------

Signed-off-by: Phil Prasek <prasek@gmail.com>
Co-authored-by: Brian MacDonald <brian.macdonald@temporal.io>

Author: prasek

docs/develop/go/temporal-nexus.mdx

@@ -194,9 +194,9 @@ var HelloOperation = temporalnexus.NewWorkflowRunOperation(service.HelloOperatio
 Workflow IDs should typically be business-meaningful IDs and are used to dedupe Workflow starts.
 For the `HelloOperation`, `input.ID` is passed as part of the Nexus Service contract.
 
-:::tip SUPPORT, STABILITY, and DEPENDENCY INFO
+:::tip RESOURCES
 
-[Attaching multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) using a [Conflict-Policy of Use-Existing](/workflow-execution/workflowid-runid#workflow-id-conflict-policy) is a [Pre-release feature](/evaluate/development-production-features/release-stages#pre-release).
+[Attach multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) with a Conflict-Policy of Use-Existing.
 
 :::
 

docs/develop/java/temporal-nexus.mdx

@@ -274,9 +274,9 @@ public class NexusServiceImpl {
 
 Workflow IDs should typically be business-meaningful IDs and are used to dedupe Workflow starts. In general, the ID should be passed in the Operation input as part of the Nexus Service contract.
 
-:::tip SUPPORT, STABILITY, and DEPENDENCY INFO
+:::tip RESOURCES
 
-[Attaching multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) using a [Conflict-Policy of Use-Existing](/workflow-execution/workflowid-runid#workflow-id-conflict-policy) is a [Pre-release feature](/evaluate/development-production-features/release-stages#pre-release).
+[Attach multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) with a Conflict-Policy of Use-Existing.
 
 :::
 

docs/develop/python/index.mdx

@@ -135,6 +135,17 @@ Use compression, encryption, and other data handling by implementing custom conv
 - [Custom Payload Codec](/develop/python/converters-and-encryption#custom-payload-codec)
 - [Payload Conversion](/develop/python/converters-and-encryption#payload-conversion)
 
+## Temporal Nexus
+
+The [Temporal Nexus](/develop/python/nexus) feature guide shows how to use Temporal Nexus to connect durable executions within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
+
+- [Create a Nexus Endpoint to route requests from caller to handler](/develop/python/nexus#create-nexus-endpoint)
+- [Define the Nexus Service contract](/develop/python/nexus#define-nexus-service-contract)
+- [Develop a Nexus Service and Operation handlers](/develop/python/nexus#develop-nexus-service-operation-handlers)
+- [Develop a caller Workflow that uses a Nexus Service](/develop/python/nexus#develop-caller-workflow-nexus-service)
+- [Make Nexus calls across Namespaces with a dev Server](/develop/python/nexus#register-the-caller-workflow-in-a-worker-and-start-the-caller-workflow)
+- [Make Nexus calls across Namespaces in Temporal Cloud](/develop/python/nexus#nexus-calls-across-namespaces-temporal-cloud)
+
 ## [Durable Timers](/develop/python/timers)
 
 Use Timers to make a Workflow Execution pause or "sleep" for seconds, minutes, days, months, or years.

docs/develop/python/temporal-nexus.mdx

@@ -180,12 +180,11 @@ class MyNexusServiceHandler:
 
 Workflow IDs should typically be business-meaningful IDs and are used to dedupe Workflow starts. In general, the ID should be passed in the Operation input as part of the Nexus Service contract.
 
-<!-- TODO: feature does not exist in Python pre-release yet -->
-<!-- :::tip SUPPORT, STABILITY, and DEPENDENCY INFO
+:::tip RESOURCES
 
-[Attaching multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) using a [Conflict-Policy of Use-Existing](/workflow-execution/workflowid-runid#workflow-id-conflict-policy) is a [Pre-release feature](/evaluate/development-production-features/release-stages#pre-release).
+[Attach multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) with a Conflict-Policy of Use-Existing.
 
-::: -->
+:::
 
 ### Register your Nexus Service handler in a Worker
 

docs/develop/typescript/index.mdx

@@ -122,6 +122,17 @@ Use compression, encryption, and other data handling by implementing custom conv
 
 - [Custom Payload Codec](/develop/typescript/converters-and-encryption#custom-payload-conversion)
 
+## Temporal Nexus
+
+The [Temporal Nexus](/develop/typescript/nexus) feature guide shows how to use Temporal Nexus to connect durable executions within and across Namespaces using a Nexus Endpoint, a Nexus Service contract, and Nexus Operations.
+
+- [Create a Nexus Endpoint to route requests from caller to handler](/develop/typescript/nexus#create-nexus-endpoint)
+- [Define the Nexus Service contract](/develop/typescript/nexus#define-nexus-service-contract)
+- [Develop a Nexus Service and Operation handlers](/develop/typescript/nexus#develop-nexus-service-operation-handlers)
+- [Develop a caller Workflow that uses a Nexus Service](/develop/typescript/nexus#develop-caller-workflow-nexus-service)
+- [Make Nexus calls across Namespaces with a dev Server](/develop/typescript/nexus#register-the-caller-workflow-in-a-worker-and-start-the-caller-workflow)
+- [Make Nexus calls across Namespaces in Temporal Cloud](/develop/typescript/nexus#nexus-calls-across-namespaces-temporal-cloud)
+
 ## [Durable Timers](/develop/typescript/timers)
 
 Use Timers to make a Workflow Execution pause or "sleep" for seconds, minutes, days, months, or years.

docs/develop/typescript/temporal-nexus.mdx

@@ -41,7 +41,7 @@ This page shows how to do the following:
 
 :::note
 
-This documentation uses source code derived from the [TypeScript Nexus sample](https://github.com/temporalio/samples-typescript/tree/main/hello_nexus).
+This documentation uses source code derived from the [TypeScript Nexus sample](https://github.com/temporalio/samples-typescript/tree/main/nexus-hello).
 
 :::
 
@@ -232,9 +232,9 @@ export const helloServiceHandler = nexus.serviceHandler(helloService, {
 Workflow IDs should typically be business-meaningful IDs and are used to dedupe Workflow starts.
 In general, the ID should be passed in the Operation input as part of the Nexus Service contract.
 
-:::tip SUPPORT, STABILITY, and DEPENDENCY INFO
+:::tip RESOURCES
 
-[Attaching multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) using a [Conflict-Policy of Use-Existing](/workflow-execution/workflowid-runid#workflow-id-conflict-policy) is a [Pre-release feature](/evaluate/development-production-features/release-stages#pre-release).
+[Attach multiple Nexus callers to a handler Workflow](/nexus/operations#attaching-multiple-nexus-callers) with a Conflict-Policy of Use-Existing.
 
 :::
 
@@ -296,6 +296,8 @@ export async function helloCallerWorkflow(name: string, language: LanguageCode):
 
 <!--SNIPEND-->
 
+### Register the caller Workflow in a Worker and start the caller Workflow
+
 This Workflow can be registered with a Worker and started using `client.startWorkflow()` or `client.executeWorkflow()`, as usual.
 Refer to the [complete TypeScript sample](https://github.com/temporalio/samples-typescript/blob/main/nexus-hello) for reference.
 
@@ -308,7 +310,7 @@ Temporal provides general guidance on [Errors in Nexus operations](https://docs.
 In TypeScript, there are three Nexus-specific exception classes:
 
 - `nexus-rpc`'s [`OperationError`](https://nexus-rpc.github.io/sdk-typescript/classes/OperationError.html): this is the exception type you should throw in a Nexus operation to indicate that it has failed according to its own application logic and should not be retried.
-- `nexus-rpc`'s [`HandlerError`](https://nexus-rpc.github.io/sdk-typescript/classes/HandlerError.html): you can throw this exception type in a Nexus operation with a specific [HandlerErrorType](https://nexus-rpc.github.io/sdk-typescript/nexusrpc.HandlerErrorType.html). The error will be marked as either retryable or non-retryable according to the type, following the [Nexus spec](https://github.com/nexus-rpc/api/blob/main/SPEC.md#predefined-handler-errors). The non-retryable handler error types are `BAD_REQUEST`, `UNAUTHENTICATED`, `UNAUTHORIZED`, `NOT_FOUND`, `NOT_IMPLEMENTED`; the retryable types are `RESOURCE_EXHAUSTED`, `INTERNAL`, `UNAVAILABLE`, `UPSTREAM_TIMEOUT`.
+- `nexus-rpc`'s [`HandlerError`](https://nexus-rpc.github.io/sdk-typescript/classes/HandlerError.html): you can throw this exception type in a Nexus operation with a specific [HandlerErrorType](https://nexus-rpc.github.io/sdk-typescript/types/HandlerErrorType.html). The error will be marked as either retryable or non-retryable according to the type, following the [Nexus spec](https://github.com/nexus-rpc/api/blob/main/SPEC.md#predefined-handler-errors). The non-retryable handler error types are `BAD_REQUEST`, `UNAUTHENTICATED`, `UNAUTHORIZED`, `NOT_FOUND`, `NOT_IMPLEMENTED`; the retryable types are `RESOURCE_EXHAUSTED`, `INTERNAL`, `UNAVAILABLE`, `UPSTREAM_TIMEOUT`.
 - `@temporalio/nexus`'s [`NexusOperationFailure`](https://typescript.temporal.io/api/classes/common.NexusOperationFailure): this is the error thrown inside a Workflow when a Nexus operation fails for any reason. Use the `cause` attribute on the exception to access the cause chain.
 
 ## Canceling a Nexus Operation {#canceling-a-nexus-operation}
@@ -397,7 +399,7 @@ tcld namespace create \
 	--retention-days 1
 ```
 
-Alternatively, you can create Namespaces through the UI: [https://cloud.temporal.io/Namespaces](https://cloud.temporal.io/Namespaces).
+Alternatively, you can create Namespaces through the UI: [https://cloud.temporal.io/namespaces](https://cloud.temporal.io/namespaces).
 
 ### Create a Nexus Endpoint to route requests from caller to handler
 

docs/encyclopedia/nexus.mdx

@@ -57,6 +57,8 @@ Nexus Operations can be implemented with Temporal primitives, like Workflows, or
 
 - [Go SDK - Nexus quick start and code sample](/develop/go/nexus)
 - [Java SDK - Nexus quick start and code sample](/develop/java/nexus)
+- [Python SDK - Nexus quick start and code sample](/develop/python/nexus)
+- [TypeScript SDK - Nexus quick start and code sample](/develop/typescript/nexus)
   :::
 
 ## Queue-based Worker architecture