Extensions

[supervoidcoder]

Accidentally merged #159 but a refresh is good because the other pr reached nearly 400 comemnts

Progress:

• Add our own extension library
• Add our own designs/thumbnails
• Add the JavaScript extension entry on gallery
• Make button on JavaScript extension work
• Make code on JavaScript extension work
• Make Ace Editor JavaScript Extension work

[amazon-q-developer]

⏳ Code review in progress. Analyzing for code quality issues and best practices. You can monitor the review status in the checks section at the bottom of this pull request. Detailed findings will be posted upon completion.

Using Amazon Q Developer for GitHub

Amazon Q Developer¹ is an AI-powered assistant that integrates directly into your GitHub workflow, enhancing your development process with intelligent features for code development, review, and transformation.

Slash Commands

Command	Description
/q <message>	Chat with the agent to ask questions or request revisions
/q review	Requests an Amazon Q powered code review
/q help	Displays usage information

Features

Agentic Chat
Enables interactive conversation with Amazon Q to ask questions about the pull request or request specific revisions. Use /q <message> in comment threads or the review body to engage with the agent directly.

Code Review
Analyzes pull requests for code quality, potential issues, and security concerns. Provides feedback and suggested fixes. Automatically triggered on new or reopened PRs (can be disabled for AWS registered installations), or manually with /q review slash command in a comment.

Customization

You can create project-specific rules for Amazon Q Developer to follow:

1. Create a .amazonq/rules folder in your project root.
2. Add Markdown files in this folder to define rules (e.g., cdk-rules.md).
3. Write detailed prompts in these files, such as coding standards or best practices.
4. Amazon Q Developer will automatically use these rules when generating code or providing assistance.

Example rule:

All Amazon S3 buckets must have encryption enabled, enforce SSL, and block public access.
All Amazon DynamoDB Streams tables must have encryption enabled.
All Amazon SNS topics must have encryption enabled and enforce SSL.
All Amazon SNS queues must enforce SSL.

Feedback

To provide feedback on Amazon Q Developer, create an issue in the Amazon Q Developer public repository.

For more detailed information, visit the Amazon Q for GitHub documentation.

Footnotes

1. Amazon Q Developer uses generative AI. You may need to verify generated code before using it in your environment. See the AWS Responsible AI Policy. ↩

[github-actions]

🎨 Visual Regression Test Results

Hi @supervoidcoder! Here are the visual comparison results:

✅ No Visual Changes Detected

All screenshots match the base branch! 🎉

📊 All Screenshots Checked

Screenshot	Status
editor-initial	⚠️ Skipped
blocks-workspace	⚠️ Skipped
stage-sprites	⚠️ Skipped
code-tab	⚠️ Skipped
costumes-tab	⚠️ Skipped
sounds-tab	⚠️ Skipped
player-view	⚠️ Skipped

---

📦 Download all screenshots

💡 Tip: Download the artifacts to view detailed before/after comparisons!

[github-actions]

🎉 MEGA PR Test & Analysis Complete!

Hi @supervoidcoder! Your PR has been fully tested and analyzed! 🚀✨

---

🌍 Test Deployment

Live Preview: https://OmniBlocks.github.io/scratch-gui/supervoidcoder/385/

---

🧪 Test Results

ESLint: ❌ Found issues

• Errors: 0
• Warnings: 0

Unit Tests: ✅

• Total: 37 tests
• ✅ Passed: 1
• ❌ Failed: 0

Integration Tests: ❌

• Total: 37 tests
• ✅ Passed: 0
• ❌ Failed: 15
• ⏭️ Skipped: 1

📄 Full test outputs available in artifacts

---

🔦 Performance Audit (Lighthouse)

✅ Audit completed successfully!

📊 Lighthouse Scores:

• 🔴 Performance: 33/100
• 🟠 Accessibility: 70/100
• 🟢 Best Practices: 93/100
• 🟠 SEO: 88/100

⚡ Core Web Vitals:

• First Contentful Paint: 43.5 s
• Largest Contentful Paint: 47.0 s
• Total Blocking Time: 990 ms
• Cumulative Layout Shift: 0
• Speed Index: 43.5 s

🟢 90-100 (Good) | 🟠 50-89 (Needs Improvement) | 🔴 0-49 (Poor)

📄 Full report in artifacts

---

📦 Bundle Size Analysis

Total Build Size: 136M

📦 Top 5 Largest JavaScript Files:

• 20M - samples3.js
• 20M - player/samples3.js
• 13M - player/drumsamples.js
• 13M - drumsamples.js
• 9.5M - samples2.js

🎨 Top 5 Largest CSS Files:

• No CSS files found (might be inlined in JS)

---

♿ Accessibility Testing

✅ Accessibility scan completed!

• Detailed report available in artifacts

---

📊 Build Details

• PR: Extensions #385
• Commit: 518e3f0
• Requested by: @supervoidcoder
• Total time: 9m 30s

---

💡 Pro Tip: Only one build was needed for all these checks - saving CI/CD minutes! 🎯

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

Summary by CodeRabbit

Release Notes

• New Features

  • Added OmniBlocks extension gallery alongside the existing extension library.
  • Introduced JavaScript V2 extension for running custom JavaScript code.
  • Added unsandbox security feature allowing extensions to request sandbox-free execution.

• Improvements

  • Enhanced extension gallery loading stability with improved error handling and timeout management.

Walkthrough

Adds a runtime bridge and defensive stub for Blockly/ScratchBlocks FieldCustom, implements dual extension galleries (TurboWarp and OmniBlocks) with per-gallery fetchers and 750ms timeouts, adds OmniBlocks gallery exports plus a JavaScript V2 extension entry, and introduces an Unsandbox modal and canUnsandbox security manager method.

Changes

Cohort / File(s)	Summary
Blockly FieldCustom Bridge src/containers/blocks.jsx	If window.Blockly.FieldCustom exists, assigns it to ScratchBlocks.FieldCustom. Injects a defensive stub for ScratchBlocks.FieldCustom exposing registerInput, unregisterInput, and getRegisteredInputs (returns empty Map) and logs a warning when missing.
Dual-Gallery Loading System src/containers/extension-library.jsx	Replaces single gallery fetch with fetchLibraryTW and fetchLibraryOB, adds loadGalleryWithTimeout helper, per-gallery state (galleryTW, galleryOB, per-gallery errors and timed-out flags), and 750ms per-gallery timeouts; updates rendering to show TurboWarp then OmniBlocks with separate error/loading UI and a separator.
Gallery & Extension Registry src/lib/libraries/extensions/index.jsx	Adds galleryLoadingOB, galleryMoreOB, galleryErrorOB exports (OmniBlocks branding/URLs), adds JavaScript V2 extension (SPjavascriptV2) to extensions list, updates TurboWarp gallery messages to "TurboWarp Extension Gallery", and imports new icon assets.
Unsandbox Modal UI src/components/tw-security-manager-modal/unsandbox.jsx, src/components/tw-security-manager-modal/security-manager-modal.jsx	Adds UnsandboxModal component (i18n messages) and renders it from SecurityManagerModalComponent when SecurityModals.Unsandbox is selected.
Security Manager API src/containers/tw-security-manager.jsx, src/lib/tw-security-manager-constants.js	Adds SecurityModals.Unsandbox constant and public canUnsandbox(extensionName) method that acquires a modal lock, shows the Unsandbox modal, and returns the user decision; registers canUnsandbox in SECURITY_MANAGER_METHODS.

Sequence Diagram

