Phone-island: remove Storybook, reduce security warnings, and align local dev with the real integration

[tonyco97]

Steps to reproduce

• Check out the security-issue branch from main
• Run npm install
• Compare the development workflow and dependency tree with main
• Run npm run dev
• Verify that development now happens through the existing integration page instead of Storybook

Expected behavior

• The project should not include unnecessary development dependencies that generate known security warnings
• The local development workflow should use the real integration page already present in the repository
• Changes to the widget should be tested in the same HTML-based flow used by real consumers
• Non-critical development issues should stay in the browser console and not appear as blocking runtime overlays

Actual behavior

• The previous setup relied on Storybook and related tooling that was no longer needed for this repository
• That tooling increased maintenance cost and contributed to security warnings in the dependency tree
• Development was happening in a separate Storybook environment instead of the actual integration page
• Some non-critical runtime issues were shown as blocking overlays during local development

Components

• Repository: phone-island
• Branch: security-issue
• Main changes included in this branch:
• Removed Storybook and related configuration, scripts, and story files
• Removed obsolete development dependencies such as react-scripts and unused Storybook packages
• Updated package-lock.json and dependency overrides to reduce security warnings from transitive dependencies
• Reworked npm run dev to use the existing HTML integration flow instead of Storybook
• Added a generated local development host based on the existing widget example page
• Kept the public integration page unchanged while enabling live reload with local widget sources
• Extended the integration demo with development controls useful for debugging and view switching
• Downgraded non-critical runtime failures from blocking errors to console warnings where appropriate

See also

• Related branch: security-issue

---

• Acknowledgements
• This work aligns local development with the real widget integration flow, simplifies the toolchain, and reduces unnecessary security noise in an open-source repository.