Separate unit placements from shift duty assignments.

Roster no longer writes temporary staff assignments; unit assignment UI drops shift fields and labels clarify the two workflows.

Co-authored-by: Cursor <cursoragent@cursor.com>

tests/Feature/CareStaffManagementTest.php

@@ -176,7 +176,6 @@ class CareStaffManagementTest extends TestCase
                 'care_unit_id' => $floatPool->id,
                 'kind' => 'primary',
                 'assignment_role' => 'float_nurse',
-                'shift_code' => 'rotating',
                 'starts_on' => now()->toDateString(),
                 'status' => 'active',
             ])
@@ -189,7 +188,6 @@ class CareStaffManagementTest extends TestCase
                 'care_unit_id' => $labour->id,
                 'kind' => 'temporary',
                 'assignment_role' => 'midwife',
-                'shift_code' => 'night',
                 'starts_on' => now()->toDateString(),
                 'ends_on' => now()->toDateString(),
                 'status' => 'active',
@@ -209,8 +207,10 @@ class CareStaffManagementTest extends TestCase
         $this->actingAs($this->owner)
             ->get(route('care.staff-assignments.index'))
             ->assertOk()
+            ->assertSee('Unit assignments')
             ->assertSee('Float Pool')
-            ->assertSee('Labour Ward');
+            ->assertSee('Labour Ward')
+            ->assertDontSee('>Shift<', false);
     }
 
     public function test_temporary_assignment_requires_unit(): void