Configure IBEX frontend for npm package publishing

[Copilot]

Enables publishing the IBEX Electron application to npm registry.

Configuration

frontend/package.json

• Version: "dev" → "0.1.0" (semver-compliant)
• License: "MIT" → "LGPL-3.0" (matches root LICENSE.txt)
• Added: repository, bugs, homepage, keywords
• Added: publishConfig with public access and npm registry URL
• Added: files array specifying build artifacts (.webpack/, out/, resources/)
• Added: publish:npm script combining build and publish steps

frontend/.npmignore
Excludes source files, config files, dev dependencies, and environment files from package.

Publishing Options

# Quick method (builds + publishes)
npm run publish:npm

# Automated via GitHub Actions
# Triggers on release creation, requires NPM_TOKEN secret

Documentation

• docs/NPM_PUBLISHING.md - Complete publishing guide with prerequisites, troubleshooting, and automated setup
• docs/NPM_SETUP_SUMMARY.md - Quick reference of changes and next steps
• Updated main and frontend READMEs with publishing guide links

GitHub Actions

.github/workflows/npm-publish.yml automates: dependency install, lint, package build, and npm publish on release creation. Includes explicit contents: read permissions.

Notes

• Package name ibex may conflict on npm registry. Consider scoped package @owner/ibex if unavailable.
• Build artifacts must exist before publishing (handled by publish:npm script).

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.