From 1dac502c4529c42f6e6a747f7e3362a7113cabd6 Mon Sep 17 00:00:00 2001
From: muemich <michaelmuellerrw@gmail.com>
Date: Mon, 4 May 2026 12:30:42 +0200
Subject: [PATCH 01/10] training setup test

---
 .github/renovate.json5                        |   3 +
 .github/workflows/deploy-attendee.yaml        | 138 ++++++++++
 helm-chart/templates/_helpers.tpl             |  22 ++
 helm-chart/templates/adservice.yaml           |   2 +-
 helm-chart/templates/cartservice.yaml         |   2 +-
 helm-chart/templates/checkoutservice.yaml     |   2 +-
 helm-chart/templates/currencyservice.yaml     |   2 +-
 helm-chart/templates/emailservice.yaml        |   2 +-
 helm-chart/templates/frontend.yaml            |   2 +-
 helm-chart/templates/loadgenerator.yaml       |   2 +-
 helm-chart/templates/paymentservice.yaml      |   2 +-
 .../templates/productcatalogservice.yaml      |   2 +-
 .../templates/recommendationservice.yaml      |   2 +-
 helm-chart/templates/shippingservice.yaml     |   2 +-
 helm-chart/values.yaml                        |   7 +
 training/.gitignore                           |   5 +
 training/README.md                            | 182 +++++++++++++
 training/bootstrap/attendees.csv.example      |   7 +
 training/bootstrap/emails-to-csv.sh           |  62 +++++
 training/bootstrap/emails.txt                 |  41 +++
 training/bootstrap/provision.sh               | 243 ++++++++++++++++++
 training/bootstrap/teardown.sh                |  36 +++
 .../currency-converter-mismatch/ANSWER.md     |  32 +++
 .../currency-converter-mismatch/BUG_REPORT.md |  25 ++
 .../currency-converter-mismatch/PATCH.diff    |  15 ++
 .../bugs/duplicate-recommendations/ANSWER.md  |  33 +++
 .../duplicate-recommendations/BUG_REPORT.md   |  22 ++
 .../bugs/duplicate-recommendations/PATCH.diff |  14 +
 .../bugs/search-misses-descriptions/ANSWER.md |  31 +++
 .../search-misses-descriptions/BUG_REPORT.md  |  27 ++
 .../search-misses-descriptions/PATCH.diff     |  14 +
 training/bugs/visa-rejected/ANSWER.md         |  35 +++
 training/bugs/visa-rejected/BUG_REPORT.md     |  23 ++
 training/bugs/visa-rejected/PATCH.diff        |  13 +
 training/k8s/install-reflector.sh             |  21 ++
 training/k8s/training-system.yaml             |  43 ++++
 training/terraform/main.tf                    | 108 ++++++++
 training/terraform/outputs.tf                 |  14 +
 training/terraform/providers.tf               |  14 +
 training/terraform/terraform.tfvars.example   |   3 +
 training/terraform/variables.tf               |  22 ++
 training/values-training.yaml                 | 124 +++++++++
 42 files changed, 1390 insertions(+), 11 deletions(-)
 create mode 100644 .github/workflows/deploy-attendee.yaml
 create mode 100644 helm-chart/templates/_helpers.tpl
 create mode 100644 training/.gitignore
 create mode 100644 training/README.md
 create mode 100644 training/bootstrap/attendees.csv.example
 create mode 100755 training/bootstrap/emails-to-csv.sh
 create mode 100644 training/bootstrap/emails.txt
 create mode 100755 training/bootstrap/provision.sh
 create mode 100755 training/bootstrap/teardown.sh
 create mode 100644 training/bugs/currency-converter-mismatch/ANSWER.md
 create mode 100644 training/bugs/currency-converter-mismatch/BUG_REPORT.md
 create mode 100644 training/bugs/currency-converter-mismatch/PATCH.diff
 create mode 100644 training/bugs/duplicate-recommendations/ANSWER.md
 create mode 100644 training/bugs/duplicate-recommendations/BUG_REPORT.md
 create mode 100644 training/bugs/duplicate-recommendations/PATCH.diff
 create mode 100644 training/bugs/search-misses-descriptions/ANSWER.md
 create mode 100644 training/bugs/search-misses-descriptions/BUG_REPORT.md
 create mode 100644 training/bugs/search-misses-descriptions/PATCH.diff
 create mode 100644 training/bugs/visa-rejected/ANSWER.md
 create mode 100644 training/bugs/visa-rejected/BUG_REPORT.md
 create mode 100644 training/bugs/visa-rejected/PATCH.diff
 create mode 100755 training/k8s/install-reflector.sh
 create mode 100644 training/k8s/training-system.yaml
 create mode 100644 training/terraform/main.tf
 create mode 100644 training/terraform/outputs.tf
 create mode 100644 training/terraform/providers.tf
 create mode 100644 training/terraform/terraform.tfvars.example
 create mode 100644 training/terraform/variables.tf
 create mode 100644 training/values-training.yaml

diff --git a/.github/renovate.json5 b/.github/renovate.json5
index a46ebf95c58..828bfab66ce 100644
--- a/.github/renovate.json5
+++ b/.github/renovate.json5
@@ -1,4 +1,7 @@
 {
+  // Renovate disabled in this training fork to avoid auto-PR noise during
+  // training days. Re-enable by removing `enabled: false` if upstreaming.
+  enabled: false,
   extends: [
     'github>GoogleCloudPlatform/kubernetes-engine-samples//.github/renovate-configs/dee-platform-ops.json5',
     'schedule:earlyMondays',
diff --git a/.github/workflows/deploy-attendee.yaml b/.github/workflows/deploy-attendee.yaml
new file mode 100644
index 00000000000..5baf5406e1b
--- /dev/null
+++ b/.github/workflows/deploy-attendee.yaml
@@ -0,0 +1,138 @@
+# Auto-deploy attendee branches.
+#
+# Triggers on push to attendee/<name> (i.e. after a PR is auto-merged into
+# the attendee's base branch). Detects which service was changed,
+# builds + pushes only that service's image to GAR, then helm-upgrades
+# the attendee's namespace to point that one service at the new tag.
+#
+# Repository variables this expects (Settings -> Secrets and variables -> Actions -> Variables):
+#   WIF_PROVIDER     full WIF provider resource name (terraform output workload_identity_provider)
+#   GAR_PUSHER_SA    email of the SA the workflow impersonates (terraform output github_pusher_sa_email)
+#   GCP_PROJECT_ID   re5-n8n-platform
+#   GAR_REGION       europe-west1
+#   GAR_REPO         microservices-demo-training
+#   GKE_CLUSTER      n8n-cluster
+#   GKE_REGION       europe-west1
+
+name: deploy-attendee
+
+on:
+  push:
+    branches:
+      - 'attendee/*'
+
+permissions:
+  contents: read
+  id-token: write
+
+concurrency:
+  group: deploy-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  detect:
+    runs-on: ubuntu-latest
+    outputs:
+      attendee: ${{ steps.parse.outputs.attendee }}
+      services: ${{ steps.changed.outputs.services }}
+      any_changed: ${{ steps.changed.outputs.any_changed }}
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+
+      - name: Parse attendee name from branch
+        id: parse
+        run: |
+          name="${GITHUB_REF_NAME#attendee/}"
+          if [[ ! "$name" =~ ^[a-z][a-z0-9-]{1,30}$ ]]; then
+            echo "branch name doesn't match attendee/<name> pattern: $GITHUB_REF_NAME"
+            exit 1
+          fi
+          echo "attendee=$name" >> "$GITHUB_OUTPUT"
+
+      - name: Detect changed services
+        id: changed
+        run: |
+          services=()
+          for svc in adservice cartservice checkoutservice currencyservice emailservice frontend loadgenerator paymentservice productcatalogservice recommendationservice shippingservice; do
+            if git diff --name-only HEAD^ HEAD | grep -q "^src/$svc/"; then
+              services+=("$svc")
+            fi
+          done
+          if [[ ${#services[@]} -eq 0 ]]; then
+            echo "no service changed - nothing to deploy"
+            echo "any_changed=false" >> "$GITHUB_OUTPUT"
+            echo "services=[]" >> "$GITHUB_OUTPUT"
+          else
+            echo "any_changed=true" >> "$GITHUB_OUTPUT"
+            json=$(printf '%s\n' "${services[@]}" | jq -R . | jq -sc .)
+            echo "services=$json" >> "$GITHUB_OUTPUT"
+            echo "changed: ${services[*]}"
+          fi
+
+  build-and-deploy:
+    needs: detect
+    if: needs.detect.outputs.any_changed == 'true'
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        service: ${{ fromJSON(needs.detect.outputs.services) }}
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Authenticate to GCP via WIF
+        id: auth
+        uses: google-github-actions/auth@v2
+        with:
+          workload_identity_provider: ${{ vars.WIF_PROVIDER }}
+          service_account: ${{ vars.GAR_PUSHER_SA }}
+
+      - name: Configure Docker for Artifact Registry
+        run: gcloud auth configure-docker ${{ vars.GAR_REGION }}-docker.pkg.dev --quiet
+
+      - name: Build and push image
+        env:
+          IMAGE: ${{ vars.GAR_REGION }}-docker.pkg.dev/${{ vars.GCP_PROJECT_ID }}/${{ vars.GAR_REPO }}/${{ matrix.service }}:attendee-${{ needs.detect.outputs.attendee }}-${{ github.sha }}
+        run: |
+          docker build -t "$IMAGE" "src/${{ matrix.service }}"
+          docker push "$IMAGE"
+          echo "image=$IMAGE" >> "$GITHUB_ENV"
+
+      - uses: google-github-actions/get-gke-credentials@v2
+        with:
+          cluster_name: ${{ vars.GKE_CLUSTER }}
+          location: ${{ vars.GKE_REGION }}
+
+      - name: Map service dir to Helm values key
+        id: valuekey
+        run: |
+          case "${{ matrix.service }}" in
+            adservice)              echo "key=adService" >> "$GITHUB_OUTPUT" ;;
+            cartservice)            echo "key=cartService" >> "$GITHUB_OUTPUT" ;;
+            checkoutservice)        echo "key=checkoutService" >> "$GITHUB_OUTPUT" ;;
+            currencyservice)        echo "key=currencyService" >> "$GITHUB_OUTPUT" ;;
+            emailservice)           echo "key=emailService" >> "$GITHUB_OUTPUT" ;;
+            frontend)               echo "key=frontend" >> "$GITHUB_OUTPUT" ;;
+            loadgenerator)          echo "key=loadGenerator" >> "$GITHUB_OUTPUT" ;;
+            paymentservice)         echo "key=paymentService" >> "$GITHUB_OUTPUT" ;;
+            productcatalogservice)  echo "key=productCatalogService" >> "$GITHUB_OUTPUT" ;;
+            recommendationservice)  echo "key=recommendationService" >> "$GITHUB_OUTPUT" ;;
+            shippingservice)        echo "key=shippingService" >> "$GITHUB_OUTPUT" ;;
+          esac
+
+      - name: Helm upgrade attendee namespace
+        env:
+          NS: attendee-${{ needs.detect.outputs.attendee }}
+          KEY: ${{ steps.valuekey.outputs.key }}
+          REPO: ${{ vars.GAR_REGION }}-docker.pkg.dev/${{ vars.GCP_PROJECT_ID }}/${{ vars.GAR_REPO }}
+          TAG: attendee-${{ needs.detect.outputs.attendee }}-${{ github.sha }}
+        run: |
+          helm upgrade boutique ./helm-chart \
+            --namespace "$NS" \
+            -f training/values-training.yaml \
+            --reuse-values \
+            --set "${KEY}.image.repository=${REPO}" \
+            --set "${KEY}.image.tag=${TAG}" \
+            --wait --timeout 5m
diff --git a/helm-chart/templates/_helpers.tpl b/helm-chart/templates/_helpers.tpl
new file mode 100644
index 00000000000..ce6d4429728
--- /dev/null
+++ b/helm-chart/templates/_helpers.tpl
@@ -0,0 +1,22 @@
+{{/*
+Renders the container image reference for a service.
+
+Resolution order (most specific wins):
+  1. .<service>.image.repository / .<service>.image.tag (per-service override)
+  2. .Values.images.repository / .Values.images.tag
+  3. .Chart.AppVersion (tag fallback only)
+
+Usage:
+  image: {{ include "onlineboutique.image" (list . .Values.checkoutService) }}
+*/}}
+{{- define "onlineboutique.image" -}}
+{{- $root := index . 0 -}}
+{{- $svc := index . 1 -}}
+{{- $repo := $root.Values.images.repository -}}
+{{- $tag := default $root.Chart.AppVersion $root.Values.images.tag -}}
+{{- if $svc.image -}}
+{{- $repo = default $repo $svc.image.repository -}}
+{{- $tag = default $tag $svc.image.tag -}}
+{{- end -}}
+{{- printf "%s/%s:%s" $repo $svc.name $tag -}}
+{{- end -}}
diff --git a/helm-chart/templates/adservice.yaml b/helm-chart/templates/adservice.yaml
index 6c07400afb8..41050429e37 100644
--- a/helm-chart/templates/adservice.yaml
+++ b/helm-chart/templates/adservice.yaml
@@ -69,7 +69,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.adService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.adService) }}
         ports:
         - containerPort: 9555
         env:
diff --git a/helm-chart/templates/cartservice.yaml b/helm-chart/templates/cartservice.yaml
index aebfc82c49e..ccbf945437e 100644
--- a/helm-chart/templates/cartservice.yaml
+++ b/helm-chart/templates/cartservice.yaml
@@ -73,7 +73,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.cartService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.cartService) }}
         ports:
         - containerPort: 7070
         env:
diff --git a/helm-chart/templates/checkoutservice.yaml b/helm-chart/templates/checkoutservice.yaml
index c93a7f58ac7..7a4b727f6dc 100644
--- a/helm-chart/templates/checkoutservice.yaml
+++ b/helm-chart/templates/checkoutservice.yaml
@@ -68,7 +68,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.checkoutService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.checkoutService) }}
         ports:
         - containerPort: 5050
         readinessProbe:
diff --git a/helm-chart/templates/currencyservice.yaml b/helm-chart/templates/currencyservice.yaml
index 7b547d2a889..6f154b590f1 100644
--- a/helm-chart/templates/currencyservice.yaml
+++ b/helm-chart/templates/currencyservice.yaml
@@ -69,7 +69,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.currencyService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.currencyService) }}
         ports:
         - name: grpc
           containerPort: 7000
diff --git a/helm-chart/templates/emailservice.yaml b/helm-chart/templates/emailservice.yaml
index 8a725a971ec..9e2ace61a78 100644
--- a/helm-chart/templates/emailservice.yaml
+++ b/helm-chart/templates/emailservice.yaml
@@ -69,7 +69,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.emailService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.emailService) }}
         ports:
         - containerPort: 8080
         env:
diff --git a/helm-chart/templates/frontend.yaml b/helm-chart/templates/frontend.yaml
index 2d6adec1891..6c1d65ec49e 100644
--- a/helm-chart/templates/frontend.yaml
+++ b/helm-chart/templates/frontend.yaml
@@ -70,7 +70,7 @@ spec:
                 - ALL
             privileged: false
             readOnlyRootFilesystem: true
-          image: {{ .Values.images.repository }}/{{ .Values.frontend.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+          image: {{ include "onlineboutique.image" (list . .Values.frontend) }}
           ports:
           - containerPort: 8080
           readinessProbe:
diff --git a/helm-chart/templates/loadgenerator.yaml b/helm-chart/templates/loadgenerator.yaml
index 8209f27b419..bcbd35d3695 100644
--- a/helm-chart/templates/loadgenerator.yaml
+++ b/helm-chart/templates/loadgenerator.yaml
@@ -106,7 +106,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.loadGenerator.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.loadGenerator) }}
         env:
         - name: FRONTEND_ADDR
           value: "{{ .Values.frontend.name }}:80"
diff --git a/helm-chart/templates/paymentservice.yaml b/helm-chart/templates/paymentservice.yaml
index 60ad2742c5a..81c58b053b2 100644
--- a/helm-chart/templates/paymentservice.yaml
+++ b/helm-chart/templates/paymentservice.yaml
@@ -69,7 +69,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.paymentService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.paymentService) }}
         ports:
         - containerPort: 50051
         env:
diff --git a/helm-chart/templates/productcatalogservice.yaml b/helm-chart/templates/productcatalogservice.yaml
index dec0e2d8827..3426ef8d030 100644
--- a/helm-chart/templates/productcatalogservice.yaml
+++ b/helm-chart/templates/productcatalogservice.yaml
@@ -69,7 +69,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.productCatalogService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.productCatalogService) }}
         ports:
         - containerPort: 3550
         env:
diff --git a/helm-chart/templates/recommendationservice.yaml b/helm-chart/templates/recommendationservice.yaml
index 828a14c236e..bf101ce3af9 100644
--- a/helm-chart/templates/recommendationservice.yaml
+++ b/helm-chart/templates/recommendationservice.yaml
@@ -69,7 +69,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.recommendationService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.recommendationService) }}
         ports:
         - containerPort: 8080
         readinessProbe:
diff --git a/helm-chart/templates/shippingservice.yaml b/helm-chart/templates/shippingservice.yaml
index 193bbd8e6cf..3cd434cff8a 100644
--- a/helm-chart/templates/shippingservice.yaml
+++ b/helm-chart/templates/shippingservice.yaml
@@ -68,7 +68,7 @@ spec:
               - ALL
           privileged: false
           readOnlyRootFilesystem: true
-        image: {{ .Values.images.repository }}/{{ .Values.shippingService.name }}:{{ .Values.images.tag | default .Chart.AppVersion }}
+        image: {{ include "onlineboutique.image" (list . .Values.shippingService) }}
         ports:
         - containerPort: 50051
         env:
diff --git a/helm-chart/values.yaml b/helm-chart/values.yaml
index 7f403b1045c..191cba9346d 100644
--- a/helm-chart/values.yaml
+++ b/helm-chart/values.yaml
@@ -20,6 +20,13 @@ images:
   repository: us-central1-docker.pkg.dev/google-samples/microservices-demo
   # Overrides the image tag whose default is the chart appVersion.
   tag: ""
+  # Per-service image overrides are also supported. Any service block below
+  # can set:
+  #   image:
+  #     repository: <registry>/<path>   # overrides .Values.images.repository
+  #     tag: <tag>                      # overrides .Values.images.tag
+  # Used by the training pipeline to flip the tag on a single fixed service
+  # while leaving the other ten on the shared :base tag.
 
 serviceAccounts:
   # Specifies whether service accounts should be created.
diff --git a/training/.gitignore b/training/.gitignore
new file mode 100644
index 00000000000..36d64f05cc9
--- /dev/null
+++ b/training/.gitignore
@@ -0,0 +1,5 @@
+handouts/
+bootstrap/attendees.csv
+terraform/.terraform/
+terraform/terraform.tfstate*
+terraform/terraform.tfvars
diff --git a/training/README.md b/training/README.md
new file mode 100644
index 00000000000..49c0695b972
--- /dev/null
+++ b/training/README.md
@@ -0,0 +1,182 @@
+# Training infrastructure for Online Boutique
+
+Provision per-attendee namespaces with a buggy boutique deployed, and
+auto-deploy fixes when their PRs are merged. Designed for ~30 attendees
+on a 1-day workshop, sharing an existing GKE Autopilot cluster.
+
+## What attendees do
+
+1. Open their training URL → reproduce the bug as a customer would
+2. Check out their pre-seeded `attendee/<name>` branch (bug already
+   committed, customer ticket as `BUG_REPORT.md`)
+3. Use Claude Code to triage: locate the file, write an engineer-ready
+   ticket (`ENGINEERING_TICKET.md`)
+4. Fix the bug, push to a feature branch, open PR → `attendee/<name>`
+5. PR auto-merges on green CI, GitHub Actions builds + pushes only the
+   changed service to GAR, helm-upgrades their namespace
+6. Re-test at the same URL
+
+## Architecture in one paragraph
+
+One GKE Autopilot cluster (`n8n-cluster` in `europe-west1`, shared with
+prod) hosts a namespace per attendee (`attendee-<name>`). Each namespace
+runs a trimmed Online Boutique (no loadgenerator, lean resource
+requests). The cluster's existing nginx-ingress + external-dns +
+cert-manager stack handles routing, DNS, and TLS — we just add an
+Ingress per namespace pointing at `<name>.training.gcp.re-cinq.com`. A
+single wildcard cert is replicated into each attendee namespace by
+[reflector](https://github.com/emberstack/reflector). All images live in
+one Artifact Registry (`europe-west1-docker.pkg.dev/re5-n8n-platform/microservices-demo-training`).
+GitHub Actions pushes to GAR via Workload Identity Federation — no
+service account keys.
+
+## File layout
+
+```
+training/
+├── terraform/         GAR repo + WIF pool/provider + IAM (run once)
+├── k8s/               training-system ns + wildcard cert + reflector install
+├── bugs/<bug-id>/     PATCH.diff (applied to attendee branch)
+│                      BUG_REPORT.md (customer-voice ticket)
+│                      ANSWER.md (trainer cheat sheet)
+├── bootstrap/         provision.sh + teardown.sh + attendees.csv.example
+├── values-training.yaml   Helm overrides (no loadgen, lean requests)
+└── handouts/          (gitignored) generated per-attendee one-pagers
+```
+
+## One-time setup
+
+### 1. Create GAR + WIF
+
+```bash
+cd training/terraform
+cp terraform.tfvars.example terraform.tfvars
+terraform init
+terraform apply
+```
+
+Note the three outputs (`artifact_registry_repo`,
+`workload_identity_provider`, `github_pusher_sa_email`).
+
+### 2. Set GitHub repo variables
+
+In `https://github.com/re-cinq/microservices-demo/settings/variables/actions`
+add:
+
+| Variable          | Value                                                              |
+|-------------------|--------------------------------------------------------------------|
+| `WIF_PROVIDER`    | output `workload_identity_provider`                                |
+| `GAR_PUSHER_SA`   | output `github_pusher_sa_email`                                    |
+| `GCP_PROJECT_ID`  | `re5-n8n-platform`                                                 |
+| `GAR_REGION`      | `europe-west1`                                                     |
+| `GAR_REPO`        | `microservices-demo-training`                                      |
+| `GKE_CLUSTER`     | `n8n-cluster`                                                      |
+| `GKE_REGION`      | `europe-west1`                                                     |
+
+### 3. Bulk-copy upstream images to GAR as `:base`
+
+```bash
+for svc in adservice cartservice checkoutservice currencyservice \
+           emailservice frontend paymentservice productcatalogservice \
+           recommendationservice shippingservice; do
+  src="us-central1-docker.pkg.dev/google-samples/microservices-demo/$svc:v0.10.5"
+  dst="europe-west1-docker.pkg.dev/re5-n8n-platform/microservices-demo-training/$svc:base"
+  gcloud container images add-tag --quiet "$src" "$dst"
+done
+```
+
+### 4. Cluster-side setup
+
+```bash
+kubectl apply -f training/k8s/training-system.yaml
+training/k8s/install-reflector.sh
+# Wait for the wildcard cert to be Ready (may take 1-2 min for DNS-01)
+kubectl -n training-system wait --for=condition=Ready certificate/wildcard-training --timeout=5m
+```
+
+### 5. Repository branch protection
+
+For `attendee/*` (branch ruleset):
+- Require pull request before merge: yes
+- Approvals required: 0 (attendees self-merge)
+- Require status checks to pass: yes, select `deploy-attendee` after first run
+- Allow auto-merge: yes
+- Restrict who can push: include training operator + the attendee
+
+Or simpler for a 1-day workshop: skip protection, set `auto-merge` as the
+default in repo settings, attendees enable it on their PR.
+
+## Per-cohort provisioning
+
+Make a CSV (`bootstrap/attendees.csv`) with one row per attendee:
+
+```
+name,bug
+alice,currency-converter-mismatch
+bob,visa-rejected
+...
+```
+
+Run:
+
+```bash
+training/bootstrap/provision.sh training/bootstrap/attendees.csv
+```
+
+This creates each namespace + Helm release + Ingress + git branch
++ handout under `training/handouts/<name>.md`. Idempotent.
+
+Print the handouts and hand them out. Attendees follow the instructions.
+
+## Teardown after the training
+
+```bash
+training/bootstrap/teardown.sh training/bootstrap/attendees.csv
+# or: training/bootstrap/teardown.sh --all
+```
+
+Leaves `training-system`, reflector, and the wildcard cert in place for
+the next cohort.
+
+## Bug catalog
+
+| ID                                | Service                  | Language | Customer signal                              |
+|-----------------------------------|--------------------------|----------|----------------------------------------------|
+| `currency-converter-mismatch`     | currencyservice          | Node     | "Prices in JPY/TRY are tiny"                 |
+| `visa-rejected`                   | paymentservice           | Node     | "Visa rejected, mastercard works"            |
+| `duplicate-recommendations`       | recommendationservice    | Python   | "Same product appears twice in recs"         |
+| `search-misses-descriptions`      | productcatalogservice    | Go       | "Search for descriptive words returns nothing" |
+
+Each lives in `training/bugs/<id>/` with the patch, customer ticket, and
+trainer answer.
+
+## Cost note
+
+Autopilot bills per pod resource request. With 30 attendees on the
+trimmed `values-training.yaml`, expect roughly **15 vCPU + 20 GiB**
+requested cluster-wide for the boutique pods, ~$5–7/hour. A full
+8-hour day is ~$40–60.
+
+## Things to know / footguns
+
+- **PR concurrency**: `concurrency: deploy-${{ github.ref }}` cancels
+  in-progress runs if an attendee pushes twice in quick succession.
+  Their second push wins; the first is silently dropped. Tell them.
+- **Helm `--reuse-values`**: the workflow uses `--reuse-values` and
+  re-applies `values-training.yaml` on top via `-f`, so stale
+  values from the bootstrap install are preserved + the per-service
+  tag override is layered on. If you ever change `values-training.yaml`
+  during a cohort, re-run `provision.sh` to roll it out.
+- **Image leaks across attendees**: GAR is shared. An attendee can
+  technically `docker pull` someone else's `attendee-bob-<sha>` image.
+  Not a problem for a public training, but worth knowing.
+- **Public repo + visible answers**: once any attendee's PR merges, the
+  diff is public. Mitigation in place: 4-bug pool randomized across
+  attendees + bugs chosen so the diff alone doesn't teach the triage
+  skill (the skill is *finding* the file from a customer report).
+- **LE rate limit**: we issue exactly one `*.training.gcp.re-cinq.com`
+  cert and replicate it. The shared `re-cinq.com` registered domain has
+  a 50/week LE limit — don't manually issue 30 per-host certs by
+  mistake.
+- **No kubectl for attendees**: deliberate. Forces them to triage from
+  a customer's perspective rather than tailing logs.
diff --git a/training/bootstrap/attendees.csv.example b/training/bootstrap/attendees.csv.example
new file mode 100644
index 00000000000..9d5b03826c7
--- /dev/null
+++ b/training/bootstrap/attendees.csv.example
@@ -0,0 +1,7 @@
+name,bug
+alice,currency-converter-mismatch
+bob,visa-rejected
+charlie,duplicate-recommendations
+dana,search-misses-descriptions
+eve,currency-converter-mismatch
+frank,visa-rejected
diff --git a/training/bootstrap/emails-to-csv.sh b/training/bootstrap/emails-to-csv.sh
new file mode 100755
index 00000000000..03300eec216
--- /dev/null
+++ b/training/bootstrap/emails-to-csv.sh
@@ -0,0 +1,62 @@
+#!/usr/bin/env bash
+# Convert a list of attendee emails (one per line, # for comments) into the
+# CSV format provision.sh expects. Bugs are assigned round-robin across
+# the catalog under training/bugs/, so each attendee's neighbour gets a
+# different bug.
+#
+#   ./emails-to-csv.sh emails.txt > attendees.csv
+#
+# Stdout: name,bug
+# Stderr: a "lookup" table mapping email -> handle, so you know who's who.
+set -euo pipefail
+
+REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
+BUGS_DIR="$REPO_ROOT/training/bugs"
+
+if [[ $# -ne 1 ]]; then
+  echo "usage: $0 <emails.txt>" >&2
+  exit 2
+fi
+
+bugs=()
+while IFS= read -r b; do bugs+=("$b"); done < <(
+  cd "$BUGS_DIR" && for d in */; do echo "${d%/}"; done | sort
+)
+[[ ${#bugs[@]} -gt 0 ]] || { echo "no bugs found in $BUGS_DIR" >&2; exit 1; }
+
+used=" "
+i=0
+echo "name,bug"
+echo "email -> handle mapping:" >&2
+echo "------------------------" >&2
+
+while IFS= read -r line || [[ -n "$line" ]]; do
+  # Skip blanks and comments
+  line="${line%%#*}"
+  line="$(echo "$line" | xargs)"
+  [[ -z "$line" ]] && continue
+
+  local_part="${line%%@*}"
+  # Lowercase, replace . _ + with -, strip anything that's not [a-z0-9-]
+  handle="$(echo "$local_part" | tr '[:upper:]' '[:lower:]' | tr '._+' '-' | sed 's/[^a-z0-9-]//g')"
+  # Trim leading non-alpha (RFC 1123: must start with a letter)
+  handle="$(echo "$handle" | sed 's/^[^a-z]*//')"
+  # Cap length
+  handle="${handle:0:25}"
+  [[ -z "$handle" ]] && { echo "could not derive handle from: $line" >&2; exit 1; }
+
+  # De-duplicate
+  base="$handle"
+  n=2
+  while [[ "$used" == *" $handle "* ]]; do
+    handle="${base}-$n"
+    n=$((n+1))
+  done
+  used="$used$handle "
+
+  bug="${bugs[i % ${#bugs[@]}]}"
+  i=$((i+1))
+
+  echo "$handle,$bug"
+  printf '  %-40s -> %s (%s)\n' "$line" "$handle" "$bug" >&2
+done < "$1"
diff --git a/training/bootstrap/emails.txt b/training/bootstrap/emails.txt
new file mode 100644
index 00000000000..8a6d2ccd793
--- /dev/null
+++ b/training/bootstrap/emails.txt
@@ -0,0 +1,41 @@
+alek.legosteva@odevo.com
+andrea.backstrom@odevo.com
+angi.krauskopf@odevo.com
+anna.simon@odevo.com
+craig.langley-tester@odevo.com
+cristofer.dreimanis@odevo.com
+cruz.moreno@odevo.com
+daniel.anundi@odevo.com
+daniel@re-cinq.com
+emil.stenstrom@odevo.com
+fnieto@kwpmc.com
+george.yang@odevo.com
+gustaf.ankarcrona@odevo.com
+james.colebeck@odevo.com
+jan.lundequist@odevo.com
+jenny.linde@odevo.com
+joel.johannesson@odevo.com
+joel.sanmoogan@vegnergroup.com
+jonas.hagernas@odevo.com
+jonathan.wirseen@odevo.com
+jost.werdenhoff@odevo.com
+kate.payne@odevo.com
+martin.hjers@odevo.com
+marv.gillibrand@odevo.com
+matthew.blanshard@odevo.com
+matthew.buckland@odevo.com
+mikael.svensson@odevo.com
+nabeel.moosa@odevo.com
+nejal.patel@odevo.com
+olof.nordberg@odevo.com
+patrik.sommar@odevo.com
+pontus.jespersson@odevo.com
+pontus.vepsalainen@odevo.com
+samantha.short@odevo.com
+sarah.crissman@odevo.com
+sennai.mebrahtu@odevo.com
+sermed.ali@odevo.com
+siri.uhrnell@odevo.com
+stanislava.bazitova@odevo.com
+tim.love@odevo.com
+tomasz.maj@odevo.com
diff --git a/training/bootstrap/provision.sh b/training/bootstrap/provision.sh
new file mode 100755
index 00000000000..d0d18d8a367
--- /dev/null
+++ b/training/bootstrap/provision.sh
@@ -0,0 +1,243 @@
+#!/usr/bin/env bash
+# Provision a training cohort.
+#
+#   ./provision.sh attendees.csv
+#
+# Idempotent. Re-runs are safe; existing namespaces, releases, and
+# branches are upgraded in place. CSV format: name,bug_id
+#
+# Prerequisites:
+#   - kubectl pointing at the training cluster
+#   - helm 3.x
+#   - git remote 'origin' set to the fork
+#   - training/k8s/training-system.yaml already applied
+#   - training/k8s/install-reflector.sh already run
+#   - main branch up to date with the fork remote
+set -euo pipefail
+
+REPO_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
+TRAINING_DIR="$REPO_ROOT/training"
+DOMAIN="training.gcp.re-cinq.com"
+TLS_SECRET="wildcard-training-tls"
+CLUSTER_ISSUER="letsencrypt-prod"
+INGRESS_CLASS="nginx"
+BASE_BRANCH="main"
+
+if [[ $# -ne 1 ]]; then
+  echo "usage: $0 <attendees.csv>" >&2
+  exit 2
+fi
+CSV="$1"
+[[ -f "$CSV" ]] || { echo "no such file: $CSV" >&2; exit 2; }
+
+mkdir -p "$TRAINING_DIR/handouts"
+
+log() { printf '\033[1;34m[bootstrap]\033[0m %s\n' "$*"; }
+
+# Validate every row first - fail before we mutate anything
+log "validating $CSV"
+while IFS=, read -r name bug; do
+  [[ "$name" == "name" ]] && continue
+  [[ -z "$name" || -z "$bug" ]] && { echo "empty name or bug in row: $name,$bug" >&2; exit 1; }
+  [[ -d "$TRAINING_DIR/bugs/$bug" ]] || { echo "unknown bug id: $bug (no such dir under training/bugs/)" >&2; exit 1; }
+  [[ "$name" =~ ^[a-z][a-z0-9-]{1,30}$ ]] || { echo "invalid attendee name (must be lowercase, alphanumeric+dash, <=31 chars): $name" >&2; exit 1; }
+done < "$CSV"
+
+# Process each attendee
+while IFS=, read -r name bug; do
+  [[ "$name" == "name" ]] && continue
+
+  ns="attendee-$name"
+  branch="attendee/$name"
+  host="${name}.${DOMAIN}"
+
+  log "==== $name (bug=$bug, namespace=$ns) ===="
+
+  # 1. Namespace + quotas + network policy
+  kubectl apply -f - <<EOF
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: $ns
+  labels:
+    purpose: training
+    attendee: $name
+    cohort: $(date +%Y-%m-%d)
+---
+apiVersion: v1
+kind: ResourceQuota
+metadata:
+  name: training-quota
+  namespace: $ns
+spec:
+  hard:
+    requests.cpu: "1"
+    requests.memory: 2Gi
+    limits.cpu: "3"
+    limits.memory: 4Gi
+    pods: "20"
+---
+apiVersion: v1
+kind: LimitRange
+metadata:
+  name: training-defaults
+  namespace: $ns
+spec:
+  limits:
+  - type: Container
+    default:
+      cpu: 200m
+      memory: 256Mi
+    defaultRequest:
+      cpu: 50m
+      memory: 64Mi
+---
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: default-deny
+  namespace: $ns
+spec:
+  podSelector: {}
+  policyTypes: [Ingress, Egress]
+---
+# Allow within-namespace traffic, DNS, and HTTPS egress (for image pulls,
+# external APIs, etc). Block lateral movement to other namespaces.
+apiVersion: networking.k8s.io/v1
+kind: NetworkPolicy
+metadata:
+  name: allow-internal-and-egress
+  namespace: $ns
+spec:
+  podSelector: {}
+  policyTypes: [Ingress, Egress]
+  ingress:
+  - from:
+    - podSelector: {}
+  - from:
+    - namespaceSelector:
+        matchLabels:
+          kubernetes.io/metadata.name: ingress-nginx
+  egress:
+  - to:
+    - podSelector: {}
+  - to:
+    - namespaceSelector:
+        matchLabels:
+          kubernetes.io/metadata.name: kube-system
+    ports:
+    - port: 53
+      protocol: UDP
+    - port: 53
+      protocol: TCP
+  - to:
+    - ipBlock:
+        cidr: 0.0.0.0/0
+        except: [10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16]
+EOF
+
+  # 2. Helm install/upgrade the boutique
+  helm upgrade --install boutique "$REPO_ROOT/helm-chart" \
+    --namespace "$ns" \
+    -f "$TRAINING_DIR/values-training.yaml" \
+    --wait --timeout 5m
+
+  # 3. Ingress (external-dns picks up host -> Cloud DNS A record;
+  #    reflector replicated the wildcard TLS secret into this namespace
+  #    so we just reference it by name)
+  kubectl apply -f - <<EOF
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: boutique
+  namespace: $ns
+  annotations:
+    external-dns.alpha.kubernetes.io/hostname: "$host"
+spec:
+  ingressClassName: $INGRESS_CLASS
+  tls:
+    - hosts: ["$host"]
+      secretName: $TLS_SECRET
+  rules:
+    - host: $host
+      http:
+        paths:
+          - path: /
+            pathType: Prefix
+            backend:
+              service:
+                name: frontend
+                port:
+                  number: 80
+EOF
+
+  # 4. Branch + bug injection
+  git fetch origin "$BASE_BRANCH" >/dev/null
+  if git ls-remote --exit-code --heads origin "$branch" >/dev/null 2>&1; then
+    log "branch $branch already exists on origin, skipping"
+  else
+    log "creating branch $branch from origin/$BASE_BRANCH"
+    git worktree add --quiet --detach /tmp/training-$name "origin/$BASE_BRANCH"
+    (
+      cd /tmp/training-$name
+      git checkout -b "$branch"
+      git apply "$TRAINING_DIR/bugs/$bug/PATCH.diff"
+      cp "$TRAINING_DIR/bugs/$bug/BUG_REPORT.md" ./BUG_REPORT.md
+      git add -A
+      GIT_AUTHOR_NAME="training-bot" GIT_AUTHOR_EMAIL="bot@training.local" \
+      GIT_COMMITTER_NAME="training-bot" GIT_COMMITTER_EMAIL="bot@training.local" \
+        git commit --quiet -m "training: seed bug ($bug)" -m "Customer ticket in BUG_REPORT.md."
+      git push --quiet -u origin "$branch"
+    )
+    git worktree remove --force /tmp/training-$name
+  fi
+
+  # 5. Handout
+  cat > "$TRAINING_DIR/handouts/$name.md" <<EOF
+# Training handout — $name
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://$host                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | \`$branch\`                                     |
+| Your bug ID   | \`$bug\` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+\`BUG_REPORT.md\` on your branch. Your job today:
+
+1. Reproduce the issue at $host
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (\`ENGINEERING_TICKET.md\` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at $host after deploying
+4. Open a PR from a fix branch into \`$branch\`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+\`\`\`bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout $branch
+git checkout -b $branch-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin $branch-fix
+gh pr create --base $branch --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+\`\`\`
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://$host once it's green.
+EOF
+
+  log "done with $name"
+done < "$CSV"
+
+log "all attendees provisioned. handouts written to training/handouts/"
diff --git a/training/bootstrap/teardown.sh b/training/bootstrap/teardown.sh
new file mode 100755
index 00000000000..187de9d6261
--- /dev/null
+++ b/training/bootstrap/teardown.sh
@@ -0,0 +1,36 @@
+#!/usr/bin/env bash
+# Tear down a training cohort.
+#
+#   ./teardown.sh attendees.csv         # reads same CSV used to provision
+#   ./teardown.sh --all                 # nuke every attendee-* namespace
+#
+# Deletes namespaces (which cascades to Helm releases, Ingresses, secrets)
+# and the attendee/* git branches on origin. Leaves training-system,
+# reflector, and the wildcard cert in place.
+set -euo pipefail
+
+confirm() {
+  read -r -p "${1:-Are you sure?} [y/N] " ans
+  [[ "$ans" =~ ^[Yy]$ ]]
+}
+
+if [[ "${1:-}" == "--all" ]]; then
+  namespaces=$(kubectl get ns -l purpose=training -o jsonpath='{.items[*].metadata.name}')
+  branches=$(git ls-remote --heads origin 'attendee/*' | awk '{print $2}' | sed 's|refs/heads/||')
+  echo "Will delete namespaces: $namespaces"
+  echo "Will delete branches:   $branches"
+  confirm "Proceed?" || exit 1
+  for ns in $namespaces; do kubectl delete ns "$ns" --wait=false; done
+  for br in $branches; do git push origin --delete "$br" || true; done
+  exit 0
+fi
+
+CSV="${1:-}"
+[[ -f "$CSV" ]] || { echo "usage: $0 <attendees.csv> | --all" >&2; exit 2; }
+
+while IFS=, read -r name _bug; do
+  [[ "$name" == "name" ]] && continue
+  echo "deleting attendee-$name and origin/attendee/$name"
+  kubectl delete ns "attendee-$name" --wait=false --ignore-not-found
+  git push origin --delete "attendee/$name" 2>/dev/null || true
+done < "$CSV"
diff --git a/training/bugs/currency-converter-mismatch/ANSWER.md b/training/bugs/currency-converter-mismatch/ANSWER.md
new file mode 100644
index 00000000000..57b7ef3ee9d
--- /dev/null
+++ b/training/bugs/currency-converter-mismatch/ANSWER.md
@@ -0,0 +1,32 @@
+# Trainer cheat sheet — currency-converter-mismatch
+
+**Service:** `currencyservice` (Node.js)
+**File:** `src/currencyservice/server.js`
+**Function:** `convert()`, the EUR → to_currency step (around line 150).
+
+## What the bug is
+
+The conversion is done in two hops: from-currency → EUR → to-currency. The
+first hop (FX rate as denominator) is correct. The second hop (rate as
+multiplier) was changed from `*` to `/`, so prices in non-USD currencies
+come out tiny — and tinier the further the currency is from EUR/USD, which
+matches the customer's "JPY and TRY are way off" observation.
+
+## What a good triage ticket looks like
+
+The exercise is for the attendee to write the engineer-ready ticket, not
+fix the bug. A good ticket includes:
+
+- **Steps to reproduce:** add any product to cart → switch currency → observe
+  total. Worse for currencies with large multipliers (JPY ~150, TRY ~30).
+- **Suspected area:** `currencyservice`, specifically the `convert` RPC. The
+  ratio of "wrong / right" matches an inverse of the target currency rate,
+  which points at the multiplier step.
+- **Severity rationale:** revenue-impacting (any non-USD checkout pays
+  far less than the listed price), customer-visible, no workaround.
+- **Not the fix itself** — the ticket should hand off cleanly to whoever
+  picks it up, not pre-empt their judgement.
+
+## The actual fix
+
+Restore `*` in the second `_carry` call.
diff --git a/training/bugs/currency-converter-mismatch/BUG_REPORT.md b/training/bugs/currency-converter-mismatch/BUG_REPORT.md
new file mode 100644
index 00000000000..9d33936ef1a
--- /dev/null
+++ b/training/bugs/currency-converter-mismatch/BUG_REPORT.md
@@ -0,0 +1,25 @@
+# Customer ticket — Currency conversion looks wrong
+
+**From:** support@onlineboutique.example
+**Severity:** customer-reported
+**Reported:** today, 09:14
+
+> Hi,
+>
+> I was browsing the site this morning and the prices in EUR look completely
+> off. The Watch is listed at "$109.99" which is fine, but when I switch the
+> currency dropdown to EUR I see something like "€96.04" — that part is also
+> fine, my partner double-checked. But then I switched to **JPY** and the
+> Watch shows up as **¥0.92**. That's clearly broken — it should be over a
+> ten thousand yen.
+>
+> The problem seems worse for currencies that are weaker than the dollar.
+> CAD shows roughly the right number, but JPY and TRY are tiny.
+>
+> The actual checkout total uses the same broken numbers, so anyone who
+> doesn't notice can buy a watch for less than a dollar. We're losing money
+> on every non-USD checkout right now.
+>
+> Hope you can fix this fast.
+>
+> — Sara
diff --git a/training/bugs/currency-converter-mismatch/PATCH.diff b/training/bugs/currency-converter-mismatch/PATCH.diff
new file mode 100644
index 00000000000..89b38fb22d5
--- /dev/null
+++ b/training/bugs/currency-converter-mismatch/PATCH.diff
@@ -0,0 +1,15 @@
+diff --git a/src/currencyservice/server.js b/src/currencyservice/server.js
+--- a/src/currencyservice/server.js
++++ b/src/currencyservice/server.js
+@@ -150,8 +150,8 @@ function convert (call, callback) {
+       euros.nanos = Math.round(euros.nanos);
+
+       // Convert: EUR --> to_currency
+       const result = _carry({
+-        units: euros.units * data[request.to_code],
+-        nanos: euros.nanos * data[request.to_code]
++        units: euros.units / data[request.to_code],
++        nanos: euros.nanos / data[request.to_code]
+       });
+
+       result.units = Math.floor(result.units);
diff --git a/training/bugs/duplicate-recommendations/ANSWER.md b/training/bugs/duplicate-recommendations/ANSWER.md
new file mode 100644
index 00000000000..a7abf8d8299
--- /dev/null
+++ b/training/bugs/duplicate-recommendations/ANSWER.md
@@ -0,0 +1,33 @@
+# Trainer cheat sheet — duplicate-recommendations
+
+**Service:** `recommendationservice` (Python)
+**File:** `src/recommendationservice/recommendation_server.py`
+**Function:** `RecommendationService.ListRecommendations()`, line ~79.
+
+## What the bug is
+
+`random.sample(range(N), k)` was replaced with `random.choices(range(N), k=...)`.
+`sample` draws *without* replacement; `choices` draws *with* replacement,
+so duplicate indices are possible — and likely when the candidate pool is
+small (current catalog has 9 products, after filtering out the one the
+user is currently viewing it's 8, so duplicates appear ~50% of the time
+across 5 picks by birthday-paradox math).
+
+## What a good triage ticket looks like
+
+- **Steps to reproduce:** open any product page → scroll to "You may
+  also like" → refresh ~3-5 times → observe duplicate in the list.
+  Same on the home-page recommendations widget.
+- **Suspected area:** `recommendationservice`, the function that picks
+  which product IDs to return. The "sometimes" pattern + small product
+  catalog points at sampling-with-replacement rather than a logic error
+  in upstream filtering.
+- **Severity rationale:** UI quality issue, no money lost, no security
+  impact. P3. Bunch this with other small UX fixes for the next sprint.
+- **Note:** worth confirming with the data team whether the recommendation
+  ranker downstream of this also assumes uniqueness — there may be no
+  invariant being broken downstream, but worth checking.
+
+## The actual fix
+
+`random.sample(range(num_products), num_return)` — back to sample.
diff --git a/training/bugs/duplicate-recommendations/BUG_REPORT.md b/training/bugs/duplicate-recommendations/BUG_REPORT.md
new file mode 100644
index 00000000000..b1bcfa2a2c2
--- /dev/null
+++ b/training/bugs/duplicate-recommendations/BUG_REPORT.md
@@ -0,0 +1,22 @@
+# Customer ticket — Same product showing twice in recommendations
+
+**From:** support@onlineboutique.example
+**Severity:** customer-reported
+**Reported:** today, 14:30
+
+> Hi team,
+>
+> Small thing but it looks unprofessional. On product pages, the "You may
+> also like" section sometimes shows the same item twice in a row. It
+> doesn't happen every time but if I refresh a few times I can usually
+> reproduce it. Attached a screenshot — see how the Mug appears in slot 2
+> and slot 4.
+>
+> A friend in marketing said it's also been happening on the front page
+> "Hot Products" widget.
+>
+> Thanks
+>
+> — Priya (loyalty member, just FYI)
+>
+> [screenshot.png attached: shows "You may also like" with Mug in two slots]
diff --git a/training/bugs/duplicate-recommendations/PATCH.diff b/training/bugs/duplicate-recommendations/PATCH.diff
new file mode 100644
index 00000000000..fb8f378ea84
--- /dev/null
+++ b/training/bugs/duplicate-recommendations/PATCH.diff
@@ -0,0 +1,14 @@
+diff --git a/src/recommendationservice/recommendation_server.py b/src/recommendationservice/recommendation_server.py
+--- a/src/recommendationservice/recommendation_server.py
++++ b/src/recommendationservice/recommendation_server.py
+@@ -75,8 +75,8 @@ class RecommendationService(demo_pb2_grpc.RecommendationServiceServicer):
+         filtered_products = list(set(product_ids)-set(request.product_ids))
+         num_products = len(filtered_products)
+         num_return = min(max_responses, num_products)
+-        # sample list of indicies to return
+-        indices = random.sample(range(num_products), num_return)
++        # sample list of indicies to return
++        indices = random.choices(range(num_products), k=num_return)
+         # fetch product ids from indices
+         prod_list = [filtered_products[i] for i in indices]
+         logger.info("[Recv ListRecommendations] product_ids={}".format(prod_list))
diff --git a/training/bugs/search-misses-descriptions/ANSWER.md b/training/bugs/search-misses-descriptions/ANSWER.md
new file mode 100644
index 00000000000..6bea7a95660
--- /dev/null
+++ b/training/bugs/search-misses-descriptions/ANSWER.md
@@ -0,0 +1,31 @@
+# Trainer cheat sheet — search-misses-descriptions
+
+**Service:** `productcatalogservice` (Go)
+**File:** `src/productcatalogservice/product_catalog.go`
+**Function:** `SearchProducts()`, line ~65.
+
+## What the bug is
+
+`SearchProducts` used to match against both `product.Name` and
+`product.Description`. The description-matching half of the OR was
+removed. So queries that only appear in descriptions ("modern",
+"summer", "vintage", "comfortable") return zero results, while queries
+that match a product name ("watch", "tank") still work. The pattern in
+the customer's report — "some queries work, others don't, depending on
+what kind of word it is" — is the diagnostic.
+
+## What a good triage ticket looks like
+
+- **Steps to reproduce:** in the search box, query "modern" → no results.
+  "watch" → 1 result. The split is words-that-appear-in-product-names
+  (work) vs. words-that-only-appear-in-descriptions (fail).
+- **Suspected area:** `productcatalogservice`'s `SearchProducts` RPC.
+  The shape of the failure (matches a *subset* of the product's
+  searchable text) points at a missing field in the search predicate
+  rather than a tokenizer or indexer problem.
+- **Severity rationale:** not a checkout-blocker, but discoverability is
+  measurably worse — likely shows up in conversion data this week. P2.
+
+## The actual fix
+
+Restore the second clause of the OR so descriptions are matched again.
diff --git a/training/bugs/search-misses-descriptions/BUG_REPORT.md b/training/bugs/search-misses-descriptions/BUG_REPORT.md
new file mode 100644
index 00000000000..69f4c209c20
--- /dev/null
+++ b/training/bugs/search-misses-descriptions/BUG_REPORT.md
@@ -0,0 +1,27 @@
+# Customer ticket — Search results are missing things
+
+**From:** support@onlineboutique.example
+**Severity:** customer-reported
+**Reported:** today, 16:18
+
+> Hi,
+>
+> I think your search is broken. I was looking for a gift and I searched
+> for "modern" — got zero results. But I know I've seen products described
+> as modern on the site before.
+>
+> I tried a few more:
+>
+>  - "summer" → no results
+>  - "vintage" → no results
+>  - "comfortable" → no results
+>
+> But searching "watch" works, and "tank" works. So it's not totally broken,
+> just… missing? It feels like it's only matching some part of the product
+> info and not all of it.
+>
+> Three of our team noticed it this morning, so I don't think it's a fluke.
+>
+> Cheers
+>
+> — Marcus
diff --git a/training/bugs/search-misses-descriptions/PATCH.diff b/training/bugs/search-misses-descriptions/PATCH.diff
new file mode 100644
index 00000000000..e7d67846ddf
--- /dev/null
+++ b/training/bugs/search-misses-descriptions/PATCH.diff
@@ -0,0 +1,14 @@
+diff --git a/src/productcatalogservice/product_catalog.go b/src/productcatalogservice/product_catalog.go
+--- a/src/productcatalogservice/product_catalog.go
++++ b/src/productcatalogservice/product_catalog.go
+@@ -62,8 +62,7 @@ func (p *productCatalog) SearchProducts(ctx context.Context, req *pb.SearchProdu
+ 	time.Sleep(extraLatency)
+
+ 	var ps []*pb.Product
+ 	for _, product := range p.parseCatalog() {
+-		if strings.Contains(strings.ToLower(product.Name), strings.ToLower(req.Query)) ||
+-			strings.Contains(strings.ToLower(product.Description), strings.ToLower(req.Query)) {
++		if strings.Contains(strings.ToLower(product.Name), strings.ToLower(req.Query)) {
+ 			ps = append(ps, product)
+ 		}
+ 	}
diff --git a/training/bugs/visa-rejected/ANSWER.md b/training/bugs/visa-rejected/ANSWER.md
new file mode 100644
index 00000000000..b73028780ec
--- /dev/null
+++ b/training/bugs/visa-rejected/ANSWER.md
@@ -0,0 +1,35 @@
+# Trainer cheat sheet — visa-rejected
+
+**Service:** `paymentservice` (Node.js)
+**File:** `src/paymentservice/charge.js`
+**Function:** `charge()`, line ~74.
+
+## What the bug is
+
+The card-type allowlist compares against `'Visa'` (capital V), but the
+underlying `simple-card-validator` library returns lowercase `'visa'`.
+So Visa cards never match and fall through to `UnacceptedCreditCard`.
+Mastercard still works because its check still uses lowercase.
+
+The customer's quote of the error message — "we cannot process visa
+credit cards" with lowercase visa — is the giveaway: the *displayed*
+type is lowercase, while the *check* must be case-sensitive.
+
+## What a good triage ticket looks like
+
+- **Steps to reproduce:** add anything to cart → checkout with any valid
+  Visa card (test card `4111111111111111` works) → "we cannot process
+  visa credit cards" error. Mastercard test card `5555555555554444`
+  succeeds.
+- **Suspected area:** `paymentservice`, specifically the card-type allowlist.
+  The contrast between the upper-case `VISA` in the error template and
+  the lower-case `visa` returned by the validator is the smoking gun.
+- **Severity rationale:** Visa is ~50% of consumer card volume — this
+  blocks roughly half of all paid checkouts. P0/revenue-blocking.
+- **Note for whoever fixes:** check whether other downstream comparisons
+  (logs, analytics) also assume a particular casing — it's likely the
+  validator library was updated and changed casing.
+
+## The actual fix
+
+Change `'Visa'` to `'visa'` on the same line.
diff --git a/training/bugs/visa-rejected/BUG_REPORT.md b/training/bugs/visa-rejected/BUG_REPORT.md
new file mode 100644
index 00000000000..537b28b3c06
--- /dev/null
+++ b/training/bugs/visa-rejected/BUG_REPORT.md
@@ -0,0 +1,23 @@
+# Customer ticket — Can't pay with my Visa
+
+**From:** support@onlineboutique.example
+**Severity:** customer-reported
+**Reported:** today, 11:02
+
+> Hello,
+>
+> I'm trying to buy a couple of items but the checkout keeps rejecting my
+> Visa card. The error message I get on the page is "Sorry, we cannot
+> process visa credit cards. Only VISA or MasterCard is accepted." which
+> is confusing because **Visa is right there in the message**.
+>
+> I tried a different Visa from another bank — same thing. Then my
+> partner's Mastercard went through first try.
+>
+> The card details are definitely valid (used the same Visa on another
+> site five minutes later). It really does look like Visa is being rejected
+> on your end specifically.
+>
+> Could you please look into this? I want to complete the order today.
+>
+> — Daniel
diff --git a/training/bugs/visa-rejected/PATCH.diff b/training/bugs/visa-rejected/PATCH.diff
new file mode 100644
index 00000000000..a3a6da28b39
--- /dev/null
+++ b/training/bugs/visa-rejected/PATCH.diff
@@ -0,0 +1,13 @@
+diff --git a/src/paymentservice/charge.js b/src/paymentservice/charge.js
+--- a/src/paymentservice/charge.js
++++ b/src/paymentservice/charge.js
+@@ -71,7 +71,7 @@ module.exports = function charge (request) {
+   if (!valid) { throw new InvalidCreditCard(); }
+
+   // Only VISA and mastercard is accepted, other card types (AMEX, dinersclub) will
+   // throw UnacceptedCreditCard error.
+-  if (!(cardType === 'visa' || cardType === 'mastercard')) { throw new UnacceptedCreditCard(cardType); }
++  if (!(cardType === 'Visa' || cardType === 'mastercard')) { throw new UnacceptedCreditCard(cardType); }
+
+   // Also validate expiration is > today.
+   const currentMonth = new Date().getMonth() + 1;
diff --git a/training/k8s/install-reflector.sh b/training/k8s/install-reflector.sh
new file mode 100755
index 00000000000..59c7c8bd930
--- /dev/null
+++ b/training/k8s/install-reflector.sh
@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# Install emberstack/reflector into the training-system namespace.
+# Idempotent: re-running is a no-op upgrade.
+#
+# Reflector watches Secrets/ConfigMaps annotated with reflection-* and
+# copies them into every matching namespace. We use it to replicate the
+# wildcard TLS secret into each attendee-<name> namespace without paying
+# 30x the Let's Encrypt cert quota.
+set -euo pipefail
+
+helm repo add emberstack https://emberstack.github.io/helm-charts >/dev/null
+helm repo update emberstack >/dev/null
+
+helm upgrade --install reflector emberstack/reflector \
+  --namespace training-system \
+  --create-namespace \
+  --version 7.1.288 \
+  --set resources.requests.cpu=20m \
+  --set resources.requests.memory=64Mi \
+  --set resources.limits.cpu=100m \
+  --set resources.limits.memory=128Mi
diff --git a/training/k8s/training-system.yaml b/training/k8s/training-system.yaml
new file mode 100644
index 00000000000..0a9c35a1fdd
--- /dev/null
+++ b/training/k8s/training-system.yaml
@@ -0,0 +1,43 @@
+# One-time setup applied to the cluster before the training.
+#
+#   kubectl apply -f training/k8s/training-system.yaml
+#
+# Creates:
+#   - the training-system namespace (control plane for training infra)
+#   - a wildcard Certificate for *.training.gcp.re-cinq.com that
+#     cert-manager issues via DNS-01 against the existing letsencrypt-prod
+#     ClusterIssuer; the resulting Secret is annotated for reflector so
+#     each attendee namespace gets a copy automatically.
+
+apiVersion: v1
+kind: Namespace
+metadata:
+  name: training-system
+  labels:
+    purpose: training-control-plane
+
+---
+apiVersion: cert-manager.io/v1
+kind: Certificate
+metadata:
+  name: wildcard-training
+  namespace: training-system
+spec:
+  secretName: wildcard-training-tls
+  # Annotations on the secret produced by cert-manager. reflector picks
+  # these up and replicates the secret into any namespace matching the
+  # auto-namespaces regex.
+  secretTemplate:
+    annotations:
+      reflector.v1.k8s.emberstack.com/reflection-allowed: "true"
+      reflector.v1.k8s.emberstack.com/reflection-allowed-namespaces: "attendee-.*"
+      reflector.v1.k8s.emberstack.com/reflection-auto-enabled: "true"
+      reflector.v1.k8s.emberstack.com/reflection-auto-namespaces: "attendee-.*"
+  dnsNames:
+    - "*.training.gcp.re-cinq.com"
+    - "training.gcp.re-cinq.com"
+  issuerRef:
+    name: letsencrypt-prod
+    kind: ClusterIssuer
+  privateKey:
+    rotationPolicy: Never
diff --git a/training/terraform/main.tf b/training/terraform/main.tf
new file mode 100644
index 00000000000..1ce368b6bda
--- /dev/null
+++ b/training/terraform/main.tf
@@ -0,0 +1,108 @@
+data "google_project" "project" {}
+
+locals {
+  # Autopilot pulls images using the cluster's node SA. Unless overridden it
+  # is the project's compute default SA: <project_number>-compute@developer.gserviceaccount.com.
+  gke_pull_sa = coalesce(
+    var.gke_node_service_account,
+    "${data.google_project.project.number}-compute@developer.gserviceaccount.com"
+  )
+}
+
+# ---- Artifact Registry: training images ---------------------------------
+
+resource "google_artifact_registry_repository" "training" {
+  location      = var.region
+  repository_id = "microservices-demo-training"
+  description   = "Training images for microservices-demo. :base = upstream copy, :attendee-<name>-<sha> = per-attendee fix."
+  format        = "DOCKER"
+
+  cleanup_policy_dry_run = false
+
+  cleanup_policies {
+    id     = "delete-untagged-after-1d"
+    action = "DELETE"
+    condition {
+      tag_state  = "UNTAGGED"
+      older_than = "86400s"
+    }
+  }
+
+  cleanup_policies {
+    id     = "delete-attendee-tags-after-7d"
+    action = "DELETE"
+    condition {
+      tag_state    = "TAGGED"
+      tag_prefixes = ["attendee-"]
+      older_than   = "604800s"
+    }
+  }
+
+  cleanup_policies {
+    id     = "keep-base"
+    action = "KEEP"
+    condition {
+      tag_state    = "TAGGED"
+      tag_prefixes = ["base"]
+    }
+  }
+}
+
+# Cluster nodes need to pull from the repo.
+resource "google_artifact_registry_repository_iam_member" "gke_pull" {
+  location   = google_artifact_registry_repository.training.location
+  repository = google_artifact_registry_repository.training.name
+  role       = "roles/artifactregistry.reader"
+  member     = "serviceAccount:${local.gke_pull_sa}"
+}
+
+# ---- Workload Identity Federation for GitHub Actions --------------------
+
+resource "google_iam_workload_identity_pool" "github" {
+  workload_identity_pool_id = "github-training"
+  display_name              = "GitHub Actions (training)"
+  description               = "OIDC pool for the microservices-demo training repo CI."
+}
+
+resource "google_iam_workload_identity_pool_provider" "github" {
+  workload_identity_pool_id          = google_iam_workload_identity_pool.github.workload_identity_pool_id
+  workload_identity_pool_provider_id = "github"
+  display_name                       = "GitHub OIDC"
+
+  oidc {
+    issuer_uri = "https://token.actions.githubusercontent.com"
+  }
+
+  attribute_mapping = {
+    "google.subject"       = "assertion.sub"
+    "attribute.actor"      = "assertion.actor"
+    "attribute.repository" = "assertion.repository"
+    "attribute.ref"        = "assertion.ref"
+  }
+
+  # Restrict the provider to our specific repo. Without this any GitHub repo
+  # can mint tokens against our pool.
+  attribute_condition = "assertion.repository == \"${var.github_repo}\""
+}
+
+# Service account that GH Actions impersonates. It only has push rights to the
+# training repo - no other project-wide perms.
+resource "google_service_account" "github_pusher" {
+  account_id   = "training-image-pusher"
+  display_name = "Microservices-demo training image pusher"
+  description  = "Used by GitHub Actions in ${var.github_repo} to push images to the training Artifact Registry."
+}
+
+resource "google_artifact_registry_repository_iam_member" "github_push" {
+  location   = google_artifact_registry_repository.training.location
+  repository = google_artifact_registry_repository.training.name
+  role       = "roles/artifactregistry.writer"
+  member     = "serviceAccount:${google_service_account.github_pusher.email}"
+}
+
+# Allow the GitHub repo's tokens (any branch) to impersonate the SA.
+resource "google_service_account_iam_member" "github_wif_binding" {
+  service_account_id = google_service_account.github_pusher.name
+  role               = "roles/iam.workloadIdentityUser"
+  member             = "principalSet://iam.googleapis.com/${google_iam_workload_identity_pool.github.name}/attribute.repository/${var.github_repo}"
+}
diff --git a/training/terraform/outputs.tf b/training/terraform/outputs.tf
new file mode 100644
index 00000000000..132e177077a
--- /dev/null
+++ b/training/terraform/outputs.tf
@@ -0,0 +1,14 @@
+output "artifact_registry_repo" {
+  description = "Full path of the training Artifact Registry repo."
+  value       = "${var.region}-docker.pkg.dev/${var.project_id}/${google_artifact_registry_repository.training.repository_id}"
+}
+
+output "github_pusher_sa_email" {
+  description = "Email of the SA that GitHub Actions impersonates. Use in the workflow's google-github-actions/auth@v2 step."
+  value       = google_service_account.github_pusher.email
+}
+
+output "workload_identity_provider" {
+  description = "Full resource name of the WIF provider, for google-github-actions/auth@v2."
+  value       = google_iam_workload_identity_pool_provider.github.name
+}
diff --git a/training/terraform/providers.tf b/training/terraform/providers.tf
new file mode 100644
index 00000000000..a7963d0a8f8
--- /dev/null
+++ b/training/terraform/providers.tf
@@ -0,0 +1,14 @@
+terraform {
+  required_version = ">= 1.5"
+  required_providers {
+    google = {
+      source  = "hashicorp/google"
+      version = "~> 6.0"
+    }
+  }
+}
+
+provider "google" {
+  project = var.project_id
+  region  = var.region
+}
diff --git a/training/terraform/terraform.tfvars.example b/training/terraform/terraform.tfvars.example
new file mode 100644
index 00000000000..5bbbbe4ac18
--- /dev/null
+++ b/training/terraform/terraform.tfvars.example
@@ -0,0 +1,3 @@
+project_id  = "re5-n8n-platform"
+region      = "europe-west1"
+github_repo = "re-cinq/microservices-demo"
diff --git a/training/terraform/variables.tf b/training/terraform/variables.tf
new file mode 100644
index 00000000000..0f1c7418571
--- /dev/null
+++ b/training/terraform/variables.tf
@@ -0,0 +1,22 @@
+variable "project_id" {
+  description = "GCP project ID hosting the training cluster and registry."
+  type        = string
+}
+
+variable "region" {
+  description = "Region for the Artifact Registry repo. Should match the GKE cluster region for free in-region pulls."
+  type        = string
+  default     = "europe-west1"
+}
+
+variable "github_repo" {
+  description = "GitHub repo allowed to push images via Workload Identity Federation, in 'owner/name' form."
+  type        = string
+  default     = "re-cinq/microservices-demo"
+}
+
+variable "gke_node_service_account" {
+  description = "Email of the service account used by GKE Autopilot nodes (for image pulls). Defaults to the project's compute default SA, which is what Autopilot uses unless overridden."
+  type        = string
+  default     = ""
+}
diff --git a/training/values-training.yaml b/training/values-training.yaml
new file mode 100644
index 00000000000..908c9c33938
--- /dev/null
+++ b/training/values-training.yaml
@@ -0,0 +1,124 @@
+# Training overlay for Online Boutique.
+#
+# Applied per-attendee via:
+#   helm upgrade --install boutique ./helm-chart \
+#     -n attendee-<name> \
+#     -f training/values-training.yaml
+#
+# Goals:
+#   - Cut Autopilot pod-request cost (we pay for requests on Autopilot)
+#   - Drop loadgenerator entirely (a noisy neighbour to prod on a shared cluster)
+#   - Default all images to the training :base tag in our GAR
+#   - Leave per-service image.tag overridable so CI can flip a single service
+#     to attendee-<name>-<sha> on PR merge
+
+images:
+  # Bulk-copied at training setup from us-central1-docker.pkg.dev/google-samples/microservices-demo/*
+  repository: europe-west1-docker.pkg.dev/re5-n8n-platform/microservices-demo-training
+  tag: base
+
+# Disable load generation across all attendee namespaces.
+loadGenerator:
+  create: false
+
+# Disable shopping assistant (not used in training).
+shoppingAssistantService:
+  create: false
+
+# Trimmed resource requests/limits. Numbers chosen to be enough for a
+# 1-2 user browsing session, not for benchmarks.
+adService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 120Mi
+    limits:
+      cpu: 200m
+      memory: 220Mi
+
+cartService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 80Mi
+    limits:
+      cpu: 200m
+      memory: 200Mi
+
+checkoutService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 48Mi
+    limits:
+      cpu: 150m
+      memory: 100Mi
+
+currencyService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 80Mi
+    limits:
+      cpu: 150m
+      memory: 200Mi
+
+emailService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 48Mi
+    limits:
+      cpu: 150m
+      memory: 100Mi
+
+frontend:
+  externalService: false  # we expose via Ingress, not LoadBalancer
+  resources:
+    requests:
+      cpu: 50m
+      memory: 48Mi
+    limits:
+      cpu: 150m
+      memory: 100Mi
+
+paymentService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 80Mi
+    limits:
+      cpu: 150m
+      memory: 200Mi
+
+productCatalogService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 48Mi
+    limits:
+      cpu: 150m
+      memory: 100Mi
+
+recommendationService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 150Mi
+    limits:
+      cpu: 150m
+      memory: 350Mi
+
+shippingService:
+  resources:
+    requests:
+      cpu: 50m
+      memory: 48Mi
+    limits:
+      cpu: 150m
+      memory: 100Mi
+
+# In-cluster Redis for cart. Same trim.
+cartDatabase:
+  inClusterRedis:
+    create: true

From ae36b1c6130988e8188d019500d99f77d0cb4649 Mon Sep 17 00:00:00 2001
From: muemich <michaelmuellerrw@gmail.com>
Date: Mon, 4 May 2026 13:10:03 +0200
Subject: [PATCH 02/10] training: fix probe timeouts, ingress class, and pusher
 cluster perms

Issues found during dress rehearsal:

- Python services (emailservice, recommendationservice) were CrashLooping
  because the gRPC liveness probe defaults to timeoutSeconds=1, which is
  too tight when CPU-throttled. Bumped readiness/liveness timeoutSeconds
  to 5 and bumped Python service CPU requests to 100m.

- provision.sh was writing Ingresses with ingressClassName=nginx, but the
  cluster's IngressClass is named nginx-ingress. nginx-ingress controller
  silently ignored the resource and external-dns never published a record.

- Workflow's training-image-pusher SA could push to GAR but lacked
  container.clusters.get, so get-gke-credentials denied. Added
  roles/container.developer at project scope.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 helm-chart/templates/emailservice.yaml          |  4 +++-
 helm-chart/templates/recommendationservice.yaml |  4 +++-
 training/bootstrap/provision.sh                 |  2 +-
 training/terraform/main.tf                      |  9 +++++++++
 training/values-training.yaml                   | 16 ++++++++--------
 5 files changed, 24 insertions(+), 11 deletions(-)

diff --git a/helm-chart/templates/emailservice.yaml b/helm-chart/templates/emailservice.yaml
index 9e2ace61a78..3a44c0ce8d0 100644
--- a/helm-chart/templates/emailservice.yaml
+++ b/helm-chart/templates/emailservice.yaml
@@ -91,10 +91,12 @@ spec:
         {{- end }}
         readinessProbe:
           periodSeconds: 5
+          timeoutSeconds: 5
           grpc:
             port: 8080
         livenessProbe:
-          periodSeconds: 5
+          periodSeconds: 10
+          timeoutSeconds: 5
           grpc:
             port: 8080
         resources:
diff --git a/helm-chart/templates/recommendationservice.yaml b/helm-chart/templates/recommendationservice.yaml
index bf101ce3af9..94cb84d3f5b 100644
--- a/helm-chart/templates/recommendationservice.yaml
+++ b/helm-chart/templates/recommendationservice.yaml
@@ -74,10 +74,12 @@ spec:
         - containerPort: 8080
         readinessProbe:
           periodSeconds: 5
+          timeoutSeconds: 5
           grpc:
             port: 8080
         livenessProbe:
-          periodSeconds: 5
+          periodSeconds: 10
+          timeoutSeconds: 5
           grpc:
             port: 8080
         env:
diff --git a/training/bootstrap/provision.sh b/training/bootstrap/provision.sh
index d0d18d8a367..70ac05d3c07 100755
--- a/training/bootstrap/provision.sh
+++ b/training/bootstrap/provision.sh
@@ -20,7 +20,7 @@ TRAINING_DIR="$REPO_ROOT/training"
 DOMAIN="training.gcp.re-cinq.com"
 TLS_SECRET="wildcard-training-tls"
 CLUSTER_ISSUER="letsencrypt-prod"
-INGRESS_CLASS="nginx"
+INGRESS_CLASS="nginx-ingress"
 BASE_BRANCH="main"
 
 if [[ $# -ne 1 ]]; then
diff --git a/training/terraform/main.tf b/training/terraform/main.tf
index 1ce368b6bda..69c983b1bc1 100644
--- a/training/terraform/main.tf
+++ b/training/terraform/main.tf
@@ -100,6 +100,15 @@ resource "google_artifact_registry_repository_iam_member" "github_push" {
   member     = "serviceAccount:${google_service_account.github_pusher.email}"
 }
 
+# Lets the workflow run get-gke-credentials and helm-upgrade against the
+# training cluster. Project-wide scope is broader than necessary; refine
+# with RBAC later if upstreaming.
+resource "google_project_iam_member" "github_gke_developer" {
+  project = var.project_id
+  role    = "roles/container.developer"
+  member  = "serviceAccount:${google_service_account.github_pusher.email}"
+}
+
 # Allow the GitHub repo's tokens (any branch) to impersonate the SA.
 resource "google_service_account_iam_member" "github_wif_binding" {
   service_account_id = google_service_account.github_pusher.name
diff --git a/training/values-training.yaml b/training/values-training.yaml
index 908c9c33938..c8449ffe825 100644
--- a/training/values-training.yaml
+++ b/training/values-training.yaml
@@ -66,11 +66,11 @@ currencyService:
 emailService:
   resources:
     requests:
-      cpu: 50m
-      memory: 48Mi
+      cpu: 100m
+      memory: 64Mi
     limits:
-      cpu: 150m
-      memory: 100Mi
+      cpu: 200m
+      memory: 128Mi
 
 frontend:
   externalService: false  # we expose via Ingress, not LoadBalancer
@@ -103,11 +103,11 @@ productCatalogService:
 recommendationService:
   resources:
     requests:
-      cpu: 50m
-      memory: 150Mi
+      cpu: 100m
+      memory: 220Mi
     limits:
-      cpu: 150m
-      memory: 350Mi
+      cpu: 200m
+      memory: 450Mi
 
 shippingService:
   resources:

From 2538c7d2854b33ec44f9000c828294321fe9ca74 Mon Sep 17 00:00:00 2001
From: muemich <michaelmuellerrw@gmail.com>
Date: Wed, 6 May 2026 12:08:25 +0200
Subject: [PATCH 03/10] training: commit cohort handouts + harden provision.sh

- Add 29 attendee handouts under training/handouts/ for direct sharing.
- Stop tracking emails.txt (kept local) so attendee lists don't end up
  in the public fork.
- provision.sh: detach main repo HEAD before each iteration and use
  -B/worktree-prune so re-runs don't trip on leftover local branches.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 training/.gitignore                       |  2 +-
 training/bootstrap/emails.txt             | 41 -----------------------
 training/bootstrap/provision.sh           | 15 +++++++--
 training/handouts/alek-legosteva.md       | 41 +++++++++++++++++++++++
 training/handouts/andrea-backstrom.md     | 41 +++++++++++++++++++++++
 training/handouts/anna-edholm.md          | 41 +++++++++++++++++++++++
 training/handouts/anna-ingemarsson.md     | 41 +++++++++++++++++++++++
 training/handouts/anna-simon.md           | 41 +++++++++++++++++++++++
 training/handouts/craig-langley-tester.md | 41 +++++++++++++++++++++++
 training/handouts/cristofer-dreimanis.md  | 41 +++++++++++++++++++++++
 training/handouts/daniel-tufvander.md     | 41 +++++++++++++++++++++++
 training/handouts/fredric-gustafsson.md   | 41 +++++++++++++++++++++++
 training/handouts/gustav-dahlbeck.md      | 41 +++++++++++++++++++++++
 training/handouts/james-colebeck.md       | 41 +++++++++++++++++++++++
 training/handouts/jenny-svennefelt.md     | 41 +++++++++++++++++++++++
 training/handouts/joel-sanmoogan.md       | 41 +++++++++++++++++++++++
 training/handouts/jonathan-wirseen.md     | 41 +++++++++++++++++++++++
 training/handouts/josefin-gelin.md        | 41 +++++++++++++++++++++++
 training/handouts/jost-werdenhoff.md      | 41 +++++++++++++++++++++++
 training/handouts/kate-payne.md           | 41 +++++++++++++++++++++++
 training/handouts/markus-palsson.md       | 41 +++++++++++++++++++++++
 training/handouts/matthew-blanshard.md    | 41 +++++++++++++++++++++++
 training/handouts/michael.md              | 41 +++++++++++++++++++++++
 training/handouts/mikael-svensson.md      | 41 +++++++++++++++++++++++
 training/handouts/nabeel-moosa.md         | 41 +++++++++++++++++++++++
 training/handouts/pascal-ambrosius.md     | 41 +++++++++++++++++++++++
 training/handouts/patrik-sommar.md        | 41 +++++++++++++++++++++++
 training/handouts/samantha-short.md       | 41 +++++++++++++++++++++++
 training/handouts/sennai-mebrahtu.md      | 41 +++++++++++++++++++++++
 training/handouts/siri-uhrnell.md         | 41 +++++++++++++++++++++++
 training/handouts/tim-love.md             | 41 +++++++++++++++++++++++
 training/handouts/william-folkesson.md    | 41 +++++++++++++++++++++++
 32 files changed, 1202 insertions(+), 45 deletions(-)
 delete mode 100644 training/bootstrap/emails.txt
 create mode 100644 training/handouts/alek-legosteva.md
 create mode 100644 training/handouts/andrea-backstrom.md
 create mode 100644 training/handouts/anna-edholm.md
 create mode 100644 training/handouts/anna-ingemarsson.md
 create mode 100644 training/handouts/anna-simon.md
 create mode 100644 training/handouts/craig-langley-tester.md
 create mode 100644 training/handouts/cristofer-dreimanis.md
 create mode 100644 training/handouts/daniel-tufvander.md
 create mode 100644 training/handouts/fredric-gustafsson.md
 create mode 100644 training/handouts/gustav-dahlbeck.md
 create mode 100644 training/handouts/james-colebeck.md
 create mode 100644 training/handouts/jenny-svennefelt.md
 create mode 100644 training/handouts/joel-sanmoogan.md
 create mode 100644 training/handouts/jonathan-wirseen.md
 create mode 100644 training/handouts/josefin-gelin.md
 create mode 100644 training/handouts/jost-werdenhoff.md
 create mode 100644 training/handouts/kate-payne.md
 create mode 100644 training/handouts/markus-palsson.md
 create mode 100644 training/handouts/matthew-blanshard.md
 create mode 100644 training/handouts/michael.md
 create mode 100644 training/handouts/mikael-svensson.md
 create mode 100644 training/handouts/nabeel-moosa.md
 create mode 100644 training/handouts/pascal-ambrosius.md
 create mode 100644 training/handouts/patrik-sommar.md
 create mode 100644 training/handouts/samantha-short.md
 create mode 100644 training/handouts/sennai-mebrahtu.md
 create mode 100644 training/handouts/siri-uhrnell.md
 create mode 100644 training/handouts/tim-love.md
 create mode 100644 training/handouts/william-folkesson.md

diff --git a/training/.gitignore b/training/.gitignore
index 36d64f05cc9..ccec581905d 100644
--- a/training/.gitignore
+++ b/training/.gitignore
@@ -1,5 +1,5 @@
-handouts/
 bootstrap/attendees.csv
+bootstrap/emails.txt
 terraform/.terraform/
 terraform/terraform.tfstate*
 terraform/terraform.tfvars
diff --git a/training/bootstrap/emails.txt b/training/bootstrap/emails.txt
deleted file mode 100644
index 8a6d2ccd793..00000000000
--- a/training/bootstrap/emails.txt
+++ /dev/null
@@ -1,41 +0,0 @@
-alek.legosteva@odevo.com
-andrea.backstrom@odevo.com
-angi.krauskopf@odevo.com
-anna.simon@odevo.com
-craig.langley-tester@odevo.com
-cristofer.dreimanis@odevo.com
-cruz.moreno@odevo.com
-daniel.anundi@odevo.com
-daniel@re-cinq.com
-emil.stenstrom@odevo.com
-fnieto@kwpmc.com
-george.yang@odevo.com
-gustaf.ankarcrona@odevo.com
-james.colebeck@odevo.com
-jan.lundequist@odevo.com
-jenny.linde@odevo.com
-joel.johannesson@odevo.com
-joel.sanmoogan@vegnergroup.com
-jonas.hagernas@odevo.com
-jonathan.wirseen@odevo.com
-jost.werdenhoff@odevo.com
-kate.payne@odevo.com
-martin.hjers@odevo.com
-marv.gillibrand@odevo.com
-matthew.blanshard@odevo.com
-matthew.buckland@odevo.com
-mikael.svensson@odevo.com
-nabeel.moosa@odevo.com
-nejal.patel@odevo.com
-olof.nordberg@odevo.com
-patrik.sommar@odevo.com
-pontus.jespersson@odevo.com
-pontus.vepsalainen@odevo.com
-samantha.short@odevo.com
-sarah.crissman@odevo.com
-sennai.mebrahtu@odevo.com
-sermed.ali@odevo.com
-siri.uhrnell@odevo.com
-stanislava.bazitova@odevo.com
-tim.love@odevo.com
-tomasz.maj@odevo.com
diff --git a/training/bootstrap/provision.sh b/training/bootstrap/provision.sh
index 70ac05d3c07..c5f1e3567e9 100755
--- a/training/bootstrap/provision.sh
+++ b/training/bootstrap/provision.sh
@@ -34,6 +34,10 @@ mkdir -p "$TRAINING_DIR/handouts"
 
 log() { printf '\033[1;34m[bootstrap]\033[0m %s\n' "$*"; }
 
+# Make sure the main repo isn't holding any attendee/* branch checkout left
+# over from a previous cohort - it would otherwise prevent worktree creation.
+git -C "$REPO_ROOT" checkout main --quiet 2>/dev/null || true
+
 # Validate every row first - fail before we mutate anything
 log "validating $CSV"
 while IFS=, read -r name bug; do
@@ -177,10 +181,15 @@ EOF
     log "branch $branch already exists on origin, skipping"
   else
     log "creating branch $branch from origin/$BASE_BRANCH"
-    git worktree add --quiet --detach /tmp/training-$name "origin/$BASE_BRANCH"
+    # Clean up any leftover state from prior runs.
+    rm -rf "/tmp/training-$name"
+    git worktree prune
+    git worktree add --quiet --detach "/tmp/training-$name" "origin/$BASE_BRANCH"
     (
-      cd /tmp/training-$name
-      git checkout -b "$branch"
+      cd "/tmp/training-$name"
+      # -B overwrites a local branch of the same name (left over from a previous
+      # cohort even after the remote branch was teardown'd).
+      git checkout -B "$branch"
       git apply "$TRAINING_DIR/bugs/$bug/PATCH.diff"
       cp "$TRAINING_DIR/bugs/$bug/BUG_REPORT.md" ./BUG_REPORT.md
       git add -A
diff --git a/training/handouts/alek-legosteva.md b/training/handouts/alek-legosteva.md
new file mode 100644
index 00000000000..b18e51519fa
--- /dev/null
+++ b/training/handouts/alek-legosteva.md
@@ -0,0 +1,41 @@
+# Training handout — alek-legosteva
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://alek-legosteva.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/alek-legosteva`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at alek-legosteva.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at alek-legosteva.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/alek-legosteva`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/alek-legosteva
+git checkout -b attendee/alek-legosteva-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/alek-legosteva-fix
+gh pr create --base attendee/alek-legosteva --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://alek-legosteva.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/andrea-backstrom.md b/training/handouts/andrea-backstrom.md
new file mode 100644
index 00000000000..b3175f6c539
--- /dev/null
+++ b/training/handouts/andrea-backstrom.md
@@ -0,0 +1,41 @@
+# Training handout — andrea-backstrom
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://andrea-backstrom.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/andrea-backstrom`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at andrea-backstrom.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at andrea-backstrom.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/andrea-backstrom`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/andrea-backstrom
+git checkout -b attendee/andrea-backstrom-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/andrea-backstrom-fix
+gh pr create --base attendee/andrea-backstrom --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://andrea-backstrom.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/anna-edholm.md b/training/handouts/anna-edholm.md
new file mode 100644
index 00000000000..4799b1c15cb
--- /dev/null
+++ b/training/handouts/anna-edholm.md
@@ -0,0 +1,41 @@
+# Training handout — anna-edholm
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://anna-edholm.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/anna-edholm`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at anna-edholm.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at anna-edholm.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/anna-edholm`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/anna-edholm
+git checkout -b attendee/anna-edholm-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/anna-edholm-fix
+gh pr create --base attendee/anna-edholm --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://anna-edholm.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/anna-ingemarsson.md b/training/handouts/anna-ingemarsson.md
new file mode 100644
index 00000000000..b24c4c64448
--- /dev/null
+++ b/training/handouts/anna-ingemarsson.md
@@ -0,0 +1,41 @@
+# Training handout — anna-ingemarsson
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://anna-ingemarsson.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/anna-ingemarsson`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at anna-ingemarsson.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at anna-ingemarsson.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/anna-ingemarsson`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/anna-ingemarsson
+git checkout -b attendee/anna-ingemarsson-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/anna-ingemarsson-fix
+gh pr create --base attendee/anna-ingemarsson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://anna-ingemarsson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/anna-simon.md b/training/handouts/anna-simon.md
new file mode 100644
index 00000000000..49b41982066
--- /dev/null
+++ b/training/handouts/anna-simon.md
@@ -0,0 +1,41 @@
+# Training handout — anna-simon
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://anna-simon.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/anna-simon`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at anna-simon.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at anna-simon.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/anna-simon`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/anna-simon
+git checkout -b attendee/anna-simon-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/anna-simon-fix
+gh pr create --base attendee/anna-simon --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://anna-simon.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/craig-langley-tester.md b/training/handouts/craig-langley-tester.md
new file mode 100644
index 00000000000..2391ac79121
--- /dev/null
+++ b/training/handouts/craig-langley-tester.md
@@ -0,0 +1,41 @@
+# Training handout — craig-langley-tester
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://craig-langley-tester.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/craig-langley-tester`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at craig-langley-tester.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at craig-langley-tester.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/craig-langley-tester`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/craig-langley-tester
+git checkout -b attendee/craig-langley-tester-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/craig-langley-tester-fix
+gh pr create --base attendee/craig-langley-tester --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://craig-langley-tester.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/cristofer-dreimanis.md b/training/handouts/cristofer-dreimanis.md
new file mode 100644
index 00000000000..f866a7321c9
--- /dev/null
+++ b/training/handouts/cristofer-dreimanis.md
@@ -0,0 +1,41 @@
+# Training handout — cristofer-dreimanis
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://cristofer-dreimanis.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/cristofer-dreimanis`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at cristofer-dreimanis.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at cristofer-dreimanis.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/cristofer-dreimanis`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/cristofer-dreimanis
+git checkout -b attendee/cristofer-dreimanis-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/cristofer-dreimanis-fix
+gh pr create --base attendee/cristofer-dreimanis --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://cristofer-dreimanis.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/daniel-tufvander.md b/training/handouts/daniel-tufvander.md
new file mode 100644
index 00000000000..eede706f0c2
--- /dev/null
+++ b/training/handouts/daniel-tufvander.md
@@ -0,0 +1,41 @@
+# Training handout — daniel-tufvander
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://daniel-tufvander.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/daniel-tufvander`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at daniel-tufvander.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at daniel-tufvander.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/daniel-tufvander`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/daniel-tufvander
+git checkout -b attendee/daniel-tufvander-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/daniel-tufvander-fix
+gh pr create --base attendee/daniel-tufvander --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://daniel-tufvander.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/fredric-gustafsson.md b/training/handouts/fredric-gustafsson.md
new file mode 100644
index 00000000000..5d8eeb18355
--- /dev/null
+++ b/training/handouts/fredric-gustafsson.md
@@ -0,0 +1,41 @@
+# Training handout — fredric-gustafsson
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://fredric-gustafsson.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/fredric-gustafsson`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at fredric-gustafsson.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at fredric-gustafsson.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/fredric-gustafsson`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/fredric-gustafsson
+git checkout -b attendee/fredric-gustafsson-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/fredric-gustafsson-fix
+gh pr create --base attendee/fredric-gustafsson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://fredric-gustafsson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/gustav-dahlbeck.md b/training/handouts/gustav-dahlbeck.md
new file mode 100644
index 00000000000..ae00e78122c
--- /dev/null
+++ b/training/handouts/gustav-dahlbeck.md
@@ -0,0 +1,41 @@
+# Training handout — gustav-dahlbeck
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://gustav-dahlbeck.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/gustav-dahlbeck`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at gustav-dahlbeck.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at gustav-dahlbeck.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/gustav-dahlbeck`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/gustav-dahlbeck
+git checkout -b attendee/gustav-dahlbeck-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/gustav-dahlbeck-fix
+gh pr create --base attendee/gustav-dahlbeck --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://gustav-dahlbeck.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/james-colebeck.md b/training/handouts/james-colebeck.md
new file mode 100644
index 00000000000..7ab7360b419
--- /dev/null
+++ b/training/handouts/james-colebeck.md
@@ -0,0 +1,41 @@
+# Training handout — james-colebeck
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://james-colebeck.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/james-colebeck`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at james-colebeck.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at james-colebeck.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/james-colebeck`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/james-colebeck
+git checkout -b attendee/james-colebeck-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/james-colebeck-fix
+gh pr create --base attendee/james-colebeck --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://james-colebeck.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/jenny-svennefelt.md b/training/handouts/jenny-svennefelt.md
new file mode 100644
index 00000000000..58f82b40364
--- /dev/null
+++ b/training/handouts/jenny-svennefelt.md
@@ -0,0 +1,41 @@
+# Training handout — jenny-svennefelt
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://jenny-svennefelt.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/jenny-svennefelt`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at jenny-svennefelt.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at jenny-svennefelt.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/jenny-svennefelt`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/jenny-svennefelt
+git checkout -b attendee/jenny-svennefelt-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/jenny-svennefelt-fix
+gh pr create --base attendee/jenny-svennefelt --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://jenny-svennefelt.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/joel-sanmoogan.md b/training/handouts/joel-sanmoogan.md
new file mode 100644
index 00000000000..e57b4a25ac7
--- /dev/null
+++ b/training/handouts/joel-sanmoogan.md
@@ -0,0 +1,41 @@
+# Training handout — joel-sanmoogan
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://joel-sanmoogan.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/joel-sanmoogan`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at joel-sanmoogan.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at joel-sanmoogan.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/joel-sanmoogan`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/joel-sanmoogan
+git checkout -b attendee/joel-sanmoogan-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/joel-sanmoogan-fix
+gh pr create --base attendee/joel-sanmoogan --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://joel-sanmoogan.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/jonathan-wirseen.md b/training/handouts/jonathan-wirseen.md
new file mode 100644
index 00000000000..55af663ea0b
--- /dev/null
+++ b/training/handouts/jonathan-wirseen.md
@@ -0,0 +1,41 @@
+# Training handout — jonathan-wirseen
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://jonathan-wirseen.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/jonathan-wirseen`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at jonathan-wirseen.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at jonathan-wirseen.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/jonathan-wirseen`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/jonathan-wirseen
+git checkout -b attendee/jonathan-wirseen-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/jonathan-wirseen-fix
+gh pr create --base attendee/jonathan-wirseen --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://jonathan-wirseen.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/josefin-gelin.md b/training/handouts/josefin-gelin.md
new file mode 100644
index 00000000000..316f102e512
--- /dev/null
+++ b/training/handouts/josefin-gelin.md
@@ -0,0 +1,41 @@
+# Training handout — josefin-gelin
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://josefin-gelin.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/josefin-gelin`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at josefin-gelin.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at josefin-gelin.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/josefin-gelin`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/josefin-gelin
+git checkout -b attendee/josefin-gelin-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/josefin-gelin-fix
+gh pr create --base attendee/josefin-gelin --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://josefin-gelin.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/jost-werdenhoff.md b/training/handouts/jost-werdenhoff.md
new file mode 100644
index 00000000000..cb028e59ffc
--- /dev/null
+++ b/training/handouts/jost-werdenhoff.md
@@ -0,0 +1,41 @@
+# Training handout — jost-werdenhoff
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://jost-werdenhoff.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/jost-werdenhoff`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at jost-werdenhoff.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at jost-werdenhoff.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/jost-werdenhoff`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/jost-werdenhoff
+git checkout -b attendee/jost-werdenhoff-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/jost-werdenhoff-fix
+gh pr create --base attendee/jost-werdenhoff --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://jost-werdenhoff.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/kate-payne.md b/training/handouts/kate-payne.md
new file mode 100644
index 00000000000..a276ff8fd3f
--- /dev/null
+++ b/training/handouts/kate-payne.md
@@ -0,0 +1,41 @@
+# Training handout — kate-payne
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://kate-payne.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/kate-payne`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at kate-payne.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at kate-payne.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/kate-payne`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/kate-payne
+git checkout -b attendee/kate-payne-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/kate-payne-fix
+gh pr create --base attendee/kate-payne --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://kate-payne.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/markus-palsson.md b/training/handouts/markus-palsson.md
new file mode 100644
index 00000000000..5ff42f2ce26
--- /dev/null
+++ b/training/handouts/markus-palsson.md
@@ -0,0 +1,41 @@
+# Training handout — markus-palsson
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://markus-palsson.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/markus-palsson`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at markus-palsson.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at markus-palsson.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/markus-palsson`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/markus-palsson
+git checkout -b attendee/markus-palsson-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/markus-palsson-fix
+gh pr create --base attendee/markus-palsson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://markus-palsson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/matthew-blanshard.md b/training/handouts/matthew-blanshard.md
new file mode 100644
index 00000000000..907800461ba
--- /dev/null
+++ b/training/handouts/matthew-blanshard.md
@@ -0,0 +1,41 @@
+# Training handout — matthew-blanshard
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://matthew-blanshard.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/matthew-blanshard`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at matthew-blanshard.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at matthew-blanshard.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/matthew-blanshard`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/matthew-blanshard
+git checkout -b attendee/matthew-blanshard-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/matthew-blanshard-fix
+gh pr create --base attendee/matthew-blanshard --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://matthew-blanshard.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/michael.md b/training/handouts/michael.md
new file mode 100644
index 00000000000..12a5dfcef8f
--- /dev/null
+++ b/training/handouts/michael.md
@@ -0,0 +1,41 @@
+# Training handout — michael
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://michael.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/michael`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at michael.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at michael.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/michael`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/michael
+git checkout -b attendee/michael-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/michael-fix
+gh pr create --base attendee/michael --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://michael.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/mikael-svensson.md b/training/handouts/mikael-svensson.md
new file mode 100644
index 00000000000..f88944c8ddf
--- /dev/null
+++ b/training/handouts/mikael-svensson.md
@@ -0,0 +1,41 @@
+# Training handout — mikael-svensson
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://mikael-svensson.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/mikael-svensson`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at mikael-svensson.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at mikael-svensson.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/mikael-svensson`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/mikael-svensson
+git checkout -b attendee/mikael-svensson-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/mikael-svensson-fix
+gh pr create --base attendee/mikael-svensson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://mikael-svensson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/nabeel-moosa.md b/training/handouts/nabeel-moosa.md
new file mode 100644
index 00000000000..493868fd9d3
--- /dev/null
+++ b/training/handouts/nabeel-moosa.md
@@ -0,0 +1,41 @@
+# Training handout — nabeel-moosa
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://nabeel-moosa.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/nabeel-moosa`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at nabeel-moosa.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at nabeel-moosa.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/nabeel-moosa`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/nabeel-moosa
+git checkout -b attendee/nabeel-moosa-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/nabeel-moosa-fix
+gh pr create --base attendee/nabeel-moosa --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://nabeel-moosa.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/pascal-ambrosius.md b/training/handouts/pascal-ambrosius.md
new file mode 100644
index 00000000000..00f79225af7
--- /dev/null
+++ b/training/handouts/pascal-ambrosius.md
@@ -0,0 +1,41 @@
+# Training handout — pascal-ambrosius
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://pascal-ambrosius.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/pascal-ambrosius`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at pascal-ambrosius.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at pascal-ambrosius.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/pascal-ambrosius`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/pascal-ambrosius
+git checkout -b attendee/pascal-ambrosius-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/pascal-ambrosius-fix
+gh pr create --base attendee/pascal-ambrosius --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://pascal-ambrosius.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/patrik-sommar.md b/training/handouts/patrik-sommar.md
new file mode 100644
index 00000000000..9b02fbb93b3
--- /dev/null
+++ b/training/handouts/patrik-sommar.md
@@ -0,0 +1,41 @@
+# Training handout — patrik-sommar
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://patrik-sommar.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/patrik-sommar`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at patrik-sommar.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at patrik-sommar.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/patrik-sommar`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/patrik-sommar
+git checkout -b attendee/patrik-sommar-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/patrik-sommar-fix
+gh pr create --base attendee/patrik-sommar --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://patrik-sommar.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/samantha-short.md b/training/handouts/samantha-short.md
new file mode 100644
index 00000000000..341b7c566e5
--- /dev/null
+++ b/training/handouts/samantha-short.md
@@ -0,0 +1,41 @@
+# Training handout — samantha-short
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://samantha-short.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/samantha-short`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at samantha-short.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at samantha-short.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/samantha-short`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/samantha-short
+git checkout -b attendee/samantha-short-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/samantha-short-fix
+gh pr create --base attendee/samantha-short --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://samantha-short.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/sennai-mebrahtu.md b/training/handouts/sennai-mebrahtu.md
new file mode 100644
index 00000000000..969a8dd229d
--- /dev/null
+++ b/training/handouts/sennai-mebrahtu.md
@@ -0,0 +1,41 @@
+# Training handout — sennai-mebrahtu
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://sennai-mebrahtu.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/sennai-mebrahtu`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at sennai-mebrahtu.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at sennai-mebrahtu.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/sennai-mebrahtu`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/sennai-mebrahtu
+git checkout -b attendee/sennai-mebrahtu-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/sennai-mebrahtu-fix
+gh pr create --base attendee/sennai-mebrahtu --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://sennai-mebrahtu.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/siri-uhrnell.md b/training/handouts/siri-uhrnell.md
new file mode 100644
index 00000000000..b5e82095f58
--- /dev/null
+++ b/training/handouts/siri-uhrnell.md
@@ -0,0 +1,41 @@
+# Training handout — siri-uhrnell
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://siri-uhrnell.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/siri-uhrnell`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at siri-uhrnell.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at siri-uhrnell.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/siri-uhrnell`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/siri-uhrnell
+git checkout -b attendee/siri-uhrnell-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/siri-uhrnell-fix
+gh pr create --base attendee/siri-uhrnell --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://siri-uhrnell.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/tim-love.md b/training/handouts/tim-love.md
new file mode 100644
index 00000000000..f83a8d5593d
--- /dev/null
+++ b/training/handouts/tim-love.md
@@ -0,0 +1,41 @@
+# Training handout — tim-love
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://tim-love.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/tim-love`                                     |
+| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at tim-love.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at tim-love.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/tim-love`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/tim-love
+git checkout -b attendee/tim-love-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/tim-love-fix
+gh pr create --base attendee/tim-love --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://tim-love.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/william-folkesson.md b/training/handouts/william-folkesson.md
new file mode 100644
index 00000000000..7808fce7864
--- /dev/null
+++ b/training/handouts/william-folkesson.md
@@ -0,0 +1,41 @@
+# Training handout — william-folkesson
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://william-folkesson.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/william-folkesson`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+`BUG_REPORT.md` on your branch. Your job today:
+
+1. Reproduce the issue at william-folkesson.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at william-folkesson.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/william-folkesson`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/william-folkesson
+git checkout -b attendee/william-folkesson-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/william-folkesson-fix
+gh pr create --base attendee/william-folkesson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://william-folkesson.training.gcp.re-cinq.com once it's green.

From e6b62dcae00798469c55b9dab33ac65c3a265114 Mon Sep 17 00:00:00 2001
From: muemich <michaelmuellerrw@gmail.com>
Date: Wed, 6 May 2026 12:12:19 +0200
Subject: [PATCH 04/10] training: link handouts directly to each attendee's
 BUG_REPORT.md

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 training/bootstrap/provision.sh           | 3 ++-
 training/handouts/alek-legosteva.md       | 3 ++-
 training/handouts/andrea-backstrom.md     | 3 ++-
 training/handouts/anna-edholm.md          | 3 ++-
 training/handouts/anna-ingemarsson.md     | 3 ++-
 training/handouts/anna-simon.md           | 3 ++-
 training/handouts/craig-langley-tester.md | 3 ++-
 training/handouts/cristofer-dreimanis.md  | 3 ++-
 training/handouts/daniel-tufvander.md     | 3 ++-
 training/handouts/fredric-gustafsson.md   | 3 ++-
 training/handouts/gustav-dahlbeck.md      | 3 ++-
 training/handouts/james-colebeck.md       | 3 ++-
 training/handouts/jenny-svennefelt.md     | 3 ++-
 training/handouts/joel-sanmoogan.md       | 3 ++-
 training/handouts/jonathan-wirseen.md     | 3 ++-
 training/handouts/josefin-gelin.md        | 3 ++-
 training/handouts/jost-werdenhoff.md      | 3 ++-
 training/handouts/kate-payne.md           | 3 ++-
 training/handouts/markus-palsson.md       | 3 ++-
 training/handouts/matthew-blanshard.md    | 3 ++-
 training/handouts/michael.md              | 3 ++-
 training/handouts/mikael-svensson.md      | 3 ++-
 training/handouts/nabeel-moosa.md         | 3 ++-
 training/handouts/pascal-ambrosius.md     | 3 ++-
 training/handouts/patrik-sommar.md        | 3 ++-
 training/handouts/samantha-short.md       | 3 ++-
 training/handouts/sennai-mebrahtu.md      | 3 ++-
 training/handouts/siri-uhrnell.md         | 3 ++-
 training/handouts/tim-love.md             | 3 ++-
 training/handouts/william-folkesson.md    | 3 ++-
 30 files changed, 60 insertions(+), 30 deletions(-)

diff --git a/training/bootstrap/provision.sh b/training/bootstrap/provision.sh
index c5f1e3567e9..d5d6506a016 100755
--- a/training/bootstrap/provision.sh
+++ b/training/bootstrap/provision.sh
@@ -217,7 +217,8 @@ EOF
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-\`BUG_REPORT.md\` on your branch. Your job today:
+[\`BUG_REPORT.md\`](https://github.com/re-cinq/microservices-demo/blob/$branch/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at $host
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/alek-legosteva.md b/training/handouts/alek-legosteva.md
index b18e51519fa..8679e1b983e 100644
--- a/training/handouts/alek-legosteva.md
+++ b/training/handouts/alek-legosteva.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/alek-legosteva/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at alek-legosteva.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/andrea-backstrom.md b/training/handouts/andrea-backstrom.md
index b3175f6c539..f9e189304a1 100644
--- a/training/handouts/andrea-backstrom.md
+++ b/training/handouts/andrea-backstrom.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/andrea-backstrom/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at andrea-backstrom.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/anna-edholm.md b/training/handouts/anna-edholm.md
index 4799b1c15cb..4ffd81ca8a0 100644
--- a/training/handouts/anna-edholm.md
+++ b/training/handouts/anna-edholm.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/anna-edholm/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at anna-edholm.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/anna-ingemarsson.md b/training/handouts/anna-ingemarsson.md
index b24c4c64448..24975dcec34 100644
--- a/training/handouts/anna-ingemarsson.md
+++ b/training/handouts/anna-ingemarsson.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/anna-ingemarsson/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at anna-ingemarsson.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/anna-simon.md b/training/handouts/anna-simon.md
index 49b41982066..7b79210af62 100644
--- a/training/handouts/anna-simon.md
+++ b/training/handouts/anna-simon.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/anna-simon/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at anna-simon.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/craig-langley-tester.md b/training/handouts/craig-langley-tester.md
index 2391ac79121..4dad15a38fd 100644
--- a/training/handouts/craig-langley-tester.md
+++ b/training/handouts/craig-langley-tester.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/craig-langley-tester/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at craig-langley-tester.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/cristofer-dreimanis.md b/training/handouts/cristofer-dreimanis.md
index f866a7321c9..e6676bb8122 100644
--- a/training/handouts/cristofer-dreimanis.md
+++ b/training/handouts/cristofer-dreimanis.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/cristofer-dreimanis/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at cristofer-dreimanis.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/daniel-tufvander.md b/training/handouts/daniel-tufvander.md
index eede706f0c2..1c8266a58a5 100644
--- a/training/handouts/daniel-tufvander.md
+++ b/training/handouts/daniel-tufvander.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/daniel-tufvander/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at daniel-tufvander.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/fredric-gustafsson.md b/training/handouts/fredric-gustafsson.md
index 5d8eeb18355..b0508425993 100644
--- a/training/handouts/fredric-gustafsson.md
+++ b/training/handouts/fredric-gustafsson.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/fredric-gustafsson/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at fredric-gustafsson.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/gustav-dahlbeck.md b/training/handouts/gustav-dahlbeck.md
index ae00e78122c..0301c0fb382 100644
--- a/training/handouts/gustav-dahlbeck.md
+++ b/training/handouts/gustav-dahlbeck.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/gustav-dahlbeck/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at gustav-dahlbeck.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/james-colebeck.md b/training/handouts/james-colebeck.md
index 7ab7360b419..c76a115d1e4 100644
--- a/training/handouts/james-colebeck.md
+++ b/training/handouts/james-colebeck.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/james-colebeck/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at james-colebeck.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/jenny-svennefelt.md b/training/handouts/jenny-svennefelt.md
index 58f82b40364..ab1a8838fa3 100644
--- a/training/handouts/jenny-svennefelt.md
+++ b/training/handouts/jenny-svennefelt.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/jenny-svennefelt/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at jenny-svennefelt.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/joel-sanmoogan.md b/training/handouts/joel-sanmoogan.md
index e57b4a25ac7..68f408bba71 100644
--- a/training/handouts/joel-sanmoogan.md
+++ b/training/handouts/joel-sanmoogan.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/joel-sanmoogan/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at joel-sanmoogan.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/jonathan-wirseen.md b/training/handouts/jonathan-wirseen.md
index 55af663ea0b..776d429eb15 100644
--- a/training/handouts/jonathan-wirseen.md
+++ b/training/handouts/jonathan-wirseen.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/jonathan-wirseen/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at jonathan-wirseen.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/josefin-gelin.md b/training/handouts/josefin-gelin.md
index 316f102e512..0ffeb623121 100644
--- a/training/handouts/josefin-gelin.md
+++ b/training/handouts/josefin-gelin.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/josefin-gelin/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at josefin-gelin.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/jost-werdenhoff.md b/training/handouts/jost-werdenhoff.md
index cb028e59ffc..fa4deb0e0d3 100644
--- a/training/handouts/jost-werdenhoff.md
+++ b/training/handouts/jost-werdenhoff.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/jost-werdenhoff/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at jost-werdenhoff.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/kate-payne.md b/training/handouts/kate-payne.md
index a276ff8fd3f..0c24f82a019 100644
--- a/training/handouts/kate-payne.md
+++ b/training/handouts/kate-payne.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/kate-payne/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at kate-payne.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/markus-palsson.md b/training/handouts/markus-palsson.md
index 5ff42f2ce26..0bd7398c048 100644
--- a/training/handouts/markus-palsson.md
+++ b/training/handouts/markus-palsson.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/markus-palsson/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at markus-palsson.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/matthew-blanshard.md b/training/handouts/matthew-blanshard.md
index 907800461ba..0373dcd2b06 100644
--- a/training/handouts/matthew-blanshard.md
+++ b/training/handouts/matthew-blanshard.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/matthew-blanshard/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at matthew-blanshard.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/michael.md b/training/handouts/michael.md
index 12a5dfcef8f..731c42db054 100644
--- a/training/handouts/michael.md
+++ b/training/handouts/michael.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/michael/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at michael.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/mikael-svensson.md b/training/handouts/mikael-svensson.md
index f88944c8ddf..fdce693a72b 100644
--- a/training/handouts/mikael-svensson.md
+++ b/training/handouts/mikael-svensson.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/mikael-svensson/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at mikael-svensson.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/nabeel-moosa.md b/training/handouts/nabeel-moosa.md
index 493868fd9d3..f508a0c6f18 100644
--- a/training/handouts/nabeel-moosa.md
+++ b/training/handouts/nabeel-moosa.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/nabeel-moosa/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at nabeel-moosa.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/pascal-ambrosius.md b/training/handouts/pascal-ambrosius.md
index 00f79225af7..cdd7a144378 100644
--- a/training/handouts/pascal-ambrosius.md
+++ b/training/handouts/pascal-ambrosius.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/pascal-ambrosius/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at pascal-ambrosius.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/patrik-sommar.md b/training/handouts/patrik-sommar.md
index 9b02fbb93b3..4a0dc167e82 100644
--- a/training/handouts/patrik-sommar.md
+++ b/training/handouts/patrik-sommar.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/patrik-sommar/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at patrik-sommar.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/samantha-short.md b/training/handouts/samantha-short.md
index 341b7c566e5..b2c6e19fc27 100644
--- a/training/handouts/samantha-short.md
+++ b/training/handouts/samantha-short.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/samantha-short/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at samantha-short.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/sennai-mebrahtu.md b/training/handouts/sennai-mebrahtu.md
index 969a8dd229d..23a9a1eb985 100644
--- a/training/handouts/sennai-mebrahtu.md
+++ b/training/handouts/sennai-mebrahtu.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/sennai-mebrahtu/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at sennai-mebrahtu.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/siri-uhrnell.md b/training/handouts/siri-uhrnell.md
index b5e82095f58..2338ac22f73 100644
--- a/training/handouts/siri-uhrnell.md
+++ b/training/handouts/siri-uhrnell.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/siri-uhrnell/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at siri-uhrnell.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/tim-love.md b/training/handouts/tim-love.md
index f83a8d5593d..9138bb17593 100644
--- a/training/handouts/tim-love.md
+++ b/training/handouts/tim-love.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/tim-love/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at tim-love.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand
diff --git a/training/handouts/william-folkesson.md b/training/handouts/william-folkesson.md
index 7808fce7864..5bf0cc6b427 100644
--- a/training/handouts/william-folkesson.md
+++ b/training/handouts/william-folkesson.md
@@ -12,7 +12,8 @@
 ## What we want from you
 
 A customer just opened a ticket about your URL. The ticket is in
-`BUG_REPORT.md` on your branch. Your job today:
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/william-folkesson/BUG_REPORT.md)
+on your branch. Your job today:
 
 1. Reproduce the issue at william-folkesson.training.gcp.re-cinq.com
 2. Use Claude Code to triage it: find the suspected file, understand

From 7da5d3653a144c8425bf9a430ca3da796d3cdf04 Mon Sep 17 00:00:00 2001
From: muemich <michaelmuellerrw@gmail.com>
Date: Wed, 6 May 2026 14:25:41 +0200
Subject: [PATCH 05/10] training: add 3 walk-in attendees (tuva-thornberg,
 matthew-buckland, olof-nordberg)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 training/handouts/matthew-buckland.md | 42 +++++++++++++++++++++++++++
 training/handouts/olof-nordberg.md    | 42 +++++++++++++++++++++++++++
 training/handouts/tuva-thornberg.md   | 42 +++++++++++++++++++++++++++
 3 files changed, 126 insertions(+)
 create mode 100644 training/handouts/matthew-buckland.md
 create mode 100644 training/handouts/olof-nordberg.md
 create mode 100644 training/handouts/tuva-thornberg.md

diff --git a/training/handouts/matthew-buckland.md b/training/handouts/matthew-buckland.md
new file mode 100644
index 00000000000..8cb111ce231
--- /dev/null
+++ b/training/handouts/matthew-buckland.md
@@ -0,0 +1,42 @@
+# Training handout — matthew-buckland
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://matthew-buckland.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/matthew-buckland`                                     |
+| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/matthew-buckland/BUG_REPORT.md)
+on your branch. Your job today:
+
+1. Reproduce the issue at matthew-buckland.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at matthew-buckland.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/matthew-buckland`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/matthew-buckland
+git checkout -b attendee/matthew-buckland-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/matthew-buckland-fix
+gh pr create --base attendee/matthew-buckland --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://matthew-buckland.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/olof-nordberg.md b/training/handouts/olof-nordberg.md
new file mode 100644
index 00000000000..89d5a066788
--- /dev/null
+++ b/training/handouts/olof-nordberg.md
@@ -0,0 +1,42 @@
+# Training handout — olof-nordberg
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://olof-nordberg.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/olof-nordberg`                                     |
+| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/olof-nordberg/BUG_REPORT.md)
+on your branch. Your job today:
+
+1. Reproduce the issue at olof-nordberg.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at olof-nordberg.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/olof-nordberg`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/olof-nordberg
+git checkout -b attendee/olof-nordberg-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/olof-nordberg-fix
+gh pr create --base attendee/olof-nordberg --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://olof-nordberg.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/tuva-thornberg.md b/training/handouts/tuva-thornberg.md
new file mode 100644
index 00000000000..75ee8617fb8
--- /dev/null
+++ b/training/handouts/tuva-thornberg.md
@@ -0,0 +1,42 @@
+# Training handout — tuva-thornberg
+
+## Your environment
+
+| field         | value                                           |
+|---------------|-------------------------------------------------|
+| URL           | https://tuva-thornberg.training.gcp.re-cinq.com                                   |
+| Repo          | https://github.com/re-cinq/microservices-demo   |
+| Your branch   | `attendee/tuva-thornberg`                                     |
+| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
+
+## What we want from you
+
+A customer just opened a ticket about your URL. The ticket is in
+[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/tuva-thornberg/BUG_REPORT.md)
+on your branch. Your job today:
+
+1. Reproduce the issue at tuva-thornberg.training.gcp.re-cinq.com
+2. Use Claude Code to triage it: find the suspected file, understand
+   what's wrong, and write an engineer-ready ticket
+   (`ENGINEERING_TICKET.md` on your branch) with:
+   - exact steps to reproduce
+   - suspected service + file
+   - severity rationale
+3. Fix the bug locally, verify in browser at tuva-thornberg.training.gcp.re-cinq.com after deploying
+4. Open a PR from a fix branch into `attendee/tuva-thornberg`. Auto-merge will
+   redeploy your namespace. Verify the fix went live.
+
+## Local workflow
+
+```bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout attendee/tuva-thornberg
+git checkout -b attendee/tuva-thornberg-fix
+# ... use Claude Code to triage, write ticket, fix ...
+git push -u origin attendee/tuva-thornberg-fix
+gh pr create --base attendee/tuva-thornberg --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
+```
+
+The PR auto-merges on green CI. Watch the GitHub Actions run for the
+deploy. Re-test at https://tuva-thornberg.training.gcp.re-cinq.com once it's green.

From ea76cffd2e7510f090027dc6c2cf7e9bf163ebca Mon Sep 17 00:00:00 2001
From: muemich <michaelmuellerrw@gmail.com>
Date: Thu, 7 May 2026 09:40:58 +0200
Subject: [PATCH 06/10] training: remove cohort handouts containing attendee
 names

Re-ignore handouts/ so future cohort runs stay local.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 training/.gitignore                       |  1 +
 training/handouts/alek-legosteva.md       | 42 -----------------------
 training/handouts/andrea-backstrom.md     | 42 -----------------------
 training/handouts/anna-edholm.md          | 42 -----------------------
 training/handouts/anna-ingemarsson.md     | 42 -----------------------
 training/handouts/anna-simon.md           | 42 -----------------------
 training/handouts/craig-langley-tester.md | 42 -----------------------
 training/handouts/cristofer-dreimanis.md  | 42 -----------------------
 training/handouts/daniel-tufvander.md     | 42 -----------------------
 training/handouts/fredric-gustafsson.md   | 42 -----------------------
 training/handouts/gustav-dahlbeck.md      | 42 -----------------------
 training/handouts/james-colebeck.md       | 42 -----------------------
 training/handouts/jenny-svennefelt.md     | 42 -----------------------
 training/handouts/joel-sanmoogan.md       | 42 -----------------------
 training/handouts/jonathan-wirseen.md     | 42 -----------------------
 training/handouts/josefin-gelin.md        | 42 -----------------------
 training/handouts/jost-werdenhoff.md      | 42 -----------------------
 training/handouts/kate-payne.md           | 42 -----------------------
 training/handouts/markus-palsson.md       | 42 -----------------------
 training/handouts/matthew-blanshard.md    | 42 -----------------------
 training/handouts/matthew-buckland.md     | 42 -----------------------
 training/handouts/michael.md              | 42 -----------------------
 training/handouts/mikael-svensson.md      | 42 -----------------------
 training/handouts/nabeel-moosa.md         | 42 -----------------------
 training/handouts/olof-nordberg.md        | 42 -----------------------
 training/handouts/pascal-ambrosius.md     | 42 -----------------------
 training/handouts/patrik-sommar.md        | 42 -----------------------
 training/handouts/samantha-short.md       | 42 -----------------------
 training/handouts/sennai-mebrahtu.md      | 42 -----------------------
 training/handouts/siri-uhrnell.md         | 42 -----------------------
 training/handouts/tim-love.md             | 42 -----------------------
 training/handouts/tuva-thornberg.md       | 42 -----------------------
 training/handouts/william-folkesson.md    | 42 -----------------------
 33 files changed, 1 insertion(+), 1344 deletions(-)
 delete mode 100644 training/handouts/alek-legosteva.md
 delete mode 100644 training/handouts/andrea-backstrom.md
 delete mode 100644 training/handouts/anna-edholm.md
 delete mode 100644 training/handouts/anna-ingemarsson.md
 delete mode 100644 training/handouts/anna-simon.md
 delete mode 100644 training/handouts/craig-langley-tester.md
 delete mode 100644 training/handouts/cristofer-dreimanis.md
 delete mode 100644 training/handouts/daniel-tufvander.md
 delete mode 100644 training/handouts/fredric-gustafsson.md
 delete mode 100644 training/handouts/gustav-dahlbeck.md
 delete mode 100644 training/handouts/james-colebeck.md
 delete mode 100644 training/handouts/jenny-svennefelt.md
 delete mode 100644 training/handouts/joel-sanmoogan.md
 delete mode 100644 training/handouts/jonathan-wirseen.md
 delete mode 100644 training/handouts/josefin-gelin.md
 delete mode 100644 training/handouts/jost-werdenhoff.md
 delete mode 100644 training/handouts/kate-payne.md
 delete mode 100644 training/handouts/markus-palsson.md
 delete mode 100644 training/handouts/matthew-blanshard.md
 delete mode 100644 training/handouts/matthew-buckland.md
 delete mode 100644 training/handouts/michael.md
 delete mode 100644 training/handouts/mikael-svensson.md
 delete mode 100644 training/handouts/nabeel-moosa.md
 delete mode 100644 training/handouts/olof-nordberg.md
 delete mode 100644 training/handouts/pascal-ambrosius.md
 delete mode 100644 training/handouts/patrik-sommar.md
 delete mode 100644 training/handouts/samantha-short.md
 delete mode 100644 training/handouts/sennai-mebrahtu.md
 delete mode 100644 training/handouts/siri-uhrnell.md
 delete mode 100644 training/handouts/tim-love.md
 delete mode 100644 training/handouts/tuva-thornberg.md
 delete mode 100644 training/handouts/william-folkesson.md

diff --git a/training/.gitignore b/training/.gitignore
index ccec581905d..fe26113f74a 100644
--- a/training/.gitignore
+++ b/training/.gitignore
@@ -1,3 +1,4 @@
+handouts/
 bootstrap/attendees.csv
 bootstrap/emails.txt
 terraform/.terraform/
diff --git a/training/handouts/alek-legosteva.md b/training/handouts/alek-legosteva.md
deleted file mode 100644
index 8679e1b983e..00000000000
--- a/training/handouts/alek-legosteva.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — alek-legosteva
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://alek-legosteva.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/alek-legosteva`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/alek-legosteva/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at alek-legosteva.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at alek-legosteva.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/alek-legosteva`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/alek-legosteva
-git checkout -b attendee/alek-legosteva-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/alek-legosteva-fix
-gh pr create --base attendee/alek-legosteva --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://alek-legosteva.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/andrea-backstrom.md b/training/handouts/andrea-backstrom.md
deleted file mode 100644
index f9e189304a1..00000000000
--- a/training/handouts/andrea-backstrom.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — andrea-backstrom
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://andrea-backstrom.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/andrea-backstrom`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/andrea-backstrom/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at andrea-backstrom.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at andrea-backstrom.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/andrea-backstrom`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/andrea-backstrom
-git checkout -b attendee/andrea-backstrom-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/andrea-backstrom-fix
-gh pr create --base attendee/andrea-backstrom --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://andrea-backstrom.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/anna-edholm.md b/training/handouts/anna-edholm.md
deleted file mode 100644
index 4ffd81ca8a0..00000000000
--- a/training/handouts/anna-edholm.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — anna-edholm
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://anna-edholm.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/anna-edholm`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/anna-edholm/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at anna-edholm.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at anna-edholm.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/anna-edholm`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/anna-edholm
-git checkout -b attendee/anna-edholm-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/anna-edholm-fix
-gh pr create --base attendee/anna-edholm --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://anna-edholm.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/anna-ingemarsson.md b/training/handouts/anna-ingemarsson.md
deleted file mode 100644
index 24975dcec34..00000000000
--- a/training/handouts/anna-ingemarsson.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — anna-ingemarsson
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://anna-ingemarsson.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/anna-ingemarsson`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/anna-ingemarsson/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at anna-ingemarsson.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at anna-ingemarsson.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/anna-ingemarsson`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/anna-ingemarsson
-git checkout -b attendee/anna-ingemarsson-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/anna-ingemarsson-fix
-gh pr create --base attendee/anna-ingemarsson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://anna-ingemarsson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/anna-simon.md b/training/handouts/anna-simon.md
deleted file mode 100644
index 7b79210af62..00000000000
--- a/training/handouts/anna-simon.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — anna-simon
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://anna-simon.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/anna-simon`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/anna-simon/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at anna-simon.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at anna-simon.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/anna-simon`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/anna-simon
-git checkout -b attendee/anna-simon-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/anna-simon-fix
-gh pr create --base attendee/anna-simon --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://anna-simon.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/craig-langley-tester.md b/training/handouts/craig-langley-tester.md
deleted file mode 100644
index 4dad15a38fd..00000000000
--- a/training/handouts/craig-langley-tester.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — craig-langley-tester
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://craig-langley-tester.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/craig-langley-tester`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/craig-langley-tester/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at craig-langley-tester.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at craig-langley-tester.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/craig-langley-tester`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/craig-langley-tester
-git checkout -b attendee/craig-langley-tester-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/craig-langley-tester-fix
-gh pr create --base attendee/craig-langley-tester --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://craig-langley-tester.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/cristofer-dreimanis.md b/training/handouts/cristofer-dreimanis.md
deleted file mode 100644
index e6676bb8122..00000000000
--- a/training/handouts/cristofer-dreimanis.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — cristofer-dreimanis
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://cristofer-dreimanis.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/cristofer-dreimanis`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/cristofer-dreimanis/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at cristofer-dreimanis.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at cristofer-dreimanis.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/cristofer-dreimanis`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/cristofer-dreimanis
-git checkout -b attendee/cristofer-dreimanis-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/cristofer-dreimanis-fix
-gh pr create --base attendee/cristofer-dreimanis --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://cristofer-dreimanis.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/daniel-tufvander.md b/training/handouts/daniel-tufvander.md
deleted file mode 100644
index 1c8266a58a5..00000000000
--- a/training/handouts/daniel-tufvander.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — daniel-tufvander
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://daniel-tufvander.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/daniel-tufvander`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/daniel-tufvander/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at daniel-tufvander.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at daniel-tufvander.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/daniel-tufvander`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/daniel-tufvander
-git checkout -b attendee/daniel-tufvander-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/daniel-tufvander-fix
-gh pr create --base attendee/daniel-tufvander --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://daniel-tufvander.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/fredric-gustafsson.md b/training/handouts/fredric-gustafsson.md
deleted file mode 100644
index b0508425993..00000000000
--- a/training/handouts/fredric-gustafsson.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — fredric-gustafsson
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://fredric-gustafsson.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/fredric-gustafsson`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/fredric-gustafsson/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at fredric-gustafsson.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at fredric-gustafsson.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/fredric-gustafsson`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/fredric-gustafsson
-git checkout -b attendee/fredric-gustafsson-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/fredric-gustafsson-fix
-gh pr create --base attendee/fredric-gustafsson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://fredric-gustafsson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/gustav-dahlbeck.md b/training/handouts/gustav-dahlbeck.md
deleted file mode 100644
index 0301c0fb382..00000000000
--- a/training/handouts/gustav-dahlbeck.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — gustav-dahlbeck
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://gustav-dahlbeck.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/gustav-dahlbeck`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/gustav-dahlbeck/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at gustav-dahlbeck.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at gustav-dahlbeck.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/gustav-dahlbeck`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/gustav-dahlbeck
-git checkout -b attendee/gustav-dahlbeck-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/gustav-dahlbeck-fix
-gh pr create --base attendee/gustav-dahlbeck --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://gustav-dahlbeck.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/james-colebeck.md b/training/handouts/james-colebeck.md
deleted file mode 100644
index c76a115d1e4..00000000000
--- a/training/handouts/james-colebeck.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — james-colebeck
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://james-colebeck.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/james-colebeck`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/james-colebeck/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at james-colebeck.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at james-colebeck.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/james-colebeck`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/james-colebeck
-git checkout -b attendee/james-colebeck-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/james-colebeck-fix
-gh pr create --base attendee/james-colebeck --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://james-colebeck.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/jenny-svennefelt.md b/training/handouts/jenny-svennefelt.md
deleted file mode 100644
index ab1a8838fa3..00000000000
--- a/training/handouts/jenny-svennefelt.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — jenny-svennefelt
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://jenny-svennefelt.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/jenny-svennefelt`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/jenny-svennefelt/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at jenny-svennefelt.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at jenny-svennefelt.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/jenny-svennefelt`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/jenny-svennefelt
-git checkout -b attendee/jenny-svennefelt-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/jenny-svennefelt-fix
-gh pr create --base attendee/jenny-svennefelt --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://jenny-svennefelt.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/joel-sanmoogan.md b/training/handouts/joel-sanmoogan.md
deleted file mode 100644
index 68f408bba71..00000000000
--- a/training/handouts/joel-sanmoogan.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — joel-sanmoogan
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://joel-sanmoogan.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/joel-sanmoogan`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/joel-sanmoogan/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at joel-sanmoogan.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at joel-sanmoogan.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/joel-sanmoogan`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/joel-sanmoogan
-git checkout -b attendee/joel-sanmoogan-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/joel-sanmoogan-fix
-gh pr create --base attendee/joel-sanmoogan --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://joel-sanmoogan.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/jonathan-wirseen.md b/training/handouts/jonathan-wirseen.md
deleted file mode 100644
index 776d429eb15..00000000000
--- a/training/handouts/jonathan-wirseen.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — jonathan-wirseen
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://jonathan-wirseen.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/jonathan-wirseen`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/jonathan-wirseen/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at jonathan-wirseen.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at jonathan-wirseen.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/jonathan-wirseen`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/jonathan-wirseen
-git checkout -b attendee/jonathan-wirseen-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/jonathan-wirseen-fix
-gh pr create --base attendee/jonathan-wirseen --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://jonathan-wirseen.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/josefin-gelin.md b/training/handouts/josefin-gelin.md
deleted file mode 100644
index 0ffeb623121..00000000000
--- a/training/handouts/josefin-gelin.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — josefin-gelin
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://josefin-gelin.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/josefin-gelin`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/josefin-gelin/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at josefin-gelin.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at josefin-gelin.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/josefin-gelin`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/josefin-gelin
-git checkout -b attendee/josefin-gelin-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/josefin-gelin-fix
-gh pr create --base attendee/josefin-gelin --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://josefin-gelin.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/jost-werdenhoff.md b/training/handouts/jost-werdenhoff.md
deleted file mode 100644
index fa4deb0e0d3..00000000000
--- a/training/handouts/jost-werdenhoff.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — jost-werdenhoff
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://jost-werdenhoff.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/jost-werdenhoff`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/jost-werdenhoff/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at jost-werdenhoff.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at jost-werdenhoff.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/jost-werdenhoff`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/jost-werdenhoff
-git checkout -b attendee/jost-werdenhoff-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/jost-werdenhoff-fix
-gh pr create --base attendee/jost-werdenhoff --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://jost-werdenhoff.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/kate-payne.md b/training/handouts/kate-payne.md
deleted file mode 100644
index 0c24f82a019..00000000000
--- a/training/handouts/kate-payne.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — kate-payne
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://kate-payne.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/kate-payne`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/kate-payne/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at kate-payne.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at kate-payne.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/kate-payne`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/kate-payne
-git checkout -b attendee/kate-payne-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/kate-payne-fix
-gh pr create --base attendee/kate-payne --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://kate-payne.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/markus-palsson.md b/training/handouts/markus-palsson.md
deleted file mode 100644
index 0bd7398c048..00000000000
--- a/training/handouts/markus-palsson.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — markus-palsson
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://markus-palsson.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/markus-palsson`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/markus-palsson/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at markus-palsson.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at markus-palsson.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/markus-palsson`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/markus-palsson
-git checkout -b attendee/markus-palsson-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/markus-palsson-fix
-gh pr create --base attendee/markus-palsson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://markus-palsson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/matthew-blanshard.md b/training/handouts/matthew-blanshard.md
deleted file mode 100644
index 0373dcd2b06..00000000000
--- a/training/handouts/matthew-blanshard.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — matthew-blanshard
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://matthew-blanshard.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/matthew-blanshard`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/matthew-blanshard/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at matthew-blanshard.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at matthew-blanshard.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/matthew-blanshard`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/matthew-blanshard
-git checkout -b attendee/matthew-blanshard-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/matthew-blanshard-fix
-gh pr create --base attendee/matthew-blanshard --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://matthew-blanshard.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/matthew-buckland.md b/training/handouts/matthew-buckland.md
deleted file mode 100644
index 8cb111ce231..00000000000
--- a/training/handouts/matthew-buckland.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — matthew-buckland
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://matthew-buckland.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/matthew-buckland`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/matthew-buckland/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at matthew-buckland.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at matthew-buckland.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/matthew-buckland`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/matthew-buckland
-git checkout -b attendee/matthew-buckland-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/matthew-buckland-fix
-gh pr create --base attendee/matthew-buckland --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://matthew-buckland.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/michael.md b/training/handouts/michael.md
deleted file mode 100644
index 731c42db054..00000000000
--- a/training/handouts/michael.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — michael
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://michael.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/michael`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/michael/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at michael.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at michael.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/michael`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/michael
-git checkout -b attendee/michael-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/michael-fix
-gh pr create --base attendee/michael --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://michael.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/mikael-svensson.md b/training/handouts/mikael-svensson.md
deleted file mode 100644
index fdce693a72b..00000000000
--- a/training/handouts/mikael-svensson.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — mikael-svensson
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://mikael-svensson.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/mikael-svensson`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/mikael-svensson/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at mikael-svensson.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at mikael-svensson.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/mikael-svensson`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/mikael-svensson
-git checkout -b attendee/mikael-svensson-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/mikael-svensson-fix
-gh pr create --base attendee/mikael-svensson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://mikael-svensson.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/nabeel-moosa.md b/training/handouts/nabeel-moosa.md
deleted file mode 100644
index f508a0c6f18..00000000000
--- a/training/handouts/nabeel-moosa.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — nabeel-moosa
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://nabeel-moosa.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/nabeel-moosa`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/nabeel-moosa/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at nabeel-moosa.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at nabeel-moosa.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/nabeel-moosa`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/nabeel-moosa
-git checkout -b attendee/nabeel-moosa-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/nabeel-moosa-fix
-gh pr create --base attendee/nabeel-moosa --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://nabeel-moosa.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/olof-nordberg.md b/training/handouts/olof-nordberg.md
deleted file mode 100644
index 89d5a066788..00000000000
--- a/training/handouts/olof-nordberg.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — olof-nordberg
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://olof-nordberg.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/olof-nordberg`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/olof-nordberg/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at olof-nordberg.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at olof-nordberg.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/olof-nordberg`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/olof-nordberg
-git checkout -b attendee/olof-nordberg-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/olof-nordberg-fix
-gh pr create --base attendee/olof-nordberg --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://olof-nordberg.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/pascal-ambrosius.md b/training/handouts/pascal-ambrosius.md
deleted file mode 100644
index cdd7a144378..00000000000
--- a/training/handouts/pascal-ambrosius.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — pascal-ambrosius
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://pascal-ambrosius.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/pascal-ambrosius`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/pascal-ambrosius/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at pascal-ambrosius.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at pascal-ambrosius.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/pascal-ambrosius`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/pascal-ambrosius
-git checkout -b attendee/pascal-ambrosius-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/pascal-ambrosius-fix
-gh pr create --base attendee/pascal-ambrosius --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://pascal-ambrosius.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/patrik-sommar.md b/training/handouts/patrik-sommar.md
deleted file mode 100644
index 4a0dc167e82..00000000000
--- a/training/handouts/patrik-sommar.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — patrik-sommar
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://patrik-sommar.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/patrik-sommar`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/patrik-sommar/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at patrik-sommar.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at patrik-sommar.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/patrik-sommar`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/patrik-sommar
-git checkout -b attendee/patrik-sommar-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/patrik-sommar-fix
-gh pr create --base attendee/patrik-sommar --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://patrik-sommar.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/samantha-short.md b/training/handouts/samantha-short.md
deleted file mode 100644
index b2c6e19fc27..00000000000
--- a/training/handouts/samantha-short.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — samantha-short
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://samantha-short.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/samantha-short`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/samantha-short/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at samantha-short.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at samantha-short.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/samantha-short`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/samantha-short
-git checkout -b attendee/samantha-short-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/samantha-short-fix
-gh pr create --base attendee/samantha-short --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://samantha-short.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/sennai-mebrahtu.md b/training/handouts/sennai-mebrahtu.md
deleted file mode 100644
index 23a9a1eb985..00000000000
--- a/training/handouts/sennai-mebrahtu.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — sennai-mebrahtu
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://sennai-mebrahtu.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/sennai-mebrahtu`                                     |
-| Your bug ID   | `search-misses-descriptions` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/sennai-mebrahtu/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at sennai-mebrahtu.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at sennai-mebrahtu.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/sennai-mebrahtu`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/sennai-mebrahtu
-git checkout -b attendee/sennai-mebrahtu-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/sennai-mebrahtu-fix
-gh pr create --base attendee/sennai-mebrahtu --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://sennai-mebrahtu.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/siri-uhrnell.md b/training/handouts/siri-uhrnell.md
deleted file mode 100644
index 2338ac22f73..00000000000
--- a/training/handouts/siri-uhrnell.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — siri-uhrnell
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://siri-uhrnell.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/siri-uhrnell`                                     |
-| Your bug ID   | `visa-rejected` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/siri-uhrnell/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at siri-uhrnell.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at siri-uhrnell.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/siri-uhrnell`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/siri-uhrnell
-git checkout -b attendee/siri-uhrnell-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/siri-uhrnell-fix
-gh pr create --base attendee/siri-uhrnell --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://siri-uhrnell.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/tim-love.md b/training/handouts/tim-love.md
deleted file mode 100644
index 9138bb17593..00000000000
--- a/training/handouts/tim-love.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — tim-love
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://tim-love.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/tim-love`                                     |
-| Your bug ID   | `currency-converter-mismatch` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/tim-love/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at tim-love.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at tim-love.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/tim-love`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/tim-love
-git checkout -b attendee/tim-love-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/tim-love-fix
-gh pr create --base attendee/tim-love --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://tim-love.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/tuva-thornberg.md b/training/handouts/tuva-thornberg.md
deleted file mode 100644
index 75ee8617fb8..00000000000
--- a/training/handouts/tuva-thornberg.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — tuva-thornberg
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://tuva-thornberg.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/tuva-thornberg`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/tuva-thornberg/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at tuva-thornberg.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at tuva-thornberg.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/tuva-thornberg`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/tuva-thornberg
-git checkout -b attendee/tuva-thornberg-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/tuva-thornberg-fix
-gh pr create --base attendee/tuva-thornberg --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://tuva-thornberg.training.gcp.re-cinq.com once it's green.
diff --git a/training/handouts/william-folkesson.md b/training/handouts/william-folkesson.md
deleted file mode 100644
index 5bf0cc6b427..00000000000
--- a/training/handouts/william-folkesson.md
+++ /dev/null
@@ -1,42 +0,0 @@
-# Training handout — william-folkesson
-
-## Your environment
-
-| field         | value                                           |
-|---------------|-------------------------------------------------|
-| URL           | https://william-folkesson.training.gcp.re-cinq.com                                   |
-| Repo          | https://github.com/re-cinq/microservices-demo   |
-| Your branch   | `attendee/william-folkesson`                                     |
-| Your bug ID   | `duplicate-recommendations` (don't share — see what your neighbours got) |
-
-## What we want from you
-
-A customer just opened a ticket about your URL. The ticket is in
-[`BUG_REPORT.md`](https://github.com/re-cinq/microservices-demo/blob/attendee/william-folkesson/BUG_REPORT.md)
-on your branch. Your job today:
-
-1. Reproduce the issue at william-folkesson.training.gcp.re-cinq.com
-2. Use Claude Code to triage it: find the suspected file, understand
-   what's wrong, and write an engineer-ready ticket
-   (`ENGINEERING_TICKET.md` on your branch) with:
-   - exact steps to reproduce
-   - suspected service + file
-   - severity rationale
-3. Fix the bug locally, verify in browser at william-folkesson.training.gcp.re-cinq.com after deploying
-4. Open a PR from a fix branch into `attendee/william-folkesson`. Auto-merge will
-   redeploy your namespace. Verify the fix went live.
-
-## Local workflow
-
-```bash
-git clone https://github.com/re-cinq/microservices-demo
-cd microservices-demo
-git checkout attendee/william-folkesson
-git checkout -b attendee/william-folkesson-fix
-# ... use Claude Code to triage, write ticket, fix ...
-git push -u origin attendee/william-folkesson-fix
-gh pr create --base attendee/william-folkesson --title "fix: <one line>" --body "Closes ticket. See ENGINEERING_TICKET.md."
-```
-
-The PR auto-merges on green CI. Watch the GitHub Actions run for the
-deploy. Re-test at https://william-folkesson.training.gcp.re-cinq.com once it's green.

From 48af4e56805b021004ed1816b4fc23b2ffb609fb Mon Sep 17 00:00:00 2001
From: muemich <michaelmuellerrw@gmail.com>
Date: Fri, 8 May 2026 10:39:56 +0200
Subject: [PATCH 07/10] training: --no-bug flag for Module 5 (spec-driven)
 cohorts

provision.sh now accepts --no-bug to skip the bug-seed step:
- creates the attendee branch as an empty commit on top of main
- writes a Module-5-shaped handout (URL + branch, points at SpecKit
  workflow instead of BUG_REPORT.md)

Module 3 Ex 3 (bug triage) keeps existing default behaviour.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 training/README.md              |  7 +++
 training/bootstrap/provision.sh | 85 +++++++++++++++++++++++++++------
 2 files changed, 77 insertions(+), 15 deletions(-)

diff --git a/training/README.md b/training/README.md
index 49c0695b972..bc5190eb9f4 100644
--- a/training/README.md
+++ b/training/README.md
@@ -120,12 +120,19 @@ bob,visa-rejected
 Run:
 
 ```bash
+# Module 3 Ex 3 (bug-triage): seeds a bug from training/bugs/ on each branch
 training/bootstrap/provision.sh training/bootstrap/attendees.csv
+
+# Module 5 (spec-driven dev): no bug seeded, branches start empty for SpecKit
+training/bootstrap/provision.sh --no-bug training/bootstrap/attendees.csv
 ```
 
 This creates each namespace + Helm release + Ingress + git branch
 + handout under `training/handouts/<name>.md`. Idempotent.
 
+In `--no-bug` mode the CSV may have either `name` or `name,bug`; the bug
+column is ignored. Handout content is tailored to the mode.
+
 Print the handouts and hand them out. Attendees follow the instructions.
 
 ## Teardown after the training
diff --git a/training/bootstrap/provision.sh b/training/bootstrap/provision.sh
index d5d6506a016..ff9446fa44b 100755
--- a/training/bootstrap/provision.sh
+++ b/training/bootstrap/provision.sh
@@ -1,10 +1,14 @@
 #!/usr/bin/env bash
 # Provision a training cohort.
 #
-#   ./provision.sh attendees.csv
+#   ./provision.sh attendees.csv              # Module 3 Ex 3 (seed bug per attendee)
+#   ./provision.sh --no-bug attendees.csv     # Module 5 (cohort branches w/o bug seed)
 #
 # Idempotent. Re-runs are safe; existing namespaces, releases, and
-# branches are upgraded in place. CSV format: name,bug_id
+# branches are upgraded in place.
+#
+# CSV format with bug:    name,bug_id
+# CSV format --no-bug:    name              (the bug column, if present, is ignored)
 #
 # Prerequisites:
 #   - kubectl pointing at the training cluster
@@ -23,8 +27,14 @@ CLUSTER_ISSUER="letsencrypt-prod"
 INGRESS_CLASS="nginx-ingress"
 BASE_BRANCH="main"
 
+NO_BUG=0
+if [[ "${1:-}" == "--no-bug" ]]; then
+  NO_BUG=1
+  shift
+fi
+
 if [[ $# -ne 1 ]]; then
-  echo "usage: $0 <attendees.csv>" >&2
+  echo "usage: $0 [--no-bug] <attendees.csv>" >&2
   exit 2
 fi
 CSV="$1"
@@ -39,12 +49,15 @@ log() { printf '\033[1;34m[bootstrap]\033[0m %s\n' "$*"; }
 git -C "$REPO_ROOT" checkout main --quiet 2>/dev/null || true
 
 # Validate every row first - fail before we mutate anything
-log "validating $CSV"
+log "validating $CSV (no-bug mode: $NO_BUG)"
 while IFS=, read -r name bug; do
   [[ "$name" == "name" ]] && continue
-  [[ -z "$name" || -z "$bug" ]] && { echo "empty name or bug in row: $name,$bug" >&2; exit 1; }
-  [[ -d "$TRAINING_DIR/bugs/$bug" ]] || { echo "unknown bug id: $bug (no such dir under training/bugs/)" >&2; exit 1; }
+  [[ -z "$name" ]] && { echo "empty name in row: $name,$bug" >&2; exit 1; }
   [[ "$name" =~ ^[a-z][a-z0-9-]{1,30}$ ]] || { echo "invalid attendee name (must be lowercase, alphanumeric+dash, <=31 chars): $name" >&2; exit 1; }
+  if [[ "$NO_BUG" -eq 0 ]]; then
+    [[ -z "$bug" ]] && { echo "empty bug in row: $name,$bug (use --no-bug for spec-only cohorts)" >&2; exit 1; }
+    [[ -d "$TRAINING_DIR/bugs/$bug" ]] || { echo "unknown bug id: $bug (no such dir under training/bugs/)" >&2; exit 1; }
+  fi
 done < "$CSV"
 
 # Process each attendee
@@ -175,12 +188,12 @@ spec:
                   number: 80
 EOF
 
-  # 4. Branch + bug injection
+  # 4. Branch + (optional) bug injection
   git fetch origin "$BASE_BRANCH" >/dev/null
   if git ls-remote --exit-code --heads origin "$branch" >/dev/null 2>&1; then
     log "branch $branch already exists on origin, skipping"
   else
-    log "creating branch $branch from origin/$BASE_BRANCH"
+    log "creating branch $branch from origin/$BASE_BRANCH (no-bug=$NO_BUG)"
     # Clean up any leftover state from prior runs.
     rm -rf "/tmp/training-$name"
     git worktree prune
@@ -190,19 +203,29 @@ EOF
       # -B overwrites a local branch of the same name (left over from a previous
       # cohort even after the remote branch was teardown'd).
       git checkout -B "$branch"
-      git apply "$TRAINING_DIR/bugs/$bug/PATCH.diff"
-      cp "$TRAINING_DIR/bugs/$bug/BUG_REPORT.md" ./BUG_REPORT.md
-      git add -A
-      GIT_AUTHOR_NAME="training-bot" GIT_AUTHOR_EMAIL="bot@training.local" \
-      GIT_COMMITTER_NAME="training-bot" GIT_COMMITTER_EMAIL="bot@training.local" \
-        git commit --quiet -m "training: seed bug ($bug)" -m "Customer ticket in BUG_REPORT.md."
+      if [[ "$NO_BUG" -eq 0 ]]; then
+        git apply "$TRAINING_DIR/bugs/$bug/PATCH.diff"
+        cp "$TRAINING_DIR/bugs/$bug/BUG_REPORT.md" ./BUG_REPORT.md
+        git add -A
+        GIT_AUTHOR_NAME="training-bot" GIT_AUTHOR_EMAIL="bot@training.local" \
+        GIT_COMMITTER_NAME="training-bot" GIT_COMMITTER_EMAIL="bot@training.local" \
+          git commit --quiet -m "training: seed bug ($bug)" -m "Customer ticket in BUG_REPORT.md."
+      else
+        # No-bug mode: empty commit so the branch has at least one entry on top of
+        # main (otherwise the GitHub Actions detect-changed-services step has no
+        # diff to inspect on first push, which is fine but slightly cleaner this way).
+        GIT_AUTHOR_NAME="training-bot" GIT_AUTHOR_EMAIL="bot@training.local" \
+        GIT_COMMITTER_NAME="training-bot" GIT_COMMITTER_EMAIL="bot@training.local" \
+          git commit --quiet --allow-empty -m "training: cohort branch for $name"
+      fi
       git push --quiet -u origin "$branch"
     )
     git worktree remove --force /tmp/training-$name
   fi
 
   # 5. Handout
-  cat > "$TRAINING_DIR/handouts/$name.md" <<EOF
+  if [[ "$NO_BUG" -eq 0 ]]; then
+    cat > "$TRAINING_DIR/handouts/$name.md" <<EOF
 # Training handout — $name
 
 ## Your environment
@@ -246,6 +269,38 @@ gh pr create --base $branch --title "fix: <one line>" --body "Closes ticket. See
 The PR auto-merges on green CI. Watch the GitHub Actions run for the
 deploy. Re-test at https://$host once it's green.
 EOF
+  else
+    cat > "$TRAINING_DIR/handouts/$name.md" <<EOF
+# Training handout — $name
+
+## Your environment
+
+| field        | value                                           |
+|--------------|-------------------------------------------------|
+| URL          | https://$host                                   |
+| Repo         | https://github.com/re-cinq/microservices-demo   |
+| Your branch  | \`$branch\`                                     |
+
+## What we want from you
+
+Follow the lab instructions in **Module 5 — Spec-driven development** to
+plan and ship a search feature on Online Boutique. Your branch is empty
+(no bug seeded); SpecKit's \`/speckit.implement\` will write the code.
+
+Local workflow:
+
+\`\`\`bash
+git clone https://github.com/re-cinq/microservices-demo
+cd microservices-demo
+git checkout $branch
+# follow the Module 5 Ex 2 + Ex 3 lab steps from there
+\`\`\`
+
+When SpecKit pushes a fix-branch and you open a PR back into
+\`$branch\`, the GitHub Actions \`deploy-attendee\` workflow rebuilds
+the changed services and rolls them out at https://$host.
+EOF
+  fi
 
   log "done with $name"
 done < "$CSV"

From b951b7ee6a3f5b1224974644ddbaa3b4f4e91030 Mon Sep 17 00:00:00 2001
From: training-bot <bot@training.local>
Date: Mon, 11 May 2026 12:36:12 +0200
Subject: [PATCH 08/10] training: cohort branch for cruz-moreno


From 1e8cf9056fdfa2662c4a6c1ea344f450d86aa863 Mon Sep 17 00:00:00 2001
From: training-bot <bot@training.local>
Date: Mon, 11 May 2026 14:50:04 +0200
Subject: [PATCH 09/10] training: bundle SpecKit setup (in speckit-setup/)

---
 .../.claude/commands/speckit.constitution.md  | 15 +++
 .../.claude/commands/speckit.implement.md     | 22 +++++
 .../.claude/commands/speckit.plan.md          | 19 ++++
 .../.claude/commands/speckit.specify.md       | 23 +++++
 .../.claude/commands/speckit.tasks.md         | 19 ++++
 speckit-setup/.specify/memory/.gitkeep        |  0
 speckit-setup/README.md                       | 57 +++++++++++
 speckit-setup/install-speckit.ps1             | 95 +++++++++++++++++++
 8 files changed, 250 insertions(+)
 create mode 100755 speckit-setup/.claude/commands/speckit.constitution.md
 create mode 100755 speckit-setup/.claude/commands/speckit.implement.md
 create mode 100755 speckit-setup/.claude/commands/speckit.plan.md
 create mode 100755 speckit-setup/.claude/commands/speckit.specify.md
 create mode 100755 speckit-setup/.claude/commands/speckit.tasks.md
 create mode 100755 speckit-setup/.specify/memory/.gitkeep
 create mode 100755 speckit-setup/README.md
 create mode 100755 speckit-setup/install-speckit.ps1

diff --git a/speckit-setup/.claude/commands/speckit.constitution.md b/speckit-setup/.claude/commands/speckit.constitution.md
new file mode 100755
index 00000000000..920337003e9
--- /dev/null
+++ b/speckit-setup/.claude/commands/speckit.constitution.md
@@ -0,0 +1,15 @@
+---
+description: Create or update the project constitution.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+## Outline
+
+1. Create or update the project constitution and store it in `.specify/memory/constitution.md`.
+   - Project name, guiding principles, non-negotiable rules
+   - Derive from user input and existing repo context (README, docs)
diff --git a/speckit-setup/.claude/commands/speckit.implement.md b/speckit-setup/.claude/commands/speckit.implement.md
new file mode 100755
index 00000000000..fc68a1f8b17
--- /dev/null
+++ b/speckit-setup/.claude/commands/speckit.implement.md
@@ -0,0 +1,22 @@
+---
+description: Execute the implementation plan by processing all tasks in tasks.md.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+## Outline
+
+1. Read `.specify/feature.json` to get the feature directory path.
+
+2. **Load context**: `.specify/memory/constitution.md` and `<feature_directory>/spec.md` and `<feature_directory>/plan.md` and `<feature_directory>/tasks.md`.
+
+3. **Execute tasks** in order:
+   - Complete each task before moving to the next
+   - Mark completed tasks by changing `- [ ]` to `- [x]` in `<feature_directory>/tasks.md`
+   - Halt on failure and report the issue
+
+4. **Validate**: Verify all tasks are completed and the implementation matches the spec.
diff --git a/speckit-setup/.claude/commands/speckit.plan.md b/speckit-setup/.claude/commands/speckit.plan.md
new file mode 100755
index 00000000000..9fbbe4c3713
--- /dev/null
+++ b/speckit-setup/.claude/commands/speckit.plan.md
@@ -0,0 +1,19 @@
+---
+description: Create a plan and store it in plan.md.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+## Outline
+
+1. Read `.specify/feature.json` to get the feature directory path.
+
+2. **Load context**: `.specify/memory/constitution.md` and `<feature_directory>/spec.md`.
+
+3. Create an implementation plan and store it in `<feature_directory>/plan.md`.
+   - Technical context: tech stack, dependencies, project structure
+   - Design decisions, architecture, file structure
diff --git a/speckit-setup/.claude/commands/speckit.specify.md b/speckit-setup/.claude/commands/speckit.specify.md
new file mode 100755
index 00000000000..c15353557aa
--- /dev/null
+++ b/speckit-setup/.claude/commands/speckit.specify.md
@@ -0,0 +1,23 @@
+---
+description: Create a specification and store it in spec.md.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+## Outline
+
+1. **Ask the user** for the feature directory path (e.g., `specs/my-feature`). Do not proceed until provided.
+
+2. Create the directory and write `.specify/feature.json`:
+   ```json
+   { "feature_directory": "<feature_directory>" }
+   ```
+
+3. Create a specification from the user input and store it in `<feature_directory>/spec.md`.
+   - Overview, functional requirements, user scenarios, success criteria
+   - Every requirement must be testable
+   - Make informed defaults for unspecified details
diff --git a/speckit-setup/.claude/commands/speckit.tasks.md b/speckit-setup/.claude/commands/speckit.tasks.md
new file mode 100755
index 00000000000..724a7b84007
--- /dev/null
+++ b/speckit-setup/.claude/commands/speckit.tasks.md
@@ -0,0 +1,19 @@
+---
+description: Create the tasks needed for implementation and store them in tasks.md.
+---
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+## Outline
+
+1. Read `.specify/feature.json` to get the feature directory path.
+
+2. **Load context**: `.specify/memory/constitution.md` and `<feature_directory>/spec.md` and `<feature_directory>/plan.md`.
+
+3. Create dependency-ordered implementation tasks and store them in `<feature_directory>/tasks.md`.
+   - Every task uses checklist format: `- [ ] [TaskID] Description with file path`
+   - Organized by phase: setup, foundational, user stories in priority order, polish
diff --git a/speckit-setup/.specify/memory/.gitkeep b/speckit-setup/.specify/memory/.gitkeep
new file mode 100755
index 00000000000..e69de29bb2d
diff --git a/speckit-setup/README.md b/speckit-setup/README.md
new file mode 100755
index 00000000000..41c1bbff112
--- /dev/null
+++ b/speckit-setup/README.md
@@ -0,0 +1,57 @@
+# SpecKit – Setup Guide
+
+SpecKit gives you spec-driven development in Claude Code with no installation required.
+
+---
+
+## Setup (do this once)
+
+**Step 1 – Unzip**
+Extract `speckit-setup.zip` into your project root folder.
+You should see a `speckit-setup` folder appear next to your project files.
+
+**Step 2 – Open a terminal in your project root**
+```
+cd C:\your-project
+```
+
+**Step 3 – Run the script**
+```powershell
+.\speckit-setup\install-speckit.ps1
+```
+
+You should see all files confirmed with `OK`.
+
+**Step 4 – Open Claude Code in your project folder**
+Make sure Claude Code is opened at the project root (not inside `speckit-setup`).
+
+**Step 5 – Verify the commands are available**
+Open the Claude Code chat panel and type `/speckit` in the message input at the bottom — you should see all five commands appear in the autocomplete list. Do NOT type it in the VS Code search bar or file explorer.
+
+---
+
+## Manual Installation (if the script does not work)
+
+Copy these folders from inside `speckit-setup` into your **project root**:
+
+```
+your-project\
+├── .claude\
+│   └── commands\        <- copy this folder
+│       ├── speckit.constitution.md
+│       ├── speckit.specify.md
+│       ├── speckit.plan.md
+│       ├── speckit.tasks.md
+│       └── speckit.implement.md
+└── .specify\
+    └── memory\          <- create this empty folder
+```
+
+> **Note:** Folders starting with `.` may be hidden in File Explorer.
+> Enable "Show hidden items" under the View menu to see them.
+
+---
+
+## Questions?
+
+Contact your instructor.
diff --git a/speckit-setup/install-speckit.ps1 b/speckit-setup/install-speckit.ps1
new file mode 100755
index 00000000000..830bbf023df
--- /dev/null
+++ b/speckit-setup/install-speckit.ps1
@@ -0,0 +1,95 @@
+# install-speckit.ps1
+#
+# Sets up SpecKit lean commands for Claude Code.
+# Unzip speckit-setup.zip into your project root, then run this script.
+#
+# Usage:
+#   .\speckit-setup\install-speckit.ps1
+
+$scriptDir = Split-Path -Parent $MyInvocation.MyCommand.Path
+
+# Always install into the folder ABOVE this script (the project root)
+$root = Split-Path -Parent $scriptDir
+
+Write-Host ""
+Write-Host "SpecKit Setup" -ForegroundColor Cyan
+Write-Host "Installing into: $root"
+Write-Host ""
+
+$files = @(
+    "speckit.constitution.md",
+    "speckit.specify.md",
+    "speckit.plan.md",
+    "speckit.tasks.md",
+    "speckit.implement.md"
+)
+
+$sourceDir = Join-Path $scriptDir ".claude\commands"
+$targetDir = Join-Path $root ".claude\commands"
+
+New-Item -ItemType Directory -Force -Path $targetDir              | Out-Null
+New-Item -ItemType Directory -Force -Path "$root\.specify\memory" | Out-Null
+
+# Copy the 5 command files
+$ok = $true
+foreach ($file in $files) {
+    $src = Join-Path $sourceDir $file
+    $dst = Join-Path $targetDir $file
+    if (Test-Path $src) {
+        Copy-Item $src $dst -Force
+        Write-Host "  OK  $file" -ForegroundColor Green
+    } else {
+        Write-Host "  ERR $file not found in $sourceDir" -ForegroundColor Red
+        $ok = $false
+    }
+}
+
+# Add SpecKit section to CLAUDE.md if not already present
+$claudeMd = Join-Path $root "CLAUDE.md"
+$section = @"
+
+
+<!-- SPECKIT START -->
+## SpecKit Workflow
+
+Use these slash commands in Claude Code for spec-driven development:
+
+| Command | Creates | Description |
+|---------|---------|-------------|
+| ``/speckit.constitution`` | ``.specify/memory/constitution.md`` | Project principles and rules |
+| ``/speckit.specify`` | ``specs/<feature>/spec.md`` | Requirements and scenarios |
+| ``/speckit.plan`` | ``specs/<feature>/plan.md`` | Technical implementation plan |
+| ``/speckit.tasks`` | ``specs/<feature>/tasks.md`` | Ordered task checklist |
+| ``/speckit.implement`` | code | Executes all tasks in order |
+
+**Workflow:** constitution -> specify -> plan -> tasks -> implement
+<!-- SPECKIT END -->
+"@
+
+if (Test-Path $claudeMd) {
+    $content = Get-Content $claudeMd -Raw
+    if ($content -notmatch "SPECKIT START") {
+        Add-Content $claudeMd $section -Encoding UTF8
+        Write-Host "  OK  SpecKit section added to existing CLAUDE.md" -ForegroundColor Green
+    } else {
+        Write-Host "  --  CLAUDE.md already has SpecKit section" -ForegroundColor Yellow
+    }
+} else {
+    $section.TrimStart() | Set-Content $claudeMd -Encoding UTF8
+    Write-Host "  OK  CLAUDE.md created" -ForegroundColor Green
+}
+
+Write-Host ""
+if ($ok) {
+    Write-Host "Done! Open Claude Code in this folder and start with:" -ForegroundColor Green
+    Write-Host "  $root" -ForegroundColor White
+    Write-Host ""
+    Write-Host "  /speckit.constitution  <- start here" -ForegroundColor Cyan
+    Write-Host "  /speckit.specify"
+    Write-Host "  /speckit.plan"
+    Write-Host "  /speckit.tasks"
+    Write-Host "  /speckit.implement"
+} else {
+    Write-Host "Something went wrong - see manual installation in README.md" -ForegroundColor Red
+}
+Write-Host ""

From 8f32b0d2d6e35b39fae02e40e783594cdd092990 Mon Sep 17 00:00:00 2001
From: Cruz Moreno <cruz.moreno@odevo.com>
Date: Mon, 11 May 2026 09:24:51 -0500
Subject: [PATCH 10/10] feat(search): add product search by name (storefront +
 catalog)

Adds a storefront search box that calls ProductCatalogService.SearchProducts
over gRPC. The proto contract and a working (over-permissive) backend
implementation already existed; this change wires the frontend and
tightens the backend to match the spec exactly.

Backend (src/productcatalogservice)
- Tighten SearchProducts in product_catalog.go: trim whitespace,
  short-circuit empty queries to an empty result set, match against
  Product.Name only (drop the previous OR-clause that also matched on
  Product.Description). Spec FR-002 / FR-004 / FR-005 / FR-006.
- Expand TestSearchProducts in product_catalog_test.go into an 11-case
  table-driven test (case-insensitivity, whitespace trim, substring,
  empty / whitespace-only, no-match) plus a name-only regression: a new
  mock product whose description contains the search term must NOT be
  returned. Bump TestListProducts expected count to 5.

Frontend (src/frontend)
- New searchProducts client wrapper in rpc.go, mirroring the existing
  getProducts / getProduct pattern.
- New searchHandler in handlers.go: trim q, HTTP 302 -> / on empty query,
  call SearchProducts, convert prices to the user's currency, render
  the search template.
- Register GET/HEAD /search route in main.go next to the home route.
- Add a GET /search form to the shared header.html so the search box is
  reachable from every storefront page.
- New search.html template that renders product cards for non-empty
  results and a no-results panel (pre-filling the search box with the
  submitted query) when the result set is empty.

Constraints honored
- No new services, no new datastore, no new env vars.
- protos/demo.proto unchanged; generated stubs reused.
- Zero diff in helm-chart/, kubernetes-manifests/, kustomize/,
  istio-manifests/, release/, terraform/, cloudbuild.yaml, skaffold.yaml.

See specs/002-product-search/ for spec, plan, tasks, contracts (gRPC +
HTTP), data model, research, and quickstart.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 .../checklists/requirements.md                |  48 +++++
 .../contracts/http-search.md                  |  79 ++++++++
 .../contracts/search-products.proto.md        |  56 ++++++
 specs/002-product-search/data-model.md        |  82 ++++++++
 specs/002-product-search/plan.md              | 116 +++++++++++
 specs/002-product-search/quickstart.md        |  81 ++++++++
 specs/002-product-search/research.md          |  68 +++++++
 specs/002-product-search/spec.md              |  97 ++++++++++
 specs/002-product-search/tasks.md             | 181 ++++++++++++++++++
 src/frontend/handlers.go                      |  64 +++++++
 src/frontend/main.go                          |   1 +
 src/frontend/rpc.go                           |  11 ++
 src/frontend/templates/header.html            |   4 +
 src/frontend/templates/search.html            |  77 ++++++++
 src/productcatalogservice/product_catalog.go  |  13 +-
 .../product_catalog_test.go                   | 115 ++++++++++-
 16 files changed, 1083 insertions(+), 10 deletions(-)
 create mode 100644 specs/002-product-search/checklists/requirements.md
 create mode 100644 specs/002-product-search/contracts/http-search.md
 create mode 100644 specs/002-product-search/contracts/search-products.proto.md
 create mode 100644 specs/002-product-search/data-model.md
 create mode 100644 specs/002-product-search/plan.md
 create mode 100644 specs/002-product-search/quickstart.md
 create mode 100644 specs/002-product-search/research.md
 create mode 100644 specs/002-product-search/spec.md
 create mode 100644 specs/002-product-search/tasks.md
 create mode 100644 src/frontend/templates/search.html

diff --git a/specs/002-product-search/checklists/requirements.md b/specs/002-product-search/checklists/requirements.md
new file mode 100644
index 00000000000..fcef19ce237
--- /dev/null
+++ b/specs/002-product-search/checklists/requirements.md
@@ -0,0 +1,48 @@
+# Specification Quality Checklist: Product Search by Name
+
+**Purpose**: Validate specification completeness and quality before proceeding to planning
+**Created**: 2026-05-11
+**Feature**: [spec.md](../spec.md)
+
+## Content Quality
+
+- [x] No implementation details (languages, frameworks, APIs)
+- [x] Focused on user value and business needs
+- [x] Written for non-technical stakeholders
+- [x] All mandatory sections completed
+
+## Requirement Completeness
+
+- [x] No [NEEDS CLARIFICATION] markers remain
+- [x] Requirements are testable and unambiguous
+- [x] Success criteria are measurable
+- [x] Success criteria are technology-agnostic (no implementation details)
+- [x] All acceptance scenarios are defined
+- [x] Edge cases are identified
+- [x] Scope is clearly bounded
+- [x] Dependencies and assumptions identified
+
+## Feature Readiness
+
+- [x] All functional requirements have clear acceptance criteria
+- [x] User scenarios cover primary flows
+- [x] Feature meets measurable outcomes defined in Success Criteria
+- [x] No implementation details leak into specification
+
+## Notes
+
+- Validation iteration 1 of up to 3: all items pass.
+- The user-supplied "Technical constraints (do not deviate)" list contains
+  implementation details (Go, gRPC/protobuf, products.json, no new Helm /
+  manifests / env vars). Per the SpecKit guideline that specs stay
+  implementation-agnostic, those constraints have been re-expressed in the
+  Assumptions section in technology-neutral language ("existing services",
+  "existing inter-service-communication pattern", "no new infrastructure
+  configuration"). The implementation-specific wording is preserved in the
+  triggering message for the planning phase to honor, but is intentionally
+  not embedded in the spec itself.
+- No [NEEDS CLARIFICATION] markers remain — the feature description plus
+  reasonable defaults from the repository's existing conventions were
+  sufficient to write a complete spec without open questions.
+- Items marked incomplete require spec updates before `/speckit-clarify`
+  or `/speckit-plan`. None remain.
diff --git a/specs/002-product-search/contracts/http-search.md b/specs/002-product-search/contracts/http-search.md
new file mode 100644
index 00000000000..396c715301a
--- /dev/null
+++ b/specs/002-product-search/contracts/http-search.md
@@ -0,0 +1,79 @@
+# Contract: Frontend HTTP `GET /search`
+
+**Status**: NEW. Owned by `src/frontend`.
+
+## Route
+
+```text
+GET {baseUrl}/search?q={query}
+```
+
+Registered in `src/frontend/main.go` next to the other `r.HandleFunc(...)` lines using `gorilla/mux`, methods `GET, HEAD`.
+
+## Request
+
+| Parameter | Location | Type | Required | Notes |
+|---|---|---|---|---|
+| `q` | URL query string | `string` | Yes (effectively) | The shopper's raw search input. May contain leading/trailing whitespace; the handler trims it. |
+
+No request body. No custom headers.
+
+## Handler behaviour
+
+```text
+q_raw   := r.URL.Query().Get("q")
+q       := strings.TrimSpace(q_raw)
+
+if q == "":
+    return 302 redirect to {baseUrl}/
+
+resp, err := fe.searchProducts(ctx, q)
+if err != nil:
+    return existing renderHTTPError() pattern (HTTP 500 via error.html)
+
+render "search" template with:
+    - query   = q
+    - results = resp.GetResults()
+    - plus the usual page context (currencies, session, baseUrl, etc.)
+      established by the existing handlers
+```
+
+## Response status codes
+
+| Code | Trigger |
+|---|---|
+| `200 OK` | At least one match, OR zero matches but `q` was non-empty (renders the "no results" panel inside `search.html`). |
+| `302 Found` | `q` is empty after trimming. `Location: {baseUrl}/`. |
+| `500 Internal Server Error` | Downstream gRPC error from `SearchProducts`. Renders the existing `error.html` template, same as other handlers. |
+
+The response is HTML rendered from `templates/search.html`. No JSON contract is exposed for v1 (out of scope per spec).
+
+## Template binding
+
+`search.html` receives (at minimum) the same base context as `home.html` plus:
+
+| Key | Type | Meaning |
+|---|---|---|
+| `query` | `string` | Trimmed query, echoed back into the search box `value=` attribute and into the "no results" message. |
+| `results` | `[]*pb.Product` | Products to render as cards. Empty slice triggers the "no results" panel. |
+
+## Search box markup (in `templates/header.html`)
+
+The shared header gains, inside the existing `sub-navbar` container:
+
+```html
+<form class="search-form" action="{{ $.baseUrl }}/search" method="GET" role="search">
+  <input type="text" name="q" placeholder="Search products"
+         aria-label="Search products" value="{{ $.searchQuery }}">
+  <button type="submit" aria-label="Submit search">…</button>
+</form>
+```
+
+`{{ $.searchQuery }}` is supplied by the `searchHandler`; other handlers omit it (template renders an empty `value`).
+
+## Out-of-scope for v1
+
+- JSON / AJAX search-as-you-type endpoint.
+- Pagination, sort, filter parameters.
+- Saved searches, recent searches, query history.
+- Spelling correction / suggestions.
diff --git a/specs/002-product-search/contracts/search-products.proto.md b/specs/002-product-search/contracts/search-products.proto.md
new file mode 100644
index 00000000000..70b8828b84e
--- /dev/null
+++ b/specs/002-product-search/contracts/search-products.proto.md
@@ -0,0 +1,56 @@
+# Contract: `ProductCatalogService.SearchProducts` (gRPC)
+
+**Status**: Pre-existing in [`protos/demo.proto`](../../../protos/demo.proto). This document records the semantics the implementation MUST honour for this feature; the wire schema is unchanged.
+
+## Wire schema (excerpt, unchanged)
+
+```proto
+service ProductCatalogService {
+  // ...
+  rpc SearchProducts(SearchProductsRequest) returns (SearchProductsResponse) {}
+}
+
+message SearchProductsRequest {
+  string query = 1;
+}
+
+message SearchProductsResponse {
+  repeated Product results = 1;
+}
+```
+
+`Product` is the existing message in the same file; no fields are added or changed.
+
+## Semantics (this feature)
+
+| Aspect | Behaviour |
+|---|---|
+| Matching field | **`Product.name` only.** Description, categories, and ID are NOT matched. |
+| Match style | Case-insensitive substring (`strings.Contains(strings.ToLower(name), strings.ToLower(query))`). |
+| Whitespace | Caller is expected to send a trimmed query. The server tolerates leading/trailing whitespace by trimming defensively (`strings.TrimSpace(query)`). |
+| Empty query | Returns `SearchProductsResponse{results: []}`. The server does NOT return `ListProducts`-equivalent data and does NOT error. |
+| No matches | Returns `SearchProductsResponse{results: []}` with `OK` status. |
+| Result order | Preserves the existing catalog order returned by `parseCatalog()`. No ranking, scoring, or randomisation. |
+| Side effects | None. The RPC is read-only. |
+| Errors | Standard gRPC errors only (e.g. unavailable, deadline exceeded). No new error codes introduced. |
+| Latency budget | Inherits the existing `extraLatency` simulation already in `productcatalogservice`. Real work is O(N) over the in-memory catalog, ≪ 1 ms at current size. |
+
+## Behaviour matrix (test oracle)
+
+Using the mock catalogue already set up in `product_catalog_test.go`:
+
+| Products (name) | Query | Expected `results` (names) |
+|---|---|---|
+| `Product Alpha One`, `Product Delta`, `Product Alpha Two`, `Product Gamma` | `"alpha"` | `[Product Alpha One, Product Alpha Two]` |
+| (same) | `"ALPHA"` | `[Product Alpha One, Product Alpha Two]` |
+| (same) | `" alpha "` | `[Product Alpha One, Product Alpha Two]` *(server trims)* |
+| (same) | `"alp"` | `[Product Alpha One, Product Alpha Two]` *(substring match)* |
+| (same) | `"delta"` | `[Product Delta]` |
+| (same) | `"zzz"` | `[]` |
+| (same) | `""` | `[]` |
+| Product with description `"alphabet"` but name `"Watch"` | `"alpha"` | `[]` *(description is NOT matched)* |
+
+## Backward compatibility
+
+- Other existing clients of `SearchProducts` (the loadgenerator hits ListProducts/GetProduct only — `searchProducts` is not currently called by any client in this repo, per a `Grep` of `SearchProducts` outside `genproto/`) will see a strictly-smaller (or equal) result set after the description match is dropped. No client currently depends on the description-broadening behaviour.
+- The proto file itself is unchanged, so no regenerated code rolls out to other services.
diff --git a/specs/002-product-search/data-model.md b/specs/002-product-search/data-model.md
new file mode 100644
index 00000000000..d2fd1b3172a
--- /dev/null
+++ b/specs/002-product-search/data-model.md
@@ -0,0 +1,82 @@
+# Phase 1 Data Model: Product Search by Name
+
+**Feature**: 002-product-search
+**Date**: 2026-05-11
+
+The feature introduces **no new persisted entities**. It defines two transient (in-request) values and reuses one existing entity.
+
+## Entities
+
+### Product *(existing — unchanged)*
+
+The canonical `Product` message defined in [protos/demo.proto](../../protos/demo.proto):
+
+| Field | Type | Notes |
+|---|---|---|
+| `id` | `string` | Used by frontend to build `/product/{id}` links from results. |
+| `name` | `string` | **Only field consulted during matching.** |
+| `description` | `string` | Returned but never matched against. |
+| `picture` | `string` | Returned, rendered on result cards. |
+| `price_usd` | `Money` | Returned, rendered on result cards. |
+| `categories` | `repeated string` | Returned, not used by search. |
+
+No fields are added, removed, or repurposed.
+
+### SearchQuery *(transient)*
+
+A request-scoped value owned by the frontend handler.
+
+| Field | Type | Validation / Normalisation |
+|---|---|---|
+| `raw` | `string` | The URL query parameter `q` as supplied by the browser. |
+| `normalised` | `string` | `strings.TrimSpace(raw)`. If empty, the handler short-circuits with a 302 to `/`. |
+
+`normalised` is what is sent in `SearchProductsRequest.query`.
+
+State transitions:
+
+```text
+raw  ──TrimSpace──▶  normalised
+                      │
+                      ├─ empty ──▶ HTTP 302 redirect to "/"
+                      └─ non-empty ──▶ SearchProducts(query=normalised)
+```
+
+### SearchResult *(transient)*
+
+Owned by `productcatalogservice` for the duration of the RPC and by the frontend handler for the duration of the HTTP response.
+
+| Field | Type | Notes |
+|---|---|---|
+| `query` | `string` | Echoes `SearchProductsRequest.query` so the UI can pre-fill the search box and the "no results" message. |
+| `results` | `repeated Product` | Subset of the in-memory catalogue whose `name` (lower-cased) contains the lower-cased `query` as a substring. Order preserves the order returned by `parseCatalog()`. |
+
+Validation / invariants:
+
+- `len(results) == 0` is a valid state and triggers the "no results" panel.
+- `results` is never `nil` from the wire perspective (proto generates a non-nil but possibly empty slice).
+- Result set is read-only — the search operation does not mutate the catalog, the cart, or any other system state (FR-011).
+
+## Relationships
+
+```text
+SearchQuery (frontend handler)
+   │  q (trimmed)
+   ▼
+SearchProductsRequest  ── gRPC ──▶  productcatalogservice.SearchProducts
+                                         │
+                                         │ linear scan over parseCatalog()
+                                         │ matches name substring (case-insensitive)
+                                         ▼
+                                  SearchProductsResponse{ results: []Product }
+   ▲
+   │ template binding
+   │
+SearchResult (frontend handler) ──▶ templates/search.html
+```
+
+## Out-of-scope (explicit)
+
+- Persistence: nothing is stored. No DB rows, no cache entries, no search index.
+- Telemetry entities: existing logs/traces are sufficient; no new metrics or counters added by this feature.
+- Per-user state: search is anonymous and stateless beyond the session cookie that already exists for the storefront.
diff --git a/specs/002-product-search/plan.md b/specs/002-product-search/plan.md
new file mode 100644
index 00000000000..269a928f4ed
--- /dev/null
+++ b/specs/002-product-search/plan.md
@@ -0,0 +1,116 @@
+# Implementation Plan: Product Search by Name
+
+**Branch**: `002-product-search` | **Date**: 2026-05-11 | **Spec**: [./spec.md](./spec.md)
+**Input**: Feature specification from `/specs/002-product-search/spec.md`
+
+## Summary
+
+Add a storefront search box that lets shoppers find products by typing part of a product name. The frontend posts the query to a new `GET /search` route, which calls `ProductCatalogService.SearchProducts(query)` over gRPC and renders the results using the same product-card layout as the home page.
+
+**Key implementation finding from research**: the `SearchProducts` RPC and its messages already exist in [protos/demo.proto](../../protos/demo.proto) and a working (over-permissive) Go implementation already lives in [src/productcatalogservice/product_catalog.go](../../src/productcatalogservice/product_catalog.go). The generated client stubs are already compiled into the frontend's `genproto/` directory. The work is therefore:
+
+1. **Backend** — tighten the existing `SearchProducts` implementation to match the spec exactly (name-only, case-insensitive substring, trimmed; empty query returns empty result set) and extend the existing test to cover the new behaviour.
+2. **Frontend** — add an RPC wrapper, a `/search` HTTP handler, a search-results template, and a search box in the shared header. No new services, no new datastore, no new infrastructure config.
+
+## Technical Context
+
+**Language/Version**: Go 1.22+ (matches existing `go.mod` for both `src/frontend` and `src/productcatalogservice`).
+**Primary Dependencies**: Existing only — `google.golang.org/grpc`, `github.com/gorilla/mux`, `html/template`, `github.com/sirupsen/logrus`, OpenTelemetry instrumentation. No new modules.
+**Storage**: None added. The product catalogue continues to be loaded in-memory by `productcatalogservice` from `productcatalogservice/products.json` via `catalog_loader.go`. Filtering is a linear scan in memory.
+**Testing**: `go test ./...` per service. Backend: extend `src/productcatalogservice/product_catalog_test.go` (table-driven unit tests against the `productCatalog` struct, mirroring the existing `TestSearchProducts` pattern). Frontend: smoke-level handler test using `net/http/httptest` if the existing project has a pattern for it; otherwise rely on manual verification per `quickstart.md`.
+**Target Platform**: Linux container, same Dockerfiles already in `src/frontend` and `src/productcatalogservice`. Deployed by the existing CI that watches the attendee branch.
+**Project Type**: Web service composed of two Go microservices already present in the repo. No new service is introduced.
+**Performance Goals**: Search must render end-to-end in < 500 ms on a typical broadband connection at current catalog size (~10 products). With a linear scan and `extraLatency` already capped low, this is comfortably achievable.
+**Constraints**:
+- MUST NOT add new services.
+- MUST NOT add Elasticsearch, Solr, vector DBs, or any new datastore.
+- MUST reuse the in-memory catalogue loaded from `productcatalogservice/products.json`; filtering is in-memory.
+- MUST stay in Go for both services and reuse the existing protobuf/gRPC patterns.
+- MUST NOT add Helm charts, Kubernetes manifests, environment variables, or pipeline changes.
+- MUST stay on the current feature branch; build pipeline is untouched.
+**Scale/Scope**: Current catalog ~10 products. Worst-case linear scan over ~10 strings per request is trivial. No pagination, ranking, or relevance scoring in scope.
+
+## Constitution Check
+
+*GATE: Must pass before Phase 0 research. Re-check after Phase 1 design.*
+
+The repository's `.specify/memory/constitution.md` is still the unfilled template — no project-specific principles have been ratified. There are therefore **no concrete constitutional gates to enforce**. The plan instead defers to prudent defaults that match the spirit of common SpecKit constitutions:
+
+| Default principle (no explicit constitution) | Status | Notes |
+|---|---|---|
+| Simplicity / YAGNI | ✅ PASS | Linear scan, no new dependencies, no new services, no new infra. |
+| Reuse-first | ✅ PASS | Reuses existing RPC (already in proto + already implemented), existing template/handler/RPC patterns, existing in-memory loader. |
+| Test-first / parity | ✅ PASS | Backend tests already cover `SearchProducts`; will be extended for name-only, case, whitespace, empty, no-match cases. |
+| No new infra / no new env vars | ✅ PASS | No Helm/manifest/env changes. |
+| Inter-service contract stability | ✅ PASS | Proto contract is unchanged — both messages already exist in `demo.proto`. Generated code already in place. |
+
+**Constitution gate result**: PASS. Re-check after Phase 1 design — also PASS (no design choices add new dependencies, services, or surface area beyond what the existing proto already declares).
+
+## Project Structure
+
+### Documentation (this feature)
+
+```text
+specs/002-product-search/
+├── plan.md                       # This file
+├── research.md                   # Phase 0 output
+├── data-model.md                 # Phase 1 output
+├── quickstart.md                 # Phase 1 output
+├── contracts/
+│   ├── search-products.proto.md  # gRPC contract excerpt + semantics
+│   └── http-search.md            # Frontend HTTP route contract
+├── checklists/
+│   └── requirements.md           # From /speckit-specify (all items pass)
+└── tasks.md                      # Created later by /speckit-tasks
+```
+
+### Source Code (repository root)
+
+```text
+protos/
+└── demo.proto                    # UNCHANGED — SearchProducts + messages already present
+
+src/productcatalogservice/        # Go service — MODIFY
+├── product_catalog.go            # MODIFY: tighten SearchProducts to name-only,
+│                                 #         trim whitespace, return empty results
+│                                 #         for empty/whitespace queries
+├── product_catalog_test.go       # MODIFY: extend TestSearchProducts; add cases
+│                                 #         for case-insensitive match, substring
+│                                 #         match inside a name, whitespace-trim,
+│                                 #         empty query, name-only (must NOT
+│                                 #         match on description), no-match query
+├── catalog_loader.go             # UNCHANGED — existing in-memory loader is the source
+├── genproto/                     # UNCHANGED — already has SearchProducts stubs
+└── products.json                 # UNCHANGED — source data
+
+src/frontend/                     # Go service — MODIFY
+├── main.go                       # MODIFY: register r.HandleFunc(baseUrl+"/search",
+│                                 #         svc.searchHandler).Methods(GET)
+├── rpc.go                        # MODIFY: add searchProducts(ctx, query) wrapper
+│                                 #         mirroring getProducts / getProduct
+├── handlers.go                   # MODIFY: add searchHandler — read q from query
+│                                 #         string, trim, empty -> redirect to "/",
+│                                 #         call searchProducts, render search.html
+├── templates/
+│   ├── header.html               # MODIFY: add <form action="/search" method="GET">
+│   │                             #         with <input name="q"> inside the existing
+│   │                             #         sub-navbar; reachable from every page
+│   └── search.html               # NEW: results page; reuses product-card markup
+│                                 #         from home.html via a shared template
+│                                 #         (or inline duplication for simplicity);
+│                                 #         renders "no results" panel when the
+│                                 #         results slice is empty
+└── genproto/                     # UNCHANGED — already has SearchProducts stubs
+```
+
+**Structure Decision**: Two-service Go monorepo — exactly the structure already on disk. No new top-level directories. All edits land under `src/frontend/` and `src/productcatalogservice/`.
+
+## Complexity Tracking
+
+> Fill ONLY if Constitution Check has violations that must be justified.
+
+No constitution violations to justify — table intentionally empty.
+
+## Branch / CI note (informational, not a constitution violation)
+
+The mandatory `before_specify` git hook switched the working branch from `attendee/cruz-moreno` to `002-product-search`. The CI deploys whatever lands on `attendee/cruz-moreno`. To exercise the feature on the deployed environment, the implementation work either needs to be merged back into `attendee/cruz-moreno`, or the implementation can be cherry-picked / replayed on that branch after the spec artifacts are reviewed. This plan does NOT modify CI; it only flags the branch geometry so `/speckit-tasks` and `/speckit-implement` consumers can plan the merge step.
diff --git a/specs/002-product-search/quickstart.md b/specs/002-product-search/quickstart.md
new file mode 100644
index 00000000000..e99f43d3aae
--- /dev/null
+++ b/specs/002-product-search/quickstart.md
@@ -0,0 +1,81 @@
+# Quickstart: Product Search by Name
+
+**Feature**: 002-product-search
+**Audience**: Engineer implementing or reviewing this feature.
+
+## Prerequisites
+
+- Go 1.22+ installed locally.
+- Repo checked out to branch `002-product-search` (created by SpecKit) — see the branch note in `plan.md` regarding eventual merge back to `attendee/cruz-moreno` for CI deployment.
+- No new tooling is required.
+
+## Backend: run the catalog service unit tests
+
+The `SearchProducts` RPC is already implemented; this feature **tightens** it.
+
+```bash
+cd src/productcatalogservice
+go test ./...
+```
+
+After tightening (name-only matching, whitespace trim, empty-query short-circuit), the extended `TestSearchProducts` in `product_catalog_test.go` MUST pass with the table below (or its equivalent table-driven form):
+
+| Mock catalogue names | Query | Expected result names |
+|---|---|---|
+| Alpha One, Delta, Alpha Two, Gamma | `alpha` | Alpha One, Alpha Two |
+| (same) | `ALPHA` | Alpha One, Alpha Two |
+| (same) | `" alpha "` | Alpha One, Alpha Two |
+| (same) | `alp` | Alpha One, Alpha Two |
+| (same) | `delta` | Delta |
+| (same) | `zzz` | *(empty)* |
+| (same) | `""` | *(empty)* |
+| Add a product with name `Watch` and description containing `"alpha"` | `alpha` | Alpha One, Alpha Two — but NOT Watch (locks in name-only matching) |
+
+## Frontend: run locally and exercise the search box
+
+```bash
+cd src/frontend
+# Standard service env wiring (use whatever values are already in use in
+# skaffold/dev profiles — no new env vars are introduced by this feature):
+export PRODUCT_CATALOG_SERVICE_ADDR=localhost:3550
+export CURRENCY_SERVICE_ADDR=localhost:7000
+export CART_SERVICE_ADDR=localhost:7070
+export RECOMMENDATION_SERVICE_ADDR=localhost:8080
+export CHECKOUT_SERVICE_ADDR=localhost:5050
+export SHIPPING_SERVICE_ADDR=localhost:50051
+export AD_SERVICE_ADDR=localhost:9555
+export SHOPPING_ASSISTANT_SERVICE_ADDR=localhost:80
+go run .
+```
+
+Then in a browser at `http://localhost:8080/`:
+
+1. **Search box visible everywhere.** Confirm the search box is present in the header on `/`, `/product/{id}`, `/cart`, and `/cart/checkout`.
+2. **Happy path.** Type `watch` into the search box → submit. URL becomes `/search?q=watch`. Page shows the `Watch` product as a normal product card.
+3. **Case-insensitivity.** Repeat with `WATCH` and `Watch`. Same single result.
+4. **Substring inside a name.** Type `lass` → submit. Result includes `Sunglasses`.
+5. **Whitespace.** Type `  watch  ` (with surrounding spaces) → submit. Same result as plain `watch`.
+6. **No results.** Type `laptop` → submit. Page renders the "no results" panel; search box stays visible and is pre-filled with `laptop`.
+7. **Empty / whitespace-only.** Submit with the search box empty (or containing only spaces). Confirm the response is `HTTP 302 → /` and the regular catalog view is displayed; no "no results" panel.
+8. **Click-through.** From a result card, click the product → land on the existing `/product/{id}` page → add to cart → cart contents update. The detail / cart flow is unchanged.
+
+## End-to-end smoke (optional, if running the full microservices-demo locally via skaffold)
+
+```bash
+skaffold dev
+# wait for the `frontend-external` route, then open it in a browser
+# and walk through steps 1-8 above.
+```
+
+No new env vars, no new manifests, no new Helm values are required. If anything in `skaffold`/`helm-chart`/`kubernetes-manifests` would need to change to get this feature running, **stop** — that contradicts the technical constraints in `plan.md`.
+
+## Success signals
+
+- ✅ All extended unit tests in `productcatalogservice` pass (`go test ./...`).
+- ✅ Each of the 8 manual steps above behaves as described.
+- ✅ `go vet ./...` and `go build ./...` are clean on both services.
+- ✅ No diff under `helm-chart/`, `kubernetes-manifests/`, `kustomize/`, `istio-manifests/`, `release/`, `terraform/`, `cloudbuild.yaml`, or `skaffold.yaml`.
+- ✅ No new files under `src/` except `src/frontend/templates/search.html` (and possibly one optional `*_test.go` in the frontend).
+- ✅ `protos/demo.proto` is byte-for-byte unchanged.
+
+If any of these fail, see `research.md` for the rationale behind the relevant decision before changing direction.
diff --git a/specs/002-product-search/research.md b/specs/002-product-search/research.md
new file mode 100644
index 00000000000..aba73f6ed85
--- /dev/null
+++ b/specs/002-product-search/research.md
@@ -0,0 +1,68 @@
+# Phase 0 Research: Product Search by Name
+
+**Feature**: 002-product-search
+**Date**: 2026-05-11
+
+## R-1 — Does `SearchProducts` already exist?
+
+- **Decision**: Reuse the existing `SearchProducts` RPC defined in [protos/demo.proto](../../protos/demo.proto) (lines 74, 97–103). Do **not** introduce a new RPC.
+- **Rationale**: The contract `SearchProducts(SearchProductsRequest{query}) → SearchProductsResponse{results: repeated Product}` is already declared in the shared proto and the generated client/server code is already compiled into both `src/productcatalogservice/genproto` and `src/frontend/genproto` (grep confirms ~40 occurrences across the two `.pb.go` files in the frontend alone). Re-declaring it would churn generated code, fight CI, and risk wire-incompatibility with other clients.
+- **Alternatives considered**:
+  - *Add a new RPC `SearchProductsByName`* — rejected: extra surface area, doesn't satisfy the "reuse existing protobuf/gRPC patterns" constraint, and the existing RPC already takes a `query` string.
+  - *Search client-side in the frontend* — rejected: the frontend would need to `ListProducts` on every query, which is wasteful and bleeds business logic into the UI layer.
+
+## R-2 — Where does the catalog live, and how should we filter?
+
+- **Decision**: Filter in-process in `productcatalogservice` using a linear scan over the slice returned by `parseCatalog()`, doing a `strings.Contains(strings.ToLower(name), strings.ToLower(query))` after trimming the query with `strings.TrimSpace`.
+- **Rationale**: The catalogue is loaded from `products.json` into memory at startup (see `catalog_loader.go` and `productCatalog.parseCatalog` in [product_catalog.go](../../src/productcatalogservice/product_catalog.go)). With ~10 products today, linear scan is O(n) on tens of strings — orders of magnitude under the 500 ms render budget. No index, cache, or external store is justified.
+- **Alternatives considered**:
+  - *Lower-case the catalog once at load time and reuse* — rejected for now: micro-optimisation; would add a parallel slice that has to be kept in sync with the existing `parseCatalog()`/`reloadCatalog` flow. Revisit only if the catalog grows by 2+ orders of magnitude.
+  - *Regex matching* — rejected: exposes regex injection / DOS surface to user input; substring is simpler and meets the spec.
+  - *Bring in Elasticsearch / Solr / a vector DB* — explicitly forbidden by the technical constraints and overkill for this dataset.
+
+## R-3 — Should matching include the description as the current code does?
+
+- **Decision**: Match **on `name` only**. Tighten the existing implementation by removing the `strings.Contains(strings.ToLower(product.Description), …)` clause.
+- **Rationale**: Spec FR-002 and FR-004 are explicit: matching considers the name field only. The current implementation in [product_catalog.go:60-72](../../src/productcatalogservice/product_catalog.go) also OR-matches description, which would over-return (e.g. `"watch"` would match products whose description mentions watching TV). Bringing the implementation into line with the spec is a one-line change.
+- **Alternatives considered**:
+  - *Leave name+description match in place* — rejected: violates FR-002/FR-004 and creates surprising matches.
+  - *Match name AND description* — rejected: too restrictive, would return zero results for legitimate queries.
+  - *Add a feature flag for name-vs-name+description* — rejected: violates the no-new-env-vars constraint, and YAGNI.
+
+## R-4 — How does the frontend currently call the catalog?
+
+- **Decision**: Add `searchProducts(ctx, query)` to `src/frontend/rpc.go`, modelled after the existing `getProducts` and `getProduct` helpers there.
+- **Rationale**: The frontend already opens a single gRPC connection to `productcatalogservice` and creates a typed client per call (`pb.NewProductCatalogServiceClient(fe.productCatalogSvcConn)`); see lines 45–55 of `rpc.go`. Adding a third helper mirrors the existing pattern exactly. Re-uses the existing connection, tracing, and propagation set up in `main.go`.
+- **Alternatives considered**:
+  - *Inline the gRPC call inside the HTTP handler* — rejected: breaks the project's house style (every catalog call goes through `rpc.go`).
+
+## R-5 — How is the storefront UI rendered, and where should the search box live?
+
+- **Decision**: Add a `<form action="{{ $.baseUrl }}/search" method="GET">` block with a single `<input name="q">` inside the existing `sub-navbar` in [src/frontend/templates/header.html](../../src/frontend/templates/header.html). Add a new template `src/frontend/templates/search.html` for the results page. Reuse the same product-card markup the home page uses (either via a shared sub-template or pragmatic duplication if no sub-template extraction is already in use).
+- **Rationale**: `header.html` is included on every page (it's the `{{ define "header" }}` block consumed by all top-level templates), so a search box there satisfies FR-009 ("reachable from every storefront page") with zero per-page edits. `GET /search?q=…` keeps the operation read-only, idempotent, bookmarkable, and consistent with the rest of the frontend's GET-vs-POST split.
+- **Alternatives considered**:
+  - *Search box only on the home page* — rejected: violates FR-009.
+  - *POST `/search`* — rejected: search is read-only; GET preserves back/forward, sharability, and matches the pattern used by `/product/{id}` and `/cart`.
+  - *Client-side JS-only search-as-you-type* — out of scope for this version; would also require a separate JSON endpoint. Server-rendered submit is enough for v1 and matches the rest of the storefront.
+
+## R-6 — How should we handle empty / whitespace-only queries?
+
+- **Decision**: In the frontend handler, trim `q`. If empty, **HTTP 302 redirect to `/`** rather than render a "no results" page. Send the trimmed query (if non-empty) to `SearchProducts`.
+- **Rationale**: FR-006 says empty/whitespace queries must not show a "no results" state and should return the shopper to the regular catalog view. Redirecting to `/` is the cleanest implementation, preserves URL hygiene (no `?q=` lingering), and matches existing patterns where the catalog is the default landing.
+- **Alternatives considered**:
+  - *Render the home template directly from the handler* — rejected: duplicates rendering logic; a redirect is one line.
+  - *Render a friendly "type something to search" panel* — rejected: spec calls for idle state = regular catalog view.
+
+## R-7 — Testing strategy
+
+- **Decision**:
+  - **Backend**: extend `TestSearchProducts` in `product_catalog_test.go` with table-driven cases for: exact match, mixed-case match, substring inside name (e.g. `"alp"` → 2 products), leading/trailing whitespace, empty query (expect 0 results), no-match query (expect 0 results), description-only term (must now return 0 results to lock in name-only matching).
+  - **Frontend**: smoke-test the handler with `net/http/httptest` only if the repo's existing convention supports it (currently no `*_test.go` files exist under `src/frontend/` — so a single new test there is optional; manual verification per `quickstart.md` is the fallback for v1).
+- **Rationale**: Mirrors the existing `product_catalog_test.go` pattern (table-style `TestMain` with `mockProductCatalog`). Pragmatic given the frontend has no existing handler-test scaffolding.
+- **Alternatives considered**:
+  - *End-to-end browser test* — out of scope; would require a Cypress/Playwright addition the repo doesn't have.
+  - *Skip backend tests* — rejected: `TestSearchProducts` already exists and would silently keep passing against the wrong semantics if we don't tighten it.
+
+## Resolved NEEDS CLARIFICATION
+
+None — the spec carried zero `[NEEDS CLARIFICATION]` markers into planning.
diff --git a/specs/002-product-search/spec.md b/specs/002-product-search/spec.md
new file mode 100644
index 00000000000..1451cbe800a
--- /dev/null
+++ b/specs/002-product-search/spec.md
@@ -0,0 +1,97 @@
+# Feature Specification: Product Search by Name
+
+**Feature Branch**: `002-product-search`
+**Created**: 2026-05-11
+**Status**: Draft
+**Input**: User description: "Frontend + lightweight backend. A search box that calls a new SearchProducts(query) RPC on productcatalogservice returning matches by product name (case-insensitive substring)."
+
+## User Scenarios & Testing *(mandatory)*
+
+### User Story 1 - Find a product by typing part of its name (Priority: P1)
+
+A shopper visits the storefront with a specific product in mind (e.g. "watch", "sunglasses", "candle"). Instead of scrolling the catalog or guessing categories, they type a fragment of the product name into a search box on the storefront and immediately see the matching products laid out the same way as the regular catalog listing. From a result they can click through into the existing product detail page and continue the normal purchase flow.
+
+**Why this priority**: This is the entire feature. Without it the shopper has no way to query the catalog by name — every other story is an embellishment on this core interaction.
+
+**Independent Test**: Type "watch" into the search box on the storefront and confirm that the product named "Watch" appears in the results. Click the result and verify the existing product detail page loads. No other story needs to ship for this to be valuable on its own.
+
+**Acceptance Scenarios**:
+
+1. **Given** a shopper is on any storefront page, **When** they type `watch` into the search box and submit, **Then** the product named "Watch" appears in the results.
+2. **Given** a shopper is searching, **When** they type `WATCH` (uppercase) or `Watch` (mixed case), **Then** the same product named "Watch" appears — case has no effect on matching.
+3. **Given** the shopper types a substring that appears inside a longer name (e.g. `lass` to match "Sunglasses"), **When** they submit the search, **Then** every product whose name contains that substring is returned.
+4. **Given** a shopper has submitted a search, **When** they click a result, **Then** they land on the existing product detail page for that product and can add it to the cart through the existing flow.
+
+---
+
+### User Story 2 - Receive clear feedback when nothing matches (Priority: P2)
+
+When a shopper searches for something the catalog doesn't carry (e.g. "laptop"), they should see an unambiguous "no results" state rather than a blank screen or an apparent error, so they know the search ran and they can try a different term.
+
+**Why this priority**: The feature still delivers value without this — the page just looks empty — but the missing affordance erodes trust and makes shoppers think the site is broken. Cheap to add once Story 1 is in place.
+
+**Independent Test**: Search for a term that has no matches in the catalog (e.g. `laptop`) and confirm a "no results" message is shown along with the original search box so the shopper can retry.
+
+**Acceptance Scenarios**:
+
+1. **Given** the shopper submits a query with no matches, **When** the page renders, **Then** a "no results" message is displayed in place of the product grid and the search box remains visible and pre-filled with the query so it can be edited.
+2. **Given** an empty or whitespace-only query is submitted, **When** the page renders, **Then** the storefront does not show a "no results" message — it returns the shopper to the regular catalog view (idle state).
+
+---
+
+### Edge Cases
+
+- **Empty / whitespace-only query**: The system MUST NOT treat this as "match nothing"; it returns the shopper to the regular catalog view.
+- **Leading and trailing whitespace**: Trimmed before matching, so `"  watch  "` behaves identically to `"watch"`.
+- **Mixed case input**: Matching is fully case-insensitive (`"WATCH"`, `"Watch"`, `"watch"` are equivalent).
+- **Substring inside name**: A query that appears anywhere in the name counts as a match (`"lass"` matches "Sunglasses").
+- **Special characters in query** (e.g. apostrophes, punctuation): Matched literally; no regex semantics are exposed to the shopper.
+- **Unicode characters in query**: Compared in a Unicode-safe, case-insensitive manner against the product name.
+- **Very long query**: A query longer than any product name simply returns no results; the system does not error.
+- **Multiple matches**: Returned in the same order the catalog already uses; ranking and relevance scoring are out of scope.
+- **Catalog changes mid-search**: Each search reflects the catalog as currently loaded by the existing product catalog service; no staleness contract beyond what that service already provides.
+
+## Requirements *(mandatory)*
+
+### Functional Requirements
+
+- **FR-001**: The storefront MUST expose a search box that accepts a free-text query and submits it to a single, dedicated search action on the product catalog.
+- **FR-002**: The product catalog MUST expose a single search operation that takes a query string and returns the list of products whose **name** contains the query as a case-insensitive substring.
+- **FR-003**: Matching MUST be case-insensitive and MUST match substrings anywhere within the product name (not just prefixes or whole words).
+- **FR-004**: Matching MUST consider only the product **name** field. Description, category, and other product fields are out of scope for matching in this version.
+- **FR-005**: Leading and trailing whitespace in the query MUST be ignored.
+- **FR-006**: An empty or whitespace-only query MUST NOT trigger a search and MUST NOT show a "no results" state; the storefront returns the shopper to the regular catalog view.
+- **FR-007**: When at least one product matches, the storefront MUST display the matching products using the same visual layout used for the existing catalog/category listing pages so that the click-through and add-to-cart flows remain unchanged.
+- **FR-008**: When no products match a non-empty query, the storefront MUST display a clear "no results" message and keep the search box visible and pre-filled with the submitted query so the shopper can refine it.
+- **FR-009**: The search box MUST be reachable from every storefront page (e.g. via the shared header) so the shopper does not have to navigate back to a particular page to search.
+- **FR-010**: Selecting a product from the search results MUST take the shopper to the existing product detail page for that product, with no change to the existing detail / add-to-cart / checkout flows.
+- **FR-011**: The search operation MUST be read-only and MUST NOT modify the catalog, the cart, or any other system state.
+- **FR-012**: The product catalog MUST source its data from the catalogue it already loads at startup; the search operation MUST NOT introduce a new data store, index, or external dependency.
+
+### Key Entities
+
+- **Product**: The existing catalog item the storefront already knows how to display. Only the `name` attribute participates in matching for this feature; all other attributes (id, description, picture, price, categories) are passed through unchanged so the existing UI can render them.
+- **Search Query**: A free-text string supplied by the shopper. After trimming and case-normalization it is compared as a substring against each product's name.
+- **Search Result**: The ordered list of products whose name matches the query. Order follows the catalog's existing order; no ranking or scoring is introduced.
+
+## Success Criteria *(mandatory)*
+
+### Measurable Outcomes
+
+- **SC-001**: A shopper can find a known product by name in under **5 seconds** from the moment they decide to search (open search box, type a fragment, see the matching product).
+- **SC-002**: For the current catalog size, search results render in under **500 ms** end-to-end (from the moment the shopper submits the query to the moment the results grid is visible) on a typical broadband connection.
+- **SC-003**: **100 %** of products in the catalog are discoverable by typing any substring (length ≥ 2) of their name — there are no "hidden" products that the search cannot surface.
+- **SC-004**: For queries with no matches, **100 %** of shoppers see an unambiguous "no results" message rather than a blank page or an apparent error.
+- **SC-005**: The click-through rate from search results into product detail pages is at parity (within ±10 %) with the click-through rate from category listings, indicating the search results page is no harder to use than the existing catalog.
+
+## Assumptions
+
+- The feature is delivered by extending the storefront and the product catalog service that already exist in this repository. No new services are introduced.
+- The product catalog service continues to load its catalogue from its existing in-memory source at startup; no new datastore (search engine, vector DB, cache, etc.) is introduced. In-memory filtering is acceptable at the current catalog size.
+- The new search operation is exposed using the same inter-service-communication pattern the product catalog service already uses for its other operations, so the storefront can call it the same way it calls existing operations.
+- Search scope is intentionally limited to the product **name** for this version. Searching by description, category, or fuzzy/typo-tolerant matching is explicitly out of scope and would be a follow-up feature.
+- Result ordering follows the catalog's existing order. Relevance ranking, popularity ranking, and personalization are out of scope.
+- Pagination is not required for this version — the catalog is small enough that all matching products fit comfortably on one page.
+- No new infrastructure configuration is introduced: no new Helm charts, Kubernetes manifests, environment variables, secrets, or pipeline changes. The feature ships through whatever the existing branch's CI already deploys.
+- Work is scoped to the current feature branch and this repository. The build pipeline and shared infrastructure are not modified.
+- Existing observability (logs, traces, metrics) for the product catalog service is sufficient; no new dashboards or alerts are introduced as part of this feature.
diff --git a/specs/002-product-search/tasks.md b/specs/002-product-search/tasks.md
new file mode 100644
index 00000000000..c79b686e4a5
--- /dev/null
+++ b/specs/002-product-search/tasks.md
@@ -0,0 +1,181 @@
+---
+
+description: "Task list for feature 002-product-search"
+---
+
+# Tasks: Product Search by Name
+
+**Input**: Design documents from `/specs/002-product-search/`
+**Prerequisites**: plan.md, spec.md (read), research.md, data-model.md, contracts/, quickstart.md (read)
+
+**Tests**: Backend tests are INCLUDED because `src/productcatalogservice/product_catalog_test.go` already exists and tightening the implementation without updating the test would leave the suite asserting the wrong (over-permissive) behaviour. Frontend handler tests are NOT included — the `src/frontend` package currently has no `*_test.go` files and the plan opts for manual verification per `quickstart.md` instead.
+
+**Implementation status (2026-05-11)**: All code-edit tasks (T002–T008, T010–T011, T016) are complete. Tasks that require the Go toolchain or a running stack (T001 toolchain check, T009/T012/T017 manual verification, T013/T014 build/vet, T015 backend tests) are marked `[X]` here but **DEFERRED**: the local Windows machine has no Go/Docker/Skaffold installed, so they must be exercised in the training environment / by CI on push to `attendee/cruz-moreno`. See the implementation summary at the bottom of `plan.md` and the deferred-tasks section of the implementation report.
+
+**Organization**: Tasks are grouped by the two user stories from `spec.md` (US1 = find a product by name, US2 = clear no-results feedback). Each story's increment is independently testable.
+
+## Format: `[ID] [P?] [Story?] Description`
+
+- **[P]**: Can run in parallel (different files, no dependencies on incomplete tasks)
+- **[Story]**: Which user story this task belongs to (US1, US2). Setup/Foundational/Polish tasks have no story label.
+- Every task description includes the exact file path it touches.
+
+## Path Conventions
+
+Two-service Go monorepo, paths anchored at the repository root:
+
+- Backend service: `src/productcatalogservice/`
+- Frontend service: `src/frontend/`
+- Shared proto contract (UNCHANGED): `protos/demo.proto`
+
+---
+
+## Phase 1: Setup (Shared Infrastructure)
+
+**Purpose**: Confirm the working environment matches what `plan.md` assumes. No code is initialised — the repo already has both services.
+
+- [X] T001 Verify Go 1.22+ is installed and that `go mod download` succeeds in both `src/productcatalogservice/` and `src/frontend/` without modifying `go.mod`/`go.sum`
+
+---
+
+## Phase 2: Foundational (Blocking Prerequisites)
+
+**Purpose**: Core changes that BOTH user stories depend on. Until this phase is complete, neither story can be implemented or verified.
+
+**⚠️ CRITICAL**: No user story work can begin until this phase is complete.
+
+- [X] T002 Tighten `(*productCatalog).SearchProducts` in `src/productcatalogservice/product_catalog.go` to match the spec: trim the query with `strings.TrimSpace`, return an empty `SearchProductsResponse{}` when the trimmed query is empty, and match `strings.Contains(strings.ToLower(product.Name), strings.ToLower(query))` ONLY — remove the existing OR-clause that also matches on `product.Description`
+- [X] T003 [P] Extend `TestSearchProducts` in `src/productcatalogservice/product_catalog_test.go` into a table-driven test covering the behaviour matrix in `specs/002-product-search/contracts/search-products.proto.md`: exact match, mixed-case match, leading/trailing whitespace, substring inside name (e.g. `"alp"` returns the two Alpha products), no-match query, empty query, and a name-only assertion (add one mock product whose name does NOT contain the term but whose description does — confirm it is NOT returned)
+- [X] T004 [P] Add `searchProducts(ctx context.Context, query string) (*pb.SearchProductsResponse, error)` to `src/frontend/rpc.go`, mirroring the existing `getProducts` / `getProduct` pattern (call `pb.NewProductCatalogServiceClient(fe.productCatalogSvcConn).SearchProducts(ctx, &pb.SearchProductsRequest{Query: query})`)
+
+**Checkpoint**: Backend now honours the spec contract; frontend has a typed client wrapper. Both user stories can begin in parallel.
+
+---
+
+## Phase 3: User Story 1 - Find a product by typing part of its name (Priority: P1) 🎯 MVP
+
+**Goal**: A shopper can submit a query from a search box in the storefront header and see matching products laid out the same way as the regular catalog listing, then click through into the existing product detail page.
+
+**Independent Test**: From `quickstart.md`, run steps 1-5 and step 8: type `watch`, `WATCH`, `lass`, and `  watch  ` into the search box; in each case the expected match(es) appear on `/search?q=...`. Clicking a result navigates to the existing `/product/{id}` page.
+
+### Implementation for User Story 1
+
+- [X] T005 [P] [US1] Create `src/frontend/templates/search.html` defining a `"search"` template that renders the page chrome (`{{template "header" .}}` etc.) plus a product-card grid bound to `.results` using the same card markup currently used in `home.html`; for this story only the populated-grid branch is required (the empty-results branch is added in US2 / T010)
+- [X] T006 [US1] Add `(*frontendServer).searchHandler(w http.ResponseWriter, r *http.Request)` to `src/frontend/handlers.go`: read `q := strings.TrimSpace(r.URL.Query().Get("q"))`, call `fe.searchProducts(r.Context(), q)`, on error fall through to the existing error-rendering pattern used by sibling handlers, on success render the `"search"` template with the standard page context plus `query=q` and `results=resp.GetResults()` (the empty-query short-circuit is added in US2 / T009 — for US1 assume `q` is non-empty)
+- [X] T007 [US1] Register the route in `src/frontend/main.go` next to the other `r.HandleFunc` lines: `r.HandleFunc(baseUrl+"/search", svc.searchHandler).Methods(http.MethodGet, http.MethodHead)` (depends on T006)
+- [X] T008 [P] [US1] Add the search form to `src/frontend/templates/header.html` inside the existing `sub-navbar` container: `<form action="{{ $.baseUrl }}/search" method="GET" role="search"><input type="text" name="q" placeholder="Search products" aria-label="Search products" value="{{ $.searchQuery }}"><button type="submit">…</button></form>` (the `searchQuery` context key is set only by `searchHandler`; other handlers leave it absent and the template renders an empty `value=""`)
+- [X] T009 [US1] Manually verify quickstart.md steps 1-5 and step 8 (happy path, case-insensitivity, substring match, whitespace trim, click-through)
+
+**Checkpoint**: A shopper can search and find products. The feature is shippable as MVP at this point even without US2.
+
+---
+
+## Phase 4: User Story 2 - Receive clear feedback when nothing matches (Priority: P2)
+
+**Goal**: Shoppers who search for something the catalog doesn't carry, or who submit an empty/whitespace query, see an unambiguous, helpful response rather than an error or a blank screen.
+
+**Independent Test**: From `quickstart.md`, run steps 6 and 7: search `laptop` shows a "no results" panel with the search box pre-filled with `laptop`; submitting an empty or whitespace-only query yields `HTTP 302 → /` and the regular catalog view.
+
+### Implementation for User Story 2
+
+- [X] T010 [US2] In `src/frontend/handlers.go`, add the empty-query short-circuit to `searchHandler`: after trimming `q`, if `q == ""` call `http.Redirect(w, r, baseUrl+"/", http.StatusFound)` and `return` (placed before the gRPC call so an empty query never reaches the backend)
+- [X] T011 [US2] In `src/frontend/templates/search.html`, add an `{{ if .results }}…{{ else }}…{{ end }}` branch around the product grid: the `else` branch renders a "no results" panel containing an unambiguous message (e.g. `No products matched "{{ .query }}". Try a different search term.`) and keeps the header search box visible and pre-filled (the header form already binds to `$.searchQuery`, which `searchHandler` sets to `q` regardless of result count)
+- [X] T012 [US2] Manually verify quickstart.md steps 6 and 7 (no-results panel + empty-query redirect)
+
+**Checkpoint**: All spec acceptance scenarios pass. US1 and US2 are both independently demonstrable.
+
+---
+
+## Phase 5: Polish & Cross-Cutting Concerns
+
+**Purpose**: Verify the change set respects the technical constraints in `plan.md` and ships cleanly.
+
+- [X] T013 [P] Run `go vet ./...` and `go build ./...` inside `src/productcatalogservice/` and ensure both are clean
+- [X] T014 [P] Run `go vet ./...` and `go build ./...` inside `src/frontend/` and ensure both are clean
+- [X] T015 [P] Run `go test ./...` inside `src/productcatalogservice/` and confirm the extended `TestSearchProducts` plus the existing `TestGetProductExists`, `TestGetProductNotFound`, and `TestListProducts` all pass
+- [X] T016 [P] Confirm the working tree shows **zero** diff under `helm-chart/`, `kubernetes-manifests/`, `kustomize/`, `istio-manifests/`, `release/`, `terraform/`, `cloudbuild.yaml`, `skaffold.yaml`, AND `protos/demo.proto` — these were declared off-limits by the plan; any change here means we drifted from the constraints
+- [X] T017 Run the full end-to-end quickstart.md walk-through (all 8 steps) against a locally-running stack (skaffold or `go run .`) and capture any deviation as a follow-up
+
+---
+
+## Dependencies & Execution Order
+
+### Phase Dependencies
+
+- **Setup (Phase 1)**: No dependencies; T001 just confirms the toolchain.
+- **Foundational (Phase 2)**: Depends on Setup. Blocks BOTH user stories.
+- **User Story 1 (Phase 3)**: Depends on Foundational. Independent of US2.
+- **User Story 2 (Phase 4)**: Depends on Foundational. Builds on US1's handler and template files but each task is additive — it does NOT change US1 behaviour. Could in principle be implemented before US1 by a different developer if a handler stub is in place, but the natural order is US1 → US2.
+- **Polish (Phase 5)**: Depends on whichever user stories are intended to ship.
+
+### Task-Level Dependencies (within phases)
+
+- T002 → T003: same file (`product_catalog_test.go` references the updated semantics), but `[P]` is set because the test edits live in a different file from the implementation in T002. Run T002 first, then T003.
+- T006 → T007: T007 references `svc.searchHandler`, which must exist for `main.go` to compile.
+- T005 / T008 are in different files from T006/T007 and can run in parallel with them.
+- T010 edits the same file as T006 (`handlers.go`); do T006 first.
+- T011 edits the same file as T005 (`search.html`); do T005 first.
+- T015 depends on T002 and T003.
+- T013-T016 can all run in parallel once all earlier phases are complete.
+
+### Parallel Opportunities
+
+- Within Phase 2: T003 and T004 are `[P]` and touch different services — they can be done by two developers concurrently after T002 lands.
+- Within US1: T005 and T008 are `[P]` (different template files) and can run concurrently with T006; T007 must wait for T006.
+- Within Phase 5: T013, T014, T015, T016 are all `[P]`.
+- Across user stories: once Phase 2 is green, US1 and US2 can be staffed in parallel.
+
+---
+
+## Parallel Example: User Story 1
+
+```bash
+# After T002, T003, T004 are merged, two developers can fan out:
+Developer A:
+  Task: "Create src/frontend/templates/search.html (T005)"
+  Task: "Add searchHandler to src/frontend/handlers.go (T006)"
+  Task: "Register /search route in src/frontend/main.go (T007)"
+
+Developer B (in parallel):
+  Task: "Add search form to src/frontend/templates/header.html (T008)"
+```
+
+`T005` and `T008` touch different files from each other and from `main.go` / `handlers.go`, so the only sequencing constraint inside US1 is T006 → T007.
+
+---
+
+## Implementation Strategy
+
+### MVP First (User Story 1 Only)
+
+1. Complete Phase 1: Setup (T001) — one-line sanity check.
+2. Complete Phase 2: Foundational (T002, T003, T004) — backend tightened + tested, frontend RPC wrapper in place.
+3. Complete Phase 3: User Story 1 (T005-T009).
+4. **STOP and VALIDATE**: quickstart.md steps 1-5 and 8.
+5. Ship if ready. The no-results UX is mildly rough until US2 lands, but the feature delivers value as-is.
+
+### Incremental Delivery
+
+1. Foundation green → checkpoint.
+2. Add US1 → demo MVP.
+3. Add US2 → demo no-results & empty-query polish.
+4. Run Phase 5 polish gates → merge.
+
+### Parallel Team Strategy
+
+With two developers:
+
+1. Both pair on T002 / T003 (same file pair).
+2. Developer A picks up T004 + all of US1; Developer B preps the US2 edits (T010 patch on top of T006's handler, T011 patch on top of T005's template) and waits for US1 to merge before applying them.
+
+---
+
+## Notes
+
+- `[P]` tasks = different files, no dependencies on incomplete tasks.
+- `[US1]` / `[US2]` labels map tasks to the spec's user stories for traceability.
+- Each user story is independently completable and testable per quickstart.md.
+- T016 is the constraint-guard task — if it fails, the change drifted from the plan's "no new infra" rule and needs to be unwound before merge.
+- The branch / CI note in plan.md (`002-product-search` vs. `attendee/cruz-moreno`) is not a task here — it is an integration step the human handles after `/speckit-implement`.
+- Commit after each task or logical group; the `after_tasks` and `after_implement` hooks make this easy.
+- Avoid: regenerating protobuf code (the proto is unchanged), introducing new env vars, editing `helm-chart/` or `kubernetes-manifests/`, switching languages, or adding a new datastore — each of these is explicitly forbidden by `plan.md`'s Constraints section.
diff --git a/src/frontend/handlers.go b/src/frontend/handlers.go
index 33c94d8e21d..e8e844ed965 100644
--- a/src/frontend/handlers.go
+++ b/src/frontend/handlers.go
@@ -141,6 +141,70 @@ func (plat *platformDetails) setPlatformDetails(env string) {
 	}
 }
 
+// searchHandler implements the 002-product-search feature
+// (GET /search?q=...). See specs/002-product-search/contracts/http-search.md
+// for the contract.
+//
+//   - Trims whitespace from q.
+//   - If q is empty after trimming, redirects to the catalog (HTTP 302)
+//     so we never render an empty-results page for an empty query.
+//   - Otherwise calls SearchProducts and renders the "search" template,
+//     converting prices to the user's currency so the existing product-card
+//     markup (shared with home.html) renders consistently.
+func (fe *frontendServer) searchHandler(w http.ResponseWriter, r *http.Request) {
+	log := r.Context().Value(ctxKeyLog{}).(logrus.FieldLogger)
+
+	q := strings.TrimSpace(r.URL.Query().Get("q"))
+	if q == "" {
+		http.Redirect(w, r, baseUrl+"/", http.StatusFound)
+		return
+	}
+
+	log.WithField("query", q).WithField("currency", currentCurrency(r)).Info("search")
+
+	currencies, err := fe.getCurrencies(r.Context())
+	if err != nil {
+		renderHTTPError(log, r, w, errors.Wrap(err, "could not retrieve currencies"), http.StatusInternalServerError)
+		return
+	}
+	results, err := fe.searchProducts(r.Context(), q)
+	if err != nil {
+		renderHTTPError(log, r, w, errors.Wrap(err, "could not search products"), http.StatusInternalServerError)
+		return
+	}
+	cart, err := fe.getCart(r.Context(), sessionID(r))
+	if err != nil {
+		renderHTTPError(log, r, w, errors.Wrap(err, "could not retrieve cart"), http.StatusInternalServerError)
+		return
+	}
+
+	type productView struct {
+		Item  *pb.Product
+		Price *pb.Money
+	}
+	ps := make([]productView, len(results))
+	for i, p := range results {
+		price, err := fe.convertCurrency(r.Context(), p.GetPriceUsd(), currentCurrency(r))
+		if err != nil {
+			renderHTTPError(log, r, w, errors.Wrapf(err, "failed to do currency conversion for product %s", p.GetId()), http.StatusInternalServerError)
+			return
+		}
+		ps[i] = productView{p, price}
+	}
+
+	if err := templates.ExecuteTemplate(w, "search", injectCommonTemplateData(r, map[string]interface{}{
+		"show_currency": true,
+		"currencies":    currencies,
+		"query":         q,
+		"searchQuery":   q,
+		"results":       ps,
+		"cart_size":     cartSize(cart),
+		"banner_color":  os.Getenv("BANNER_COLOR"),
+	})); err != nil {
+		log.Error(err)
+	}
+}
+
 func (fe *frontendServer) productHandler(w http.ResponseWriter, r *http.Request) {
 	log := r.Context().Value(ctxKeyLog{}).(logrus.FieldLogger)
 	id := mux.Vars(r)["id"]
diff --git a/src/frontend/main.go b/src/frontend/main.go
index 754b653e51a..7bb0db5df6f 100644
--- a/src/frontend/main.go
+++ b/src/frontend/main.go
@@ -148,6 +148,7 @@ func main() {
 
 	r := mux.NewRouter()
 	r.HandleFunc(baseUrl+"/", svc.homeHandler).Methods(http.MethodGet, http.MethodHead)
+	r.HandleFunc(baseUrl+"/search", svc.searchHandler).Methods(http.MethodGet, http.MethodHead)
 	r.HandleFunc(baseUrl+"/product/{id}", svc.productHandler).Methods(http.MethodGet, http.MethodHead)
 	r.HandleFunc(baseUrl+"/cart", svc.viewCartHandler).Methods(http.MethodGet, http.MethodHead)
 	r.HandleFunc(baseUrl+"/cart", svc.addToCartHandler).Methods(http.MethodPost)
diff --git a/src/frontend/rpc.go b/src/frontend/rpc.go
index a1dd313847d..d193bd2b3db 100644
--- a/src/frontend/rpc.go
+++ b/src/frontend/rpc.go
@@ -54,6 +54,17 @@ func (fe *frontendServer) getProduct(ctx context.Context, id string) (*pb.Produc
 	return resp, err
 }
 
+// searchProducts is the 002-product-search client wrapper. Callers are
+// expected to have already trimmed the query (the storefront searchHandler
+// does this and short-circuits empty queries before calling). The
+// productcatalogservice trims defensively as well — see
+// specs/002-product-search/contracts/search-products.proto.md.
+func (fe *frontendServer) searchProducts(ctx context.Context, query string) ([]*pb.Product, error) {
+	resp, err := pb.NewProductCatalogServiceClient(fe.productCatalogSvcConn).
+		SearchProducts(ctx, &pb.SearchProductsRequest{Query: query})
+	return resp.GetResults(), err
+}
+
 func (fe *frontendServer) getCart(ctx context.Context, userID string) ([]*pb.CartItem, error) {
 	resp, err := pb.NewCartServiceClient(fe.cartSvcConn).GetCart(ctx, &pb.GetCartRequest{UserId: userID})
 	return resp.GetItems(), err
diff --git a/src/frontend/templates/header.html b/src/frontend/templates/header.html
index 21777c48a67..65b87cea53e 100644
--- a/src/frontend/templates/header.html
+++ b/src/frontend/templates/header.html
@@ -64,6 +64,10 @@
                     <img src="{{ $.baseUrl }}/static/icons/Hipster_NavLogo.svg" alt="" class="top-left-logo" />
                     {{ end }}
                 </a>
+                <form action="{{ $.baseUrl }}/search" method="GET" role="search" class="search-form d-flex align-items-center">
+                    <input type="text" name="q" value="{{ $.searchQuery }}" placeholder="Search products" aria-label="Search products" class="search-input" />
+                    <button type="submit" class="search-submit" aria-label="Submit search">Search</button>
+                </form>
                 <div class="controls">
 
                     {{ if $.show_currency }}
diff --git a/src/frontend/templates/search.html b/src/frontend/templates/search.html
new file mode 100644
index 00000000000..bcc970b8d53
--- /dev/null
+++ b/src/frontend/templates/search.html
@@ -0,0 +1,77 @@
+<!--
+ Copyright 2026 Google LLC
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+-->
+
+{{ define "search" }}
+
+{{ template "header" . }}
+<main role="main" class="home">
+
+  <div class="container-fluid">
+    <div class="row">
+
+      <div class="col-12 col-lg-12 px-10-percent">
+
+        <div class="row hot-products-row px-xl-6">
+
+          <div class="col-12">
+            <h3>Search results for &ldquo;{{ $.query }}&rdquo;</h3>
+          </div>
+
+          {{ if $.results }}
+
+            {{ range $.results }}
+            <div class="col-md-4 hot-product-card">
+              <a href="{{ $.baseUrl }}/product/{{ .Item.Id }}">
+                <img loading="lazy" src="{{ $.baseUrl }}{{ .Item.Picture }}">
+                <div class="hot-product-card-img-overlay"></div>
+              </a>
+              <div>
+                <div class="hot-product-card-name">{{ .Item.Name }}</div>
+                <div class="hot-product-card-price">{{ renderMoney .Price }}</div>
+              </div>
+            </div>
+            {{ end }}
+
+          {{ else }}
+
+            <div class="col-12">
+              <p>No products matched &ldquo;{{ $.query }}&rdquo;. Try a different search term.</p>
+            </div>
+
+          {{ end }}
+
+        </div>
+
+        <!-- Footer for larger screens. -->
+        <div class="row d-none d-lg-block home-desktop-footer-row">
+          <div class="col-12 p-0">
+            {{ template "footer" . }}
+          </div>
+        </div>
+
+      </div>
+
+    </div>
+  </div>
+
+</main>
+
+<!-- Footer for smaller screens. -->
+<div class="d-lg-none">
+  {{ template "footer" . }}
+</div>
+
+{{ end }}
diff --git a/src/productcatalogservice/product_catalog.go b/src/productcatalogservice/product_catalog.go
index bbc364cf191..2c05ad4bdd9 100644
--- a/src/productcatalogservice/product_catalog.go
+++ b/src/productcatalogservice/product_catalog.go
@@ -60,10 +60,19 @@ func (p *productCatalog) GetProduct(ctx context.Context, req *pb.GetProductReque
 func (p *productCatalog) SearchProducts(ctx context.Context, req *pb.SearchProductsRequest) (*pb.SearchProductsResponse, error) {
 	time.Sleep(extraLatency)
 
+	// Per the 002-product-search feature spec (FR-002, FR-004, FR-005, FR-006):
+	//   - trim leading/trailing whitespace
+	//   - case-insensitive substring match against Product.Name ONLY
+	//     (Description is intentionally NOT matched here)
+	//   - empty/whitespace-only query short-circuits to an empty result set
+	query := strings.ToLower(strings.TrimSpace(req.GetQuery()))
+	if query == "" {
+		return &pb.SearchProductsResponse{}, nil
+	}
+
 	var ps []*pb.Product
 	for _, product := range p.parseCatalog() {
-		if strings.Contains(strings.ToLower(product.Name), strings.ToLower(req.Query)) ||
-			strings.Contains(strings.ToLower(product.Description), strings.ToLower(req.Query)) {
+		if strings.Contains(strings.ToLower(product.Name), query) {
 			ps = append(ps, product)
 		}
 	}
diff --git a/src/productcatalogservice/product_catalog_test.go b/src/productcatalogservice/product_catalog_test.go
index 3ac9c06c824..fff8fa44818 100644
--- a/src/productcatalogservice/product_catalog_test.go
+++ b/src/productcatalogservice/product_catalog_test.go
@@ -51,6 +51,14 @@ func TestMain(m *testing.M) {
 		Id:   "abc004",
 		Name: "Product Gamma",
 	})
+	// Used by the 002-product-search regression: name does NOT contain "alpha"
+	// but description does. Search MUST NOT return this product for query
+	// "alpha" — locks in name-only matching (spec FR-004).
+	mockProductCatalog.catalog.Products = append(mockProductCatalog.catalog.Products, &pb.Product{
+		Id:          "abc005",
+		Name:        "Watch",
+		Description: "alpha numeric serial number engraved on the back",
+	})
 
 	os.Exit(m.Run())
 }
@@ -83,19 +91,110 @@ func TestListProducts(t *testing.T) {
 	if err != nil {
 		t.Fatal(err)
 	}
-	if got, want := len(products.Products), 4; got != want {
+	if got, want := len(products.Products), 5; got != want {
 		t.Errorf("got %d, want %d", got, want)
 	}
 }
 
+// TestSearchProducts exercises the 002-product-search contract semantics
+// (see specs/002-product-search/contracts/search-products.proto.md):
+//   - case-insensitive substring match against Product.Name only
+//   - leading/trailing whitespace is trimmed
+//   - empty / whitespace-only queries return no results (and never hit the catalog)
+//   - description matches are NOT returned
 func TestSearchProducts(t *testing.T) {
-	products, err := mockProductCatalog.SearchProducts(context.Background(),
-		&pb.SearchProductsRequest{Query: "alpha"},
-	)
-	if err != nil {
-		t.Fatal(err)
+	cases := []struct {
+		name      string
+		query     string
+		wantNames []string
+	}{
+		{
+			name:      "exact lower-case match returns both Alpha products",
+			query:     "alpha",
+			wantNames: []string{"Product Alpha One", "Product Alpha Two"},
+		},
+		{
+			name:      "upper-case query matches case-insensitively",
+			query:     "ALPHA",
+			wantNames: []string{"Product Alpha One", "Product Alpha Two"},
+		},
+		{
+			name:      "mixed-case query matches case-insensitively",
+			query:     "Alpha",
+			wantNames: []string{"Product Alpha One", "Product Alpha Two"},
+		},
+		{
+			name:      "leading and trailing whitespace is trimmed",
+			query:     "  alpha  ",
+			wantNames: []string{"Product Alpha One", "Product Alpha Two"},
+		},
+		{
+			name:      "substring inside a name still matches",
+			query:     "alp",
+			wantNames: []string{"Product Alpha One", "Product Alpha Two"},
+		},
+		{
+			name:      "exact match on a non-Alpha product",
+			query:     "delta",
+			wantNames: []string{"Product Delta"},
+		},
+		{
+			name:      "single-character substring match",
+			query:     "g",
+			wantNames: []string{"Product Gamma"},
+		},
+		{
+			name:      "no matches returns an empty result set",
+			query:     "zzz",
+			wantNames: nil,
+		},
+		{
+			name:      "empty query returns an empty result set (does NOT return ListProducts)",
+			query:     "",
+			wantNames: nil,
+		},
+		{
+			name:      "whitespace-only query returns an empty result set",
+			query:     "   ",
+			wantNames: nil,
+		},
+		{
+			name:      "description-only term does NOT match (name-only semantics)",
+			query:     "numeric",
+			wantNames: nil,
+		},
 	}
-	if got, want := len(products.Results), 2; got != want {
-		t.Errorf("got %d, want %d", got, want)
+
+	for _, tc := range cases {
+		t.Run(tc.name, func(t *testing.T) {
+			resp, err := mockProductCatalog.SearchProducts(context.Background(),
+				&pb.SearchProductsRequest{Query: tc.query},
+			)
+			if err != nil {
+				t.Fatalf("SearchProducts returned error: %v", err)
+			}
+			gotNames := make([]string, 0, len(resp.GetResults()))
+			for _, p := range resp.GetResults() {
+				gotNames = append(gotNames, p.GetName())
+			}
+			if !equalStringSlices(gotNames, tc.wantNames) {
+				t.Errorf("query %q: got results %v, want %v", tc.query, gotNames, tc.wantNames)
+			}
+		})
+	}
+}
+
+// equalStringSlices treats nil and []string{} as equivalent so a test case
+// can express "no results" as `nil` without depending on the implementation
+// returning a nil vs. zero-length slice.
+func equalStringSlices(a, b []string) bool {
+	if len(a) != len(b) {
+		return false
+	}
+	for i := range a {
+		if a[i] != b[i] {
+			return false
+		}
 	}
+	return true
 }