Change to OmniBlocks

[supervoidcoder]

currently, literally everything is wired to TurboWarp, i mean, obviously since I literally just forked it.

But it needs to be changed to our app.
Currently, we don't have winget or microsoft store or any code signing, so we should focus on getting something on GitHub releases for now. We have to create new CI workflows for that

[supervoidcoder]

@coderabbitai please read OmniBlocks/scratch-gui README.md so you know that this is and then make a plan

[traycerai]

Plan

Observations

Forked TurboWarp Desktop Electron app wrapping scratch-gui with extras like .sb3 file icons. No current OmniBlocks references (grep search found zero matches). package.json deps point to TurboWarp/scratch-gui#develop and TurboWarp/extensions#master. .gitmodules has TurboWarp/desktop-screenshots. OmniBlocks/scratch-gui GitHub fork exists (updated Nov 2025), rebranded/enhanced TurboWarp GUI for multi-language IDE (future Python/C editors), AGPLv3, with integrated extensions in src/lib/libraries/extensions/.

Approach

Phased rebranding leveraging existing OmniBlocks/scratch-gui fork for core UI (already rebranded over 10+ months). Simplify CI/CD to GitHub releases only (no signing/stores/winget). Update desktop wrapper branding, Linux metadata, docs, and scripts. Test incrementally: local builds first, then CI validation, finally tagged releases. Prioritizes functional GitHub artifacts quickly while ensuring consistency.

Implementation Steps

Phase 1: CI/CD Simplification

1.1 Remove Unnecessary Workflows

• Delete file:.github/workflows/winget.yml
• Retain file:.github/workflows/build-auto.yml (PR validation) and file:.github/workflows/build.yml (manual)

1.2 Simplified file:.github/workflows/release.yml

Linux (release-linux): Debian/AppImage/tar.gz only; update uploads to OmniBlocks/desktop.
macOS (release-mac): DMG only (node release-automation/build.mjs --mac --universal); remove notarization/signing/MAS.
Windows (release-windows): NSIS/portable only; remove SignPath/MS Store/signed variants; update uploads.

Phase 2: Core Branding

2.1 Config Files

file:src-main/brand.js:

PLATFORM_NAME: 'OmniBlocks'
APP_NAME: 'OmniBlocks Desktop'
PACKAGER_NAME: 'OmniBlocks Packager'

file:package.json:

• name: "omniblocks-desktop"
• description: "OmniBlocks Desktop: Block-based IDE wrapper with compiler, addons, themes."
• author: {name: "OmniBlocks", email: "support@omniblocks.org"} (update as needed)
• homepage: "https://omniblocks.org/desktop" (or GitHub)
• repository.url: "https://github.com/OmniBlocks/desktop.git"
• bugs: Update URLs/email
• build.appId: "org.omniblocks.desktop"
• build.productName: "OmniBlocks Desktop"
• Remove build.appx; update build.linux.executableName: "omniblocks-desktop"
• Update build.linux.synopsis/description
• Key deps update:
  • "scratch-gui": "github:OmniBlocks/scratch-gui#develop"
  • "@turbowarp/extensions": "github:TurboWarp/extensions#master" (retain temporarily; verify compatibility with OmniBlocks/scratch-gui or integrate from its extensions/)

2.2 Docs

file:README.md: Replace TurboWarp→OmniBlocks; update URLs/paths (omniblocks-desktop data dir).
file:changelog.md: Add rebrand entry atop.

2.3 Linux Metadata

Rename/update:

• file:linux-files/org.turbowarp.TurboWarp.desktop → org.omniblocks.OmniBlocks.desktop
  • Name: "OmniBlocks Desktop", Exec: /opt/OmniBlocks/omniblocks-desktop %U, Icon: "org.omniblocks.OmniBlocks"
• file:linux-files/org.turbowarp.TurboWarp.metainfo.xml → org.omniblocks.OmniBlocks.metainfo.xml (update id/name/developer/urls)
• file:linux-files/org.turbowarp.TurboWarp.mime.xml → org.omniblocks.OmniBlocks.mime.xml

Phase 3: Website/Docs

Update file:docs/:

• file:docs/CNAME: OmniBlocks domain or remove.
• file:docs/index.html: Branding, logos, links, metadata, screenshots.
• file:docs/privacy.html, file:docs/uninstall.html (paths), file:docs/changelog.json.

Phase 4: Submodules/Scripts

file:.gitmodules: Update docs/screenshots to OmniBlocks/desktop-screenshots (create if needed) or remove.

Scripts:

• file:scripts/download-packager.mjs: Update to OmniBlocks packager if available; else retain.
• file:scripts/prepare-extensions.mjs: Verify post-scratch-gui update.

Phase 5: Localization/Stores

file:src-main/l10n/en.json: OmniBlocks strings/URLs.
Remove file:store-listings/imported.json.

Phase 6: Build/Release Scripts

file:release-automation/build.mjs, file:release-automation/linux.sh: Remove signing; update names.
file:scripts/generate-changelogs.mjs: Branding.

Phase 7: UI/Wrapper Specifics

Scan/update file:src-main/, file:src-renderer-webpack/, file:src-preload/ for titles/menus/dialogs (.sb3 icons preserved).

Phase 8: Test/Release

1. npm ci && npm run fetch && npm run webpack:prod && npm run electron:start (verify OmniBlocks UI).
2. npm run electron:package:dir.
3. Test branch → build-auto.yml.
4. Tag v1.0.0 → release.yml → GitHub artifacts.

Sequence Diagram

sequenceDiagram
    participant Dev
    participant Repo
    participant CI
    participant GHReleases

    Note over Dev,GHReleases: Phases 1-2: CI/Core
    Dev->>Repo: Simplify workflows, delete winget
    Dev->>Repo: brand.js, package.json (deps→OmniBlocks/scratch-gui)
    Dev->>Repo: Linux files, README

    Note over Dev,GHReleases: Phases 3-6: Docs/Scripts
    Dev->>Repo: docs/, l10n, scripts, submodules

    Note over Dev,GHReleases: Phase 7-8: Finalize/Test
    Dev->>Repo: UI files
    Repo->>CI: Test branch (build-auto)
    Dev->>Repo: Tag v1.0.0
    Repo->>CI: release.yml
    CI->>GHReleases: Linux/macOS/Win artifacts

Loading

Key Files Table

