Rename Composer package to basicrum/basicrum-magento-2

[ceckoslab]

Summary

• Rename the Composer identity to basicrum/basicrum-magento-2 while retaining Basicrum Analytics as the public/Admin title.
• Add homepage/support metadata; retain Composer-generated version-specific source links.
• Keep the rename explicit: no replace, provide, compatibility shims, or automatic migration. Remove the initial old-name conflict because Packagist imports the feature branch under the old default-branch name and rejects it as a self-conflict. Composer does not prevent co-installation during this transition; remove the old requirement and inspect the lock file.
• Add an offline regression using Composer's real validating VCS importer, the candidate metadata and a synthetic historical tag, with both old-name and new-name default branches.
• Rename the distribution ZIP and all build/install/release-gate consumers together. Document the separate Packagist migration and require ^0.1 so imported 0.0.x tags cannot silently select the old implementation.
• Fix the native Admin test by opening Magento's collapsible Basicrum group before locating the exact settings link; retain exact label assertions.
• Rebuild the disposable catalog search index using Magento's standard command before native browser tests. Reused application/database volumes may outlive OpenSearch data; no vendor patches or timeout increases are used.
• Remove CI's --no-check-publish validation exemption.

Magento module, namespace, ACL identifiers, configuration paths, monitoring behavior and licensing are unchanged.

Consultation and corrections

The initial naming changes were discussed with Opus 5.5 Max (claude-opus-5-5) and Grok (grok-4.7-build) through their CLIs. We retained the no-alias decision and release-before-Packagist-submission ordering, but removed their initially recommended conflict after reproducing the hosted import failure. The new VCS regression failed with the original self-conflict and passes after its removal. Standalone validation and the earlier synthetic dependency-solver smoke did not cover that import stage; the old co-installation-rejection claim no longer applies. Decisions and maintainer steps are recorded in docs/PACKAGE-NAMING-MIGRATION.md.

Checks actually run locally

• Focused PHP suite: 18 groups passed on PHP 8.2, 8.3 and 8.4. Tracked PHP/PHTML syntax checks passed. The minimal PHP CLI images require Git for archive tests, as CI already installs it.
• Browser/real-Boomerang suite: 48 passed; loader minification/provenance checks passed.
• Magento-aware PHPStan level 8 and Magento coding standards passed (existing upstream deprecation notices remain).
• Composer 2.10 strict validation passed. The validating VCS import passes under both package names with network disabled. Optimized strict production autoload passed with 13 production classes, no test doubles.
• Committed production ZIP: 34 expected files; all 4 archive-corruption regressions passed.
• Exact-commit native gate on b369c72bda669fdedd4e311669396280d7857098 passed on Magento Open Source 2.4.7-p10 / PHP 8.3, including upgrade, DI compilation, static deployment, search indexing, 10 configuration-save checks, and 21 browser tests passed / 4 intentionally skipped. Admin, first-party enforcing CSP, intercepted beacons and cached-page consent are exercised.
• The first full local gate exposed a missing OpenSearch index in the reused stack; the standard indexing step fixed it, and the full gate then passed. The disposable stack has been stopped again.
• JavaScript/shell syntax and git diff --check passed.

Not performed / release boundary

The four native skips are the optional checkout journey and three sample-data routes. This change does not claim those ran, a published-package Magento Composer installation, or a broader platform matrix. All 25 GitHub checks passed for b369c72bda669fdedd4e311669396280d7857098, including the fresh pinned-native-Magento run and the new Composer VCS-import regression.

No Packagist registration, abandonment, tag, release, deployment or license approval was performed. Owner-approved root LICENSE text and exact-commit verification remain required before publishing 0.1.0. Existing tags and the old Packagist listing must be preserved. The existing Packagist listing automatically updated successfully at 2026-09-23 17:59 UTC: its dev-codex/composer-package-naming version now points to b369c72bda669fdedd4e311669396280d7857098 and lists no conflicts. This verifies the hosted import recovery, not completion of the new-listing migration.