file_explanations.py
Source file: tools/docs/file_explanations.py
Module: tools-docs
Size: 72 lines
SHA-256: 9d04b740a0410c34cec6516d09909b637fa9cff00bdb6d8e7ea288c8fbc20c71
Responsibility
Implements this named HSLG source responsibility; inspect its declarations and tests before changing behaviour.
Declared entry points
requires— source line 20.listens— source line 53.
Imports and dependencies
No direct import declarations detected in this file.
Behaviour and audit locations
- Line 3:
'apps/mobile/src/CapacitorBoot.ts': """## Bootstrap sequence and safety - Line 6:
'apps/mobile/native-adapters/CapacitorDeviceServices.ts': """## Plugin callbacks and their limits - Line 8:
The adapter uses Capacitor Network for device state, App for incoming and cold-start links, Barcode Scanner for QR camera input, Haptics for tactile outcomes, Keyboard fo - Line 20:
This class requires an injected native SQLite driver exposing execution, lookup and atomic transaction operations. It creates hslg_order_outbox records keyed by a rando - Line 38:
This controller registers account and order-draft REST routes under hslg/v1. Anonymous account operations still require HTTPS. Protected operations validate a Bearer to - Line 44:
This repository stores and validates customer account credentials, login sessions, rate-limit activity and one-time challenges using HSLG-owned data rather than wp_users - Line 45:
'wordpress/hslg-app-api/src/database/WordPressOrderDraftRepository.php': """## Draft idempotency and ownership - Line 47:
The repository stores draft requests associated with authenticated customer, venue and table, keyed by a stable idempotency value. Reuse of the same key with differing co
Relationship to the system
This page is the file-level source reference, not the architecture rationale. Read the module explanation, the corresponding architecture decision and user guide before changing behaviour. Names and line locations above are extracted from this exact source version; they are reference points, not proof that an external service or a phone feature works.
Change verification
Review the entry points and errors in this file, then run the module’s associated tests, source dependency gate, history gate and documentation coverage check. If the file changes an API response, user interaction, data model, deployment or third-party dependency, revise those human explanations and disaster recovery/licensing when relevant. Do not infer actual native or external API operation from source presence.