Source version and installed-release boundary
This manual covers the reviewed newer product source workflow. It requires its matching released core, additive database structure and signed modules where applicable. The separately approved licensed 1.3.8 archive can have an earlier workflow. Do not assume these screens or commands exist merely from a numeric version label, and do not copy newer source files over a signed installation. Documentation publication does not upgrade the product or enable any external account.
The Configuration hub is a compact directory of unique destinations, grouped by providers, sales, storefronts, access and platform tools. Each row links directly to its settings page. Payment, domain and server pages have their own navigation; unrelated provider categories are not repeated as payment tabs.
Each provider appears once. Expanding its row reveals saved regional accounts, connection test results, configuration and guarded actions. Module installation and account enablement are separate states. In use includes only enabled accounts whose enabled module has a successful, valid saved verification timestamp. Disabled, unverified and unconfigured providers remain under Available with their saved accounts intact. No accounts or module settings are changed by this reorganization.
Payments include online gateways and offline bank methods. Offline status comes from the existing addon and authorized saved method metadata; bank instructions and payment slip workflows remain in their existing settings. Domains include registrars, DNS providers and the existing registrar/PKNIC lookup tools. WHOIS does not invent a separate module category or perform a lookup when the directory opens. Servers group saved hosting accounts under their provider module and preserve package inventory and readiness diagnostics.
System search groups provider results before counting and pagination, so multiple regional accounts do not appear as duplicate gateway results. A provider match opens the appropriate workspace and expanded provider row. A unique exact account name or public hostname can still open that account directly. Business search and optional broader matching are unchanged.
Installation and development
Each provider workspace has an Install tab containing a category-scoped ZIP upload, checksum field, verified package review and explicit installation acknowledgment. The Domains installer accepts registrar or DNS packages. Its development guide links both starter contracts and labels the displayed example. The generic module library remains available for other package types.
The inline guide documents API version 1, the actual category contract, bootstrap and configuration schema, package.json, supported signing/build tools and the sequence from disabled installation to module enablement, credentials, connection testing and account enablement. It links the starter files in sdk/contracts/. It contains no merchant credentials or business defaults.
Uploads and installations retain the existing PackageInstaller, manifest inventory, checksum/signature verification, permissions, password confirmation and trust acknowledgment. A scoped upload rejects a package from a different category. Installation never enables the module or any account automatically. The original unscoped module-library workflow is preserved.
Presentation and read-only behavior
Provider rows and directory links use compact spacing, native disclosures, readable hover/focus states and responsive layouts. Version, webhook, package, nameserver and diagnostic details appear inside the relevant provider/account. Native navigation and disclosures work without JavaScript. The module library labels module state explicitly and keeps management controls inside each compact row.
Opening a provider workspace or searching it reads local metadata only. It does not load provider code, call an API, refresh inventory, decrypt credentials or modify account enablement. Existing CSRF, password, permission and backend verification rules remain authoritative.
Validation
php tests/integration-workspace-state.php
php tests/integration-module-workspace.php
php tests/provider-install-workspace.php
php tests/system-module-workspace.php
php tests/admin-search-providers.php
php tests/admin-search-relevance.php
php tests/hosting-readiness-presentation.php
php tests/template-compilation.php
Associated browser checks render isolated fixtures with outbound requests intercepted. They cover compact rows, provider grouping and disclosures, mobile and dark layouts, hover/focus contrast, password cancellation, single submission and required acknowledgments. Live checks read saved state without contacting payment, registrar or hosting providers.