Publish Electron inspector under Flying Changes Code

[StoneHub]

Outcome

Finalize the unpublished Electron inspector as @flyingchangescode/dev-feedback-electron under the new public npm organization.

Changes

• rename every package, install, and import reference
• assert the final package name and author in the release contract test
• use Flying Changes Code rather than a personal name in package metadata and the packaged MIT license
• preserve the guarded one-line development import and all runtime identifiers

Verification

• npm test
• npm run check
• git diff --check
• script-enabled npm pack --dry-run --json
• exact 10-file tarball privacy and secret scan
• independent Luna max reference audit
• independent Luna max privacy release audit
• fixed-point Standards review: no findings
• fixed-point Spec review: no findings

Privacy gate

The tarball contains no personal email, phone, name, home path, farm/customer data, token, key, account ID, internal URL, host identifier, test, source map, hidden file, lockfile, node_modules, or build script. Commit metadata uses the StoneHub GitHub noreply address.