changed spellings

Author: ShahalaKP-Tridz

AGENTS.MD

@@ -21,7 +21,7 @@ The system covers the full restaurant workflow: menu management, table managemen
 ury/                          ← repo root
 ├── ury/                      ← Frappe app Python package (main backend)
 ├── pos/                      ← React 19 POS frontend (v2, current)
-├── Mosaic/                ← Vue 3 KOT kitchen display app
+├── mosaic/                ← Vue 3 KOT kitchen display app
 ├── urypos/                   ← Vue 3 POS frontend (v1, legacy)
 ├── DEMO/                     ← Demo screenshots / assets
 ├── requirements.txt          ← Python dependencies
@@ -30,7 +30,7 @@ ury/                          ← repo root
 └── FEATURES.md / README.md   ← Human-readable documentation
 ```
 
-The Yarn workspace (`package.json`) at the root manages three JS sub-projects: `pos/`, `Mosaic/`, and `urypos/`.
+The Yarn workspace (`package.json`) at the root manages three JS sub-projects: `pos/`, `mosaic/`, and `urypos/`.
 
 ---
 
@@ -82,7 +82,7 @@ ury/
 │   │   ├── ury_pos_kot.js            ← KOT related JS
 │   │   └── sign-message.js / jsrsasign-all-min.js  ← QZ Tray signing
 │   ├── pos/              ← Built React POS assets (output of `cd pos && yarn build`)
-│   ├── Mosaic/        ← Built KOT display assets
+│   ├── mosaic/        ← Built KOT display assets
 │   └── urypos/           ← Built legacy POS assets
 │
 ├── fixtures/             ← Data fixtures exported via `bench export-fixtures`
@@ -166,16 +166,16 @@ ury/
 ### Frontend Apps
 - **`/pos`** — React POS v2 (see `pos/AGENTS.MD`)
 - **`/urypos`** — Vue POS v1 (legacy, `urypos/`)
-- **`/Mosaic/<production_unit>`** — Vue KOT display (see `Mosaic/AGENTS.MD`)
+- **`/mosaic/<production_unit>`** — Vue KOT display (see `mosaic/AGENTS.MD`)
 
 All frontends are served as Frappe web pages. Route rules in `hooks.py` (`website_route_rules`) handle SPA routing:
 ```python
 {"from_route": "/pos/<path:app_path>", "to_route": "pos"},
-{"from_route": "/Mosaic/<path:app_path>", "to_route": "Mosaic"},
+{"from_route": "/mosaic/<path:app_path>", "to_route": "mosaic"},
 ```
 
 ### Real-time (Socket.io)
-- KOT updates are broadcast via Frappe's Socket.io to the `Mosaic` kitchen display.
+- KOT updates are broadcast via Frappe's Socket.io to the `mosaic` kitchen display.
 - Channel format: `kot_update_{branch}_{production_unit}`
 
 ### QZ Tray
@@ -190,13 +190,13 @@ All frontends are served as Frappe web pages. Route rules in `hooks.py` (`websit
 | App | Source | Build output | URL |
 |---|---|---|---|
 | POS v2 (React) | `pos/src/` | `ury/public/pos/` | `/pos` |
-| KOT display (Vue) | `Mosaic/src/` | `ury/public/Mosaic/` | `/Mosaic/<unit>` |
+| KOT display (Vue) | `mosaic/src/` | `ury/public/mosaic/` | `/mosaic/<unit>` |
 | POS v1 (Vue, legacy) | `urypos/src/` | `ury/public/urypos/` | `/urypos` |
 
 Build commands (from repo root):
 ```bash
 cd pos && yarn build       # builds React POS
-cd Mosaic && yarn build # builds KOT display
+cd mosaic && yarn build # builds KOT display
 cd urypos && yarn build    # builds legacy POS
 ```
 
@@ -212,7 +212,7 @@ After building, run `bench build --app ury` to copy assets to the Frappe public
 → Work in `pos/`. Read `pos/AGENTS.MD` first.
 
 **To modify KOT display logic:**
-→ Work in `Mosaic/`. Read `Mosaic/AGENTS.MD` first.
+→ Work in `mosaic/`. Read `mosaic/AGENTS.MD` first.
 
 **To add or modify a Frappe API endpoint:**
 → Edit `ury/ury_pos/api.py` (main POS API) or `ury/ury/api/<module>.py`.
@@ -235,6 +235,6 @@ After building, run `bench build --app ury` to copy assets to the Frappe public
 → Hook registration is in `hooks.py` `doc_events`.
 
 **Never:**
