fleetbase/fleetbase/issues/559

[roncodes]

View bug reported on fleetbase/fleetbase#559 & patch made in fleetops which might need to be made in storefront fleetbase/fleetops@8603f93

[github-actions]

Triage comment:

The issue asks whether a FleetOps bugfix from fleetbase/fleetops#251 should also be applied in Storefront. I could not access the linked GitHub issue/PR from this environment, so this triage is based on the local Storefront code and should not assume the exact FleetOps patch.

Likely affected Storefront areas:

• Storefront order-config support in server/src/Support/Storefront.php.
• Store/network default order config storage and fallback logic in server/src/Models/Store.php, server/src/Models/Network.php, and server/migrations/2025_09_01_041353_add_default_order_config_column.php.
• Checkout order creation in server/src/Http/Controllers/v1/CheckoutController.php, which already sets order_config_uuid from the store/network.
• Store/network settings UI for selecting “Default Order Config”.
• Possible gap: server/src/Observers/OrderObserver.php exists and sets a default order_config_uuid, but it is not registered in StorefrontServiceProvider::$observers.

This does not look ready for agent implementation yet because the issue body does not describe the actual bug or expected behavior, and the referenced FleetOps patch could not be verified. If the intended change is narrowly to mirror FleetOps order-config assignment behavior, it is probably safe for agent implementation after confirming the exact diff and avoiding broader checkout/order-flow rewrites.

Documentation impact for fleetbase/fleetbase.io: likely needed if this changes visible Storefront configuration behavior, such as default order config selection for stores/networks or how Storefront orders inherit flows. No docs impact if the final patch is only an internal bugfix preserving existing behavior.

API reference impact for fleetbase/postman: likely no impact for a purely internal fallback/observer fix. API spec review is needed if request/response schemas, validation, or exposed store/network fields around order_config_uuid change.

Suggested validation for the implementing agent:

• composer test:lint
• composer test:types
• composer test:unit or targeted backend tests if added
• pnpm lint
• pnpm test:ember if UI/model behavior changes
• Checkout smoke coverage for store and network order creation assigning the expected order_config_uuid

Blocking questions:

• What exact behavior from fleetbase/fleetbase#559 should Storefront reproduce?
• Please paste or summarize the relevant fleetbase/fleetops#251 diff, since the linked patch is the only concrete implementation reference.
• Should Storefront register its existing OrderObserver for Fleetbase\FleetOps\Models\Order, or should order config assignment remain limited to Storefront checkout creation paths?

AGENT_STATUS: blocked_needs_human