Add food-delivery category schema

[keepsloading]

Goal

Add a food-delivery category schema for apps that understand meal and ordering preferences.

This should help Memact turn food-delivery activity into user-readable Wiki entries that users can approve, edit, reject, or delete.

Context examples

Food-delivery apps may know things like:

• preferred cuisines
• disliked cuisines
• common order timing
• budget range signals
• dietary preferences the user explicitly chooses to store
• repeated restaurants
• delivery vs pickup preferences
• temporary cravings vs stable preferences

Work to do

• Define useful context fields for the food-delivery category
• Add example raw app context dumps
• Add normalized context examples
• Add user-facing Wiki entry templates
• Mark fields that require extra care clearly
• Suggest category-level permissions apps should request
• Add tests for safe context shaping

Important product rule

Do not treat every order as a stable preference. Shared orders, temporary cravings, and one-off situations should be modeled carefully.

Acceptance criteria

• Schema separates stable preferences from temporary food intent
• Raw app input examples exist
• Normalized output examples exist
• Wiki entry examples are human-readable
• Tests cover at least one valid and one misleading order case

[BHOGALA-SRIKA]

Hi! I'm an SSoC Season 5 contributor. I'd like to work on this issue. I'll define the context fields, raw examples, normalized examples, Wiki entry templates, and basic tests for this category. Can I be assigned?

[keepsloading]

Assigned to you, @BHOGALA-SRIKA.

Please keep the first PR focused on the food-delivery category schema. Include useful context fields, raw input examples, normalized outputs, Wiki entry examples, permission suggestions, and basic tests.

Main rule: do not treat every order as a stable preference. Shared orders, temporary cravings, and one-off orders should be modeled carefully.