fix: prevent orchestrator_priority null constraint violation on order creation

[roncodes]

Problem

When a user creates an order via the order/form component without filling in the orchestrator constraints section (Orchestrator Priority, Required Skills, Time Window), the following error is thrown:

SQLSTATE[23000]: Integrity constraint violation: 1048
Column 'orchestrator_priority' cannot be null

Root Cause

The migration 2026_04_08_000003_add_orchestrator_columns_to_orders_table defines orchestrator_priority as NOT NULL with a database-level default(50). However, MySQL's column default is only used when the column is omitted from the INSERT statement entirely. When Eloquent receives an explicit null for the key, it includes orchestrator_priority = NULL in the INSERT, which violates the NOT NULL constraint and bypasses the DB default.

Both controllers use $request->only([..., 'orchestrator_priority']), which returns null for any key absent from the request payload. That null is then forwarded directly to Order::create() / Order::update().

Fix — Defence-in-depth across four layers

1. Order model — $attributes default

Added protected $attributes = ['orchestrator_priority' => 50] so every new Order instance starts with a valid value before any input is applied.

2. Order model — setOrchestratorPriorityAttribute mutator

A new Eloquent mutator coerces null or any non-numeric value to 50 at the model layer, ensuring the constraint can never be violated regardless of the call site — including future code paths not yet written.

3. Controllers — explicit null-guard before create / update

Both Api\v1\OrderController (create + update) and Internal\v1\OrderController (createRecord) now check whether orchestrator_priority is missing or non-numeric and default it to 50 before passing $input to Eloquent. This mirrors the existing pattern already used for type and status.

4. New migration — make column nullable for existing installations

Added 2026_04_20_000001_make_orchestrator_priority_nullable_on_orders_table which alters the column to nullable on databases that have already run the original migration. The application layer guarantees 50 is always written, so NULL will not appear in practice; the nullable flag is a belt-and-suspenders safety net.

Files Changed

File	Change
server/src/Models/Order.php	Added $attributes default + setOrchestratorPriorityAttribute mutator
server/src/Http/Controllers/Internal/v1/OrderController.php	Null-guard in createRecord before-callback
server/src/Http/Controllers/Api/v1/OrderController.php	Null-guard in both create and update methods
server/migrations/2026_04_20_000001_make_orchestrator_priority_nullable_on_orders_table.php	New migration to alter column on existing DBs

Testing

To reproduce the bug before this fix:

1. Open the order creation form
2. Fill in all required fields but leave the Orchestrator Priority field blank
3. Submit — the SQLSTATE[23000] error is returned

After this fix, the order is created successfully with orchestrator_priority = 50 (the default).