/**
 * Fixture for the `stock-adjustment-processing` business flow.
 *
 * Auth is handled by the shared `./user` fixture, whose `page` is already signed
 * in for real through the app's OAuth hosted login as a broadly permissioned
 * admin. That single actor holds the inventory permission gating both the
 * Inventory Manager actions (create / submit / cancel) and the Approver's
 * confirm / reject on the detail screen, so one authenticated page drives the
 * whole flow end to end (separation of duties is not enforced at the application
 * level, per the actor docs).
 *
 * This flow's prerequisites (items, storage locations, inventory) all come from
 * seed data, so there are no flow-specific data fixtures to add on top.
 */
export { test, expect } from "./user";