fix: POS gaps — geofencing, iot-smart-pos, terminal-ownership, batch settlement, leases schema

[devin-ai-integration]

Summary

Fixes all 6 POS gaps identified in the production readiness audit to bring POS features from 8.2/10 → 10/10:

1. pos-geofencing — replaced hardcoded {"in_zone": True, "alerts": []} stubs with real haversine distance computation + asyncpg PostgreSQL persistence (tables: geofences, geofence_events, terminal_locations)

2. iot-smart-pos — added Python service with fixed FastAPI constructor (previously had unclosed paren with imports injected mid-expression preventing startup) + asyncpg connection pooling

3. terminal-ownership — expanded from 159-line stub to full lifecycle service (530 lines) with domain-specific status transitions (provisioned → assigned → active → suspended → maintenance → decommissioned/lost/stolen), 4 PostgreSQL tables, audit trail

4. posBatchSettlement — new dedicated tRPC router with 7 procedures: createBatch, list, getById, processBatch, failBatch, reconcileBatch, stats. Aggregates POS transactions by terminal, calculates net amounts via calculateFee(), proper writeAuditLog() integration

5. terminal_leases + pos_settlement_batches — two new Drizzle schema tables with FK constraints and indexes, replacing JSON storage in platformSettings

6. terminalLeasing router — rewritten to use dedicated terminalLeases table instead of platformSettings JSON. Proper writeAuditLog({...}) signature matching existing router patterns"

Link to Devin session: https://app.devin.ai/sessions/3ebd42bf0430422a9a2bd85ed9f9cd4c

[devin-ai-integration]

Original prompt from Patrick

https://drive.google.com/file/d/1ko3y7OBp1tJIXGTbe2QGFRHMQfxMTWHX/view?usp=sharing

1. Extract ALL everything in the archive
2. how do ensure and assess that features for example domain and business logic/rules/requirements are fully impemented and production ready and complete - can you thoroughly assess each files and features to determine there are ready for production

1. Database integration (replace in-memory with real Postgres)
2. Inter-service HTTP wiring with retries/circuit breakers
3. Security hardening (JWT everywhere, remove hardcoded creds, mTLS)
4. Integration tests for critical flows
5. Graceful shutdown, observability, alerting
   3)search for orphan, partially and generic scaffolded features across the platform - fully implement them end to end -generic CRUD-only patterns , modules with no domain logic, disconnected features, and incomplete implementations.

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring