JavaScript track: exercises 06 and 07 appear to be in the wrong order

Summary

06-discover-connected-crimes.md references code that's only introduced in 07-solve-the-crime.md:

• Around line 238, it calls this.orchestrationClient.chatCompletion(...), but orchestrationClient as a class field is only declared and constructed in exercise 07's Step 1 (07-solve-the-crime.md, "Add orchestrationClient as a class field and initialize it in the constructor").
• Around line 213, it instructs learners to add the new node "before leadDetectiveNode" — but leadDetectiveNode is also only created in exercise 07.

Effect

Following the exercises in their numbered order (06 then 07), a learner's investigationWorkflow.ts wouldn't type-check at exercise 06's step — this.orchestrationClient doesn't exist as a class member yet, and leadDetectiveNode doesn't exist to insert before.

Suggested fix

Either:

1. Swap the exercise order (make current 07's class-field/constructor setup + Lead Detective node come before current 06's Intelligence Researcher node), or
2. Move the orchestrationClient class-field/constructor setup into exercise 06 itself, and have exercise 07 only add leadDetectiveNode.

Either way, the sequencing needs to match what the code in each step actually depends on.

Environment

Reproduced on a personal SAP AI Core tenant, JavaScript/TypeScript track, exercises 01–07 followed in numbered order.

Comienza con 06-discover-connected-crimes.md y 07-solve-the-crime.md, comparando los pasos referenciados de investigationWorkflow.ts y su orden numerado. Comprueba que orchestrationClient y leadDetectiveNode se introduzcan antes de que el ejercicio 06 los use y, después, sigue los ejercicios 01–07 para confirmar que el flujo de trabajo de JavaScript/TypeScript pasa la comprobación de tipos en cada paso.