Org Web Adapter

Editing hungryroot/jira/be_6889_remove_references_to_deprecated_foods_and_recipes_routes.org

:PROPERTIES:
:ID:       7086172d-3413-4bf9-ad74-2cc9371cc69c
:END:
#+title: BE-6889 Remove references to deprecated /foods and /recipes routes

- source :: https://hungryroot.atlassian.net/browse/BE-6889
- tags ::   [[id:3a477c02-e26d-40f7-a719-0aa1cd169dd8][Hungryroot API Project]] 
- epic ::   [[id:86327fb4-0f66-4bc6-9068-c414cea77042][EP-411 Eng Parking Lot]]
- sprint :: [[id:26939bb8-164c-402e-8a6a-6ae8c99d3e59][HR BE Sprint 102]]
- status :: [[id:a0ae5b03-760c-432f-8e3e-ff8c290676d0][Status - Needs QA]]

* Tasks
** DONE Ask Cursor to review usage of the legacy endpoints :api:v1:work:hungryroot:ep411:be6889:chore:sprint102:
:PROPERTIES:
:ID:       3f4f9758-094a-952e-0828-30a2e9079d22
:END:
** DONE Open a pull request for BE-6889 :api:v1:work:hungryroot:ep411:be6889:chore:sprint102:
:PROPERTIES:
:ID:       a3e881ee-dc1a-e75a-afce-517450845a9a
:END:
* Description
The legacy /foods and /recipes routes are now permanently redirected (301) to
their corresponding new pages in Production. We should remove any remaining
references to these deprecated routes across the codebase to avoid unnecessary
redirects, reduce technical debt, and ensure all internal navigation and links
point directly to the new canonical pages.

Scope / Tasks

Identify and remove references to /foods and /recipes in:

Backend code (routes, serializers, redirects, constants)

Frontend code (links, navigation, config, hardcoded URLs)

Templates, emails, and notifications

Tests, fixtures, and mocks

Documentation and comments, where applicable

Replace with the appropriate new canonical URLs.

Verify no internal requests or links rely on the 301 redirects.

Confirm in production monitoring (e.g., logs or Datadog) that traffic to /foods
and /recipes is no longer originating from first-party code after changes are
deployed.

Acceptance Criteria

No first-party code references /foods or /recipes.

All internal links route directly to the new pages without triggering 301
redirects.

Tests pass and no regressions are introduced.

Post-deployment verification shows a reduction or elimination of internal
traffic to the deprecated routes.