2026-07-28

Tasks

workhungryroot

chore

- Note taken on Tue Jul 28, 202614:38

No new gherkin framework needed. Repo got no pytest-bdd/behave infra, adding one = new dep + tooling overhead for

one feature. Against YAGNI rule here.

But scenarios still worth port — as regular pytest tests with descriptive names/docstrings mirroring

Given/When/Then. Ticket BE-8166 logic (ingredient availability → pairing in-stock → Braze event) is pure backend

domain logic, not UI-specific. Most of those Gherkin scenarios probably describe:

- ingredient combos in/out of stock

- pairing availability computed correctly

- event fires/doesn't fire

That's exactly what unit/integration tests in app/tests/ should cover already. Split:

- Backend-testable: any scenario about availability computation, event payload, event triggering conditions → write

as pytest, Given/When/Then in docstring or comments for traceability back to doc.

- Frontend-testable: anything about UI display of in-stock badge, client-side rendering, user-facing copy → belongs

in frontend suite, not here.

Recommend: keep Gherkin doc as spec/traceability artifact (source of truth per your existing pattern — see

feedback_spec_doc_source_of_truth]] memory), translate scenarios 1:1 into pytest test names/docstrings, skip

introducing actual .feature files unless multiple teams need to read/run same suite non-technically (e.g. QA

authoring scenarios themselves).

- Note taken on Tue Jul 28, 202615:13

Got releases working, so you can now download the proper arch version directly from github.

This should make it easier for folks to get started with this tool. A skill

file and a binary somewhere on their path ... and honestly agents can probably

pull and use it themselves too in abitrary sessions.

workhungryrootmeeting

Tue Jul 28, 202614:00–14:30