OpsFlow - Production-Oriented Full-Stack CMMS -- 2

I have already laid down the core of OpsFlow—a Flutter / Dart front-end, Go REST back-end, PostgreSQL database, and a Docker-based deployment stack complete with MinIO object storage, role-based auth, notifications, audit logs, and automated health checks.

For the very first public release I want to polish and ship a solid work-order workflow. The scope for this milestone is focused and clear: enable streamlined “work-order creation and assignment” from end to end.

What you will find waiting for you
• A clean Flutter UI skeleton and shared component library
• Fully documented Go micro-services with CRUD scaffolding in place
• Auth, user, asset, and inventory tables already seeded in PostgreSQL
• Docker-compose scripts for local orchestration, plus CI hooks for staging

What I need you to deliver
1. Front-end screens that let an authenticated user create a work order, pick assets, set priority, attach photos or manuals (stored in MinIO), and assign the task to another user.
2. Back-end endpoints that validate input, persist the order, update audit logs, and trigger existing notification hooks (e-mail + in-app).
3. Real-time status updates over WebSocket or SSE so assignees see new work instantly.
4. Unit and integration tests covering happy-path and failure cases.
5. A concise README update explaining local dev, migrations, and new environment variables.

Acceptance criteria
• Creating a work order inserts a row in the work_orders table with a unique sequential code.
• Assignment must enforce my current RBAC rules (admin, technician, manager already configured).
• Attachments are retrievable via signed MinIO URLs valid for 24 h.
• All new Go code reaches ≥ 85 % test coverage; Flutter widget tests run green in CI.
• docker compose up spins the entire stack with one command and the new feature works out of the box.

Preferred stack: Flutter 3, Dart 2.19+, Go 1.20+, GORM, PostgreSQL 15, Docker v24.

If this slice lands smoothly we will roll straight into progress tracking, completion, and review phases, so clean, idiomatic code and clear documentation are essential.