Code and module reference
Start with the relevant module overview: it describes what the code is responsible for, how data and calls flow through it, failure behaviour and verification. Its child file references identify declarations, dependencies and exact source locations for the current release. A checksum and file list alone are not a user explanation.
Review workflow
Locate the feature in its module overview, follow the source files, examine the relevant contract and test, and then read the matching Architecture and User Guide pages. A code change must update the explanation of changed behaviour, not merely rebuild file hashes. Generated file-level references are supporting evidence; the longer human chapters carry design reasoning.
Release state
The browser presenter demonstrates flows with fictional adapters. The Android source has actual Capacitor plugin adapters but no verified full native build from this checkpoint. APIs and database migrations require real staging checks. Do not infer deployment completion from an existing source file.
Code modules
- App Demo Runtime
- App Mobile
- Backend Contracts
- Backend Database
- Backend Payment Modules
- Backend Root
- Backend Services
- Deployment Ubuntu Virtualmin
- Package App Core
- Package App Ui
- Package Content WordPress
- Scripts
- Tests Backend
- Tests Build Worker
- Tests Contracts
- Tests Governance
- Tests Runtime
- Tools Docs
- Tools Governance
- Tools Packaging
- WordPress Hslg App Api
- WordPress Hslg Docs Publisher
- WordPress Hslg Presentation