Category	Files
CI/CD	.github/workflows/release.yml, delete winget.yml
Core	package.json (deps/appId), src-main/brand.js
Linux	linux-files/*.desktop/xml (rename/update)
Docs	README.md, docs/index.html, changelog.md
Scripts	release-automation/*, scripts/download-packager.mjs
Other	src-main/l10n/en.json, .gitmodules

Priority

1. Immediate (Release-blocking): Phase 1-2 (CI/deps/brand).
2. Next: Phases 3-5 (docs/localization).
3. Polish: 6-8 (scripts/UI/test).

Import In IDE

🤖 Prompt for AI Agents

## Observations

Forked TurboWarp Desktop Electron app wrapping scratch-gui with extras like .sb3 file icons. No current OmniBlocks references (grep search found zero matches). package.json deps point to TurboWarp/scratch-gui#develop and TurboWarp/extensions#master. .gitmodules has TurboWarp/desktop-screenshots. OmniBlocks/scratch-gui GitHub fork exists (updated Nov 2025), rebranded/enhanced TurboWarp GUI for multi-language IDE (future Python/C editors), AGPLv3, with integrated extensions in src/lib/libraries/extensions/.

## Approach

Phased rebranding leveraging existing OmniBlocks/scratch-gui fork for core UI (already rebranded over 10+ months). Simplify CI/CD to GitHub releases only (no signing/stores/winget). Update desktop wrapper branding, Linux metadata, docs, and scripts. Test incrementally: local builds first, then CI validation, finally tagged releases. Prioritizes functional GitHub artifacts quickly while ensuring consistency.

## Implementation Steps

### Phase 1: CI/CD Simplification

#### 1.1 Remove Unnecessary Workflows
- Delete `file:.github/workflows/winget.yml`
- Retain `file:.github/workflows/build-auto.yml` (PR validation) and `file:.github/workflows/build.yml` (manual)

#### 1.2 Simplified `file:.github/workflows/release.yml`
**Linux (`release-linux`):** Debian/AppImage/tar.gz only; update uploads to `OmniBlocks/desktop`.
**macOS (`release-mac`):** DMG only (`node release-automation/build.mjs --mac --universal`); remove notarization/signing/MAS.
**Windows (`release-windows`):** NSIS/portable only; remove SignPath/MS Store/signed variants; update uploads.

### Phase 2: Core Branding

#### 2.1 Config Files
`file:src-main/brand.js`:
```
PLATFORM_NAME: 'OmniBlocks'
APP_NAME: 'OmniBlocks Desktop'
PACKAGER_NAME: 'OmniBlocks Packager'
```

`file:package.json`:
- `name`: `"omniblocks-desktop"`
- `description`: "OmniBlocks Desktop: Block-based IDE wrapper with compiler, addons, themes."
- `author`: `{name: "OmniBlocks", email: "support@omniblocks.org"}` (update as needed)
- `homepage`: "https://omniblocks.org/desktop" (or GitHub)
- `repository.url`: "https://github.com/OmniBlocks/desktop.git"
- `bugs`: Update URLs/email
- `build.appId`: `"org.omniblocks.desktop"`
- `build.productName`: `"OmniBlocks Desktop"`
- Remove `build.appx`; update `build.linux.executableName`: `"omniblocks-desktop"`
- Update `build.linux.synopsis/description`
- **Key deps update:**
  - `"scratch-gui": "github:OmniBlocks/scratch-gui#develop"`
  - `"@turbowarp/extensions": "github:TurboWarp/extensions#master"` (retain temporarily; verify compatibility with OmniBlocks/scratch-gui or integrate from its extensions/)

#### 2.2 Docs
`file:README.md`: Replace TurboWarp→OmniBlocks; update URLs/paths (`omniblocks-desktop` data dir).
`file:changelog.md`: Add rebrand entry atop.

#### 2.3 Linux Metadata
Rename/update:
- `file:linux-files/org.turbowarp.TurboWarp.desktop` → `org.omniblocks.OmniBlocks.desktop`
  - `Name`: "OmniBlocks Desktop", `Exec`: `/opt/OmniBlocks/omniblocks-desktop %U`, `Icon`: "org.omniblocks.OmniBlocks"
- `file:linux-files/org.turbowarp.TurboWarp.metainfo.xml` → `org.omniblocks.OmniBlocks.metainfo.xml` (update id/name/developer/urls)
- `file:linux-files/org.turbowarp.TurboWarp.mime.xml` → `org.omniblocks.OmniBlocks.mime.xml`

### Phase 3: Website/Docs
Update `file:docs/`:
- `file:docs/CNAME`: OmniBlocks domain or remove.
- `file:docs/index.html`: Branding, logos, links, metadata, screenshots.
- `file:docs/privacy.html`, `file:docs/uninstall.html` (paths), `file:docs/changelog.json`.

### Phase 4: Submodules/Scripts
`file:.gitmodules`: Update `docs/screenshots` to OmniBlocks/desktop-screenshots (create if needed) or remove.

Scripts:
- `file:scripts/download-packager.mjs`: Update to OmniBlocks packager if available; else retain.
- `file:scripts/prepare-extensions.mjs`: Verify post-scratch-gui update.

### Phase 5: Localization/Stores
`file:src-main/l10n/en.json`: OmniBlocks strings/URLs.
Remove `file:store-listings/imported.json`.

### Phase 6: Build/Release Scripts
`file:release-automation/build.mjs`, `file:release-automation/linux.sh`: Remove signing; update names.
`file:scripts/generate-changelogs.mjs`: Branding.

### Phase 7: UI/Wrapper Specifics
Scan/update `file:src-main/`, `file:src-renderer-webpack/`, `file:src-preload/` for titles/menus/dialogs (.sb3 icons preserved).

### Phase 8: Test/Release
1. `npm ci && npm run fetch && npm run webpack:prod && npm run electron:start` (verify OmniBlocks UI).
2. `npm run electron:package:dir`.
3. Test branch → `build-auto.yml`.
4. Tag `v1.0.0` → `release.yml` → GitHub artifacts.

## Sequence Diagram

```mermaid
sequenceDiagram
    participant Dev
    participant Repo
    participant CI
    participant GHReleases

    Note over Dev,GHReleases: Phases 1-2: CI/Core
    Dev->>Repo: Simplify workflows, delete winget
    Dev->>Repo: brand.js, package.json (deps→OmniBlocks/scratch-gui)
    Dev->>Repo: Linux files, README

    Note over Dev,GHReleases: Phases 3-6: Docs/Scripts
    Dev->>Repo: docs/, l10n, scripts, submodules

    Note over Dev,GHReleases: Phase 7-8: Finalize/Test
    Dev->>Repo: UI files
    Repo->>CI: Test branch (build-auto)
    Dev->>Repo: Tag v1.0.0
    Repo->>CI: release.yml
    CI->>GHReleases: Linux/macOS/Win artifacts
```

## Key Files Table

| Category | Files |
|----------|-------|
| **CI/CD** | `.github/workflows/release.yml`, delete `winget.yml` |
| **Core** | `package.json` (deps/appId), `src-main/brand.js` |
| **Linux** | `linux-files/*.desktop/xml` (rename/update) |
| **Docs** | `README.md`, `docs/index.html`, `changelog.md` |
| **Scripts** | `release-automation/*`, `scripts/download-packager.mjs` |
| **Other** | `src-main/l10n/en.json`, `.gitmodules` |

## Priority
1. **Immediate (Release-blocking):** Phase 1-2 (CI/deps/brand).
2. **Next:** Phases 3-5 (docs/localization).
3. **Polish:** 6-8 (scripts/UI/test).

---

Execution Information

Branch: master
Commit: 0b39467

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[supervoidcoder]

im out of codespaces again ughh literally just before winter break can you believe it

[coderabbitai]

Tip

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

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Fetch the README.md from OmniBlocks/scratch-gui repository
gh api repos/OmniBlocks/scratch-gui/readme --jq '.content' | base64 -d

Length of output: 28951

---

@supervoidcoder, I've read the OmniBlocks/scratch-gui README and now understand the project! OmniBlocks is an enhanced fork of TurboWarp/Scratch that aims to become a full multi-language IDE. The scratch-gui is the main editor interface that connects all the packages together.

Here's a comprehensive plan for rebranding the desktop repository from TurboWarp to OmniBlocks:

🎯 Phase 1: Identify Current State (Discovery)

Goal: Understand what needs to be changed

1. Audit TurboWarp references

   • Search for "TurboWarp" in all files (code, configs, docs)
   • Find TurboWarp URLs (turbowarp.org, etc.)
   • Identify TurboWarp branding assets (icons, images)
   • Locate hardcoded references to TurboWarp services

2. Document current architecture

   • Identify Electron entry point
   • Find where scratch-gui is integrated
   • Map out build process and dependencies

🔧 Phase 2: Core Rebranding (High Priority)

Goal: Make it work as OmniBlocks

2.1 Package Metadata

• Update package.json:
  • App name: "omniblocks-desktop" or "OmniBlocks"
  • Description, keywords, author
  • Repository URLs → OmniBlocks organization
  • Homepage → omniblocks.github.io
  • Bug tracker URLs
• Update package-lock.json if package name changes

2.2 Application Identity

• Update app name in Electron configuration
• Change productName to "OmniBlocks"
• Update appId (e.g., com.omniblocks.desktop)
• Modify window titles to show "OmniBlocks"
• Update About dialog/menu:
  • App name
  • Description
  • Website link
  • License info (AGPLv3)

2.3 Branding Assets

• Replace app icons with OmniBlocks logo:
  • macOS: .icns file
  • Windows: .ico file
  • Linux: .png files (various sizes)
• Add OmniBlocks mascot "Boxy" if used in UI
• Update splash screen (if exists)
• Replace any TurboWarp imagery

2.4 URLs and Endpoints

• Change default homepage → https://omniblocks.github.io
• Update help/documentation links
• Modify any API endpoints (if desktop calls backend)
• Update auto-update URLs (for future use)
• Change deep-link protocol (e.g., omniblocks://)

2.5 Integration with scratch-gui

• Point to OmniBlocks/scratch-gui repository
• Ensure it loads the OmniBlocks editor (not TurboWarp)
• Verify Aqua theme is default
• Test that OmniBlocks addons work

🚀 Phase 3: CI/CD Setup for GitHub Releases

Goal: Automated builds and releases

3.1 GitHub Actions Workflows

Create .github/workflows/build.yml:

name: Build Desktop App

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]
  release:
    types: [created]

jobs:
  build:
    strategy:
      matrix:
        os: [ubuntu-latest, windows-latest, macos-latest]
    runs-on: ${{ matrix.os }}
    
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '22'
      
      - name: Install dependencies
        run: npm ci
      
      - name: Build app
        run: npm run build
      
      - name: Upload artifacts
        uses: actions/upload-artifact@v4
        with:
          name: omniblocks-${{ matrix.os }}
          path: dist/*

Create .github/workflows/release.yml:

name: Release Desktop App

on:
  push:
    tags:
      - 'v*'

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Create Release
        uses: softprops/action-gh-release@v1
        with:
          files: dist/*
          draft: true
          generate_release_notes: true

3.2 Build Configuration

• Configure electron-builder for all platforms
• Set up proper build targets:
  • Windows: .exe, portable
  • macOS: .dmg, .zip
  • Linux: .AppImage, .deb, .rpm
• Configure file associations (.sb3 files)
• Set up proper app categories

3.3 Version Management

• Implement semantic versioning
• Sync version with releases
• Add version display in app

📝 Phase 4: Documentation Updates

Goal: Clear, accurate documentation

• Update README.md:
  • Replace TurboWarp references
  • Add OmniBlocks branding/badges
  • Installation instructions for releases
  • Development setup
  • Contributing guidelines
• Create CHANGELOG.md
• Add LICENSE file (AGPLv3)
• Update any CONTRIBUTING.md
• Add issue templates for desktop-specific bugs

🧪 Phase 5: Testing & Quality Assurance

Goal: Ensure everything works

• Test on all platforms (Windows, macOS, Linux)
• Verify scratch-gui loads correctly
• Test file operations (open/save .sb3 files)
• Check all menu items and dialogs
• Verify no TurboWarp references visible to users
• Test auto-update mechanism (when implemented)
• Ensure addons work
• Test PWA fallback instructions

🎨 Phase 6: Polish & Optional Enhancements

Goal: Make it shine

• Add custom window frame (optional)
• Implement native file dialogs
• Add desktop notifications
• Create installer customization:
  • Custom installer screens
  • License agreement display
• Add crash reporting (with privacy)
• Implement telemetry opt-in (optional)

📋 Implementation Order (Recommended)

1. Week 1: Phase 1 (Discovery) + Phase 2.1-2.2 (Basic metadata)
2. Week 2: Phase 2.3-2.5 (Branding and URLs) + Phase 3.2 (Build config)
3. Week 3: Phase 3.1, 3.3 (CI/CD workflows)
4. Week 4: Phase 4 (Documentation) + Phase 5 (Testing)
5. Week 5+: Phase 6 (Polish) + first release!

🔑 Key Files to Focus On

Based on typical Electron desktop apps, you'll likely need to modify:

• package.json - Core metadata
• electron-builder.json or build config - Build settings
• src/main.js or main/index.js - Electron main process
• src/renderer/ - UI code
• Icons in build/ or assets/ directory
• .github/workflows/ - CI/CD

🚨 Important Notes

• No code signing initially - Users will see security warnings, that's okay for now
• No auto-updates yet - Users manually download from GitHub releases
• Test on all platforms - Especially important without code signing
• License compliance - Ensure AGPLv3 is properly attributed
• Don't impersonate - As per your licensing notes about logo/mascot

Would you like me to help with any specific phase first? I can generate scripts to search for TurboWarp references, create the CI workflow files, or help with any other specific task!

[supervoidcoder]

i was gonna nolife my way into a gazillion OmniBlocks features but i guess my plans are over unless i throw cash at GitHub @coderabbitai 😭✌️

[coderabbitai]

Tip

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

@supervoidcoder, I feel your pain! Running out of Codespaces right before break is terrible timing 😭

But don't worry - you have options to keep working on OmniBlocks without paying! Here are your best alternatives:

🏠 Local Development (Best Option)

Set up the project locally on your machine:

# Clone the repo
git clone https://github.com/OmniBlocks/desktop.git
cd desktop

# Install dependencies
npm install

# Run in development mode
npm start

Pros:

• Unlimited usage, no quotas
• Faster (no network latency)
• Works offline
• Full control over your environment

Cons:

• Initial setup needed
• Need Node.js installed locally

☁️ Free Cloud IDE Alternatives

1. GitPod - 50 hours/month free

   • Similar to Codespaces
   • Just prefix your GitHub URL with gitpod.io/#

2. VSCode.dev - Completely free

   • Open directly in browser: vscode.dev/github/OmniBlocks/desktop
   • Lightweight editing, git operations
   • Limited terminal access

3. StackBlitz - Free for open source

   • Web-based, runs Node.js in browser
   • Good for frontend work

4. Replit - Free tier available

   • Collaborative, cloud-based
   • Good for testing and development

📅 GitHub Codespaces Free Tier

FYI, the free tier resets monthly:

• 120 core-hours/month
• 15 GB storage
• Resets on your billing date (usually 1st of month)

So you might get access back soon if it's about to reset!

🎓 Student Programs

If you're a student:

• GitHub Student Developer Pack gives you extra Codespaces hours
• Free access at: education.github.com

💡 Recommendation

For heavy feature development, go with local setup. It's the most sustainable approach and gives you unlimited time to work. You can still use git to push/pull, and you won't be blocked by quotas.

You've got this! Don't let a quota stop your momentum - just shift to local dev and keep building those gazillion features! 🚀

Need help setting up locally? Let me know what OS you're on and I can provide specific setup instructions!

[supervoidcoder]

@coderabbitai
okay.hmmm i have a headache rn so it's hard to think but lemme read what you said

phase1-2 aren't really that hard/complex, the desktop app, as far as I'm aware, is just an electron wrapper for scratch-gui with some extra fancy features such as being able to show custom file icons on .sb3 files and whatnot. obviously i'm not trying to downplay how complex it is, I'm just saying that all the rebranding has been done over the past, what like 10 months since we started OmniBlocks

[coderabbitai]

Tip

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

🧩 Analysis chain

@supervoidcoder, got it! Sorry for the info overload - let me simplify 😊

You're absolutely right - since scratch-gui is already rebranded, the desktop wrapper just needs some straightforward updates. Let me check what's actually in the desktop repo right now to see what still needs changing:

This will show me what's already updated and what still needs work, then I can give you a much shorter, focused list! 🎯

---

🏁 Script executed:

#!/bin/bash
# Check package.json to see current state
echo "=== PACKAGE.JSON ==="
cat package.json | jq '{name, description, repository, homepage, bugs, author}'

echo -e "\n=== APP ID/PRODUCT NAME (electron-builder config) ==="
cat package.json | jq '.build.appId, .build.productName'

echo -e "\n=== TURBOWARP REFERENCES COUNT ==="
rg -i "turbowarp" --type-not=lock -c | head -20

echo -e "\n=== EXISTING CI/CD WORKFLOWS ==="
ls -la .github/workflows/ 2>/dev/null || echo "No workflows directory found"

echo -e "\n=== CURRENT ICONS/ASSETS ==="
fd -e ico -e icns -e png "icon" -x ls -lh

Length of output: 2124

---

🏁 Script executed:

#!/bin/bash
# Quick look at the existing workflows to understand what they do
echo "=== BUILD.YML (first 30 lines) ==="
head -n 30 .github/workflows/build.yml

echo -e "\n=== RELEASE.YML (first 30 lines) ==="
head -n 30 .github/workflows/release.yml

echo -e "\n=== What does release.yml publish to? ==="
rg -A 2 "publish|release|upload" .github/workflows/release.yml | head -20

Length of output: 2109

---

@supervoidcoder, perfect! So the desktop repo hasn't been touched yet, but the good news is the CI/CD infrastructure is already there - you just need to rebrand it. Here's the actually focused todo list:

🎯 What Actually Needs Changing

1. package.json (5 min)

{
  "name": "omniblocks-desktop",
  "description": "Full multi-language IDE with Scratch compatibility...",
  "repository": "https://github.com/OmniBlocks/desktop.git",
  "homepage": "https://omniblocks.github.io/",
  "bugs": "https://github.com/OmniBlocks/desktop/issues",
  "author": "Your Name / OmniBlocks Contributors",
  "build": {
    "appId": "io.github.omniblocks.desktop",
    "productName": "OmniBlocks"
  }
}

2. Icons (10 min)

Replace these with OmniBlocks logo:

• build/icon.ico (Windows)
• build/icon.icns (macOS)
• art/icon.png (source)

3. Text References (~30 min)

Find/replace "TurboWarp" with "OmniBlocks" in the ~20 files found:

• All HTML files in src-renderer/
• src-main/*.js files
• Update URLs (turbowarp.org → omniblocks.github.io)

4. GitHub Release Upload Script (2 min)

In scripts/upload-to-github-releases.mjs, change the repo owner/name when it uploads:

- TurboWarp desktop
+ OmniBlocks desktop

5. Remove Winget Workflow (1 min)

Delete .github/workflows/winget.yml since you don't have that yet

6. README (5 min)

Update with OmniBlocks branding and point to omniblocks.github.io

✅ What's Already Good

• ✅ Build workflows exist and work
• ✅ Release workflow publishes to GitHub releases on tags
• ✅ Multi-platform builds (Linux, Windows, macOS)
• ✅ Artifact uploads configured

🚀 To Release

Once rebranded:

git tag v1.0.0
git push origin v1.0.0

The release workflow will automatically build and publish to GitHub releases! 🎉

That's it - way simpler than my massive plan 😅 Want me to help with any specific part?

---

✏️ Learnings added

Learnt from: supervoidcoder
URL: https://github.com/OmniBlocks/desktop/issues/1

Timestamp: 2025-12-14T20:50:37.271Z
Learning: The OmniBlocks desktop repository is an Electron wrapper around the already-rebranded scratch-gui, with existing CI/CD infrastructure that publishes to GitHub releases.

Note: Learnings are effective only in the context of similar code segments. To apply general coding guidelines, please configure review instructions. You can manage existing learnings in the app.

[traycerai]

I have updated the Implementation Plan to reflect the recent changes in the ticket.

Previous Plan

Observations

This is a forked TurboWarp Desktop application with extensive branding throughout the codebase. The existing CI/CD infrastructure includes sophisticated release workflows with code signing (SignPath for Windows, Apple notarization for macOS), Microsoft Store builds, and winget integration. The app uses submodules for scratch-gui and extensions, both pointing to TurboWarp repositories. The codebase has comprehensive localization, documentation, and a website in the docs/ folder.

Approach

The rebranding will be executed in phases: first, simplify CI/CD by removing unavailable features (code signing, store distributions, winget), then create a basic GitHub releases workflow, and finally update all branding references throughout the codebase. This approach prioritizes getting functional releases on GitHub first, as requested, while systematically replacing TurboWarp references with OmniBlocks branding.

Implementation Steps

Phase 1: CI/CD Simplification

1.1 Remove Unnecessary Workflows

Delete or disable workflows that depend on unavailable infrastructure:

• Remove file:.github/workflows/winget.yml entirely (no winget support yet)
• Keep file:.github/workflows/build-auto.yml as-is for PR validation
• Keep file:.github/workflows/build.yml for manual testing

1.2 Create Simplified Release Workflow

Modify file:.github/workflows/release.yml to remove code signing and store builds:

For Linux job (release-linux):

• Remove Microsoft Store and code signing references
• Keep: Debian, AppImage, and tar.gz builds
• Update upload commands to use OmniBlocks and desktop as owner/repo parameters in the upload script calls

For macOS job (release-mac):

• Remove all Apple notarization steps (lines 74-96 with APPLE_API_* secrets)
• Remove code signing certificate steps (CSC_LINK, CSC_KEY_PASSWORD)
• Remove Mac App Store builds (--mas flags)
• Keep only basic DMG builds without signing: node release-automation/build.mjs --mac --universal
• Update upload commands to use OmniBlocks and desktop

For Windows job (release-windows):

• Remove SignPath signing steps (lines 171-189)
• Remove Microsoft Store builds (--microsoft-store flag)
• Keep only basic NSIS installer and portable builds
• Update upload commands to use OmniBlocks and desktop
• Remove separate signed/unsigned artifact uploads

Phase 2: Core Branding Updates

2.1 Central Configuration Files

Update file:src-main/brand.js:

PLATFORM_NAME: 'OmniBlocks'
APP_NAME: 'OmniBlocks Desktop'
PACKAGER_NAME: 'OmniBlocks Packager'

Update file:package.json:

• name: "omniblocks-desktop"
• description: Update to describe OmniBlocks
• author: Update to OmniBlocks team information
• homepage: Update to OmniBlocks website URL
• repository.url: "https://github.com/OmniBlocks/desktop.git"
• bugs.url: "https://github.com/OmniBlocks/desktop/issues"
• bugs.email: Update to OmniBlocks contact email
• build.appId: "org.omniblocks.desktop"
• build.productName: "OmniBlocks"
• Remove or update build.appx section (Microsoft Store config)
• Update build.linux.executableName: "omniblocks-desktop"
• Update build.linux.synopsis and description

2.2 Documentation Files

Update file:README.md:

• Replace all "TurboWarp" references with "OmniBlocks"
• Update clone URL to OmniBlocks repository
• Update download links to point to OmniBlocks releases
• Update data path locations (replace turbowarp-desktop with omniblocks-desktop)
• Remove code signing policy section
• Update uninstall link

Update file:changelog.md:

• Add new entry at top documenting the rebrand to OmniBlocks
• Keep existing TurboWarp history for reference (optional: add note that earlier versions were TurboWarp)

2.3 Linux Metadata Files

Update file:linux-files/org.turbowarp.TurboWarp.desktop:

• Rename file to org.omniblocks.OmniBlocks.desktop
• Update Name: "OmniBlocks"
• Update Exec path: /opt/OmniBlocks/omniblocks-desktop %U
• Update Icon: "org.omniblocks.OmniBlocks"
• Update StartupWMClass: "omniblocks-desktop"
• Update Comment to describe OmniBlocks

Update file:linux-files/org.turbowarp.TurboWarp.metainfo.xml:

• Rename file to org.omniblocks.OmniBlocks.metainfo.xml
• Update <id>: "org.omniblocks.OmniBlocks"
• Update <launchable>: "org.omniblocks.OmniBlocks.desktop"
• Update <name>: "OmniBlocks"
• Update <developer> information
• Update all <url> elements to point to OmniBlocks domains/repositories
• Update <description> content
• Update screenshot URLs (will need new screenshots)
• Update release URLs in <releases> section to point to OmniBlocks repository

Update file:linux-files/org.turbowarp.TurboWarp.mime.xml:

• Rename file to org.omniblocks.OmniBlocks.mime.xml
• Update mime type IDs if needed

Phase 3: Website and Documentation

3.1 Website Files in docs/

Update file:docs/CNAME:

• Change domain to OmniBlocks domain (or remove if using GitHub Pages default)

Update file:docs/index.html:

• Replace all TurboWarp branding with OmniBlocks
• Update logo SVG
• Update download links to OmniBlocks releases
• Update repository links
• Update privacy policy link
• Update screenshot images
• Update Open Graph and Twitter card metadata
• Update changelog section with OmniBlocks releases

Update other docs files:

• file:docs/privacy.html - Update branding and contact information
• file:docs/uninstall.html - Update instructions with OmniBlocks paths
• file:docs/stats.html - Update or remove if TurboWarp-specific
• file:docs/update_available.html - Update branding
• file:docs/changelog.json - Update with OmniBlocks releases

3.2 Submodules

Update file:.gitmodules:

• Change screenshot submodule URL to OmniBlocks repository (create OmniBlocks/desktop-screenshots repo first)
• Or remove submodule if not needed initially

Phase 4: Dependencies and Extensions

4.1 Package Dependencies

In file:package.json, evaluate these dependencies:

• "scratch-gui": "github:TurboWarp/scratch-gui#develop" - Check if OmniBlocks has a fork at github:OmniBlocks/scratch-gui
• "@turbowarp/extensions": "github:TurboWarp/extensions#master" - Check if OmniBlocks has a fork

If OmniBlocks forks exist, update the URLs. Otherwise, keep TurboWarp dependencies temporarily.

4.2 Scripts

Update file:scripts/packager.json:

• Update src URL if OmniBlocks has its own packager
• Otherwise keep TurboWarp packager temporarily

Phase 5: Localization and Store Listings

5.1 Localization Files

Update file:src-main/l10n/en.json:

• Replace TurboWarp references in strings with OmniBlocks
• Update website URLs in developer comments
• Update app name placeholders

Update file:src-main/l10n/generated-translations.json:

• This file is generated, so it will be updated when translations are regenerated
• May need to run translation generation scripts after updating source strings

5.2 Store Listings

Update or remove file:store-listings/imported.json:

• Either remove entirely (no store presence yet)
• Or update all TurboWarp references to OmniBlocks for future use

Phase 6: Build and Release Scripts

6.1 Release Automation

Update file:release-automation/build.mjs:

• Review for any hardcoded TurboWarp references
• Update any branding strings
• Remove code signing logic if present

Update file:release-automation/linux.sh:

• Update any TurboWarp references
• Update package names

6.2 Other Scripts

Review and update scripts in file:scripts/ directory:

• generate-changelogs.mjs - Update for OmniBlocks branding
• download-packager.mjs - Update if using OmniBlocks packager
• prepare-extensions.mjs - Update if using OmniBlocks extensions

Phase 7: Miscellaneous Files

Update remaining files with TurboWarp references:

• file:webpack.config.cjs - Check for any hardcoded paths or references
• file:src-renderer-webpack/ files - Update any branding in UI components
• file:src-main/ files - Update window titles, menu items, dialogs
• file:src-preload/ files - Update any exposed branding
• file:debian/ files - Update Debian packaging scripts

Phase 8: Testing and Validation

After all changes:

1. Test local build:

   • Run npm ci
   • Run npm run fetch
   • Run npm run webpack:prod
   • Run npm run electron:start
   • Verify app launches with OmniBlocks branding

2. Test packaging:

   • Run npm run electron:package:dir
   • Verify packaged app works correctly

3. Test CI workflow:

   • Push changes to a test branch
   • Verify build-auto.yml workflow succeeds
   • Create a test tag (e.g., v0.1.0-test)
   • Verify simplified release.yml workflow builds and uploads artifacts

4. Create first release:

   • Tag with v1.0.0 or appropriate version
   • Verify all artifacts are uploaded to GitHub releases
   • Test downloads from GitHub releases

Implementation Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Repo as Repository
    participant CI as GitHub Actions
    participant Release as GitHub Releases

    Note over Dev,Release: Phase 1: CI/CD Simplification
    Dev->>Repo: Remove winget.yml
    Dev->>Repo: Simplify release.yml (remove signing)
    Dev->>Repo: Update upload script calls

    Note over Dev,Release: Phase 2: Core Branding
    Dev->>Repo: Update brand.js
    Dev->>Repo: Update package.json
    Dev->>Repo: Update README.md
    Dev->>Repo: Update Linux metadata files

    Note over Dev,Release: Phase 3: Website & Docs
    Dev->>Repo: Update docs/index.html
    Dev->>Repo: Update docs/CNAME
    Dev->>Repo: Update other docs files

    Note over Dev,Release: Phase 4: Dependencies
    Dev->>Repo: Update package.json dependencies
    Dev->>Repo: Update submodules

    Note over Dev,Release: Phase 5: Localization
    Dev->>Repo: Update l10n files
    Dev->>Repo: Update/remove store listings

    Note over Dev,Release: Phase 6: Build Scripts
    Dev->>Repo: Update release-automation scripts
    Dev->>Repo: Update helper scripts

    Note over Dev,Release: Phase 7: Miscellaneous
    Dev->>Repo: Update remaining files

    Note over Dev,Release: Phase 8: Testing
    Dev->>Repo: Push to test branch
    Repo->>CI: Trigger build-auto workflow
    CI->>Dev: Build success/failure
    Dev->>Repo: Create test tag
    Repo->>CI: Trigger release workflow
    CI->>Release: Upload artifacts
    Dev->>Release: Verify downloads
    Dev->>Repo: Create v1.0.0 tag
    Repo->>CI: Trigger release workflow
    CI->>Release: Upload official release

Loading

Files Requiring Updates

Category	Files
CI/CD	.github/workflows/release.yml, .github/workflows/winget.yml (delete)
Core Config	package.json, src-main/brand.js, webpack.config.cjs
Documentation	README.md, changelog.md
Linux Metadata	linux-files/org.turbowarp.TurboWarp.desktop, linux-files/org.turbowarp.TurboWarp.metainfo.xml, linux-files/org.turbowarp.TurboWarp.mime.xml
Website	docs/index.html, docs/CNAME, docs/privacy.html, docs/uninstall.html, docs/changelog.json, docs/update_available.html
Localization	src-main/l10n/en.json, src-main/l10n/generated-translations.json
Store Listings	store-listings/imported.json (remove or update)
Build Scripts	release-automation/build.mjs, release-automation/linux.sh, scripts/generate-changelogs.mjs
Submodules	.gitmodules
Dependencies	package.json (scratch-gui, extensions)

Priority Order

1. High Priority (Required for first release):

   • CI/CD workflow simplification
   • Core branding files (brand.js, package.json)
   • README.md
   • Linux metadata files

2. Medium Priority (Important but not blocking):

   • Website files in docs/
   • Localization updates
   • Build scripts

3. Low Priority (Can be done later):

   • Store listings cleanup
   • Complete translation regeneration
   • Screenshot updates

Import In IDE

🤖 Prompt for AI Agents

## Observations

This is a forked TurboWarp Desktop application with extensive branding throughout the codebase. The existing CI/CD infrastructure includes sophisticated release workflows with code signing (SignPath for Windows, Apple notarization for macOS), Microsoft Store builds, and winget integration. The app uses submodules for scratch-gui and extensions, both pointing to TurboWarp repositories. The codebase has comprehensive localization, documentation, and a website in the `docs/` folder.

## Approach

The rebranding will be executed in phases: first, simplify CI/CD by removing unavailable features (code signing, store distributions, winget), then create a basic GitHub releases workflow, and finally update all branding references throughout the codebase. This approach prioritizes getting functional releases on GitHub first, as requested, while systematically replacing TurboWarp references with OmniBlocks branding.

## Implementation Steps

### Phase 1: CI/CD Simplification

#### 1.1 Remove Unnecessary Workflows

Delete or disable workflows that depend on unavailable infrastructure:
- Remove `file:.github/workflows/winget.yml` entirely (no winget support yet)
- Keep `file:.github/workflows/build-auto.yml` as-is for PR validation
- Keep `file:.github/workflows/build.yml` for manual testing

#### 1.2 Create Simplified Release Workflow

Modify `file:.github/workflows/release.yml` to remove code signing and store builds:

**For Linux job (`release-linux`):**
- Remove Microsoft Store and code signing references
- Keep: Debian, AppImage, and tar.gz builds
- Update upload commands to use `OmniBlocks` and `desktop` as owner/repo parameters in the upload script calls

**For macOS job (`release-mac`):**
- Remove all Apple notarization steps (lines 74-96 with APPLE_API_* secrets)
- Remove code signing certificate steps (CSC_LINK, CSC_KEY_PASSWORD)
- Remove Mac App Store builds (`--mas` flags)
- Keep only basic DMG builds without signing: `node release-automation/build.mjs --mac --universal`
- Update upload commands to use `OmniBlocks` and `desktop`

**For Windows job (`release-windows`):**
- Remove SignPath signing steps (lines 171-189)
- Remove Microsoft Store builds (`--microsoft-store` flag)
- Keep only basic NSIS installer and portable builds
- Update upload commands to use `OmniBlocks` and `desktop`
- Remove separate signed/unsigned artifact uploads

### Phase 2: Core Branding Updates

#### 2.1 Central Configuration Files

Update `file:src-main/brand.js`:
```
PLATFORM_NAME: 'OmniBlocks'
APP_NAME: 'OmniBlocks Desktop'
PACKAGER_NAME: 'OmniBlocks Packager'
```

Update `file:package.json`:
- `name`: `"omniblocks-desktop"`
- `description`: Update to describe OmniBlocks
- `author`: Update to OmniBlocks team information
- `homepage`: Update to OmniBlocks website URL
- `repository.url`: `"https://github.com/OmniBlocks/desktop.git"`
- `bugs.url`: `"https://github.com/OmniBlocks/desktop/issues"`
- `bugs.email`: Update to OmniBlocks contact email
- `build.appId`: `"org.omniblocks.desktop"`
- `build.productName`: `"OmniBlocks"`
- Remove or update `build.appx` section (Microsoft Store config)
- Update `build.linux.executableName`: `"omniblocks-desktop"`
- Update `build.linux.synopsis` and `description`

#### 2.2 Documentation Files

Update `file:README.md`:
- Replace all "TurboWarp" references with "OmniBlocks"
- Update clone URL to OmniBlocks repository
- Update download links to point to OmniBlocks releases
- Update data path locations (replace `turbowarp-desktop` with `omniblocks-desktop`)
- Remove code signing policy section
- Update uninstall link

Update `file:changelog.md`:
- Add new entry at top documenting the rebrand to OmniBlocks
- Keep existing TurboWarp history for reference (optional: add note that earlier versions were TurboWarp)

#### 2.3 Linux Metadata Files

Update `file:linux-files/org.turbowarp.TurboWarp.desktop`:
- Rename file to `org.omniblocks.OmniBlocks.desktop`
- Update `Name`: `"OmniBlocks"`
- Update `Exec` path: `/opt/OmniBlocks/omniblocks-desktop %U`
- Update `Icon`: `"org.omniblocks.OmniBlocks"`
- Update `StartupWMClass`: `"omniblocks-desktop"`
- Update `Comment` to describe OmniBlocks

Update `file:linux-files/org.turbowarp.TurboWarp.metainfo.xml`:
- Rename file to `org.omniblocks.OmniBlocks.metainfo.xml`
- Update `<id>`: `"org.omniblocks.OmniBlocks"`
- Update `<launchable>`: `"org.omniblocks.OmniBlocks.desktop"`
- Update `<name>`: `"OmniBlocks"`
- Update `<developer>` information
- Update all `<url>` elements to point to OmniBlocks domains/repositories
- Update `<description>` content
- Update screenshot URLs (will need new screenshots)
- Update release URLs in `<releases>` section to point to OmniBlocks repository

Update `file:linux-files/org.turbowarp.TurboWarp.mime.xml`:
- Rename file to `org.omniblocks.OmniBlocks.mime.xml`
- Update mime type IDs if needed

### Phase 3: Website and Documentation

#### 3.1 Website Files in docs/

Update `file:docs/CNAME`:
- Change domain to OmniBlocks domain (or remove if using GitHub Pages default)

Update `file:docs/index.html`:
- Replace all TurboWarp branding with OmniBlocks
- Update logo SVG
- Update download links to OmniBlocks releases
- Update repository links
- Update privacy policy link
- Update screenshot images
- Update Open Graph and Twitter card metadata
- Update changelog section with OmniBlocks releases

Update other docs files:
- `file:docs/privacy.html` - Update branding and contact information
- `file:docs/uninstall.html` - Update instructions with OmniBlocks paths
- `file:docs/stats.html` - Update or remove if TurboWarp-specific
- `file:docs/update_available.html` - Update branding
- `file:docs/changelog.json` - Update with OmniBlocks releases

#### 3.2 Submodules

Update `file:.gitmodules`:
- Change screenshot submodule URL to OmniBlocks repository (create `OmniBlocks/desktop-screenshots` repo first)
- Or remove submodule if not needed initially

### Phase 4: Dependencies and Extensions

#### 4.1 Package Dependencies

In `file:package.json`, evaluate these dependencies:
- `"scratch-gui": "github:TurboWarp/scratch-gui#develop"` - Check if OmniBlocks has a fork at `github:OmniBlocks/scratch-gui`
- `"@turbowarp/extensions": "github:TurboWarp/extensions#master"` - Check if OmniBlocks has a fork

If OmniBlocks forks exist, update the URLs. Otherwise, keep TurboWarp dependencies temporarily.

#### 4.2 Scripts

Update `file:scripts/packager.json`:
- Update `src` URL if OmniBlocks has its own packager
- Otherwise keep TurboWarp packager temporarily

### Phase 5: Localization and Store Listings

#### 5.1 Localization Files

Update `file:src-main/l10n/en.json`:
- Replace TurboWarp references in strings with OmniBlocks
- Update website URLs in developer comments
- Update app name placeholders

Update `file:src-main/l10n/generated-translations.json`:
- This file is generated, so it will be updated when translations are regenerated
- May need to run translation generation scripts after updating source strings

#### 5.2 Store Listings

Update or remove `file:store-listings/imported.json`:
- Either remove entirely (no store presence yet)
- Or update all TurboWarp references to OmniBlocks for future use

### Phase 6: Build and Release Scripts

#### 6.1 Release Automation

Update `file:release-automation/build.mjs`:
- Review for any hardcoded TurboWarp references
- Update any branding strings
- Remove code signing logic if present

Update `file:release-automation/linux.sh`:
- Update any TurboWarp references
- Update package names

#### 6.2 Other Scripts

Review and update scripts in `file:scripts/` directory:
- `generate-changelogs.mjs` - Update for OmniBlocks branding
- `download-packager.mjs` - Update if using OmniBlocks packager
- `prepare-extensions.mjs` - Update if using OmniBlocks extensions

### Phase 7: Miscellaneous Files

Update remaining files with TurboWarp references:
- `file:webpack.config.cjs` - Check for any hardcoded paths or references
- `file:src-renderer-webpack/` files - Update any branding in UI components
- `file:src-main/` files - Update window titles, menu items, dialogs
- `file:src-preload/` files - Update any exposed branding
- `file:debian/` files - Update Debian packaging scripts

### Phase 8: Testing and Validation

After all changes:

1. **Test local build:**
   - Run `npm ci`
   - Run `npm run fetch`
   - Run `npm run webpack:prod`
   - Run `npm run electron:start`
   - Verify app launches with OmniBlocks branding

2. **Test packaging:**
   - Run `npm run electron:package:dir`
   - Verify packaged app works correctly

3. **Test CI workflow:**
   - Push changes to a test branch
   - Verify `build-auto.yml` workflow succeeds
   - Create a test tag (e.g., `v0.1.0-test`)
   - Verify simplified `release.yml` workflow builds and uploads artifacts

4. **Create first release:**
   - Tag with `v1.0.0` or appropriate version
   - Verify all artifacts are uploaded to GitHub releases
   - Test downloads from GitHub releases

## Implementation Sequence Diagram

```mermaid
sequenceDiagram
    participant Dev as Developer
    participant Repo as Repository
    participant CI as GitHub Actions
    participant Release as GitHub Releases

    Note over Dev,Release: Phase 1: CI/CD Simplification
    Dev->>Repo: Remove winget.yml
    Dev->>Repo: Simplify release.yml (remove signing)
    Dev->>Repo: Update upload script calls

    Note over Dev,Release: Phase 2: Core Branding
    Dev->>Repo: Update brand.js
    Dev->>Repo: Update package.json
    Dev->>Repo: Update README.md
    Dev->>Repo: Update Linux metadata files

    Note over Dev,Release: Phase 3: Website & Docs
    Dev->>Repo: Update docs/index.html
    Dev->>Repo: Update docs/CNAME
    Dev->>Repo: Update other docs files

    Note over Dev,Release: Phase 4: Dependencies
    Dev->>Repo: Update package.json dependencies
    Dev->>Repo: Update submodules

    Note over Dev,Release: Phase 5: Localization
    Dev->>Repo: Update l10n files
    Dev->>Repo: Update/remove store listings

    Note over Dev,Release: Phase 6: Build Scripts
    Dev->>Repo: Update release-automation scripts
    Dev->>Repo: Update helper scripts

    Note over Dev,Release: Phase 7: Miscellaneous
    Dev->>Repo: Update remaining files

    Note over Dev,Release: Phase 8: Testing
    Dev->>Repo: Push to test branch
    Repo->>CI: Trigger build-auto workflow
    CI->>Dev: Build success/failure
    Dev->>Repo: Create test tag
    Repo->>CI: Trigger release workflow
    CI->>Release: Upload artifacts
    Dev->>Release: Verify downloads
    Dev->>Repo: Create v1.0.0 tag
    Repo->>CI: Trigger release workflow
    CI->>Release: Upload official release
```

## Files Requiring Updates

| Category | Files |
|----------|-------|
| **CI/CD** | `.github/workflows/release.yml`, `.github/workflows/winget.yml` (delete) |
| **Core Config** | `package.json`, `src-main/brand.js`, `webpack.config.cjs` |
| **Documentation** | `README.md`, `changelog.md` |
| **Linux Metadata** | `linux-files/org.turbowarp.TurboWarp.desktop`, `linux-files/org.turbowarp.TurboWarp.metainfo.xml`, `linux-files/org.turbowarp.TurboWarp.mime.xml` |
| **Website** | `docs/index.html`, `docs/CNAME`, `docs/privacy.html`, `docs/uninstall.html`, `docs/changelog.json`, `docs/update_available.html` |
| **Localization** | `src-main/l10n/en.json`, `src-main/l10n/generated-translations.json` |
| **Store Listings** | `store-listings/imported.json` (remove or update) |
| **Build Scripts** | `release-automation/build.mjs`, `release-automation/linux.sh`, `scripts/generate-changelogs.mjs` |
| **Submodules** | `.gitmodules` |
| **Dependencies** | `package.json` (scratch-gui, extensions) |

## Priority Order

1. **High Priority (Required for first release):**
   - CI/CD workflow simplification
   - Core branding files (brand.js, package.json)
   - README.md
   - Linux metadata files

2. **Medium Priority (Important but not blocking):**
   - Website files in docs/
   - Localization updates
   - Build scripts

3. **Low Priority (Can be done later):**
   - Store listings cleanup
   - Complete translation regeneration
   - Screenshot updates

---

Execution Information

Branch: master
Commit: 0b39467

New Plan

Observations

Forked TurboWarp Desktop Electron app wrapping scratch-gui with extras like .sb3 file icons. No current OmniBlocks references (grep search found zero matches). package.json deps point to TurboWarp/scratch-gui#develop and TurboWarp/extensions#master. .gitmodules has TurboWarp/desktop-screenshots. OmniBlocks/scratch-gui GitHub fork exists (updated Nov 2025), rebranded/enhanced TurboWarp GUI for multi-language IDE (future Python/C editors), AGPLv3, with integrated extensions in src/lib/libraries/extensions/.

Approach

Phased rebranding leveraging existing OmniBlocks/scratch-gui fork for core UI (already rebranded over 10+ months). Simplify CI/CD to GitHub releases only (no signing/stores/winget). Update desktop wrapper branding, Linux metadata, docs, and scripts. Test incrementally: local builds first, then CI validation, finally tagged releases. Prioritizes functional GitHub artifacts quickly while ensuring consistency.

Implementation Steps

Phase 1: CI/CD Simplification

1.1 Remove Unnecessary Workflows

• Delete file:.github/workflows/winget.yml
• Retain file:.github/workflows/build-auto.yml (PR validation) and file:.github/workflows/build.yml (manual)

1.2 Simplified file:.github/workflows/release.yml

Linux (release-linux): Debian/AppImage/tar.gz only; update uploads to OmniBlocks/desktop.
macOS (release-mac): DMG only (node release-automation/build.mjs --mac --universal); remove notarization/signing/MAS.
Windows (release-windows): NSIS/portable only; remove SignPath/MS Store/signed variants; update uploads.

Phase 2: Core Branding

2.1 Config Files

file:src-main/brand.js:

PLATFORM_NAME: 'OmniBlocks'
APP_NAME: 'OmniBlocks Desktop'
PACKAGER_NAME: 'OmniBlocks Packager'

file:package.json:

• name: "omniblocks-desktop"
• description: "OmniBlocks Desktop: Block-based IDE wrapper with compiler, addons, themes."
• author: {name: "OmniBlocks", email: "support@omniblocks.org"} (update as needed)
• homepage: "https://omniblocks.org/desktop" (or GitHub)
• repository.url: "https://github.com/OmniBlocks/desktop.git"
• bugs: Update URLs/email
• build.appId: "org.omniblocks.desktop"
• build.productName: "OmniBlocks Desktop"
• Remove build.appx; update build.linux.executableName: "omniblocks-desktop"
• Update build.linux.synopsis/description
• Key deps update:
  • "scratch-gui": "github:OmniBlocks/scratch-gui#develop"
  • "@turbowarp/extensions": "github:TurboWarp/extensions#master" (retain temporarily; verify compatibility with OmniBlocks/scratch-gui or integrate from its extensions/)

2.2 Docs

file:README.md: Replace TurboWarp→OmniBlocks; update URLs/paths (omniblocks-desktop data dir).
file:changelog.md: Add rebrand entry atop.

2.3 Linux Metadata

Rename/update:

• file:linux-files/org.turbowarp.TurboWarp.desktop → org.omniblocks.OmniBlocks.desktop
  • Name: "OmniBlocks Desktop", Exec: /opt/OmniBlocks/omniblocks-desktop %U, Icon: "org.omniblocks.OmniBlocks"
• file:linux-files/org.turbowarp.TurboWarp.metainfo.xml → org.omniblocks.OmniBlocks.metainfo.xml (update id/name/developer/urls)
• file:linux-files/org.turbowarp.TurboWarp.mime.xml → org.omniblocks.OmniBlocks.mime.xml

Phase 3: Website/Docs

Update file:docs/:

• file:docs/CNAME: OmniBlocks domain or remove.
• file:docs/index.html: Branding, logos, links, metadata, screenshots.
• file:docs/privacy.html, file:docs/uninstall.html (paths), file:docs/changelog.json.

Phase 4: Submodules/Scripts

file:.gitmodules: Update docs/screenshots to OmniBlocks/desktop-screenshots (create if needed) or remove.

Scripts:

• file:scripts/download-packager.mjs: Update to OmniBlocks packager if available; else retain.
• file:scripts/prepare-extensions.mjs: Verify post-scratch-gui update.

Phase 5: Localization/Stores

file:src-main/l10n/en.json: OmniBlocks strings/URLs.
Remove file:store-listings/imported.json.

Phase 6: Build/Release Scripts

file:release-automation/build.mjs, file:release-automation/linux.sh: Remove signing; update names.
file:scripts/generate-changelogs.mjs: Branding.

Phase 7: UI/Wrapper Specifics

Scan/update file:src-main/, file:src-renderer-webpack/, file:src-preload/ for titles/menus/dialogs (.sb3 icons preserved).

Phase 8: Test/Release

1. npm ci && npm run fetch && npm run webpack:prod && npm run electron:start (verify OmniBlocks UI).
2. npm run electron:package:dir.
3. Test branch → build-auto.yml.
4. Tag v1.0.0 → release.yml → GitHub artifacts.

Sequence Diagram

sequenceDiagram
    participant Dev
    participant Repo
    participant CI
    participant GHReleases

    Note over Dev,GHReleases: Phases 1-2: CI/Core
    Dev->>Repo: Simplify workflows, delete winget
    Dev->>Repo: brand.js, package.json (deps→OmniBlocks/scratch-gui)
    Dev->>Repo: Linux files, README

    Note over Dev,GHReleases: Phases 3-6: Docs/Scripts
    Dev->>Repo: docs/, l10n, scripts, submodules

    Note over Dev,GHReleases: Phase 7-8: Finalize/Test
    Dev->>Repo: UI files
    Repo->>CI: Test branch (build-auto)
    Dev->>Repo: Tag v1.0.0
    Repo->>CI: release.yml
    CI->>GHReleases: Linux/macOS/Win artifacts

Loading

Key Files Table

Category	Files
CI/CD	.github/workflows/release.yml, delete winget.yml
Core	package.json (deps/appId), src-main/brand.js
Linux	linux-files/*.desktop/xml (rename/update)
Docs	README.md, docs/index.html, changelog.md
Scripts	release-automation/*, scripts/download-packager.mjs
Other	src-main/l10n/en.json, .gitmodules

Priority

1. Immediate (Release-blocking): Phase 1-2 (CI/deps/brand).
2. Next: Phases 3-5 (docs/localization).
3. Polish: 6-8 (scripts/UI/test).

Import In IDE

🤖 Prompt for AI Agents

## Observations

Forked TurboWarp Desktop Electron app wrapping scratch-gui with extras like .sb3 file icons. No current OmniBlocks references (grep search found zero matches). package.json deps point to TurboWarp/scratch-gui#develop and TurboWarp/extensions#master. .gitmodules has TurboWarp/desktop-screenshots. OmniBlocks/scratch-gui GitHub fork exists (updated Nov 2025), rebranded/enhanced TurboWarp GUI for multi-language IDE (future Python/C editors), AGPLv3, with integrated extensions in src/lib/libraries/extensions/.

## Approach

Phased rebranding leveraging existing OmniBlocks/scratch-gui fork for core UI (already rebranded over 10+ months). Simplify CI/CD to GitHub releases only (no signing/stores/winget). Update desktop wrapper branding, Linux metadata, docs, and scripts. Test incrementally: local builds first, then CI validation, finally tagged releases. Prioritizes functional GitHub artifacts quickly while ensuring consistency.

## Implementation Steps

### Phase 1: CI/CD Simplification

#### 1.1 Remove Unnecessary Workflows
- Delete `file:.github/workflows/winget.yml`
- Retain `file:.github/workflows/build-auto.yml` (PR validation) and `file:.github/workflows/build.yml` (manual)

#### 1.2 Simplified `file:.github/workflows/release.yml`
**Linux (`release-linux`):** Debian/AppImage/tar.gz only; update uploads to `OmniBlocks/desktop`.
**macOS (`release-mac`):** DMG only (`node release-automation/build.mjs --mac --universal`); remove notarization/signing/MAS.
**Windows (`release-windows`):** NSIS/portable only; remove SignPath/MS Store/signed variants; update uploads.

### Phase 2: Core Branding

#### 2.1 Config Files
`file:src-main/brand.js`:
```
PLATFORM_NAME: 'OmniBlocks'
APP_NAME: 'OmniBlocks Desktop'
PACKAGER_NAME: 'OmniBlocks Packager'
```

`file:package.json`:
- `name`: `"omniblocks-desktop"`
- `description`: "OmniBlocks Desktop: Block-based IDE wrapper with compiler, addons, themes."
- `author`: `{name: "OmniBlocks", email: "support@omniblocks.org"}` (update as needed)
- `homepage`: "https://omniblocks.org/desktop" (or GitHub)
- `repository.url`: "https://github.com/OmniBlocks/desktop.git"
- `bugs`: Update URLs/email
- `build.appId`: `"org.omniblocks.desktop"`
- `build.productName`: `"OmniBlocks Desktop"`
- Remove `build.appx`; update `build.linux.executableName`: `"omniblocks-desktop"`
- Update `build.linux.synopsis/description`
- **Key deps update:**
  - `"scratch-gui": "github:OmniBlocks/scratch-gui#develop"`
  - `"@turbowarp/extensions": "github:TurboWarp/extensions#master"` (retain temporarily; verify compatibility with OmniBlocks/scratch-gui or integrate from its extensions/)

#### 2.2 Docs
`file:README.md`: Replace TurboWarp→OmniBlocks; update URLs/paths (`omniblocks-desktop` data dir).
`file:changelog.md`: Add rebrand entry atop.

#### 2.3 Linux Metadata
Rename/update:
- `file:linux-files/org.turbowarp.TurboWarp.desktop` → `org.omniblocks.OmniBlocks.desktop`
  - `Name`: "OmniBlocks Desktop", `Exec`: `/opt/OmniBlocks/omniblocks-desktop %U`, `Icon`: "org.omniblocks.OmniBlocks"
- `file:linux-files/org.turbowarp.TurboWarp.metainfo.xml` → `org.omniblocks.OmniBlocks.metainfo.xml` (update id/name/developer/urls)
- `file:linux-files/org.turbowarp.TurboWarp.mime.xml` → `org.omniblocks.OmniBlocks.mime.xml`

### Phase 3: Website/Docs
Update `file:docs/`:
- `file:docs/CNAME`: OmniBlocks domain or remove.
- `file:docs/index.html`: Branding, logos, links, metadata, screenshots.
- `file:docs/privacy.html`, `file:docs/uninstall.html` (paths), `file:docs/changelog.json`.

### Phase 4: Submodules/Scripts
`file:.gitmodules`: Update `docs/screenshots` to OmniBlocks/desktop-screenshots (create if needed) or remove.

Scripts:
- `file:scripts/download-packager.mjs`: Update to OmniBlocks packager if available; else retain.
- `file:scripts/prepare-extensions.mjs`: Verify post-scratch-gui update.

### Phase 5: Localization/Stores
`file:src-main/l10n/en.json`: OmniBlocks strings/URLs.
Remove `file:store-listings/imported.json`.

### Phase 6: Build/Release Scripts
`file:release-automation/build.mjs`, `file:release-automation/linux.sh`: Remove signing; update names.
`file:scripts/generate-changelogs.mjs`: Branding.

### Phase 7: UI/Wrapper Specifics
Scan/update `file:src-main/`, `file:src-renderer-webpack/`, `file:src-preload/` for titles/menus/dialogs (.sb3 icons preserved).

### Phase 8: Test/Release
1. `npm ci && npm run fetch && npm run webpack:prod && npm run electron:start` (verify OmniBlocks UI).
2. `npm run electron:package:dir`.
3. Test branch → `build-auto.yml`.
4. Tag `v1.0.0` → `release.yml` → GitHub artifacts.

## Sequence Diagram

```mermaid
sequenceDiagram
    participant Dev
    participant Repo
    participant CI
    participant GHReleases

    Note over Dev,GHReleases: Phases 1-2: CI/Core
    Dev->>Repo: Simplify workflows, delete winget
    Dev->>Repo: brand.js, package.json (deps→OmniBlocks/scratch-gui)
    Dev->>Repo: Linux files, README

    Note over Dev,GHReleases: Phases 3-6: Docs/Scripts
    Dev->>Repo: docs/, l10n, scripts, submodules

    Note over Dev,GHReleases: Phase 7-8: Finalize/Test
    Dev->>Repo: UI files
    Repo->>CI: Test branch (build-auto)
    Dev->>Repo: Tag v1.0.0
    Repo->>CI: release.yml
    CI->>GHReleases: Linux/macOS/Win artifacts
```

## Key Files Table

| Category | Files |
|----------|-------|
| **CI/CD** | `.github/workflows/release.yml`, delete `winget.yml` |
| **Core** | `package.json` (deps/appId), `src-main/brand.js` |
| **Linux** | `linux-files/*.desktop/xml` (rename/update) |
| **Docs** | `README.md`, `docs/index.html`, `changelog.md` |
| **Scripts** | `release-automation/*`, `scripts/download-packager.mjs` |
| **Other** | `src-main/l10n/en.json`, `.gitmodules` |

## Priority
1. **Immediate (Release-blocking):** Phase 1-2 (CI/deps/brand).
2. **Next:** Phases 3-5 (docs/localization).
3. **Polish:** 6-8 (scripts/UI/test).

---

Execution Information

Branch: master
Commit: 0b39467

[ampelectrecuted]

@supervoidcoder can i do all the flatpak stuff

[supervoidcoder]

@supervoidcoder can i do all the flatpak stuff

um ok