Rename to @edge.app/ecpair + bump to 2.1.0-edge.1

[peachbits]

Summary

Renames this package to @edge.app/ecpair and bumps to 2.1.0-edge.1, with publishConfig.access = "public". After merging, publish manually:

git checkout master && git pull
npm ci && npm run build
npm publish --access public

Why

EdgeApp's edge-currency-plugins (and transitively edge-exchange-plugins) currently pulls this fork in via a git URL. That triggers an npm bug (npm/cli#9005) when min-release-age is set in user-level ~/.npmrc. Publishing as a regular npm package eliminates the git-dep code path.

How consumers use it

Because the original ecpair name on npm is owned by bitcoinjs, the EdgeApp fork is scoped. Consumers can use npm's package-alias feature to keep require('ecpair') in source untouched:

"dependencies": {
  "ecpair": "npm:@edge.app/ecpair@^2.1.0-edge.1"
}

Test plan

• Land this PR
• npm publish --access public from a clean checkout of master
• Confirm @edge.app/ecpair@2.1.0-edge.1 appears on npm
• Use the alias in a follow-up PR on edge-currency-plugins and verify sfw npm install works cleanly with min-release-age=7

[cursor]

Stale comment

Performed security orchestrator triage on this PR revision and identified 1 net-new actionable finding after module deduplication/validation.

  

_{Sent by Cursor Security Agent: Security Reviewer}