changing format back

Author: MasonEgger

instruqt/01-run-monolith/assignment.md

@@ -48,11 +48,13 @@ timelimit: 600
 enhanced_loading: null
 ---
 
+# Chapter 1: Run the Monolith
+
 Before you decouple anything, run the application as it ships today and
 feel where the seams are. This chapter is observation only. There is no
 code to edit.
 
-# Why this chapter exists
+## Why this chapter exists
 
 Every distributed-systems story has a "before" picture, and this is ours.
 
@@ -96,7 +98,7 @@ half independently. The bridge between the two will be a Temporal
 
 But first, the monolith.
 
-# What you will do
+## What you will do
 
 - Start the Payments Worker as it exists today (compliance and all).
 - Run three transactions through it: a low-risk approval, a medium-risk
@@ -105,7 +107,7 @@ But first, the monolith.
   ordinary `ActivityTaskScheduled` event in the Payments workflow's
   history. There is no boundary to be seen.
 
-# Step 1: Start the Payments Worker
+## Step 1: Start the Payments Worker
 
 Click the [button label="Worker" background="#444CE7"](tab-1) terminal.
 Start the Worker:
@@ -137,7 +139,7 @@ Two things to notice in that banner:
 
 Leave the Worker running. The next step uses a different terminal.
 
-# Step 2: Run three transactions
+## Step 2: Run three transactions
 
 Click the [button label="Starter" background="#444CE7"](tab-2)
 terminal. Run the starter:
@@ -188,7 +190,7 @@ blocks should look something like this:
 > function returned cleanly. This distinction matters again in
 > Chapter 7 when we look at real failures.
 
-# Step 3: Inspect the Web UI
+## Step 3: Inspect the Web UI
 
 Click the [button label="Temporal UI" background="#444CE7"](tab-3) tab.
 Make sure the namespace selector at the top is set to `default`.
@@ -219,7 +221,7 @@ replace the Activity call with a **Nexus Operation** call: a typed
 remote-invocation primitive that runs in a different namespace, with a
 different worker, owned by a different team.
 
-# Step 4: Stop the Worker
+## Step 4: Stop the Worker
 
 Back in the [button label="Worker" background="#444CE7"](tab-1)
 terminal, stop the Worker with `Ctrl+C` so it does not pollute the next