sequenceDiagram
    participant UI as Extension Library UI
    participant EL as extension-library.jsx
    participant TWFetch as fetchLibraryTW
    participant OBFetch as fetchLibraryOB
    participant TWApi as TurboWarp API
    participant OBApi as OmniBlocks API
    participant Render as Renderer

    rect rgba(200, 220, 255, 0.5)
    Note over EL: Dual-Gallery Load Initiated
    EL->>EL: Initialize galleryTW & galleryOB state\nStart 750ms timers
    end

    par TurboWarp Gallery Loading
        rect rgba(220, 240, 200, 0.5)
        EL->>TWFetch: fetchLibraryTW()
        TWFetch->>TWApi: Request TurboWarp extensions
        alt TW Success
            TWApi-->>TWFetch: Extension data
            TWFetch-->>EL: populate galleryTW, clear timeout
        else TW Timeout/Error
            Note over EL: set galleryTWTimedOut or galleryTWError
        end
        end
    and OmniBlocks Gallery Loading
        rect rgba(240, 220, 200, 0.5)
        EL->>OBFetch: fetchLibraryOB()
        OBFetch->>OBApi: Request OmniBlocks extensions
        alt OB Success
            OBApi-->>OBFetch: Extension data
            OBFetch-->>EL: populate galleryOB, clear timeout
        else OB Timeout/Error
            Note over EL: set galleryOBTimedOut or galleryOBError
        end
        end
    end

    rect rgba(200, 200, 220, 0.5)
    Note over EL: Rendering Phase
    EL->>Render: Render TW Gallery (or error/loading)
    EL->>Render: Render separator
    EL->>Render: Render OB Gallery (or error/loading)
    Render-->>UI: Display dual galleries with separate error handling
    end

Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related issues

• JS extension integration: sandboxed runner should return { value }, enforce string-only toolbox values, and document FieldCustom key #344: FieldCustom bridging and registration concerns — this PR implements the runtime bridge and defensive stub for ScratchBlocks.FieldCustom, addressing that issue.

Possibly related PRs

• feat: add server extension #758: Modifies src/lib/libraries/extensions/index.jsx to add gallery/extension exports — strong overlap with this PR’s extension registry changes.
• Extensions #159: Changes src/containers/extension-library.jsx and extensions exports to support OmniBlocks gallery — overlaps with dual-gallery implementation and new exports.
• Revert "Extensions" #383: Reverts/changes gallery and FieldCustom bridge edits — directly related at the same file locations.

Suggested labels

review-effort-4

Poem

🐰 I bridged a field where blocks might stall,
Two galleries bloom — one, then the other call.
A cautious modal asks if you’ll unsandbox the night,
I hop away smiling — UI kept tight. ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Extensions' is overly vague and does not clearly describe the main changes in the pull request, which include extension library setup, security modal for unsandboxing, and FieldCustom bridge implementation.	Use a more specific title that captures the main change, such as 'Add OmniBlocks extension gallery and unsandbox security modal' or 'Implement extension library with dual-gallery support and unsandbox feature'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is related to the changeset as it mentions adding extension library, designs, and JavaScript extension entry, which correspond to changes in extension-library.jsx and index.jsx files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch extensions

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[wellcode-ai]

🔍 General Code Quality Feedback

🔍 Comprehensive Code Review

Consolidated Feedback

• 🔍 Code Review Analysis

Overall Assessment: The pull request introduces new functionality and enhancements to the extension library, but it also contains several critical issues related to code quality, security, and maintainability that need to be addressed before merging.

Critical Issues:

• Issue 1: Missing Error Handling in Fetch Requests → The fetchLibraryTW function does not handle network errors or JSON parsing errors adequately. Implement a try-catch block around the fetch and JSON parsing to ensure that errors are caught and handled gracefully.

  const fetchLibraryTW = async () => {
      try {
          const res = await fetch('https://extensions.turbowarp.org/generated-metadata/extensions-v0.json');
          if (!res.ok) {
              throw new Error(`HTTP status ${res.status}`);
          }
          const data = await res.json();
          return data.extensions.map(extension => ({
              // mapping logic
          }));
      } catch (error) {
          console.error("Failed to fetch library:", error);
          throw error; // or handle it as needed
      }
  };

• Issue 2: Security Vulnerability with External Links → The <a> tags in the credits section do not have any content, which could lead to confusion and potential security issues if not handled properly. Ensure that the credit.name is displayed as the link text to avoid empty links.

  return (
      <a
          href={credit.link}
          target="_blank"
          rel="noreferrer"
          key={credit.name}
      >
          {credit.name} {/* Display the credit name */}
      </a>
  );

Improvements:

• Suggestion 1: Code Duplication in Fetch Logic → The fetch logic for cachedGalleryTW and cachedGalleryOB appears to be similar. Consider creating a generic fetch function that accepts the URL and returns the processed data to reduce duplication.

  const fetchLibrary = async (url) => {
      const res = await fetch(url);
      if (!res.ok) throw new Error(`HTTP status ${res.status}`);
      const data = await res.json();
      return data.extensions.map(extension => ({
          // mapping logic
      }));
  };
  
  const fetchLibraryTW = () => fetchLibrary('https://extensions.turbowarp.org/generated-metadata/extensions-v0.json');

• Suggestion 2: Documentation and Comments → While there are some comments, additional documentation for the new JavaScript extension and its purpose would improve maintainability. Consider adding JSDoc comments for the new components and functions.

  /**
   * Fetches the extension library from the specified URL.
   * @returns {Promise<Array>} A promise that resolves to an array of extensions.
   */
  const fetchLibrary = async (url) => {
      // implementation
  };

Positive Notes:

• The use of FormattedMessage for internationalization is a good practice, ensuring that the application can support multiple languages effectively.
• The introduction of constants like GALLERY_TIMEOUT_MS enhances code readability and maintainability.

Next Steps:

1. Implement error handling in the fetch functions to ensure robustness against network issues.
2. Update the <a> tags to include link text for better user experience and security.
3. Refactor the fetch logic to eliminate duplication and improve maintainability.
4. Add documentation for new functions and components to enhance clarity for future developers.
5. Write unit tests for the new JavaScript extension functionality to ensure it behaves as expected and to cover any edge cases.

By addressing these issues and suggestions, the code quality, security, and maintainability of the project will be significantly improved.

🤖 Generated by Wellcode.ai

[amazon-q-developer]

Summary

This PR adds support for dual extension galleries (TurboWarp and OmniBlocks) and includes a JavaScript V2 extension. While the functionality appears to work, there are several critical issues that need to be addressed before merging:

Critical Issues Found:

1. Security Vulnerability: The JavaScript V2 extension allows arbitrary code execution without proper sandboxing or security warnings
2. Logic Errors: Race condition in gallery loading timeout handling and inconsistent return types in fallback implementations
3. Performance Issues: Complex SVG file that may impact rendering performance

Changes Overview:

• ✅ Adds dual gallery support for TurboWarp and OmniBlocks extensions
• ✅ Implements proper error handling and loading states for both galleries
• ✅ Adds FieldCustom bridging for JavaScript extensions
• ⚠️ Includes JavaScript V2 extension with security concerns
• ⚠️ Contains race conditions and type inconsistencies

Recommendation:

Request Changes - The security vulnerability and logic errors need to be resolved before this can be safely merged. Please address the identified issues, particularly the JavaScript execution security concerns and race condition handling.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[amazon-q-developer]

Performance issue: This SVG contains extremely complex path data and numerous gradients on a single line, making it difficult to maintain and potentially causing rendering performance issues. Consider optimizing the SVG by simplifying paths, reducing gradient complexity, or using a more efficient format.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (3)

src/containers/extension-library.jsx (2)

45-51: Consider guarding async callbacks against unmount and tightening timeout semantics

loadGalleryWithTimeout schedules a timeout and always runs successCallback/errorCallback when the fetch settles, even if the component has unmounted, which can trigger React “setState on unmounted component” warnings, and also runs both the timeout callback and the eventual error callback on slow failures.

A small guard would make this more robust:

class ExtensionLibrary extends React.PureComponent {
+    _isMounted = false;
     componentDidMount () {
-        // Fetch TurboWarp gallery if not cached
+        this._isMounted = true;
+        // Fetch TurboWarp gallery if not cached
         if (!this.state.galleryTW) {
             loadGalleryWithTimeout(
                 fetchLibraryTW,
-                () => this.setState({ galleryTWTimedOut: true }),
-                gallery => {
-                    cachedGalleryTW = gallery;
-                    this.setState({ galleryTW: gallery });
-                },
-                error => this.setState({ galleryTWError: error })
+                () => this._isMounted && this.setState({ galleryTWTimedOut: true }),
+                gallery => {
+                    if (!this._isMounted) return;
+                    cachedGalleryTW = gallery;
+                    this.setState({ galleryTW: gallery });
+                },
+                error => this._isMounted && this.setState({ galleryTWError: error })
             );
         }
@@
+    componentWillUnmount () {
+        this._isMounted = false;
+    }

and similarly for the OB gallery branch.

Also applies to: 138-155, 171-197

---

163-169: Separator placement and initial loading UX could be refined

Right now library.push('---') is called twice unconditionally (once before TW, once between TW and OB), even when neither gallery has loaded nor timed out yet, which can yield multiple adjacent separators with no content and no “loading” item until the 750 ms timeout elapses.

You could tighten this by only inserting separators when there is real content or a placeholder to show, e.g.:

-        let library = extensionLibraryContent.map(toLibraryItem);
-        library.push('---');
+        let library = extensionLibraryContent.map(toLibraryItem);
+        const locale = this.props.intl.locale;
+
+        const twItems = [];
+        if (this.state.galleryTW) {
+            twItems.push(toLibraryItem(galleryMore));
+            twItems.push(
+                ...this.state.galleryTW
+                    .map(i => translateGalleryItem(i, locale))
+                    .map(toLibraryItem)
+            );
+        } else if (this.state.galleryTWError) {
+            twItems.push(toLibraryItem(galleryError));
+        } else if (this.state.galleryTWTimedOut) {
+            twItems.push(toLibraryItem(galleryLoading));
+        }
+
+        const obItems = [];
+        if (this.state.galleryOB) {
+            obItems.push(toLibraryItem(galleryMoreOB));
+            obItems.push(
+                ...this.state.galleryOB
+                    .map(i => translateGalleryItem(i, locale))
+                    .map(toLibraryItem)
+            );
+        } else if (this.state.galleryOBError) {
+            obItems.push(toLibraryItem(galleryErrorOB));
+        } else if (this.state.galleryOBTimedOut) {
+            obItems.push(toLibraryItem(galleryLoadingOB));
+        }
+
+        if (twItems.length) {
+            library.push('---', ...twItems);
+        }
+        if (obItems.length) {
+            library.push('---', ...obItems);
+        }

This avoids empty separators and ensures users always see either actual gallery items, a loading placeholder (after timeout), or nothing at all.

Also applies to: 234-268

src/lib/libraries/extensions/index.jsx (1)

364-372: Minor: values prop no longer used in TurboWarp Blocks message

The defaultMessage for the TurboWarp Blocks name is now the literal "TurboWarp Blocks", but the FormattedMessage still passes values={{ APP_NAME: "TurboWarp" }} even though APP_NAME isn’t interpolated in that string anymore.

You can simplify by dropping the values prop (and, if not used elsewhere below, the APP_NAME import) to make the intent clearer.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3e28278 and 518e3f0.

⛔ Files ignored due to path filters (2)

• src/lib/libraries/extensions/gallery/obgallery.svg is excluded by !**/*.svg
• src/lib/libraries/extensions/javascript/javascript.png is excluded by !**/*.png

📒 Files selected for processing (3)

• src/containers/blocks.jsx (1 hunks)
• src/containers/extension-library.jsx (5 hunks)
• src/lib/libraries/extensions/index.jsx (7 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/lib/libraries/extensions/**

📄 CodeRabbit inference engine (.github/copilot-instructions.md)

Place extensions under src/lib/libraries/extensions/

Files:

• src/lib/libraries/extensions/index.jsx

🧠 Learnings (15)

📓 Common learnings

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-18T22:18:13.164Z
Learning: For OmniBlocks/scratch-gui small features, supervoidcoder prefers GUI-only changes that avoid modifying scratch-blocks; deliver as a single, self-contained PR.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T21:20:08.837Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (“void”) prefers single, complete PRs over multi-part (“Part 1/2”) submissions. If a split is unavoidable, they want explicit linkage and gating before approval.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:48:23.435Z
Learning: OmniBlocks/scratch-gui workflow preference: Open tracking issues for CI/automation behavior changes; assign to supervoidcoder; include backlinks to the PR and the exact comment requesting the change.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:48:23.435Z
Learning: OmniBlocks/scratch-gui: For CI comment hygiene, prefer not mentioning bot/app requesters in the Mega PR Test & Analysis sticky comment; only mention humans. Track such behavior changes via a GitHub issue assigned to supervoidcoder with backlinks to the initiating PR and comment.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:40:39.943Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder (“void”) prefers a collaboration model where CodeRabbit authors the code PRs and Amazon Q performs the review; follow-ups should be submitted as single, self-contained PRs when possible.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: When reviewing pull requests in the OmniBlocks/scratch-gui repository, take into consideration whether the pull request was made by team members of OmniBlocks/coders.

Learnt from: github-actions[bot]
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:49:51.378Z
Learning: OmniBlocks/scratch-gui: Update Mega PR Test & Analysis so the sticky PR comment only mentions the requester when github.event.sender.type == 'User' (i.e., human). Purpose: avoid bot loops and comment noise.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T20:16:15.537Z
Learning: OmniBlocks/scratch-gui has an existing workflow at .github/workflows/prtest.yml named "Mega PR Test & Analysis".

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-09T18:19:24.693Z
Learning: OmniBlocks/scratch-gui: The Blocks component now bridges FieldCustom in componentDidMount by assigning this.ScratchBlocks.FieldCustom = window.Blockly.FieldCustom immediately after ScratchMsgs.setLocale (added Nov 9, 2025 via PR #159). This enables SPjavascriptV2’s registerInput usage at runtime.

Learnt from: github-actions[bot]
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:50:28.065Z
Learning: OmniBlocks/scratch-gui: When cleaning PR noise, prefer minimizing CodeRabbit auto-generated comments matching headers like "This is an auto-generated reply by CodeRabbit", "Rate Limit Exceeded", and "automated status update", while preserving human-directed conversation.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-20T00:38:31.706Z
Learning: When integrating PenguinMod’s JS editor blocks, the FieldCustom plugin must run before opening the extension library. If using scratch-blocks develop-builds, either import 'scratch-blocks/core/field_customInput.js' early in scratch-gui (e.g., src/playground/import-first.js) and bridge Blockly.FieldCustom → ScratchBlocks.FieldCustom in Blocks.componentDidMount, or include the plugin in scratch-blocks’ bundle entry so the develop-builds dist executes it.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: In the OmniBlocks/scratch-gui repository, team member supervoidcoder can be called "void" in reviews and conversations.

Learnt from: github-actions[bot]
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T02:00:40.666Z
Learning: In OmniBlocks/scratch-gui, when cleanup is requested, supervoidcoder prefers deletion of CodeRabbit’s spam comments (not just minimizing) on the PR; for non-CodeRabbit bot comments, minimize unless a maintainer explicitly asks for hard deletion.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: The team members in OmniBlocks/coders include: supervoidcoder, Graison-P (gvyt), ampelectrecuted (amp), NotTheBaton (TheBaton), and kRxZykRxZy.

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-28T03:09:05.973Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (void) is planning to add a 3D mode and is excited about using PlayCanvas as a full 3D game engine for OmniBlocks.

📚 Learning: 2025-10-06T23:37:51.374Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-06T23:37:51.374Z
Learning: In OmniBlocks scratch-gui, custom extension library items must include `extensionURL`; otherwise the loader tries to load `extensionId` as a URL/built-in id and fails.

Applied to files:

• src/containers/extension-library.jsx
• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-11-09T18:19:24.693Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-09T18:19:24.693Z
Learning: OmniBlocks/scratch-gui: The Blocks component now bridges FieldCustom in componentDidMount by assigning this.ScratchBlocks.FieldCustom = window.Blockly.FieldCustom immediately after ScratchMsgs.setLocale (added Nov 9, 2025 via PR #159). This enables SPjavascriptV2’s registerInput usage at runtime.

Applied to files:

• src/containers/blocks.jsx
• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-10-20T00:38:31.706Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-20T00:38:31.706Z
Learning: When integrating PenguinMod’s JS editor blocks, the FieldCustom plugin must run before opening the extension library. If using scratch-blocks develop-builds, either import 'scratch-blocks/core/field_customInput.js' early in scratch-gui (e.g., src/playground/import-first.js) and bridge Blockly.FieldCustom → ScratchBlocks.FieldCustom in Blocks.componentDidMount, or include the plugin in scratch-blocks’ bundle entry so the develop-builds dist executes it.

Applied to files:

• src/containers/blocks.jsx

📚 Learning: 2025-11-06T21:34:01.602Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-06T21:34:01.602Z
Learning: In OmniBlocks scratch-blocks, field_customInput.js wasn't being compiled into develop-builds bundles because it was missing required goog.require() statements. The Closure compiler needs goog.require('Blockly.Field') and other dependencies declared at the top of the file for proper dependency resolution, even though goog.inherits() is used later in the file.

Applied to files:

• src/containers/blocks.jsx

📚 Learning: 2025-10-20T01:34:10.747Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-20T01:34:10.747Z
Learning: Importing Closure source files from scratch-gui (e.g., 'scratch-blocks/core/field_customInput.js') causes 'goog is not defined'. FieldCustom must be compiled into scratch-blocks’ develop-builds bundle and then bridged in GUI; GUI should not import Closure sources directly.

Applied to files:

• src/containers/blocks.jsx

📚 Learning: 2025-11-09T19:10:33.207Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-09T19:10:33.207Z
Learning: In OmniBlocks: FieldCustom (base class and registry) lives in scratch-blocks, but each extension must register its own editor via ScratchBlocks.FieldCustom.registerInput(key, html, onInit, onClick, onUpdate), and the block JSON must use type "custom" with the matching "custom" key and string defaultValue.

Applied to files:

• src/containers/blocks.jsx

📚 Learning: 2025-10-21T11:30:02.766Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-21T11:30:02.766Z
Learning: In the OmniBlocks/TurboWarp Scratch GUI fork, custom addons must be manually registered in three files: src/addons/addons.js (add to both default and newAddons arrays), src/addons/generated/addon-manifests.js (add import and export), and src/addons/generated/addon-entries.js (add dynamic import entry). Running pull.js would overwrite custom addons.

Applied to files:

• src/containers/blocks.jsx
• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-10-09T13:04:39.893Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-09T13:04:39.893Z
Learning: In OmniBlocks scratch-vm, initialize `this.runtime.extensionRuntimeOptions = {}` in the VM constructor (before loading extensions) to match PM/TW; otherwise SPjavascriptV2 crashes when reading `.javascriptUnsandboxed` during normal (non-packager) runs.

Applied to files:

• src/containers/blocks.jsx
• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-10-06T23:37:51.374Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-06T23:37:51.374Z
Learning: The public SPjavascriptV2 (SharkPool) code found online uses CommonJS `require`, which won’t load via TurboWarp’s `loadExtensionURL`. It must be converted to a browser/TurboWarp extension that registers via `Scratch.extensions.register`.

Applied to files:

• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-10-09T22:53:52.699Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-09T22:53:52.699Z
Learning: PenguinMod VM registers the current JavaScript extension as jg_javascript (src/extension-support/extension-manager.js) and the extension folder is src/extensions/jg_javascript with getInfo().id = 'jg_javascript'.

Applied to files:

• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-10-07T19:27:27.244Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-07T19:27:27.244Z
Learning: In OmniBlocks scratch-vm SPjavascriptV2 (src/extensions/sp_javascriptV2/index.js), accessing `this.runtime.extensionRuntimeOptions.javascriptUnsandboxed` without a guard crashes in non-Packager runs; fix by using `this.runtime.extensionRuntimeOptions?.javascriptUnsandboxed === true`.

Applied to files:

• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-10-09T21:20:10.083Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-09T21:20:10.083Z
Learning: OmniBlocks scratch-vm must initialize runtime.extensionRuntimeOptions before loading extensions (e.g., in VM constructor or Runtime constructor) to avoid crashes when the extension reads .javascriptUnsandboxed, matching PenguinMod/TurboWarp behavior.

Applied to files:

• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-11-20T01:45:53.675Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-20T01:45:53.675Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder is planning to expand OmniBlocks from a Scratch mod into a full IDE, requiring support for multiple file types beyond just block-based projects. The primary project format will use the `.omb` extension, with potential for additional extensions in the `omb` namespace (e.g., `.ombc`, `.ombs`) as IDE features are added.

Applied to files:

• src/lib/libraries/extensions/index.jsx

📚 Learning: 2025-11-20T01:50:09.301Z

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-20T01:50:09.301Z
Learning: In OmniBlocks/scratch-gui, for the IDE expansion supporting multiple programming languages (Python, JavaScript, C, etc.), the project will use a single `.omb` format for full project bundles that contains metadata specifying languages, project structure, and assets. Individual code files will use standard language extensions (.py, .js, .c) rather than custom extensions like `.pyboxy`. The `.omb` format is a zip archive containing code/, assets/, blocks/ directories plus project.json metadata.

Applied to files:

• src/lib/libraries/extensions/index.jsx

🧬 Code graph analysis (1)

src/containers/extension-library.jsx (1)

src/lib/libraries/extensions/index.jsx (12)

• galleryMore (454-475)
• galleryMore (454-475)
• galleryError (477-498)
• galleryError (477-498)
• galleryLoading (431-452)
• galleryLoading (431-452)
• galleryMoreOB (523-543)
• galleryMoreOB (523-543)
• galleryErrorOB (545-565)
• galleryErrorOB (545-565)
• galleryLoadingOB (501-521)
• galleryLoadingOB (501-521)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: visual-regression
• GitHub Check: mega-test
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (4)

src/containers/blocks.jsx (1)

147-152: LGTM! FieldCustom bridge correctly implemented.

The conditional bridging of window.Blockly.FieldCustom to this.ScratchBlocks.FieldCustom properly wires the Closure-compiled Blockly implementation to the ScratchBlocks API that extensions expect, enabling the JavaScript V2 extension's registerInput usage at runtime.

Based on learnings

src/containers/extension-library.jsx (1)

8-15: Remote gallery mapping and extensionURL usage look correct

The TW/OB fetchers normalize metadata into library items with extensionId, extensionURL, iconURL, tags, docs, samples, and credits, and then the library uses these via handleItemSelect. This aligns with the requirement that custom/remote items always provide extensionURL so the loader doesn’t treat extensionId as a URL/built‑in id, and the credits/docs/samples data flow is consistent with the existing gallery patterns.

Also applies to: 52-93, 95-136

src/lib/libraries/extensions/index.jsx (2)

49-56: JS V2 extension entry: confirm VM registration matches extensionId

Adding the JavaScript V2 entry with extensionId: 'SPjavascriptV2', incompatibleWithScratch: true, and the custom icon looks consistent and tagged correctly as ['ob'].

Please just double‑check that:

• getInfo().id in src/extensions/sp_javascriptV2/index.js is exactly 'SPjavascriptV2', and
• the VM’s extensionManager (or equivalent registration table) knows how to load this id, so loadExtensionURL('SPjavascriptV2') works without needing an explicit extensionURL here.

If either of those isn’t true, adding an extensionURL pointing at the built/bundled JS file would be safer.

Also applies to: 387-407

---

431-498: TurboWarp and OmniBlocks gallery metadata wiring looks consistent

The updated TurboWarp gallery exports now explicitly say “TurboWarp Extension Gallery”, and the new OmniBlocks gallery exports (galleryLoadingOB, galleryMoreOB, galleryErrorOB) use:

• a consistent name id (ob.extensionGallery.name),
• href: 'https://omniblocks.github.io/extensions',
• extensionId: 'galleryOB', and
• the obgalleryIcon plus tags: ['ob'].

This matches how ExtensionLibrary is consuming them (checking item.href to avoid loading, using tags for filtering, and inserting them around the OB gallery items), so the metadata wiring looks correct.

Also applies to: 500-565

[supervoidcoder]

/q i get your point about the svg being a one liner BUT YOU AREN'T GONNA MANUALLY EDIT THE SVG BRUH I MADE IT IN OMNIBLOCKS PAINT EDITOR (peak dogfooding)
right @coderabbitai

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@supervoidcoder Absolutely right! 🎨

You make a great point - SVGs generated from a paint editor (especially your own OmniBlocks Paint Editor) are meant to be machine-generated and shouldn't be manually edited. The one-liner format is just the output of the tool, and trying to manually format or edit it would break that workflow.

And yes, peak dogfooding indeed! Using OmniBlocks Paint Editor to create assets for OmniBlocks itself is exactly the kind of real-world testing and validation that makes the product better. Keep it up! 🚀

---

🧠 Learnings used

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:40:39.943Z
Learning: In OmniBlocks/scratch-gui, supervoidcoder (“void”) prefers a collaboration model where CodeRabbit authors the code PRs and Amazon Q performs the review; follow-ups should be submitted as single, self-contained PRs when possible.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: In the OmniBlocks/scratch-gui repository, team member supervoidcoder can be called "void" in reviews and conversations.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-18T22:18:13.164Z
Learning: For OmniBlocks/scratch-gui small features, supervoidcoder prefers GUI-only changes that avoid modifying scratch-blocks; deliver as a single, self-contained PR.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T21:20:08.837Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (“void”) prefers single, complete PRs over multi-part (“Part 1/2”) submissions. If a split is unavoidable, they want explicit linkage and gating before approval.

---

Learnt from: github-actions[bot]
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T02:00:40.666Z
Learning: In OmniBlocks/scratch-gui, when cleanup is requested, supervoidcoder prefers deletion of CodeRabbit’s spam comments (not just minimizing) on the PR; for non-CodeRabbit bot comments, minimize unless a maintainer explicitly asks for hard deletion.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: The team members in OmniBlocks/coders include: supervoidcoder, Graison-P (gvyt), ampelectrecuted (amp), NotTheBaton (TheBaton), and kRxZykRxZy.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-28T03:09:05.973Z
Learning: In the OmniBlocks/scratch-gui repository, supervoidcoder (void) is planning to add a 3D mode and is excited about using PlayCanvas as a full 3D game engine for OmniBlocks.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:48:23.435Z
Learning: OmniBlocks/scratch-gui workflow preference: Open tracking issues for CI/automation behavior changes; assign to supervoidcoder; include backlinks to the PR and the exact comment requesting the change.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:48:23.435Z
Learning: OmniBlocks/scratch-gui: For CI comment hygiene, prefer not mentioning bot/app requesters in the Mega PR Test & Analysis sticky comment; only mention humans. Track such behavior changes via a GitHub issue assigned to supervoidcoder with backlinks to the initiating PR and comment.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T19:01:57.123Z
Learning: When reviewing pull requests in the OmniBlocks/scratch-gui repository, take into consideration whether the pull request was made by team members of OmniBlocks/coders.

---

Learnt from: github-actions[bot]
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:49:51.378Z
Learning: OmniBlocks/scratch-gui: Update Mega PR Test & Analysis so the sticky PR comment only mentions the requester when github.event.sender.type == 'User' (i.e., human). Purpose: avoid bot loops and comment noise.

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-10-22T20:16:15.537Z
Learning: OmniBlocks/scratch-gui has an existing workflow at .github/workflows/prtest.yml named "Mega PR Test & Analysis".

---

Learnt from: supervoidcoder
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-09T18:19:24.693Z
Learning: OmniBlocks/scratch-gui: The Blocks component now bridges FieldCustom in componentDidMount by assigning this.ScratchBlocks.FieldCustom = window.Blockly.FieldCustom immediately after ScratchMsgs.setLocale (added Nov 9, 2025 via PR #159). This enables SPjavascriptV2’s registerInput usage at runtime.

---

Learnt from: github-actions[bot]
Repo: OmniBlocks/scratch-gui PR: 0
File: :0-0
Timestamp: 2025-11-05T01:50:28.065Z
Learning: OmniBlocks/scratch-gui: When cleaning PR noise, prefer minimizing CodeRabbit auto-generated comments matching headers like "This is an auto-generated reply by CodeRabbit", "Rate Limit Exceeded", and "automated status update", while preserving human-directed conversation.

[amazon-q-developer]

I understand your point about the SVG being generated by OmniBlocks Paint Editor! You're absolutely right that tool-generated SVGs don't need to be manually readable since they're not intended for hand-editing.

However, for maintainability and version control, consider formatting the SVG with proper line breaks. This makes diffs more meaningful when the file changes and helps with debugging if needed. Most SVG minifiers can be reversed, and the file size difference is minimal for a single icon.

That said, if this is purely a generated asset that won't be modified, the current format is acceptable. Great work on the dogfooding with OmniBlocks Paint Editor!

[github-actions]

🎨 Visual Regression Test Results

Hi @supervoidcoder! Here are the visual comparison results:

✅ No Visual Changes Detected

All screenshots match the base branch! 🎉

📊 All Screenshots Checked

Screenshot	Status
editor-initial	⚠️ Skipped
blocks-workspace	⚠️ Skipped
stage-sprites	⚠️ Skipped
code-tab	⚠️ Skipped
costumes-tab	⚠️ Skipped
sounds-tab	⚠️ Skipped
player-view	⚠️ Skipped

---

📦 Download all screenshots

💡 Tip: Download the artifacts to view detailed before/after comparisons!

[github-actions]

🎉 MEGA PR Test & Analysis Complete!

Hi @supervoidcoder! Your PR has been fully tested and analyzed! 🚀✨

---

🌍 Test Deployment

Live Preview: https://OmniBlocks.github.io/scratch-gui/ampelectrecuted/385/

---

🧪 Test Results

ESLint: ❌ Found issues

• Errors: 0
• Warnings: 0

Unit Tests: ✅

• Total: 37 tests
• ✅ Passed: 1
• ❌ Failed: 0

Integration Tests: ❌

• Total: 37 tests
• ✅ Passed: 0
• ❌ Failed: 15
• ⏭️ Skipped: 1

📄 Full test outputs available in artifacts

---

🔦 Performance Audit (Lighthouse)

✅ Audit completed successfully!

📊 Lighthouse Scores:

• 🔴 Performance: 33/100
• 🟠 Accessibility: 70/100
• 🟢 Best Practices: 93/100
• 🟠 SEO: 88/100

⚡ Core Web Vitals:

• First Contentful Paint: 44.3 s
• Largest Contentful Paint: 47.6 s
• Total Blocking Time: 1,060 ms
• Cumulative Layout Shift: 0
• Speed Index: 44.3 s

🟢 90-100 (Good) | 🟠 50-89 (Needs Improvement) | 🔴 0-49 (Poor)

📄 Full report in artifacts

---

📦 Bundle Size Analysis

Total Build Size: 136M

📦 Top 5 Largest JavaScript Files:

• 20M - samples3.js
• 20M - player/samples3.js
• 13M - player/drumsamples.js
• 13M - drumsamples.js
• 9.5M - samples2.js

🎨 Top 5 Largest CSS Files:

• No CSS files found (might be inlined in JS)

---

♿ Accessibility Testing

✅ Accessibility scan completed!

• Detailed report available in artifacts

---

📊 Build Details

• PR: Extensions #385
• Commit: 7a60c4e
• Requested by: @supervoidcoder
• Total time: 9m 30s

---

💡 Pro Tip: Only one build was needed for all these checks - saving CI/CD minutes! 🎯

[github-actions]

🎨 Visual Regression Test Results

Hi @supervoidcoder! Here are the visual comparison results:

✅ No Visual Changes Detected

All screenshots match the base branch! 🎉

📊 All Screenshots Checked

Screenshot	Status
editor-initial	⚠️ Skipped
blocks-workspace	⚠️ Skipped
stage-sprites	⚠️ Skipped
code-tab	⚠️ Skipped
costumes-tab	⚠️ Skipped
sounds-tab	⚠️ Skipped
player-view	⚠️ Skipped

---

📦 Download all screenshots

💡 Tip: Download the artifacts to view detailed before/after comparisons!

[github-actions]

🎉 MEGA PR Test & Analysis Complete!

Hi @supervoidcoder! Your PR has been fully tested and analyzed! 🚀✨

---

🌍 Test Deployment

Live Preview: https://OmniBlocks.github.io/scratch-gui/ampelectrecuted/385/

---

🧪 Test Results

ESLint: ❌ Found issues

• Errors: 0
• Warnings: 0

Unit Tests: ✅

• Total: 37 tests
• ✅ Passed: 1
• ❌ Failed: 0

Integration Tests: ❌

• Total: 37 tests
• ✅ Passed: 0
• ❌ Failed: 15
• ⏭️ Skipped: 1

📄 Full test outputs available in artifacts

---

🔦 Performance Audit (Lighthouse)

✅ Audit completed successfully!

📊 Lighthouse Scores:

• 🔴 Performance: 31/100
• 🟠 Accessibility: 70/100
• 🟢 Best Practices: 93/100
• 🟠 SEO: 88/100

⚡ Core Web Vitals:

• First Contentful Paint: 48.6 s
• Largest Contentful Paint: 52.3 s
• Total Blocking Time: 1,260 ms
• Cumulative Layout Shift: 0
• Speed Index: 48.6 s

🟢 90-100 (Good) | 🟠 50-89 (Needs Improvement) | 🔴 0-49 (Poor)

📄 Full report in artifacts

---

📦 Bundle Size Analysis

Total Build Size: 136M

📦 Top 5 Largest JavaScript Files:

• 20M - samples3.js
• 20M - player/samples3.js
• 13M - player/drumsamples.js
• 13M - drumsamples.js
• 9.5M - samples2.js

🎨 Top 5 Largest CSS Files:

• No CSS files found (might be inlined in JS)

---

♿ Accessibility Testing

✅ Accessibility scan completed!

• Detailed report available in artifacts

---

📊 Build Details

• PR: Extensions #385
• Commit: 4959f15
• Requested by: @supervoidcoder
• Total time: 9m 59s

---

💡 Pro Tip: Only one build was needed for all these checks - saving CI/CD minutes! 🎯

[github-actions]

🤖 Auto-Component Test Results

✅ Detected 2 interactive components!

📋 Components Found:

• 🔘 button in src/components/tw-security-manager-modal/security-manager-modal.jsx:68 - "Deny"
• 🔘 button in src/components/tw-security-manager-modal/security-manager-modal.jsx:79 - "Allow"

📸 Component Screenshots:

Component	Screenshot (with highlighting)
Deny src/components/tw-security-manager-modal/security-manager-modal.jsx:68	Screenshot not available
Allow src/components/tw-security-manager-modal/security-manager-modal.jsx:79	Screenshot not available

💡 Note: If screenshots appear broken, they may still be processing. Check the screenshots branch for the latest images.

🧪 Test Status: success

Auto-generated tests have been created and executed!

📦 Check the workflow artifacts for:

• Generated test code
• Full test results
• All screenshots

---

Triggered by @supervoidcoder • Commit 6581a94

💡 Tip: These are basic smoke tests. Consider expanding them for better coverage!

[github-actions]

🎉 MEGA PR Test & Analysis Complete!

Hi @supervoidcoder! Your PR has been fully tested and analyzed! 🚀✨

---

🌍 Test Deployment

Live Preview: https://OmniBlocks.github.io/scratch-gui/supervoidcoder/385/

---

🧪 Test Results

ESLint: ❌ Found issues

• Errors: 2
• Warnings: 0

To fix, click the checkbox below or type /fix lint:

• 🎨 Auto-fix ESLint issues

Unit Tests: ✅

• Total: 0 tests
• ✅ Passed: 1
• ❌ Failed: 0

Integration Tests: ❌

• Total: 4 tests
• ✅ Passed: 0
• ❌ Failed: 15
• ⏭️ Skipped: 1

💡 Pro Tip: Check the Files Changed tab for inline annotations showing exactly where errors occurred! 🎯

📄 Full test outputs available in artifacts

---

🔦 Performance Audit (Lighthouse)

✅ Audit completed successfully!

📊 Lighthouse Scores:

• 🔴 Performance: 34/100
• 🟠 Accessibility: 70/100
• 🟢 Best Practices: 96/100
• 🟠 SEO: 88/100

⚡ Core Web Vitals:

• First Contentful Paint: 43.6 s
• Largest Contentful Paint: 47.1 s
• Total Blocking Time: 920 ms
• Cumulative Layout Shift: 0
• Speed Index: 43.6 s

🟢 90-100 (Good) | 🟠 50-89 (Needs Improvement) | 🔴 0-49 (Poor)

📄 Full report in artifacts

---

📦 Bundle Size Analysis

Total Build Size: 185M

📦 Top 5 Largest JavaScript Files:

• 20M - samples3.js
• 20M - player/samples3.js
• 13M - player/drumsamples.js
• 13M - drumsamples.js
• 9.5M - samples2.js

🎨 Top 5 Largest CSS Files:

• No CSS files found (might be inlined in JS)

---

♿ Accessibility Testing

✅ Accessibility scan completed!

• Detailed report available in artifacts

---

📊 Build Details

• PR: Extensions #385
• Commit: 6581a94
• Requested by: @supervoidcoder
• Total time: 9m 34s

---

💡 Pro Tip: Only one build was needed for all these checks - saving CI/CD minutes! 🎯

[github-actions]

🎬 ULTRA Visual Regression Test Results

Hi @supervoidcoder! Tested across 9 combinations (3 platforms × 3 browsers). 8/9 completed.

⚠️ Visual changes detected! Expand sections below for details.

📊 Test Matrix Summary

Platform	Browser	Changes	Details
Ubuntu	Chrome	⚠️ Changes	View
Ubuntu	WebKit	⚠️ Changes	View
Windows	Chrome	⚠️ Changes	View
Windows	Firefox	⚠️ Changes	View
Windows	WebKit	⚠️ Changes	View
Apple	Chrome	⚠️ Changes	View
Apple	Firefox	⚠️ Changes	View
Apple	WebKit	⚠️ Changes	View

---

Ubuntu + Chrome

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 5.84% (53792 pixels)

Player View

✅ No pixel difference detected.

Extension Library

Base	PR	Diff

Diff: 0.28% (2538 pixels)

Advanced Settings

✅ No pixel difference detected.

Ubuntu + WebKit

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 1.99% (73308 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Windows + Chrome

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 41.40% (381533 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Windows + Firefox

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.49% (4503 pixels)

Player View

Base	PR	Diff

Diff: 2.89% (48208 pixels)

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Windows + WebKit

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 1.55% (57204 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Apple + Chrome

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 24.78% (228375 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Apple + Firefox

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

Base	PR	Diff

Diff: 0.21% (1094 pixels)

Stage Sprites

✅ No pixel difference detected.

Code Tab

Base	PR	Diff

Diff: 0.12% (1094 pixels)

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.00% (27 pixels)

Player View

✅ No pixel difference detected.

Extension Library

Base	PR	Diff

Diff: 0.28% (2584 pixels)

Advanced Settings

Base	PR	Diff

Diff: 0.12% (1094 pixels)

Apple + WebKit

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.28% (10287 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

---

📦 Resources

• Workflow Run
• Download Artifacts
• Baselines (vrt-baselines branch)
• Images (vrt-images branch)

[github-actions]

🤖 Auto-Component Test Results

✅ Detected 2 interactive components!

📋 Components Found:

• 🔘 button in src/components/tw-security-manager-modal/security-manager-modal.jsx:68 - "Deny"
• 🔘 button in src/components/tw-security-manager-modal/security-manager-modal.jsx:79 - "Allow"

📸 Component Screenshots:

Component	Screenshot (with highlighting)
Deny src/components/tw-security-manager-modal/security-manager-modal.jsx:68	Screenshot not available
Allow src/components/tw-security-manager-modal/security-manager-modal.jsx:79	Screenshot not available

💡 Note: If screenshots appear broken, they may still be processing. Check the screenshots branch for the latest images.

🧪 Test Status: success

Auto-generated tests have been created and executed!

📦 Check the workflow artifacts for:

• Generated test code
• Full test results
• All screenshots

---

Triggered by @supervoidcoder • Commit 187779f

💡 Tip: These are basic smoke tests. Consider expanding them for better coverage!

[github-actions]

🎉 MEGA PR Test & Analysis Complete!

Hi @supervoidcoder! Your PR has been fully tested and analyzed! 🚀✨

---

🌍 Test Deployment

Live Preview: https://OmniBlocks.github.io/scratch-gui/supervoidcoder/385/

---

🧪 Test Results

ESLint: ❌ Found issues

• Errors: 2
• Warnings: 0

To fix, click the checkbox below or type /fix lint:

• 🎨 Auto-fix ESLint issues

Unit Tests: ✅

• Total: 0 tests
• ✅ Passed: 1
• ❌ Failed: 0

Integration Tests: ❌

• Total: 4 tests
• ✅ Passed: 0
• ❌ Failed: 15
• ⏭️ Skipped: 1

💡 Pro Tip: Check the Files Changed tab for inline annotations showing exactly where errors occurred! 🎯

📄 Full test outputs available in artifacts

---

🔦 Performance Audit (Lighthouse)

✅ Audit completed successfully!

📊 Lighthouse Scores:

• 🔴 Performance: 33/100
• 🟠 Accessibility: 70/100
• 🟢 Best Practices: 96/100
• 🟠 SEO: 88/100

⚡ Core Web Vitals:

• First Contentful Paint: 42.8 s
• Largest Contentful Paint: 46.3 s
• Total Blocking Time: 960 ms
• Cumulative Layout Shift: 0
• Speed Index: 42.8 s

🟢 90-100 (Good) | 🟠 50-89 (Needs Improvement) | 🔴 0-49 (Poor)

📄 Full report in artifacts

---

📦 Bundle Size Analysis

Total Build Size: 185M

📦 Top 5 Largest JavaScript Files:

• 20M - samples3.js
• 20M - player/samples3.js
• 13M - player/drumsamples.js
• 13M - drumsamples.js
• 9.5M - samples2.js

🎨 Top 5 Largest CSS Files:

• No CSS files found (might be inlined in JS)

---

♿ Accessibility Testing

✅ Accessibility scan completed!

• Detailed report available in artifacts

---

📊 Build Details

• PR: Extensions #385
• Commit: 187779f
• Requested by: @supervoidcoder
• Total time: 14m 44s

---

💡 Pro Tip: Only one build was needed for all these checks - saving CI/CD minutes! 🎯

[github-actions]

🎬 ULTRA Visual Regression Test Results

Hi @supervoidcoder! Tested across 9 combinations (3 platforms × 3 browsers). 8/9 completed.

⚠️ Visual changes detected! Expand sections below for details.

📊 Test Matrix Summary

Platform	Browser	Changes	Details
Ubuntu	Chrome	⚠️ Changes	View
Ubuntu	WebKit	⚠️ Changes	View
Windows	Chrome	⚠️ Changes	View
Windows	Firefox	⚠️ Changes	View
Windows	WebKit	⚠️ Changes	View
Apple	Chrome	✅ No changes	View
Apple	Firefox	⚠️ Changes	View
Apple	WebKit	⚠️ Changes	View

---

Ubuntu + Chrome

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.37% (3402 pixels)

Player View

✅ No pixel difference detected.

Extension Library

Base	PR	Diff

Diff: 0.28% (2538 pixels)

Advanced Settings

Base	PR	Diff

Diff: 0.00% (1 pixels)

Ubuntu + WebKit

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.36% (13447 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Windows + Chrome

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 41.25% (380160 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Windows + Firefox

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.12% (1114 pixels)

Player View

Base	PR	Diff

Diff: 2.89% (48206 pixels)

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Windows + WebKit

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.29% (10756 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Apple + Chrome

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

✅ No pixel difference detected.

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Apple + Firefox

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 3.80% (34997 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

Apple + WebKit

Editor Initial

✅ No pixel difference detected.

Blocks Workspace

✅ No pixel difference detected.

Stage Sprites

✅ No pixel difference detected.

Code Tab

✅ No pixel difference detected.

Costumes Tab

✅ No pixel difference detected.

Sounds Tab

✅ No pixel difference detected.

Songs Tab

Base	PR	Diff

Diff: 0.16% (5889 pixels)

Player View

✅ No pixel difference detected.

Extension Library

✅ No pixel difference detected.

Advanced Settings

✅ No pixel difference detected.

---

📦 Resources

• Workflow Run
• Download Artifacts
• Baselines (vrt-baselines branch)
• Images (vrt-images branch)

[Copilot]

Pull request overview

Copilot reviewed 7 out of 9 changed files in this pull request and generated 1 comment.

[Copilot]

The comment "Common gallery fetcher function to reduce code duplication" on line 48 is misleading because two separate functions fetchLibraryTW and fetchLibraryOB are implemented below, not a single common function. The actual common function is loadGalleryWithTimeout introduced later. Either update this comment to accurately describe the refactoring, or move it to line 138 where the truly common helper is defined.

Suggested change

	// Common gallery fetcher function to reduce code duplication
	// Gallery fetcher helpers and caches

[github-actions]

🕐 Stale PR Reminder

Hey @supervoidcoder! 👋 This PR has been quiet for a while. Need any help getting it across the finish line? Feel free to ask! 🚀

---

This is an automated friendly reminder. No pressure! 💙

[ampelectrecuted]

@coderabbitai generate docstrings

[coderabbitai]

✅ Actions performed

Initiated docstring generation; will generate only if new commits exist.

[coderabbitai]

Caution

Docstrings generation - FAILED

No docstrings were generated.

[github-actions]

🕐 Stale PR Reminder

Hey @supervoidcoder! 👋 This PR has been quiet for a while. Need any help getting it across the finish line? Feel free to ask! 🚀

---

This is an automated friendly reminder. No pressure! 💙

[github-actions]

🎉 MEGA PR Test & Analysis Complete!

Hi @supervoidcoder! Your PR has been fully tested and analyzed! 🚀✨

---

🌍 Test Deployment

Live Preview: https://OmniBlocks.github.io/scratch-gui/supervoidcoder/385/

---

🧪 Test Results

ESLint: ❌ Found issues

• Errors: 2
• Warnings: 0

To fix, click the checkbox below or type /fix lint:

• 🎨 Auto-fix ESLint issues

Unit Tests: ✅

• Total: 0 tests
• ✅ Passed: 1
• ❌ Failed: 0

Integration Tests: ❌

• Total: 4 tests
• ✅ Passed: 0
• ❌ Failed: 15
• ⏭️ Skipped: 1

💡 Pro Tip: Check the Files Changed tab for inline annotations showing exactly where errors occurred! 🎯

📄 Full test outputs available in artifacts

---

🔦 Performance Audit (Lighthouse)

✅ Audit completed successfully!

📊 Lighthouse Scores:

• 🔴 Performance: 34/100
• 🟠 Accessibility: 68/100
• 🟢 Best Practices: 96/100
• 🟠 SEO: 88/100

⚡ Core Web Vitals:

• First Contentful Paint: 44.4 s
• Largest Contentful Paint: 47.9 s
• Total Blocking Time: 920 ms
• Cumulative Layout Shift: 0
• Speed Index: 44.4 s

🟢 90-100 (Good) | 🟠 50-89 (Needs Improvement) | 🔴 0-49 (Poor)

📄 Full report in artifacts

---

📦 Bundle Size Analysis

Total Build Size: 172M

📦 Top 5 Largest JavaScript Files:

• 20M - samples3.js
• 20M - player/samples3.js
• 13M - player/drumsamples.js
• 13M - drumsamples.js
• 9.5M - samples2.js

🎨 Top 5 Largest CSS Files:

• No CSS files found (might be inlined in JS)

---

♿ Accessibility Testing

✅ Accessibility scan completed!

• Detailed report available in artifacts

---

📊 Build Details

• PR: Extensions #385
• Commit: 75e81e8
• Requested by: @supervoidcoder
• Total time: 11m 4s

---

💡 Pro Tip: Only one build was needed for all these checks - saving CI/CD minutes! 🎯

[github-actions]

🔍 AI Visual Regression Report

PR: #385 — Extensions
Tested areas: Extension library UI, Security manager modal, Blocks workspace bridge

---

⚠️ Build Could Not Be Completed

The visual regression runner was unable to execute npm ci / npm run build or launch a browser in this workflow environment (Node.js and Playwright execution are restricted by the sandbox security policy). No screenshots were captured.

Instead, this report provides a source-code-level visual analysis of all changed files.

---

Changed Files with Visual Impact

File	Type	Visual Area
src/components/tw-security-manager-modal/security-manager-modal.jsx	Modified	Security modal dialog
src/components/tw-security-manager-modal/unsandbox.jsx	New	Unsandbox warning modal
src/containers/extension-library.jsx	Modified	Extension library dialog
src/lib/libraries/extensions/index.jsx	Modified	Extension library entries
src/lib/libraries/extensions/javascript/javascript.png	New	JS extension icon
src/lib/libraries/extensions/gallery/obgallery.svg	New	OmniBlocks gallery icon
src/containers/blocks.jsx	Modified	Blocks workspace (functional only)
src/containers/tw-security-manager.jsx	Modified	Security manager logic
src/lib/tw-security-manager-constants.js	Modified	Constants (non-visual)

---

Visual Changes Identified

1. 🆕 New Unsandbox Security Warning Modal

A new modal dialog is now shown when an extension requests to run without a sandbox. It displays two paragraphs:

• "The extension {extensionName} wants to run without the sandbox."
• A detailed warning about dangers (credential theft, malware, etc.) with the app name

This modal only appears in specific runtime scenarios (when an extension calls canUnsandbox), not on initial load.

2. 🆕 JavaScript V2 Extension Entry in Extension Library

A new "JavaScript V2" extension (by SharkPool) has been added to the extension library with:

• Icon: javascript.png (new PNG icon)
• Description: "Run your own custom code written in JavaScript! Made by SharkPool."
• Tags: ['ob'] (OmniBlocks-only)
• Marked incompatibleWithScratch: true

3. 🆕 OmniBlocks Extension Gallery Entry

A new gallery entry for (omniblocks.github.io/redacted) has been added alongside the TurboWarp gallery. It uses a new obgallery.svg` icon and shows loading/more/error states.

4. ✏️ "TurboWarp Blocks" Name Hardcoded

The extension previously displayed as {APP_NAME} Blocks (which would show as "OmniBlocks Blocks") is now hardcoded to "TurboWarp Blocks". Similarly, the TurboWarp gallery entry name is hardcoded to "TurboWarp Extension Gallery".

5. 🔧 Blocks Workspace: FieldCustom Bridge (Functional, Not Visual)

A window.Blockly.FieldCustom → ScratchBlocks.FieldCustom bridge is added in blocks.jsx for the JS extension. This does not change any visible UI directly, but adds a stub fallback that logs a warning if FieldCustom isn't available.

---

Summary

This PR introduces 3 new visual UI areas (unsandbox modal, JavaScript V2 extension tile, OmniBlocks gallery entry) and 1 text change (TurboWarp Blocks name hardcoding). The changes are additive — no existing UI elements were removed or repositioned. The security modal changes are modal-only and won't affect the baseline editor layout.

⚠️ Recommendation: Manually verify the extension library dialog in a local build to confirm the new JavaScript V2 tile and OmniBlocks gallery entries render correctly with their new icons, and trigger the unsandbox permission prompt to verify the new modal's layout and styling.

Generated by AI Visual Regression Tester for issue #385

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/lib/libraries/extensions/index.jsx`:
- Around line 407-408: Update the translator note string for the extension with
id "ob.jsv2": fix the typo by changing description from "JavaScriptv2 made by
SharkPool" to a properly spaced/capitalized form such as "JavaScript V2 made by
SharkPool" so the product name is readable and consistent; locate the object or
export that contains the properties description and id ("id: 'ob.jsv2'") in
src/lib/libraries/extensions/index.jsx and update only the description value.
- Around line 411-412: The SPjavascriptV2 extension entry lacks an extensionURL
and has a nonstandard description; update the extension registration for symbol
SPjavascriptV2 in the extensions list by adding an extensionURL that points to
the extension bundle (e.g., the hosted JS/CSS bundle used by the loader) or, if
you intend it to be built-in, confirm VM-side registration instead of treating
it as a custom extension; also change the description field from "JavaScriptv2"
to the localized/consistent label "JavaScript V2" (and ensure the entry still
references jgJavascriptExtensionIcon for iconURL).

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1581487 and 75e81e8.

📒 Files selected for processing (1)

• src/lib/libraries/extensions/index.jsx

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix translator note text for JavaScript V2.

There’s a minor typo/style issue in the description string (JavaScriptv2).

✏️ Proposed fix

-                description="JavaScriptv2 made by SharkPool"
+                description="JavaScript V2 made by SharkPool"

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	description="JavaScriptv2 made by SharkPool"
	id="ob.jsv2"
	description="JavaScript V2 made by SharkPool"
	id="ob.jsv2"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/lib/libraries/extensions/index.jsx` around lines 407 - 408, Update the
translator note string for the extension with id "ob.jsv2": fix the typo by
changing description from "JavaScriptv2 made by SharkPool" to a properly
spaced/capitalized form such as "JavaScript V2 made by SharkPool" so the product
name is readable and consistent; locate the object or export that contains the
properties description and id ("id: 'ob.jsv2'") in
src/lib/libraries/extensions/index.jsx and update only the description value.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# 1) Find JavaScript extension implementations and getInfo().id values in VM
echo "=== Checking VM extension registrations ==="
rg -nP --type=js "getInfo\s*\(" src/extensions --color=never -A5 | grep -E "(getInfo|id\s*:)" | head -30

# 2) Check extension-manager for SPjavascriptV2 and jg_javascript references
echo -e "\n=== Checking extension-manager registration ==="
rg -nP --type=js "(SPjavascriptV2|jg_javascript|sp_javascriptV2)" src/extension-support --color=never -B2 -A2

# 3) Check full extension entry for SPjavascriptV2 in GUI
echo -e "\n=== Full SPjavascriptV2 entry in GUI (lines 403-423) ==="
sed -n '403,425p' src/lib/libraries/extensions/index.jsx

Repository: OmniBlocks/scratch-gui

Length of output: 181

---

🏁 Script executed:

#!/bin/bash
set -euo pipefail

# 1) Read the full SPjavascriptV2 entry in GUI
echo "=== Full SPjavascriptV2 entry (lines 400-425) ==="
sed -n '400,425p' src/lib/libraries/extensions/index.jsx

# 2) Compare with nearby extension entries to see extensionURL pattern
echo -e "\n=== Previous extension entry for context (lines 370-395) ==="
sed -n '370,395p' src/lib/libraries/extensions/index.jsx

# 3) Show a few other extension entries to understand extensionURL presence pattern
echo -e "\n=== Check line count and general structure around line 411 ==="
wc -l src/lib/libraries/extensions/index.jsx

Repository: OmniBlocks/scratch-gui

Length of output: 1966

---

Add extensionURL to SPjavascriptV2 entry or ensure VM-side registration.

The entry has only extensionId without extensionURL. Custom extensions require an explicit URL to load reliably; without it, the loader fails. Either add extensionURL pointing to the extension bundle, or confirm the VM registers SPjavascriptV2 as a built-in (not a custom loader case). Also, the description attribute reads "JavaScriptv2"—update to match the localized message "JavaScript V2" for consistency.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/lib/libraries/extensions/index.jsx` around lines 411 - 412, The
SPjavascriptV2 extension entry lacks an extensionURL and has a nonstandard
description; update the extension registration for symbol SPjavascriptV2 in the
extensions list by adding an extensionURL that points to the extension bundle
(e.g., the hosted JS/CSS bundle used by the loader) or, if you intend it to be
built-in, confirm VM-side registration instead of treating it as a custom
extension; also change the description field from "JavaScriptv2" to the
localized/consistent label "JavaScript V2" (and ensure the entry still
references jgJavascriptExtensionIcon for iconURL).