Org Web Adapter

Editing journals/2026_07_28.org

:PROPERTIES:
:ID:       29abd9d6-dc52-48f6-924a-47a38fb9d7a3
:END:
#+title: 2026-07-28

* Tasks :work:hungryroot:
** DONE Review Claude's BE-8166 output, open PR
:PROPERTIES:
:ID:       9bf78f5d-030e-d0ce-02f0-9e60c849dacd
:END:
** DONE Look for more V1 endpoints to remove from mobile web :chore:
:PROPERTIES:
:ID:       a1bc08eb-04e9-7363-cd25-f0e875cbf31d
:END:
** DONE Finsh cleaning up the cookbook autotagger BE-8045
:PROPERTIES:
:ID:       ab0aa839-0ccf-c949-2793-9144bda2771f
:END:
** DONE Experiment with Gherkin tests on backend
:PROPERTIES:
:ID:       e3c39813-9f06-67ef-67ed-0042fb525a4b
:END:

- Note taken on [2026-07-28 Tue 14: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).
    
** DONE Try git-native sessions in hungryroot using sesh 
:PROPERTIES:
:ID:       6fe433a9-ca48-7d56-c1f2-8fb39156c0de
:END:
** DONE Fix up building releases for sesh 
:PROPERTIES:
:ID:       31dddc71-f9ec-8b9e-66b9-78248d7a42b2
:END:

- Note taken on [2026-07-28 Tue 15: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.
  
** DONE Follow up on un-auth'd home feed project
:PROPERTIES:
:ID:       b569dc9b-82ad-ad3a-8b7b-9d3119de9ecc
:END:
* Meetings :work:hungryroot:meeting:
** DONE Popsicle Weekly standup 
:PROPERTIES:
:ID:       8416c83e-232e-4d68-6658-55f4626fdfce
:END:
<2026-07-28 Tue 14:00-14:30>