@@ -235,7 +237,7 @@ You can also stop it from the Starter terminal with:
 pkill -f "payments.worker" || true
 ```
 
-# Wrapping up
+## Wrapping up
 
 In this chapter you ran the application as it exists before any Nexus
 work. Three transactions executed end-to-end through a single Worker

instruqt/02-service-contract/assignment.md

@@ -44,12 +44,14 @@ timelimit: 1200
 enhanced_loading: null
 ---
 
+# Chapter 2: Define the Nexus Service Contract
+
 In this chapter you define the shared Nexus Service contract between the
 Payments and Compliance teams, and stand up the routing infrastructure
 that will carry calls across the team boundary: a Nexus Endpoint that
 points callers at the Compliance team's task queue.
 
-# Why this chapter exists
+## Why this chapter exists
 
 Nexus exists so that two teams can call each other's Temporal code
 without sharing a codebase or a namespace. The mechanism that makes that
@@ -85,7 +87,7 @@ reads first when they want to call your Service.
 > what makes the contract a third artifact rather than something
 > either team can change unilaterally.
 
-# What you will do
+## What you will do
 
 - Apply **TODO 1** to add `@nexusrpc.service` and the typed Operation
   declarations to `shared/service.py`.
@@ -94,7 +96,7 @@ reads first when they want to call your Service.
   CLI, attaching a Markdown description from `compliance-endpoint.md`.
 - Find the Endpoint in the Web UI and read its Markdown description.
 
-# Step 1: Apply TODO 1 in `shared/service.py`
+## Step 1: Apply TODO 1 in `shared/service.py`
 
 Open `shared/service.py` in the
 [button label="Code Editor" background="#444CE7"](tab-0). The file
@@ -146,7 +148,7 @@ stub until Chapter 6 turns it into a real Update sender.
 > lines must use the `nexusrpc.Operation[Input, Output]` annotation
 > form (no `=`, no body).
 
-# Step 2: Verify the namespaces
+## Step 2: Verify the namespaces
 
 The Payments and Compliance teams will live in separate namespaces from
 Chapter 3 onwards. Each namespace is its own isolated execution
@@ -163,7 +165,7 @@ temporal operator namespace list
 You should see `payments-namespace` and `compliance-namespace`
 alongside `default` and `temporal-system`.
 
-# Step 3: Create the Nexus Endpoint
+## Step 3: Create the Nexus Endpoint
 
 A Nexus Endpoint is a routing rule. It tells the server: when a caller
 invokes the Endpoint named `compliance-endpoint`, deliver the request
@@ -198,7 +200,7 @@ temporal operator nexus endpoint get --name compliance-endpoint
 The `get` output should include the Markdown description from
 `compliance-endpoint.md` under the `Description` field.
 
-# Step 4: Find the Endpoint in the Web UI
+## Step 4: Find the Endpoint in the Web UI
 
 Click the [button label="Temporal UI" background="#444CE7"](tab-2)
 tab. In the left navigation, click **Nexus Endpoints** (or browse to
@@ -213,7 +215,7 @@ exposes before writing a caller workflow against it.**
 The Endpoint exists at the cluster level. It is not scoped to any one
 namespace. That is what lets it bridge teams.
 
-# Wrapping up
+## Wrapping up
 
 You wrote the contract that the Payments and Compliance teams will
 share, and you registered the routing rule that the dev server will use

instruqt/03-sync-handler/assignment.md

@@ -56,13 +56,15 @@ timelimit: 1800
 enhanced_loading: null
 ---
 
+# Chapter 3: Implement the Sync Handler
+
 Now you write the Compliance side. By the end of the chapter the
 Compliance Worker will be running in `compliance-namespace`, polling
 the `compliance-risk` task queue, with a registered handler for the
 `check_compliance` Nexus Operation. Payments is unchanged; it still
 calls a local Activity.
 
-# Why this chapter exists
+## Why this chapter exists
 
 A Nexus Operation has two sides: the **caller** (the workflow that
 invokes the Operation) and the **handler** (the code that fulfills it).
@@ -90,7 +92,7 @@ The decorator stack that turns a class into a Nexus handler is small:
 That is the whole API. The handler is just an async method that takes
 the typed input and returns the typed output.
 
-# What you will do
+## What you will do
 
 - Apply **TODO 2** to decorate `ComplianceNexusServiceHandler` and
   implement the `check_compliance` and `submit_review` methods.
@@ -104,7 +106,7 @@ because Chapter 4 has not happened yet. The Compliance Worker is up
 but nothing is calling it. That is expected. We are validating the
 plumbing, not the data flow.
 
-# Step 1: Apply TODO 2 in `compliance/service_handler.py`
+## Step 1: Apply TODO 2 in `compliance/service_handler.py`
 
 Open `compliance/service_handler.py` in the
 [button label="Code Editor" background="#444CE7"](tab-0). The file
@@ -154,7 +156,7 @@ contract. If you mistype the input or output, Python's type checker
 will not catch it at file-load time, but the Nexus runtime will reject
 the registration when the Worker starts.
 
-# Step 2: Apply TODO 3 in `compliance/worker.py`
+## Step 2: Apply TODO 3 in `compliance/worker.py`
 
 Open `compliance/worker.py`. Find the TODO 3 comment in the `Worker(...)`
 constructor call. Add the `nexus_service_handlers` argument:
@@ -171,7 +173,7 @@ The Worker polls the `compliance-risk` task queue (set above by the
 `TASK_QUEUE` constant). That name **must** match the
 `--target-task-queue` you gave when creating the Endpoint in Chapter 2.
 
-# Step 3: Start the Compliance Worker
+## Step 3: Start the Compliance Worker
 
 Click the
 [button label="Compliance Worker" background="#444CE7"](tab-1)
@@ -198,7 +200,7 @@ Two things to notice:
 
 Leave the Worker running.
 
-# Step 4: Start the Payments Worker
+## Step 4: Start the Payments Worker
 
 Click the
 [button label="Payments Worker" background="#444CE7"](tab-2) terminal.
@@ -212,7 +214,7 @@ This is still the **monolith** version of the Payments Worker. It runs
 in `payments-namespace`, polls `payments-processing`, and uses its
 local `check_compliance` Activity. We swap that out in Chapter 4.
 
-# Step 5: Run the starter
+## Step 5: Run the starter
 
 Click the [button label="Starter" background="#444CE7"](tab-3)
 terminal. Run the starter:
@@ -230,7 +232,7 @@ routed through Nexus yet.**
 That is the expected end-state for Chapter 3. The Compliance Worker is
 a Nexus participant, but no caller has been wired to it.
 
-# Step 6: Confirm both Workers are healthy
+## Step 6: Confirm both Workers are healthy
 
 In the Web UI, click **Workers** in the left navigation. Switch
 namespaces with the selector at the top.
@@ -242,7 +244,7 @@ namespaces with the selector at the top.
 
 Both Workers are alive. Chapter 4 connects them.
 
-# Step 7: Stop both Workers
+## Step 7: Stop both Workers
 
 Press `Ctrl+C` in both Worker terminals (or use the cleanup at the
 end of the challenge). You can also stop them from the Starter
@@ -253,7 +255,7 @@ pkill -f "compliance.worker" || true
 pkill -f "payments.worker"   || true
 ```
 
