Inline core generation engine support, full repo refactor along with frontend package | dropped electron support

.env.example

@@ -1,8 +1,25 @@
-# ComfyUI backend the user points Storyline at. Falls back to this if no in-app
-# setting is configured. See electron/main/comfy/ for how it is consumed.
-COMFYUI_URL=http://127.0.0.1:8188
-
-# fal.ai API key for the closed-model generation engine (openai/gpt-image-2, LTX, ...).
-# Bring your own key from https://fal.ai/dashboard/keys. Overridden by the in-app setting
-# (stored encrypted). See electron/main/fal/ for how it is consumed.
-FAL_KEY=
+# Inline Studio is configured through INLINE_* environment variables read by Inline Core (the engine
+# in core/). You usually don't need a .env — the friendly `core/webui.sh` flags set these for you
+# (see `./webui.sh --help` or the README's Command-line options). This file just documents them.
+
+# --- Server bind ---
+# INLINE_HOST=127.0.0.1        # 0.0.0.0 to allow other machines on the network (webui.sh --listen)
+# INLINE_PORT=8848
+
+# --- Paths ---
+# INLINE_MODELS_DIR=./models   # where model weights are scanned from (drop files here)
+# INLINE_DATA_DIR=./.inline    # runs + generated takes
+# INLINE_FRONTEND_ROOT=../dist-web   # serve a local SPA build instead of the installed UI package (dev)
+
+# --- Device / memory ---
+# INLINE_PROFILE=              # gpu-max | lowvram | cpu (default: auto-detected)
+# INLINE_VRAM_BUDGET_GB=       # treat the GPU as having this many GB of usable VRAM
+# INLINE_PARALLEL=             # multi-GPU split, e.g. pipefusion=2 (auto with 2+ GPUs)
+
+# --- Z-Image model overrides (optional; the model popup / dropping files under models/ is preferred) ---
+# INLINE_ZIMAGE_MODEL=         # a diffusion .safetensors file or a diffusers dir
+# INLINE_ZIMAGE_VAE=           # a local VAE file or dir
+# INLINE_ZIMAGE_TEXT_ENCODER=  # a local HF-format text-encoder dir
+
+# The fal.ai API key for hosted models is NOT set here — add it in the app's Settings (stored
+# server-side under Core's data dir), so it never lives in your shell environment or a checked-in file.

.github/workflows/publish-core.yml

@@ -0,0 +1,59 @@
+# Publish the Inline Core engine (inline-core) to PyPI, so `pip install -r requirements.txt`
+# pulls the engine + runtime with no source checkout. The prebuilt web UI is published separately by
+# publish-frontend.yml — kept in its own file so each package's PyPI *pending* trusted publisher has a
+# distinct GitHub config (owner + repo + workflow filename + environment), which PyPI requires.
+#
+# Trigger: push a tag like `v1.1.1`, publish a GitHub Release, or run manually (workflow_dispatch with
+# an explicit version). The version is derived from the tag and stamped into core/pyproject.toml.
+#
+# Auth: PyPI Trusted Publishing (OIDC) — add a pending publisher on PyPI for project
+# `inline-core`, repo, workflow `publish-core.yml`, environment blank. No secrets to store. To
+# use an API token instead, drop `permissions.id-token` and pass
+# `password: ${{ secrets.PYPI_API_TOKEN }}` to the publish step.
+name: Publish engine to PyPI
+
+on:
+  push:
+    tags: ['v*']
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Version to publish (e.g. 1.1.1). Defaults to the tag.'
+        required: false
+
+jobs:
+  engine:
+    name: Publish inline-core
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write # PyPI Trusted Publishing (OIDC)
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Resolve version
+        id: ver
+        run: |
+          VERSION="${{ github.event.inputs.version }}"
+          if [ -z "$VERSION" ]; then VERSION="${GITHUB_REF_NAME#v}"; fi
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+          echo "Publishing version $VERSION"
+
+      - name: Stamp the package version
+        run: |
+          sed -i "s/^version = .*/version = \"${{ steps.ver.outputs.version }}\"/" core/pyproject.toml
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Build the wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build core --outdir dist
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist

.github/workflows/publish-frontend.yml

@@ -0,0 +1,80 @@
+# Build the SPA and publish the prebuilt-frontend wheel (inline-studio-frontend) to PyPI, so end
+# users get the UI with no Node build — mirroring ComfyUI's comfyui-frontend-package. The engine
+# (inline-core) is published by its own workflow, publish-core.yml. They are split into two
+# files on purpose: PyPI requires each *pending* trusted publisher to have a unique GitHub config
+# (owner + repo + workflow filename + environment), so two packages can't share one workflow file
+# until both projects exist. See packages/frontend/README.md for the manual equivalent.
+#
+# Trigger: push a tag like `v1.1.1`, publish a GitHub Release, or run manually (workflow_dispatch with
+# an explicit version). The version is derived from the tag (`v1.1.1` -> `1.1.1`) and stamped into the
+# wheel so it version-tracks the release.
+#
+# Auth: PyPI Trusted Publishing (OIDC) — add a pending publisher on PyPI for project
+# `inline-studio-frontend`, repo, workflow `publish-frontend.yml`, environment blank. No secrets to
+# store. To use an API token instead, drop `permissions.id-token` and pass
+# `password: ${{ secrets.PYPI_API_TOKEN }}` to the publish step.
+name: Publish frontend to PyPI
+
+on:
+  push:
+    tags: ['v*']
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      version:
+        description: 'Version to publish (e.g. 1.1.1). Defaults to the tag.'
+        required: false
+
+jobs:
+  frontend:
+    name: Build SPA + publish inline-studio-frontend
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write # PyPI Trusted Publishing (OIDC)
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Resolve version
+        id: ver
+        run: |
+          VERSION="${{ github.event.inputs.version }}"
+          if [ -z "$VERSION" ]; then VERSION="${GITHUB_REF_NAME#v}"; fi
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+          echo "Publishing version $VERSION"
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          cache: 'npm'
+
+      - name: Build the SPA
+        run: |
+          npm ci
+          npm run build:spa   # -> dist-web/
+
+      - name: Stage the build into the wheel payload
+        run: |
+          rm -rf packages/frontend/inline_studio_frontend/static
+          mkdir -p packages/frontend/inline_studio_frontend/static
+          cp -r dist-web/* packages/frontend/inline_studio_frontend/static/
+          test -f packages/frontend/inline_studio_frontend/static/index.html
+
+      - name: Stamp the package version
+        run: |
+          sed -i "s/^version = .*/version = \"${{ steps.ver.outputs.version }}\"/" \
+            packages/frontend/pyproject.toml
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Build the wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build packages/frontend --outdir dist
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          packages-dir: dist

.gitignore

@@ -1,6 +1,10 @@
 node_modules
 out
 dist
+dist-web
+# The built SPA copied into the PyPI frontend package at publish time (keep the .gitkeep).
+packages/frontend/inline_studio_frontend/static/*
+!packages/frontend/inline_studio_frontend/static/.gitkeep
 *.log
 .DS_Store
 .env