Motir

Estimate: 40m · Depends on: 2.7.4

End-to-end browser test (tests/e2e/work-item-type.spec.ts) closing the story from the user’s seat: pick a type + executor on create, see them on the detail, then filter the list by type.

The spec.

1. Sign in as zhuyue@motir.co on the seeded moooon/motir tenant (the existing signIn helper — no new auth plumbing).
2. Open the issue create modal; choose kind = task (a leaf), then pick type = code — assert the executor control SEEDED to coding_agent (the default map). Create it. Open a second create, pick type = manual — assert the executor seeded to human; OVERRIDE it to coding_agent and assert the override sticks; create it.
3. On the first item’s detail rail, assert the hued code type chip + the coding_agent executor indicator render; assert they are inline-editable (open the picker).
4. Assert the type picker is ABSENT when the chosen kind is a story (leaf-only) — open a create, pick kind = story, confirm no type control.
5. On /issues, build a filter type = code over the 6.1.1 filter builder — assert the first item is present and the manual item is absent; switch to type = manual and assert the inverse.

Acceptance criteria

• pnpm test:e2e work-item-type passes locally + in CI.
• The spec asserts: the executor default-seeds per the map (code → coding_agent, manual → human), an override sticks, the detail chip + indicator render + edit, the type control is leaf-only (absent for story), and the type filter slices the list correctly both ways.
• The spec uses the established E2E patterns (the signIn helper, the combobox-option selectors, explicit waits — no fixed sleeps; mind the combobox-option-name gotcha: option name = label + secondary).

Context refs

• 2.7.4 (the picker UI under test), 2.7.6 (the type filter facet under test).
• motir-core/tests/e2e/ — the existing create-modal + filter E2E patterns (sign-in helper, combobox selectors) to mirror.
• 2.7.1 — the design panels the rendered surfaces must match.