-# Wrapping up
+## Wrapping up
 
 You wrote the synchronous handler that fulfills the `check_compliance`
 contract, and you stood up a brand new Compliance Worker to serve it.

instruqt/04-caller-swap/assignment.md

@@ -56,12 +56,14 @@ timelimit: 1500
 enhanced_loading: null
 ---
 
+# Chapter 4: Swap the Caller to Nexus
+
 This is the moment the application stops being a monolith. The
 Payments Workflow stops calling a local Activity for compliance and
 starts calling the Compliance team's Nexus Operation instead. Once
 that swap lands, no Compliance code runs in the Payments Worker.
 
-# Why this chapter exists
+## Why this chapter exists
 
 Chapter 3 stood up the Compliance handler. Chapter 2 created the
 Endpoint. Both halves of the routing infrastructure exist. What is
@@ -94,7 +96,7 @@ Payments Worker's Activities list. The Payments Worker no longer
 needs that import; it lives entirely on the caller side of the Nexus
 boundary.
 
-# What you will do
+## What you will do
 
 - Apply **TODO 4** to swap the activity call for a Nexus call in
   `payments/workflows.py`.
@@ -107,7 +109,7 @@ boundary.
 - Inspect the Event History to confirm the two-event sync pattern
   (`NexusOperationScheduled`, `NexusOperationCompleted`).
 
-# Step 1: Apply TODO 4 in `payments/workflows.py`
+## Step 1: Apply TODO 4 in `payments/workflows.py`
 
 Open `payments/workflows.py` in the
 [button label="Code Editor" background="#444CE7"](tab-0). Find the
@@ -160,7 +162,7 @@ Two things to notice:
 Also remove the now-unused `check_compliance` import from the top of
 the file. Your editor or `ruff` will flag it.
 
-# Step 2: Apply TODO 5 in `payments/worker.py`
+## Step 2: Apply TODO 5 in `payments/worker.py`
 
 Open `payments/worker.py`. Find the TODO 5 comment in the Activities
 list:
@@ -193,7 +195,7 @@ Two cleanups:
 After this, **the Payments Worker no longer imports any Compliance
 code.** Browse the file imports if you want to verify.
 
-# Step 3: Start the Compliance Worker
+## Step 3: Start the Compliance Worker
 
 Click the
 [button label="Compliance Worker" background="#444CE7"](tab-1)
@@ -205,7 +207,7 @@ uv run python -m compliance.worker
 
 Same Worker as Chapter 3. Leave it running.
 
-# Step 4: Start the Payments Worker
+## Step 4: Start the Payments Worker
 
 Click the
 [button label="Payments Worker" background="#444CE7"](tab-2) terminal:
@@ -220,7 +222,7 @@ is created inside the workflow at runtime, not registered on the
 Worker.) The Activities list should be `validate_payment,
 execute_payment` only.
 
-# Step 5: Run the starter
+## Step 5: Run the starter
 
 Click the [button label="Starter" background="#444CE7"](tab-3)
 terminal:
@@ -237,7 +239,7 @@ TXN-C declined HIGH. **Same outcomes, different mechanism.**
 > real human-in-the-loop review by replacing the sync handler with a
 > workflow-backed one that waits on a Workflow Update.
 
-# Step 6: Inspect the Event History
+## Step 6: Inspect the Event History
 
 Click the
 [button label="Temporal UI" background="#444CE7"](tab-4) tab. Switch
@@ -264,7 +266,7 @@ the Endpoint, and the namespace boundary, **without** paying for a
 second workflow. For short interactions, that is exactly what you
 want.
 
-# Step 7: Stop both Workers
+## Step 7: Stop both Workers
 
 Press `Ctrl+C` in both Worker terminals, or:
 
@@ -273,7 +275,7 @@ pkill -f "compliance.worker" || true
 pkill -f "payments.worker"   || true
 ```
 
-# Wrapping up
+## Wrapping up
 
 This was the structural pivot of the workshop. Before this chapter,
 Compliance and Payments were one process. After this chapter, they