docs: number all tasks for reference

Assigned reference numbers to all remaining tasks in documentation:
- Task #34: Full STL Removal
- Task #35: CRT Replacement
- Task #36: Blender Exporter
- Task #37: Asset Ingestion
- Task #38: Runtime Loader
- Task #39: Visual Debugging System
- Task #40: Advanced Lighting & Transparency
- Task #41: Spectrogram Editor HTML Tool
- Task #42: Vectorial Spectrogram Reader (C++)
- Task #43: Spectrogram Drawing Bricks

Ensured consistent task numbering across PROJECT_CONTEXT.md and TODO.md.

3 files changed, 8 insertions, 8 deletions

diff --git a/doc/3D.md b/doc/3D.md
index e944cbe..5c5d1bd 100644
--- a/doc/3D.md
+++ b/doc/3D.md
@@ -35,16 +35,16 @@ removed with STRIP_ALL) that:
    d) displays the ray/object intersection interactively
    e) show the lights (direction, cone, ...), display their shadow-map in 3d and on-screen (2d).
 
-This must be captured and tracked as a sub-task
+This must be captured and tracked as **Task #39: Visual Debugging System**.
 
 
 ## future step
 
 Have an exporter from Blender modelling software. That would be a converter
 from simple blender-exported files to our internal format (as an asset for
-our AssetManager or as c++ code directly)
+our AssetManager or as c++ code directly) - **Task #36: Blender Exporter**.
 
 ## latter improvement
 
 How to handle transparency? Multi-Ray-casting?
-We need to think about the lighting strategy.
+We need to think about the lighting strategy. - **Task #40: Advanced Lighting & Transparency**.
diff --git a/doc/ASSET_SYSTEM.md b/doc/ASSET_SYSTEM.md
index 5f89380..aea99a2 100644
--- a/doc/ASSET_SYSTEM.md
+++ b/doc/ASSET_SYSTEM.md
@@ -268,4 +268,4 @@ For the **64k goal**, prioritize in this order:
 2. **Task #29** (Shader Minification) - Easy win, low risk
 3. **Task #28** (Spectrogram Quantization) - Medium effort, high impact
 4. **Task #18.1** (3D Assets) - Once size budget allows
-5. **Full STL Removal** - Deferred to final optimization phase.
+5. **Task #34: Full STL Removal** - Deferred to final optimization phase.
diff --git a/doc/SPEC_EDITOR.md b/doc/SPEC_EDITOR.md
index cde0cdd..497a5a2 100644
--- a/doc/SPEC_EDITOR.md
+++ b/doc/SPEC_EDITOR.md
@@ -1,4 +1,4 @@
-# spectrogram editing tool in a browser
+# spectrogram editing tool in a browser (Task #5)
 
 The sub-project is about have an editing tool in a browser
 that will allow generating, editing, compacting .spec files
@@ -24,17 +24,17 @@ to the synth
 ## the work
 
 Analyze the requirement for the HTML tool. It must remain simple and easy to
-use. Don't over-engineer it.
+use. Don't over-engineer it. - **Task #41: Spectrogram Editor HTML Tool**.
 Still, the tool must have a decent load/save offer, to:
   * load the .wav
   * save the .spec
   * save/export the descriptive compressed version in vectorial form (like the SVG format, in fact)
   * be able to load this vectorial form
 
-Then we need a reader for the vectorial form in c++ to use in the demo.
+Then we need a reader for the vectorial form in c++ to use in the demo. - **Task #42: Vectorial Spectrogram Reader (C++)**.
 We also need to elementary tools / bricks to: draw a line / bezier curve /
 rectangle, ellipse, etc. in frequency domain, to generate the spectrogram on
-the flight.
+the flight. - **Task #43: Spectrogram Drawing Bricks**.
 We also need controllable random noise generation to add some 'texture' to
 the spectrogram.