Fix RST indentation errors causing build failure

Fixed "Unexpected indentation" errors in three files:
- command-compositions.rst: Flattened nested bullets describing parallel group implementation into single bullet
- structuring-v3-project.rst: Flattened nested directory tree into single line description
- telemetry-and-debugging.rst: Flattened nested bullets under "Scheduler events" into single bullet

All ERROR-level indentation issues resolved. Build now passes.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: jasondaming

source/docs/software/commandbased/commands-v3/command-compositions.rst

@@ -32,13 +32,7 @@
    Explain parallel command groups in detail. Cover:
    - What parallel groups do: run multiple commands simultaneously
    - How to create a parallel group
-   - Note: All composition groups (parallel, race, deadline) are implemented as parallel groups with different configurations:
-     - Parallel groups have _n_ required commands and _m_ optional commands
-     - The group exits once all _n_ required commands have exited
-     - "Traditional" parallel groups: _m_ = 0 (every command is required)
-     - Race groups: _n_ = 0 (every command is optional, exits when any finishes)
-     - Deadline groups: both _n_ and _m_ are nonzero (mix of required and optional)
-     - Note: v2 deadlines were special case where _n_ = 1 and _m_ ≥ 1; v3 deadlines are generalized
+   - Note: All composition groups (parallel, race, deadline) are implemented as parallel groups with different configurations: Parallel groups have _n_ required commands and _m_ optional commands. The group exits once all _n_ required commands have exited. "Traditional" parallel groups: _m_ = 0 (every command is required). Race groups: _n_ = 0 (every command is optional, exits when any finishes). Deadline groups: both _n_ and _m_ are nonzero (mix of required and optional). Note: v2 deadlines were special case where _n_ = 1 and _m_ ≥ 1; v3 deadlines are generalized.
    - Requirements handling with overlapping requirements
    - What happens if one command is interrupted
    - Common use cases for parallel groups

source/docs/software/commandbased/commands-v3/structuring-v3-project.rst

@@ -12,18 +12,7 @@
    - Where command functions/classes should be organized
    - Organization of constants and configuration
    - Separation of concerns between different code areas
-   - Example directory tree:
-     - Autos.java
-     - ControllerBindings.java
-     - Main.java
-     - Robot.java
-     - mechanisms/
-       - drive/
-         - DriveConstants.java
-         - Drive.java
-       - elevator/
-         - ElevatorConstants.java
-         - Elevator.java
+   - Example directory tree: Autos.java, ControllerBindings.java, Main.java, Robot.java, mechanisms/ (with subdirectories per mechanism like drive/ containing DriveConstants.java and Drive.java, elevator/ containing ElevatorConstants.java and Elevator.java)
 
 ## Robot.java and Controller Bindings
 

source/docs/software/commandbased/commands-v3/telemetry-and-debugging.rst

@@ -9,9 +9,7 @@
    Overview of telemetry features in v3. Cover:
    - Telemetry API and Epilogue compatibility (protobuf serialization)
    - Mechanism state visibility
-   - Scheduler events
-     - Detail the subtypes of `SchedulerEvent` and when they are emitted
-     - Add event listeners to listen for them
+   - Scheduler events: Detail the subtypes of `SchedulerEvent` and when they are emitted. Add event listeners to listen for them.
    - Command lifecycle events
    - Priority and interruption logging
    - How telemetry integrates with the scheduler