Add stage crew assignments with timeline visualization

[Tim020]

Summary

Adds a complete crew assignment feature to the stage management system, enabling users to assign crew members to props and scenery items with full timeline visualization and conflict detection.

Phased implementation

• Phase 1 (9352d7b): Backend API — CrewAssignment model, Alembic migration, REST endpoints with validation and conflict detection
• Phase 2 (312a7f5): Timeline side panel — crew list in the stage timeline sidebar with add/remove UI
• Phase 3 (f661795): Stage Manager UI — crew assignment management within the Stage Manager panel
• Phase 4 (fc68af7): Timeline visualization — crew assignment bars on the stage timeline with overlap/conflict detection
• Phase 5 (e217365): Crew names in Plan modal and orphan warning dialogs
• Phase 6 (4e60649): User documentation with screenshots

Supporting changes

• Fix module discovery prefix collision filtering out crew.py controller (142b508)
• Fix ruff import sorting in CrewAssignment migration (e59ff6a)
• Fix ruff formatting in block_computation.py (f9ca833)
• Reduce test code duplication with shared stage fixtures (2388568)
• Fix error message field mismatch in crew assignment Vuex actions (e6157b7)

Test plan

• Backend: pytest suite covers CRUD, validation, conflict detection, and cascade deletion
• Frontend: crew assignments appear in timeline side panel and Stage Manager
• Timeline: crew bars render correctly with conflict highlighting
• Plan modal and orphan warnings display crew names
• Error messages from the server surface correctly in toast notifications

🤖 Generated with Claude Code

[github-actions]

Client Test Results

99 tests  +16   99 ✅ +16   0s ⏱️ ±0s
 4 suites + 1    0 💤 ± 0 
 1 files   ± 0    0 ❌ ± 0 

Results for commit e6157b7. ± Comparison against base commit 3d9e56d.

♻️ This comment has been updated with latest results.

[github-actions]

Python Test Results

  1 files  ± 0    1 suites  ±0   50s ⏱️ -1s
506 tests +59  506 ✅ +59  0 💤 ±0  0 ❌ ±0 
511 runs  +59  511 ✅ +59  0 💤 ±0  0 ❌ ±0 

Results for commit e6157b7. ± Comparison against base commit 3d9e56d.

♻️ This comment has been updated with latest results.

[Tim020]

Code review

Found 1 issue:

1. Frontend error handling reads errorData.error but backend sends {"message": ...}, so specific error messages are never displayed to the user -- they always see the generic fallback instead. The backend defines detailed error constants (e.g., "Either prop_id or scenery_id must be provided", "Crew assignment already exists") that will never reach the user.

Frontend (client/src/store/modules/stage.js):

DigiScript/client/src/store/modules/stage.js

Lines 455 to 460 in f9ca833

	} else {
	const errorData = await response.json().catch(() => ({}));
	const errorMsg = errorData.error || 'Unable to add crew assignment';
	log.error(errorMsg);
	Vue.$toast.error(errorMsg);
	return { success: false, error: errorMsg };

Backend (server/controllers/api/show/stage/crew_assignments.py):

DigiScript/server/controllers/api/show/stage/crew_assignments.py

Lines 93 to 96 in f9ca833

	if crew_id is None:
	self.set_status(400)
	await self.finish({"message": ERROR_CREW_ID_MISSING})
	return

Fix: change errorData.error to errorData.message on line 457 of stage.js (and similarly for DELETE_CREW_ASSIGNMENT if applicable).

🤖 Generated with Claude Code

_{- If this code review was useful, please react with 👍. Otherwise, react with 👎.}

[sonarqubecloud]

Quality Gate passed

Issues
19 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.0% Duplication on New Code

See analysis details on SonarQube Cloud