Browse a bay’s compatible module types

User intention

Review the compatible module types for a transceiver bay type.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both

BeforeThe defect at the parent commit

0:00.00 / 0:00.00Frame 0

Compare the manufacturer-labeled catalog with the bay’s model-only compatible list and inspect the sections below it.

AfterThe same script once the merged fix is applied

0:00.00 / 0:00.00Frame 0

Browse manufacturer-labeled compatible types, change column ordering, and inspect both bounded pages and the lower bay section.

How is it judged?

01 · Given

Restore the data and starting state.

A signed-in administrator is browsing module types on desktop. SFP28 transceiver bay has 38 assigned compatible module types, including distinct Cisco and Generic module types both named SFP-25G-SR-C. The starting filtered Module Types catalog visibly associates each model with its manufacturer.

02 · When

Perform the interaction.

Follow Module Bay Types in the Devices navigation, open SFP28 transceiver bay, review its compatible module types and available browsing controls, inspect the lower bay-information sections, and return to the beginning of the compatible collection.

03 · Judge

Rationale: Manufacturer and model together identify compatible module choices. A long model-only list obscures those distinctions and pushes other bay information out of reach; organized browsing supports comparison while retaining access to every type.

Require

On the bay detail page, associate each compatible model with its manufacturer so same-model types are distinguishable without opening individual records. Offer discoverable ordering by model and manufacturer and bounded browsing that reaches every assigned type, without requiring traversal of the entire collection to reach other bay information.

Allowed

A table, grouped rows, or another collection presentation is acceptable if manufacturer/model association remains clear and each item still leads to the correct module type; exact table classes, column placement, and full-width styling are not required.
Pagination, a separately scrollable collection, or another bounded collection mechanism is acceptable if all assigned types remain reachable and the current browsing location is understandable. No specific page size or number of pages is required.
Sorting controls may use column headings, a selector, or equivalent affordances. No particular initial order, sort algorithm, or placement of duplicate names is required.
Other bay sections may appear above, alongside, or independently of the collection. Scrolling is allowed; exact card placement and fitting every section into the initial viewport are not required.