# The Armory — website review package

This package preserves the current version 74 browser interface. It is a preparation milestone, **not a production website or secure login system**. Nothing has been published.

## Open locally

1. Extract the ZIP into a new folder. Do not place it inside your live data/sync folder.
2. Serve that extracted folder with a static HTTP server. For example, if Python is installed: `python -m http.server 8880 --bind 127.0.0.1`.
3. Open `http://127.0.0.1:8880/`. Do not open the HTML files by double-clicking; browser storage and security APIs may behave differently on file URLs.
4. Choose Driver, Management, Creator, or the fictional sample route. Use test passwords and fictional data only.

The login prototype uses browser cryptography and needs localhost or HTTPS. An HTTP address on another device is not equivalent to localhost. No software installation, hosting account, or paid service is bundled.

## Included

- Management interface: both workspaces, scheduling, fleet, people, stores, reports, alerts, service and current theme/dark-mode styling.
- Driver login and route interface, required completion checks, mileage calculation, notes, equipment-request controls, messages and weekly recap UI.
- Creator company/configuration preview, including Big Heavy and separate customer drafts.
- Browser source, branding images, source manifest/checksums and integration requirements.

## Still not connected

- Real authentication, authorization, tenant/market isolation and account revocation.
- Shared online database, attachments, route publication and driver-to-dashboard/report updates.
- Equipment approval alerts and approved Fleet changes across devices.
- SMS/push delivery, reliable offline sync, automatic backups and point-in-time recovery.
- Full customer operational workspaces: new customer screens remain configuration/blank-layout previews, not isolated live tenants.
- Desktop-only file import/export and PDF functions need browser/server implementations. Current print/PDF appearance is not a verified hosted export service.

Browser storage is per browser/device/origin and can be cleared. It is not a backup or shared database. Preview role restrictions and feature switches are UI demonstrations, not security. A shared market password cannot reliably identify an individual or revoke one person without affecting other people using it.

The start screen remembers Driver, Management or Creator on this browser. Opening the site root again goes directly to that entry's login. “Back to start” clears that entry preference and displays the choices again. This is separate from Remember Me and never grants account access. Different phones/browsers make their own choice. A future home-screen shortcut should point to the site root so the remembered choice applies.

## Desktop data migration — later

Keep the original desktop backups untouched. The future Creator-only Load Data flow must validate a supported export, show company/workspace and record counts, take a safety backup, then import transactionally after confirmation. A folder dragged onto a static host does **not** migrate a database. Attachments need a separate inventory and upload step. No installed data, private exports, backup archives, credentials or databases are included here.

## Files and hosting

`index.html` is the review launcher; `app/` contains the preserved browser app with its relative URLs intact. Serve the entire folder, not just one HTML file. `SOURCE-MANIFEST.json` lists every packaged file and SHA-256 digest. Do not put real data into this static package or publish it as an operational application. Provider-specific deployment configuration should be added after backend and access-control choices are reviewed.

## Rebuild from the source workspace

The maintained packaging project is `work/armory-web-preview`. Run `npm run build` there, then `npm run check`. The builder writes a new timestamped folder under `outputs/armory-website-preview-*`; it does not modify the Electron source or live data. The browser source uses an explicit export allowlist. Server bridges, repair scripts, Electron main/preload code, installed data, old builds and dependencies are excluded.
