Cleanup: Remove outdated workaround comments

The printf issue is specific to app_main after task_spawn, not within
task functions themselves. Clean up misleading workaround comments.

Task functions can printf normally - they run in their own context with
proper stack and scheduler state.

Author: jserv

app/mutex.c

@@ -18,7 +18,6 @@ static int currently_in_critical_section = 0;
 /* Enhanced Task A */
 void task_a(void)
 {
-    /* WORKAROUND: Printf may hang - skip diagnostic */
     printf("Task A (ID %d) starting...\n", mo_task_id());
 
     for (int i = 0; i < MAX_ITERATIONS; i++) {
@@ -71,7 +70,6 @@ void task_a(void)
 /* Enhanced Task B */
 void task_b(void)
 {
-    /* WORKAROUND: Printf may hang - skip diagnostic */
     printf("Task B (ID %d) starting...\n", mo_task_id());
 
     for (int i = 0; i < MAX_ITERATIONS; i++) {
@@ -132,7 +130,6 @@ void task_b(void)
 /* Simple monitor task */
 void monitor_task(void)
 {
-    /* WORKAROUND: Printf may hang - skip diagnostic */
     printf("Monitor starting...\n");
 
     int cycles = 0;