-- Modify `ury/public/pos/`, `ury/public/Mosaic/`, or `ury/public/urypos/` directly — these are build output, not source.
+- Modify `ury/public/pos/`, `ury/public/mosaic/`, or `ury/public/urypos/` directly — these are build output, not source.
 - Edit `fixtures/custom_field.json` directly — export from Frappe desk instead.
 - Add business logic to `www/pos.py` — it should only return boot context data.

FEATURES.md

@@ -139,7 +139,7 @@ A POS Closing Entry must be created at the end of each day to complete the daily
 	- Each production unit has its own dedicated web-based interface, displaying specific items.
 	- Printers can be configured separately for each production unit.
 	- KDS displays are organised by these units , access KDS via 
-		`/Mosaic/<URY_Production_Unit>`   
+		`/mosaic/<URY_Production_Unit>`   
 
 - **KOT Display**
 	- KDS make easy to monitor kitchen orders (KOTs) on a screen..

SETUP.md

@@ -250,7 +250,7 @@ This guide takes you step-by-step through setting up URY on top of ERPNext
     - **KOT Print Format** : Select print format for KOT .
     - **Block Takeaway KOT** : Enable for block Takeaway KOT printing .
 
-> **Note:** To access KDS follow the site url with `/Mosaic/Production%20Unit%20Name`. eg: [https://ury.xxxx.com/Mosaic/Kitchen](https://ury.xxx.com/Mosaic/Kitchen)
+> **Note:** To access KDS follow the site url with `/mosaic/Production%20Unit%20Name`. eg: [https://ury.xxxx.com/mosaic/Kitchen](https://ury.xxx.com/mosaic/Kitchen)
 
 ### Step 11 : User Permissions
 

Mosaic/.gitignore mosaic/.gitignoreMosaic/.gitignore renamed to mosaic/.gitignore

@@ -1,12 +1,12 @@
-# Mosaic — Agent Documentation
+# mosaic — Agent Documentation
 
 ## 1. Overview
 
-**Mosaic** is a Vue 3 real-time Kitchen Order Ticket (KOT) display system. It runs on a screen in the kitchen and shows live order tickets as they are placed or modified by the POS. Kitchen staff use it to track what to prepare and mark orders as served.
+**mosaic** is a Vue 3 real-time Kitchen Order Ticket (KOT) display system. It runs on a screen in the kitchen and shows live order tickets as they are placed or modified by the POS. Kitchen staff use it to track what to prepare and mark orders as served.
 
-- **URL:** `/Mosaic/<production_unit_name>` (e.g., `/Mosaic/Kitchen`)
-- **Served as:** Frappe web page (`ury/www/Mosaic.html`)
-- **Build output:** `ury/public/Mosaic/`
+- **URL:** `/mosaic/<production_unit_name>` (e.g., `/mosaic/Kitchen`)
+- **Served as:** Frappe web page (`ury/www/mosaic.html`)
+- **Build output:** `ury/public/mosaic/`
 
 The production unit name in the URL determines which KOTs are displayed. Each physical kitchen station has its own URL pointing to its production unit.
 
@@ -29,7 +29,7 @@ The production unit name in the URL determines which KOTs are displayed. Each ph
 ## 3. Project Structure
 
 ```
-Mosaic/
+mosaic/
 ├── src/
 │   ├── main.js           ← Vue app entry point
 │   ├── App.vue           ← Root component: mounts Header + KOT
@@ -207,7 +207,7 @@ KOTs are hidden from the board by setting `kot.showDiv = true` (not by removing
 `audio_alert` is fetched from the backend (`POS Profile` / `URY Printer Settings`). Audio only plays if `audio_alert === 1` AND the user has clicked the page at least once (browser autoplay policy). The `showAudioAlertMessage` banner guides users to click.
 
 ### Authentication
-If `auth()` fails, `this.showModal = true` shows a "Not Permitted / Login" modal. The redirect goes to `/login?redirect-to=Mosaic/{production}`. Do not remove this auth check.
+If `auth()` fails, `this.showModal = true` shows a "Not Permitted / Login" modal. The redirect goes to `/login?redirect-to=mosaic/{production}`. Do not remove this auth check.
 
 ### What NOT to change
 - The `kot_channel` computation — changing it breaks real-time updates.

Mosaic/.vscode/extensions.json mosaic/.vscode/extensions.jsonMosaic/.vscode/extensions.json renamed to mosaic/.vscode/extensions.json

@@ -4,7 +4,7 @@
     <meta charset="UTF-8" />
     <link rel="icon" href="/ury.ico" />
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>URY Mosaic</title>
+    <title>URY mosaic</title>
   </head>
   <body>
     <div id="app"></div>