Develop

.eslintrc.cjs

@@ -7,7 +7,13 @@ module.exports = {
     'plugin:react/jsx-runtime',
     'plugin:react-hooks/recommended',
   ],
-  ignorePatterns: ['dist', '.eslintrc.cjs'],
+  ignorePatterns: ['dist', '.eslintrc.cjs', 'public/', 'nginx/'],
+  overrides: [
+    {
+      files: ['server/**/*.js', 'vite.config.js'],
+      env: { node: true },
+    },
+  ],
   parserOptions: { ecmaVersion: 'latest', sourceType: 'module' },
   settings: { react: { version: '18.2' } },
   plugins: ['react-refresh'],

.github/workflows/deploy-pages.yml

@@ -0,0 +1,64 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches: [main]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: pages
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Configure Pages
+        id: pages
+        uses: actions/configure-pages@v5
+
+      - run: npm ci
+
+      # The flamapy wheels served to the browser are not tracked in git (see
+      # .gitignore); regenerate them from flamapy.version before the build so
+      # Vite copies them into dist/.
+      - name: Build flamapy wheels
+        run: make build-wheels
+
+      - name: Build
+        env:
+          VITE_BASE_PATH: ${{ steps.pages.outputs.base_path }}/
+        run: npm run build
+
+      - name: SPA fallback
+        run: cp dist/index.html dist/404.html
+
+      - uses: actions/upload-pages-artifact@v3
+        with:
+          path: dist
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - id: deployment
+        uses: actions/deploy-pages@v4

.github/workflows/docker-image.yml

@@ -8,6 +8,7 @@ on:
 jobs:
   build-and-publish:
     runs-on: ubuntu-latest
+    if: github.event.workflow_run.conclusion == 'success'
 
     steps:
       - name: Checkout the code
@@ -33,6 +34,7 @@ jobs:
 
   deploy:
     runs-on: ubuntu-latest
+    if: github.event.workflow_run.conclusion == 'success'
 
     steps:
       - name: Deploy

.github/workflows/lint.yml

@@ -0,0 +1,29 @@
+name: Lint
+
+on:
+  pull_request:
+    branches:
+      - main
+  push:
+    branches:
+      - develop
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run ESLint
+        run: npm run lint

.github/workflows/pytest.yaml

@@ -16,13 +16,25 @@ jobs:
       - name: Set up Python
         uses: actions/setup-python@v5
         with:
-          python-version: "3.10"
+          python-version: "3.11"
+
+      # The flamapy wheels served to the browser are not tracked in git (see
+      # .gitignore); regenerate them from flamapy.version so the tests run
+      # against the same artifacts the browser loads.
+      - name: Build flamapy wheels
+        run: make build-wheels
 
       - name: Install dependencies
         run: |
-          python -m pip install --upgrade pip
+          python -m pip install --upgrade pip setuptools wheel
+          # Install the exact flamapy wheels served to the browser (not a PyPI
+          # pin), so the tests run against the shipped artifacts. The z3_solver
+          # wheel is WASM-only and cannot install natively, so it is excluded;
+          # the native z3-solver comes from requirements.txt instead.
+          pip install --no-deps $(ls public/flamapy/*.whl | grep -v 'wasm')
+          # Native solver backends + test tooling (python-sat, z3-solver, pytest).
           pip install -r requirements.txt
 
       - name: Run tests
         run: |
-          pytest
+          pytest --cov=public tests/

.github/workflows/release-please.yml

@@ -18,4 +18,8 @@ jobs:
           # this is a built-in strategy in release-please, see "Action Inputs"
           # for more options
           release-type: node
-          token: ${{ secrets.RELEASE_TOKEN }}
+          # Built-in token (auto-provisioned, never expires). The job's
+          # permissions block below grants the contents/PR write access
+          # release-please needs. The Docker workflow still triggers because it
+          # listens on `workflow_run`, which fires regardless of the token used.
+          token: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/update-flamapy-wheels.yml

@@ -0,0 +1,54 @@
+name: Update flamapy wheels
+
+# Keeps the flamapy-authored wheels in public/flamapy/ in sync with the flamapy
+# release pinned in ./flamapy.version. Runs whenever that file changes and on
+# demand; opens a pull request whenever the bundle changes. Third-party deps and
+# the z3_solver wasm wheel are not touched (use `make build-wheels` for those).
+on:
+  push:
+    paths:
+      - "flamapy.version"
+  workflow_dispatch:
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  update:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+
+      - name: Update flamapy wheels from the latest release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: python scripts/update_flamapy_wheels.py
+
+      - name: Open a pull request with the refreshed wheels
+        uses: peter-evans/create-pull-request@v6
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          branch: chore/update-flamapy-wheels
+          delete-branch: true
+          title: "chore: update flamapy wheels to the pinned release"
+          commit-message: "chore: sync flamapy wheels with the pinned flamapy release"
+          body: |
+            Automated update of the flamapy-authored wheels in `public/flamapy/`
+            from the [flamapy release](https://github.com/flamapy/flamapy/releases)
+            pinned in `flamapy.version`.
+
+            Refreshed `flamapy`, `flamapy-fw`, `flamapy-fm`, `flamapy-sat`,
+            `flamapy-bdd` and `flamapy-z3`, and rewrote the matching filenames in
+            `plugins.conf.json`. Third-party dependencies and the `z3_solver`
+            wasm wheel are unchanged.
+
+            > Note: PRs opened with the default `GITHUB_TOKEN` do not trigger
+            > other workflows. Push an empty commit or re-open the PR to run CI.
+          add-paths: |
+            public/flamapy/*.whl
+            public/flamapy/plugins.conf.json

.gitignore

@@ -24,4 +24,26 @@ dist-ssr
 *.sw?
 .venv
 */__pycache__
-*/*/__pycache__
+*/*/__pycache__
+
+env/
+
+# Claude Code
+CLAUDE.md
+.claude/
+
+# Local environment variables
+.env
+.env.example
+
+# start_coding.sh local environments
+start_coding.sh
+
+# Flamapy wheels served to the browser are build artifacts: they are
+# regenerated by `make build-wheels` (versions from flamapy.version + the
+# Makefile dep list) and the deploy pipelines rebuild them before bundling, so
+# they are not tracked. The two wheels below are manually vendored and have no
+# PyPI/release-bundle source, so they MUST stay tracked.
+public/flamapy/*.whl
+!public/flamapy/flamapy_configurator-*.whl
+!public/flamapy/z3_solver-*.whl

Dockerfile

@@ -25,12 +25,26 @@ EXPOSE 5173
 # Start the Vite development server
 CMD ["npm", "run", "dev", "--", "--host"]
 
-# Stage 3: Production Build
+# Stage 3: Regenerate the flamapy wheels served to the browser.
+# These wheels are not tracked in git (see .gitignore); `make build-wheels`
+# rebuilds them from flamapy.version + the Makefile dep list. The two manually
+# vendored wheels (flamapy-configurator, z3_solver wasm) are copied in from the
+# build context, which `make build-wheels` leaves untouched.
+FROM python:3.11 AS wheels
+WORKDIR /app
+COPY Makefile flamapy.version ./
+COPY public/flamapy ./public/flamapy
+RUN make build-wheels
+
+# Stage 4: Production Build
 FROM base AS build
 
 # Set environment to production
 ENV NODE_ENV=production
 
+# Pull in the regenerated wheels so Vite copies them into dist/
+COPY --from=wheels /app/public/flamapy ./public/flamapy
+
 # Build the app
 RUN npm run build
 
@@ -43,9 +57,12 @@ ENV NODE_ENV=production
 # Copy built files from the build stage
 COPY --from=build /app/dist /usr/share/nginx/html
 
-# Copy custom Nginx configuration, if needed (optional)
+# Copy custom Nginx configuration
 COPY nginx.conf /etc/nginx/nginx.conf
 
+# Copy njs script for the /raw endpoint (UVLHub integration)
+COPY nginx/raw.js /etc/nginx/njs/raw.js
+
 # Expose port 80 for the Nginx server
 EXPOSE 80