docs: week 3 task 4 report (selection behavior audit)

Week-3/Task-4/report.md

@@ -1 +1,33 @@
-# Task 4 Report
+# Selection Audit Report: Week 3 Task 4 - Multi-Selectable Objects
+
+## Objective
+Evaluate the scalability and reliability of selection behavior across multiple 3D objects.
+
+## Audit Test Cases & Results
+- **Native 3D Selection**: [FAIL] Continued lack of support for direct 3D interaction.
+- **Scaling to Multiple Objects (Sphere, Cube, Torus)**: [FAIL] Managing "Single Select" via manual button triggers is tedious and high-risk.
+- **Visual Feedback**: [PASS] Property shifts (scaling/glow) are visually consistent across the Sphere/Cube/Torus.
+- **Persistence**: [FAIL] Selection state resets on browser refresh.
+
+## Observations
+- **Missing Primitives**: **Selected State Management** & **Native 3D Raycasting**.
+- **State Complexity**: Managing "Deselect" logic is the most difficult part of the workflow.
+- **Usefulness**: Limited to simple 2-3 object toggles. Not suitable for complex parts-selection or deep tours.
+
+## Classification
+- **Component Limitation**: Critical (No Selection Group component).
+- **Event System Limitation**: Critical (No 3D Click triggers).
+- **Editor UX**: Fragile.
+
+## Reliability Verdict
+**NOT SUPPORTED (for Native 3D Selection) / FRAGILE (Simulated)**
+
+---
+
+## Product Lens
+- **Is this pattern useful for real customers?**: Yes, but the current implementation is too hard to maintain.
+- **Does Thob feel strong enough for this use case?**: **No**. It lacks the "Smart" selection logic found in other 3D builders.
+- **What would improve the experience?**: A "RadioGroup" equivalent for 3D meshes that manages mutual exclusivity automatically.
+
+## Recommendation
+This is the highest priority for interaction improvement. Thob should introduce a **"Selection Group"** logic node that handles the "Single Select / Multi Select" rules automagically for any mesh added to the group.