Publish package as rainfalljs for exact npm registry discoverability

[Copilot]

The package was published under a scoped name, so exact lookups for rainfalljs reported no standalone package. This change aligns published metadata and public usage docs with the unscoped package name users are searching for.

• Package identity

  • Renamed npm package from @morf_engineering/rainfalljs to rainfalljs in package.json.
  • Synced lockfile root metadata to the same package/version identity.

• Consumer-facing usage updates

  • Updated install and execution references across docs and CLI guidance:
    • npm install rainfalljs
    • npx rainfalljs ...
  • Replaced scoped import examples with unscoped imports (including /datamap and /mapper subpaths).

• Release/publish consistency

  • Updated release and publish documentation/scripts to reference rainfalljs and unscoped npm package URLs/verification commands.

• Regression guard

  • Added a package-manifest assertion to enforce pkg.name === "rainfalljs" and prevent accidental reversion.

{
  "name": "rainfalljs",
  "version": "0.4.0"
}

• Fixes why is not stating in registry #56