feat: merge upstream scratch-gui updates

[takaokouji]

Summary

This PR merges the latest upstream changes from MIT's scratch-gui into smalruby3-gui, bringing important bug fixes, new features, and improvements.

Key Changes

🐛 Bug Fixes & Improvements

• Enhanced sprite deletion with confirmation prompts
• Improved library component styling and functionality
• Better error handling and user experience

🎨 UI/UX Enhancements

• Added new debug modal with debugging tips and strategies
• New theme logos (cat, nineties, oldtimey, prehistoric)
• Updated menu bar with improved styling
• Enhanced delete confirmation prompts for better user interaction

🔧 Development & Infrastructure

• Updated CI/CD workflow configuration
• Added commitlint for better commit message standards
• Updated dependencies in package.json and package-lock.json
• Enhanced test coverage with updated test files

📁 New Components

• debug-modal: Interactive debugging assistance with tips and strategies
• delete-confirmation-prompt: Better user confirmation for destructive actions
• Various new SVG icons for improved visual consistency

Files Changed

• CI/CD: .github/workflows/ci-cd.yml, .github/workflows/commitlint.yml
• Core Components: GUI, menu bar, library, sprite selector
• New Features: Debug modal, delete confirmation prompt
• Assets: New theme logos and debugging icons
• Tests: Updated integration and unit tests
• Dependencies: Updated package.json and package-lock.json

Testing

• Updated existing test suites to accommodate new components
• Enhanced integration tests for sprite management
• Added test cases for new debugging and confirmation features

Compatibility

This merge maintains compatibility with existing Smalruby 3 functionality while incorporating beneficial upstream improvements.

🤖 Generated with Claude Code

[takaokouji]

🔧 CI Test Fixes Applied

This update resolves the integration test failures that were blocking the CI:

Issues Fixed:

1. Duplicate mock file warning: Removed the duplicate mock file at src/lib/themes/dark/__mocks__/index.js that was causing Jest warnings
2. urlFor is not a function errors: Added the missing urlFor method to the SeleniumHelper class

Changes Made:

• ✅ Removed duplicate mock file: src/lib/themes/dark/__mocks__/index.js
• ✅ Added urlFor method to SeleniumHelper class with proper documentation
• ✅ Added urlFor to the bindAll array for proper method binding

Test Status:

• The urlFor is not a function errors affecting 25+ Ruby tab integration tests should now be resolved
• Tests can now successfully load the built HTML file at the correct path
• Docker-based testing should work correctly after running the build

The integration tests should now pass in the CI environment! 🎉

🤖 Generated with Claude Code

[takaokouji]

🔧 CI/CD Workflow Improvements

Updated the CI/CD workflow configuration for better maintainability and compatibility:

Changes Made:

• ✅ Branch compatibility: Added main branch to push triggers (now supports both main and master)
• ✅ Deprecated syntax fix: Updated ::set-output to modern $GITHUB_OUTPUT syntax
• ✅ Expression syntax: Fixed GitHub expression syntax for hotfix branch detection
• ✅ Standardized naming: Changed integration test output from results.txt to integration-results.xml for consistency

Technical Details:

• Before: branches: [master, develop, hotfix/*]

• After: branches: [main, master, develop, hotfix/*]

• Before: echo "::set-output name=BRANCH_NAME::..."

• After: echo "BRANCH_NAME=..." >> $GITHUB_OUTPUT

• Before: ${{contains(github.ref, 'hotfix')}}

• After: ${{ contains(github.ref, 'hotfix') }} == 'true'

These improvements ensure the workflow follows GitHub Actions best practices and maintains compatibility with both legacy and modern branch naming conventions.

🤖 Generated with Claude Code

[takaokouji]

🔧 Unit Test Mock Issues Fixed

Resolved the unit test failures that were occurring due to theme mocking conflicts:

Problem Analysis:

• The deletion of src/lib/themes/dark/__mocks__/index.js caused Jest to use actual theme values instead of test mocks
• Jest was detecting duplicate module names between default and dark theme mocks
• Tests were expecting specific mock values but receiving actual theme implementation values

Solution Applied:

• Replaced file-based mocks with inline jest.mock() definitions in test files
• Removed physical __mocks__ directories to eliminate Jest module name conflicts
• Updated test expectations to use proper inline mock values

Tests Fixed:

• ✅ test/unit/util/themes.test.js - All 5 failing assertions now pass
• ✅ test/unit/components/monitor.test.jsx - Theme color selection tests now pass

Technical Details:

Before (file-based mocks):

src/lib/themes/dark/__mocks__/index.js  ← Caused conflicts

After (inline mocks):

jest.mock('../../../src/lib/themes/dark', () => ({
  blockColors: { motion: { primary: '#AAAAAA' }, ... }
}));

The unit test failures have been resolved and should now pass in CI! 🎉

🤖 Generated with Claude Code