docs: define recipe creation target architecture

[dgee2]

Why

The Menu app can currently create only a minimal recipe with a name and ingredient links, which is not enough for real recipe authoring, search, sharing, or public display. This spec documents a target architecture so future implementation work can extend the existing stack coherently across the frontend, API, and database.

Summary

This PR adds a detailed architecture spec for recipe creation and lifecycle management in docs/specs/recipe-creation-target-architecture.md.

It covers:

• the current state of recipe support in the frontend, API, and database
• the target data model for recipes, ingredients, steps, ownership, sharing, publication, and search
• naming decisions for the new domain concepts
• SQL Server full-text search as the initial search architecture for recipe name, ingredients, and recipe content
• the frontend, API, and database changes needed to support the target model
• display-oriented fields needed for authenticated and curated public recipe pages

Key decisions

• Keep the recipe write model relational in SQL Server rather than moving to a JSON-first design.
• Introduce MenuUser and make recipe ownership explicit.
• Replace global recipe-name uniqueness with owner-scoped uniqueness.
• Treat recipe ingredients as recipe-owned content with authored text as the source of truth, while allowing optional canonical links.
• Model sharing, authenticated visibility, and public publication as separate concerns.
• Add a denormalized RecipeSearchIndex and use SQL Server full-text search first instead of introducing an external search service.
• Keep public recipe routes separate from authenticated API routes.

Notes for reviewers

• This is a docs-only change; it defines target architecture and does not implement the feature yet.
• The spec includes mermaid diagrams and records the main tradeoffs that shaped the target design, including publication lifecycle, slug behavior, user provisioning, and search consistency expectations.
• The document was refined to stay aligned with the current Menu codebase rather than inventing a parallel model.

[Copilot]

Pull request overview

Adds a draft architecture spec for evolving recipe creation from the current minimal model into a full aggregate with ownership, sharing, publication, search, and richer display data. The document inventories the current frontend/API/database state, proposes a target domain model with new entities (MenuUser, RecipeStep, RecipeShare, RecipePublication, RecipeSearchIndex), and outlines the changes required across each layer. It is docs-only and does not change any code.

Changes:

• New target architecture spec covering data model, search via SQL Server full-text, and access/publication model.
• Documents required frontend, API, and database changes plus naming decisions and rejected alternatives.
• Includes mermaid ERD and flow diagrams to illustrate the proposed structure.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud