## Why

`App\Console\Kernel::schedule` already defines a daily task (`Order::summaryLogging()`), but nothing on the dev server ever runs `php artisan schedule:run`, so the task never executes and `customer_order_summary` is never populated on dev. Laravel's documented way to drive the scheduler is a system cron entry that invokes `schedule:run` every minute; on Laravel 5.6 there is no `schedule:work` alternative, so cron is the only option.

## What Changes

- Add a versioned cron definition `deploy/cron.d/tnx-pos-dev` that runs `php artisan schedule:run` every minute as `www-data` from the dev project root.
- Extend the `pos-dev` GitLab CI job to install that file into `/etc/cron.d/` on every deploy (root-owned, mode 644), so the cron entry is reproducible and never drifts from the repo.
- Pin `deploy/cron.d/*` to LF line endings in `.gitattributes` (cron silently ignores CRLF entries).
- Document the scheduler mechanism, the required sudoers rule for `gitlab-runner`, and the verification steps in `README.md`.

## Capabilities

### New Capabilities
- `dev-scheduler-cron`: The dev server automatically triggers the Laravel scheduler every minute via a repo-managed, CI-deployed cron entry running as the web server user.

### Modified Capabilities
<!-- none — no existing spec covers deployment or scheduling -->

## Impact

- **New**: `deploy/cron.d/tnx-pos-dev`, `deploy/` directory.
- **Modified**: `.gitlab-ci.yml` (job `pos-dev`), `.gitattributes`, `README.md`.
- **Server (one-time, outside repo)**: a scoped sudoers rule allowing `gitlab-runner` to run `install` for exactly this file into `/etc/cron.d/`. CI already uses `sudo rm -rf`; this adds one narrowly scoped command.
- **Runtime**: `Order::summaryLogging()` will start running nightly at 00:00 Asia/Ho_Chi_Minh (17:00 UTC) on dev. Cron invocations run as `www-data`, matching Apache/mod_php, so log and cache files created by the scheduler remain writable by the web server.
- Out of scope: local Docker scheduler, `withoutOverlapping()` on existing tasks, staging/prod environments.
