ERP AtlasDocs

Guides

Local verification — 9 October 2026

This report records the local checks completed before commit, push and deployment.

This report records the local checks completed before commit, push and deployment. The subsequent production rollout is recorded in production-release.md.

Inventory and relationships

  • 72 ERP variants, 789 Micro-ERP configurations, 2,367 application configurations and 4,734 contextual extension mappings from the supplied document.
  • Existing 365 ERP and 20 extension seed records are retained. Final local inventories: ERP 1,226; applications 2,367; extensions 4,754.
  • All 7,962 source records and 41,080 relationship targets resolve. Source scopes, workflows, roles, hosts and dependencies are checked against the supplied JSON.
  • Complete migration chains run successfully in SQLite and local Wrangler D1. Migration replay preserves owner, stage, priority, configured infrastructure and custom metadata.
  • Thirty existing MicroERP repository READMEs enrich sixty functional/reusable records. This documents capabilities and planned work; it does not establish their runtime readiness.

Executed checks

  • TypeScript checks passed in all 40 catalog repositories.
  • ESLint passed for changed detail components across the fleet; full lint passed in ERP, application and extension catalogs.
  • Product catalog unit tests: 6 passed. Directory catalog unit tests: 56 passed.
  • Production Next builds passed for ERP, application and extension catalogs. A representative toolkit production build also passed.
  • The editor shell package builds successfully. Its SVG title uses one text child to prevent the hydration mismatch observed during browser review.
  • Local API inventory requests returned HTTP 200 with the totals above. Eight HTTP detail probes returned the expected title and HTTP 200.
  • Eight representative detail pages were reviewed in Chrome at 390px and 1,440px: ERP, Micro-ERP, application, extension, toolkit, editor, website and directory. All sixteen viewport checks show no horizontal document overflow and no raw relationship JSON.
  • ERP → Micro-ERP → application → extension navigation and extension → ERP navigation reached the expected records. Relationship type filtering and source-ID search return the expected application. List pagination reaches records 37–72, and searching ERP-072 resets to the eleven matching ERP/module records.
  • Git whitespace checks passed across all 40 catalog repositories.

Browser navigation was exercised through chrome-use. Some offscreen link actions used its DOM-dispatch fallback; the resulting URL, page title and request were checked. This is navigation evidence, not a claim of trusted-pointer or full end-to-end interaction coverage.

Scope of evidence

All 40 catalogs receive the detail redesign, but browser review covers the eight representative pages above. Production builds were run for the three hierarchy catalogs and toolkit, not all 40 repositories. These checks establish local behavior; live Cloudflare migration, Worker size/package validation and release verification remain separate work.

Cross-catalog links use the published domains by default. The running local previews override those domains through process environment variables so the linked hierarchy can be reviewed locally.

See erp-hierarchy-review.md for data semantics and regeneration commands, and verification-results.json for the recorded inventory, build and responsive measurements.

Last updated 2 November 2026