Initial kitchen scaffold — Phase 1 kitchen port (build-verified 2026-07-11)

FastAPI backend (Python 3.11, MSSQL ODBC for SambaPOS, Azure DI OCR),
kitchen_db on central PG. React/TS/Vite frontend with navy sidebar layout.

Backend: auth.py (APP_SLUG=kitchen, SimpleNamespace — archive routes use
.kitchen_id/.is_admin without modification), main.py (51 migrations, scheduler,
internal router for KDS bookings feed), api/internal.py, full archive API
(31 routers: invoices, recipes, menus, sambapos, resos, newbook, disputes,
purchase_orders, etc.), models, migrations, OCR pipeline.
kitchen_id pinned to 1 (B1 — single hotel).

Frontend: AuthGate (app=kitchen, token shim for archive compat — B5b pending),
Layout (navy sidebar, 6 sections, Lucide icons, teal --app-primary),
App.tsx (Outlet pattern, UploadApp outside Layout), index.css (full :root block).
strict: false — archive components have type issues; build clean.

Note: 45 archive components call fetch('/api/...') without /kitchen/ prefix
(B5b). Runtime 404s; deferred until after initial testing.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

frontend/node_modules/chart.js/dist/scales/scale.timeseries.d.ts

@@ -0,0 +1,39 @@
+export default TimeSeriesScale;
+declare class TimeSeriesScale extends TimeScale {
+    /** @type {object[]} */
+    _table: object[];
+    /** @type {number} */
+    _minPos: number;
+    /** @type {number} */
+    _tableRange: number;
+    /**
+       * @protected
+       */
+    protected initOffsets(): void;
+    /**
+       * Returns an array of {time, pos} objects used to interpolate a specific `time` or position
+       * (`pos`) on the scale, by searching entries before and after the requested value. `pos` is
+       * a decimal between 0 and 1: 0 being the start of the scale (left or top) and 1 the other
+       * extremity (left + width or top + height). Note that it would be more optimized to directly
+       * store pre-computed pixels, but the scale dimensions are not guaranteed at the time we need
+       * to create the lookup table. The table ALWAYS contains at least two items: min and max.
+       * @param {number[]} timestamps
+       * @return {object[]}
+       * @protected
+       */
+    protected buildLookupTable(timestamps: number[]): object[];
+    /**
+      * Generates all timestamps defined in the data.
+      * Important: this method can return ticks outside the min and max range, it's the
+      * responsibility of the calling code to clamp values if needed.
+      * @protected
+      */
+    protected _generate(): any;
+    /**
+       * Returns all timestamps
+       * @return {number[]}
+       * @private
+       */
+    private _getTimestampsForTable;
+}
+import TimeScale from "./scale.time.js";