BUTCHERY MODULE UPGRADE — v3.6.0

1. Back up the database and application directory.
2. Import database/migrations/upgrade_v3_6_0_butchery.sql in phpMyAdmin (select the application's existing database).
3. Upload/replace the application files from this archive.
4. Sign in as a manager/admin and open Butchery POS & Stock.
5. Create a user with the existing Waiter role/PIN for butchery counter sales. The POS uses the normal authenticated user and branch session.
6. Only Superadmin, Admin and Manager can receive meat, record loss/spoilage, transfer meat to restaurant, record closing stock, or change printer settings. Cashiers/waiters can sell available stock.
7. Butchery quantities are stored as whole grams. Selling price is KSh per kg; line amount = grams × selling price per kg ÷ 1000.
   Example: 3 kg = 3,000 g; at KSh 900/kg, a KSh 200 sale is 222.222...g (rounded by the POS to whole grams: 222g), leaving 2,778g.
8. The butchery transfer to restaurant is recorded as a separate stock movement and deducted from butchery stock. It is not automatically posted as a restaurant menu product because the application has no existing meat-to-menu-item mapping.
9. Bar and Rooms are disabled in the module catalogue and Bar/Rooms pages are blocked. Close Sales is restricted to the restaurant outlet and includes a separate butchery close summary.

Important: run the SQL migration before relying on the sidebar entry on an existing installation. The butchery pages also create their operational tables defensively, but the migration is what registers the module and disables Bar/Rooms in the catalogue.
