intervalssync 0.9.3__tar.gz

intervalssync-0.9.3/.env.example

@@ -0,0 +1,19 @@
+# Local development only. Copy to .env and run:
+#   uv run --env-file .env intervalssync-gui                         # GUI (uv loads env)
+#   uv run intervalssync sync --env-file .env                        # iGPSPORT → intervals.icu
+#   uv run intervalssync sync --source bryton --env-file .env         # Bryton → intervals.icu
+#   uv run intervalssync upload-workouts --env-file .env               # intervals.icu → iGPSPORT workouts
+#   uv run intervalssync sync-zones --env-file .env                    # intervals.icu → iGPSPORT profile
+#
+# iGPSPORT sync requires INTERVALSSYNC_IGPSPORT_* + INTERVALSSYNC_INTERVALS_API_KEY.
+# Bryton sync requires INTERVALSSYNC_BRYTON_* + INTERVALSSYNC_INTERVALS_API_KEY.
+# IGPSYNC_DROPBOX_APP_KEY is optional (Dropbox secondary upload in the GUI).
+IGPSYNC_DROPBOX_APP_KEY=
+
+INTERVALSSYNC_IGPSPORT_USER=
+INTERVALSSYNC_IGPSPORT_PASSWORD=
+# international (default) or china — use china for app.igpsport.cn accounts
+INTERVALSSYNC_IGPSPORT_REGION=international
+INTERVALSSYNC_BRYTON_EMAIL=
+INTERVALSSYNC_BRYTON_PASSWORD=
+INTERVALSSYNC_INTERVALS_API_KEY=

intervalssync-0.9.3/.github/FUNDING.yml

@@ -0,0 +1 @@
+ko_fi: jorge_huxley

intervalssync-0.9.3/.github/pull_request_template.md

@@ -0,0 +1,27 @@
+<!--
+Title (the field above): one imperative line with a Conventional Commits prefix,
+e.g. feat(android): build and publish an APK on release
+Common prefixes: feat, fix, ci, docs, refactor, test, chore, build, perf
+-->
+
+## Summary
+
+<!-- 2-3 sentences: what changed and *why*. The motivation matters more than the
+diff, which reviewers can read themselves. -->
+
+## Changes
+
+<!-- Short bullets, grouped by area. -->
+-
+
+## Verification
+
+<!-- What you checked, and honestly what you didn't. -->
+- [ ] Tests pass (`uv run pytest`)
+-
+
+## Notes / follow-ups
+
+<!-- Deferred work, risks, anything reviewers should know.
+Link issues with "Closes #123" to auto-close them on merge. -->
+-

intervalssync-0.9.3/.github/workflows/release.yml

@@ -0,0 +1,235 @@
+# Builds the Windows app, macOS app, Android APK, and Python package. GUI
+# artifacts go to one GitHub Release; stable Python packages also go to PyPI.
+#
+# It runs only when you push a version tag like "v0.1.0" — see how to do that
+# in the README's "Cutting a release" section. The build jobs upload their
+# artifacts; a final release job attaches them to one release and generates the
+# notes once (so they aren't duplicated).
+
+name: Release
+
+on:
+  push:
+    tags:
+      - "v*" # any tag starting with v, e.g. v0.1.0, v1.2.3
+
+# The automatic GITHUB_TOKEN needs write access to create the Release.
+permissions:
+  contents: write
+
+env:
+  PYTHONUTF8: "1" # make Python use UTF-8 everywhere (our progress text uses •, ↷, …)
+  FLET_CLI_NO_RICH_OUTPUT: "1" # plain, log-friendly output from `flet build`
+
+jobs:
+  python-package:
+    # Pre-releases remain GitHub-only. `uvx intervalssync@latest` therefore
+    # always resolves to a tested stable release from PyPI.
+    if: ${{ !contains(github.ref_name, '-') }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+
+      - name: Compute version from tag
+        run: echo "APP_VERSION=${GITHUB_REF_NAME#v}" >> "$GITHUB_ENV"
+
+      - name: Stamp package and runtime versions
+        run: |
+          uv version "$APP_VERSION" --frozen
+          echo "__version__ = \"$APP_VERSION\"" > src/intervalssync/_version.py
+
+      - name: Build distributions
+        run: uv build
+
+      - name: Validate distributions
+        run: uvx --from twine twine check dist/*
+
+      - name: Smoke-test the wheel
+        run: |
+          wheel="dist/intervalssync-${APP_VERSION}-py3-none-any.whl"
+          uvx --python 3.13 --from "$wheel" intervalssync --version
+          uvx --python 3.13 --from "$wheel" intervalssync --help
+          mkdir -p "$RUNNER_TEMP/hermes"
+          {
+            echo "INTERVALSSYNC_IGPSPORT_USER=test@example.com"
+            echo "INTERVALSSYNC_IGPSPORT_PASSWORD=test-password"
+            echo "INTERVALSSYNC_INTERVALS_API_KEY=test-api-key"
+          } > "$RUNNER_TEMP/hermes/.env"
+          HERMES_HOME="$RUNNER_TEMP/hermes" uvx --python 3.13 --from "$wheel" intervalssync check --json
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: python-package
+          path: dist/*
+
+  windows:
+    runs-on: windows-latest # ships with Visual Studio 2022 + C++
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+
+      # The git tag is the single source of truth for the version. Strip the
+      # leading "v" (v0.2.1 -> 0.2.1) for flet's x.y.z build-version.
+      - name: Compute version from tag
+        shell: bash
+        run: echo "APP_VERSION=${GITHUB_REF_NAME#v}" >> "$GITHUB_ENV"
+
+      # Stamp it into the app so the in-app About dialog shows the real version.
+      - name: Stamp version into the app
+        shell: bash
+        run: echo "__version__ = \"$APP_VERSION\"" > src/intervalssync/_version.py
+
+      - name: Stamp Dropbox app key into the app
+        shell: pwsh
+        env:
+          IGPSYNC_DROPBOX_APP_KEY: ${{ secrets.IGPSYNC_DROPBOX_APP_KEY }}
+        run: |
+          python -c "from pathlib import Path; import os; Path('src/intervalssync/_dropbox_app_key.py').write_text('DROPBOX_APP_KEY = ' + repr(os.getenv('IGPSYNC_DROPBOX_APP_KEY', '')) + '\n', encoding='utf-8')"
+
+      - name: Build Windows app
+        run: uv run flet build windows --yes --verbose --build-version "${{ env.APP_VERSION }}"
+
+      # Name the zip after the tag, e.g. intervalssync-v0.2.0-windows.zip
+      - name: Package into a versioned zip
+        shell: pwsh
+        run: Compress-Archive -Path build/windows/* -DestinationPath "intervalssync-${{ github.ref_name }}-windows.zip"
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: windows
+          path: "intervalssync-${{ github.ref_name }}-windows.zip"
+
+  android:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+
+      - name: Compute version from tag
+        run: echo "APP_VERSION=${GITHUB_REF_NAME#v}" >> "$GITHUB_ENV"
+
+      - name: Stamp version into the app
+        run: echo "__version__ = \"$APP_VERSION\"" > src/intervalssync/_version.py
+
+      - name: Stamp Dropbox app key into the app
+        env:
+          IGPSYNC_DROPBOX_APP_KEY: ${{ secrets.IGPSYNC_DROPBOX_APP_KEY }}
+        run: |
+          python -c "from pathlib import Path; import os; Path('src/intervalssync/_dropbox_app_key.py').write_text('DROPBOX_APP_KEY = ' + repr(os.getenv('IGPSYNC_DROPBOX_APP_KEY', '')) + '\n', encoding='utf-8')"
+
+      # Use a stable release key if the keystore secrets are configured, so every
+      # release shares one signature and Android installs updates over the top
+      # (no uninstall). Without the secrets, flet falls back to a debug key.
+      - name: Configure APK signing (if keystore secret is set)
+        env:
+          KEYSTORE_B64: ${{ secrets.ANDROID_KEYSTORE_BASE64 }}
+          KEYSTORE_PASSWORD: ${{ secrets.ANDROID_KEYSTORE_PASSWORD }}
+          KEY_ALIAS: ${{ secrets.ANDROID_KEY_ALIAS }}
+        run: |
+          if [ -n "$KEYSTORE_B64" ]; then
+            echo "$KEYSTORE_B64" | base64 -d > "$RUNNER_TEMP/release.jks"
+            {
+              echo "FLET_ANDROID_SIGNING_KEY_STORE=$RUNNER_TEMP/release.jks"
+              echo "FLET_ANDROID_SIGNING_KEY_STORE_PASSWORD=$KEYSTORE_PASSWORD"
+              echo "FLET_ANDROID_SIGNING_KEY_PASSWORD=$KEYSTORE_PASSWORD"
+              echo "FLET_ANDROID_SIGNING_KEY_ALIAS=$KEY_ALIAS"
+            } >> "$GITHUB_ENV"
+            echo "Release signing configured."
+          else
+            echo "No keystore secret set — APK will be debug-signed."
+          fi
+
+      # flet build apk auto-installs the Flutter/Android SDK + JDK on first run.
+      # It picks up the FLET_ANDROID_SIGNING_* env vars set above when present.
+      - name: Build Android APK
+        run: uv run flet build apk --yes --verbose --build-version "${{ env.APP_VERSION }}"
+
+      - name: Rename APK with the version
+        run: mv build/apk/*.apk "intervalssync-${{ github.ref_name }}-android.apk"
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: android
+          path: "intervalssync-${{ github.ref_name }}-android.apk"
+
+  macos:
+    runs-on: macos-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v6
+
+      - name: Compute version from tag
+        run: echo "APP_VERSION=${GITHUB_REF_NAME#v}" >> "$GITHUB_ENV"
+
+      - name: Stamp version into the app
+        run: echo "__version__ = \"$APP_VERSION\"" > src/intervalssync/_version.py
+
+      - name: Stamp Dropbox app key into the app
+        env:
+          IGPSYNC_DROPBOX_APP_KEY: ${{ secrets.IGPSYNC_DROPBOX_APP_KEY }}
+        run: |
+          python -c "from pathlib import Path; import os; Path('src/intervalssync/_dropbox_app_key.py').write_text('DROPBOX_APP_KEY = ' + repr(os.getenv('IGPSYNC_DROPBOX_APP_KEY', '')) + '\n', encoding='utf-8')"
+
+      - name: Build macOS app
+        run: uv run flet build macos --yes --verbose --build-version "${{ env.APP_VERSION }}"
+
+      - name: Package into a versioned zip
+        run: |
+          for app in build/macos/*.app; do
+            if [ -d "$app" ]; then
+              ditto -c -k --sequesterRsrc --keepParent "$app" "intervalssync-${{ github.ref_name }}-macos.zip"
+              exit 0
+            fi
+          done
+          echo "No macOS .app bundle found in build/macos" >&2
+          exit 1
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: macos
+          path: "intervalssync-${{ github.ref_name }}-macos.zip"
+
+  pypi-publish:
+    if: ${{ !contains(github.ref_name, '-') }}
+    needs: python-package
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/intervalssync
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - name: Download Python distributions
+        uses: actions/download-artifact@v4
+        with:
+          name: python-package
+          path: dist
+
+      - name: Publish distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+  release:
+    needs: [windows, android, macos]
+    runs-on: ubuntu-latest
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v4
+        with:
+          path: dist
+
+      # Create (or update) the Release for this tag, attach all files, and
+      # generate the notes a single time (avoids the duplicate notes you get
+      # when each build job generates them).
+      #
+      # Tags with a hyphen (e.g. v0.3.0-rc1) are marked as pre-releases: GitHub
+      # keeps the last stable as "Latest", the in-app update check (which uses
+      # the /releases/latest API) ignores them, and they aren't offered to users.
+      - name: Publish Release
+        uses: softprops/action-gh-release@v2
+        with:
+          files: dist/**/*
+          generate_release_notes: true
+          prerelease: ${{ contains(github.ref_name, '-') }}
+          make_latest: ${{ !contains(github.ref_name, '-') }}

intervalssync-0.9.3/.github/workflows/test.yml

@@ -0,0 +1,25 @@
+# Runs the test suite on every push and pull request, so regressions (including
+# from contributors' PRs) are caught before merging.
+
+name: Tests
+
+on:
+  push:
+    branches: ["master"]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v4
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v6
+
+      - name: Install dependencies (incl. dev group)
+        run: uv sync
+
+      - name: Run tests
+        run: uv run pytest -q

intervalssync-0.9.3/.gitignore

@@ -0,0 +1,19 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+
+.env
+
+Downloads/
+downloads/
+
+# Flet build output
+build/
+.flet/

intervalssync-0.9.3/.python-version

@@ -0,0 +1 @@
+3.13

intervalssync-0.9.3/CLAUDE.md

@@ -0,0 +1,67 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## What this is
+
+**Intervals Sync** — a cross-platform app that syncs cycling activities to **intervals.icu** from **iGPSPORT** or **Bryton Active**, and can upload planned workouts from intervals.icu back to iGPSPORT. It ships as a **Flet** GUI (`intervalssync-gui`) plus a headless **CLI** (`intervalssync`). Dependency management uses [uv](https://docs.astral.dev/uv/) (Python 3.13).
+
+## Commands
+
+```bash
+uv sync
+uv run intervalssync-gui
+uv run intervalssync sync                          # iGPSPORT (default)
+uv run intervalssync sync --source bryton          # Bryton Active
+uv run intervalssync upload-workouts --json        # intervals.icu → iGPSPORT
+uv run intervalssync sync-zones --env-file .env --json   # intervals.icu → iGPSPORT profile
+uv run intervalssync check --source bryton
+uv run flet build windows
+uv run pytest
+```
+
+## Tests
+
+`pytest` under `tests/` — offline, no network. iGPSPORT tests in `test_igpsport_core.py`; Bryton in `test_bryton_core.py`. Config tests redirect `CONFIG_PATH` to a tmp dir.
+
+## Architecture
+
+Package root: `src/intervalssync/`. **CLI** and **GUI** are separate subpackages; **activity sources** are sibling subpackages under the root.
+
+```
+src/intervalssync/
+  cli/main.py, env.py, config.py                 # headless CLI
+  gui/app.py, views, config.py, secrets.py       # Flet UI (dual-source: iGPSPORT + Bryton)
+  igpsport/core.py, workout.py                   # iGPSPORT source
+  bryton/ddp.py, api.py, core.py                 # Bryton source
+  intervals_icu.py, dropbox_client.py            # shared by sources
+```
+
+- **`intervals_icu.py`** — shared upload, skip-existing (`external_id`), sport PUT, calendar workout fetch, sport-settings lookup (`fetch_sport_settings`, `max_hr`).
+- **`igpsport/core.py`** — `sync(SyncConfig, progress)`: login → list → FIT URL → download → upload. `external_id`: `igpsport_{ride_id}`.
+- **`igpsport/profile_sync.py`** — `sync_profile_zones`: intervals.icu sport settings + athlete weight → iGPSPORT profile thresholds/zones/weight.
+- **`igpsport/workout.py`** — planned workouts intervals.icu → iGPSPORT.
+- **`bryton/ddp.py`** — Meteor DDP login + `activityList` subscription.
+- **`bryton/api.py`** — `GET https://m3.brytonactive.com/api/activity?id=…` (FIT download; Android app API).
+- **`bryton/core.py`** — `sync(SyncConfig, progress)`. `external_id`: `bryton_{activity_id}`.
+- **`gui/secrets.py`** — async OS vault via `flet-secure-storage`.
+- **`gui/config.py`** — GUI JSON settings: `enable_igpsport` / `enable_bryton`, per-source usernames, shared sync options.
+- **`gui/sync_view.py`** — dispatches to `igpsport.core.sync` or `bryton.core.sync` per enabled source; workout upload is iGPSPORT-only.
+- **`cli/env.py`** — `.env` credential loading for the headless CLI.
+
+## iGPSPORT API notes
+
+1. **International:** POST `i.igpsport.com/Auth/Login` → `loginToken` cookie URL-decoded as Bearer token.
+2. **China:** POST `prod.zh.igpsport.com/service/auth/account/login` with `{appId, username, password}` → JSON `data.access_token` as Bearer.
+3. `Activity/ActivityList` (intl) or `queryMyActivity` (China) — PascalCase / camelCase field names respectively.
+4. FIT URL: `{prod.en|zh}.igpsport.com/.../queryActivityDetail/{id}` or `getDownloadUrl/{id}`.
+
+## Bryton API notes
+
+1. Login: Meteor DDP `login` with email + SHA-256 password digest on `m3.brytonactive.com`.
+2. List: subscribe `activityList` → `userActivities` collection.
+3. FIT: REST `GET /api/activity?id={_id}` with `X-User-Id`, `X-Auth-Token`, static `x-api-key` (not the web `activity.detail.2` samples API).
+
+## Flet version note
+
+Built against Flet 0.86.x. Uses `ft.Icons` / `ft.Colors`, `page.show_dialog`, `ft.run(main)`.

intervalssync-0.9.3/CONTRIBUTING.md

@@ -0,0 +1,156 @@
+# Contributing
+
+Thanks for your interest in improving **Intervals Sync**! This guide covers how to
+set up the project, make a change, and open a pull request.
+
+## Prerequisites
+
+- [uv](https://docs.astral.sh/uv/) (manages Python and dependencies)
+- Python 3.13 (uv will install it for you from `.python-version`)
+
+## Setup
+
+```bash
+git clone https://github.com/jorge-huxley/intervalssync.git
+cd intervalssync
+uv sync          # installs runtime + dev dependencies into .venv
+```
+
+Run the app while developing:
+
+```bash
+uv run intervalssync-gui          # launch the GUI
+```
+
+Headless sync and agent integration: [docs/AGENT.md](docs/AGENT.md).
+
+## Running the tests
+
+```bash
+uv run pytest
+```
+
+Tests are **offline** — they fake the network and never use real credentials, so
+they're safe to run anywhere. Please add or update tests for any behavior you
+change; the same suite runs in CI on every pull request and must pass before a
+change can be merged.
+
+## Project layout
+
+See `CLAUDE.md` for the full picture:
+
+- `src/intervalssync/` — package root (CLI, GUI, config, shared `intervals_icu.py`)
+- `src/intervalssync/igpsport/` — iGPSPORT activity sync + workout upload
+- `src/intervalssync/bryton/` — Bryton Active activity sync
+- `src/intervalssync/gui/` — Flet UI (`intervalssync-gui` entry)
+
+Keep source logic testable and UI-free; CLI/GUI stay thin orchestration.
+
+## Working on the Dropbox upload (optional)
+
+Dropbox is an optional, off-by-default upload target in the **GUI** (iGPSPORT
+and Bryton sync). The headless CLI uploads to intervals.icu only. You only need
+to set this up if you're working on that feature — without a key the Dropbox
+switch in Settings stays disabled and the rest of the app works normally.
+
+The app authenticates with Dropbox using the **PKCE** OAuth flow, which needs a
+Dropbox **app key**. Releases get the key stamped in by CI from a repository
+secret. For local development, **create your own Dropbox app** rather than
+reusing the production one:
+
+1. In the [Dropbox App Console](https://www.dropbox.com/developers/apps), create
+   an app with **Scoped access** and **App folder** access, and enable the
+   `account_info.read`, `files.metadata.read`, and `files.content.write` scopes.
+2. Copy the app's **App key**.
+3. Copy `.env.example` to `.env`, set `IGPSYNC_DROPBOX_APP_KEY` to your key, and
+   run with uv's `--env-file` flag (which loads the file into the environment):
+
+   ```bash
+   cp .env.example .env        # then edit .env and paste your app key
+   uv run --env-file .env intervalssync-gui
+   ```
+
+`.env` is gitignored. The app key for a PKCE public client isn't a secret (it
+ships inside released builds), but use your own for development so you don't
+share the production app's rate limit.
+
+## Making a change
+
+1. **Fork** the repository (or create a branch if you're a collaborator).
+2. Create a topic branch: `git switch -c feat/short-description`.
+3. Make your change and add tests.
+4. Run `uv run pytest` and make sure everything passes.
+5. Commit using **[Conventional Commits](https://www.conventionalcommits.org/)**,
+   e.g. `feat(gui): add gravel ride to type list` or `fix(core): handle empty
+   activity list`. Common types: `feat`, `fix`, `docs`, `test`, `refactor`,
+   `chore`, `ci`.
+6. Push your branch and **open a pull request** against `master`. Describe what
+   changed and why.
+
+## Things to keep in mind
+
+- **Never commit secrets.** Credentials live in the OS-native credential vault
+  (Windows Credential Manager / macOS Keychain / Android Keystore / Linux
+  libsecret) via the `flet-secure-storage` service — never in a file. Don't add
+  real API keys, passwords, or personal data to the repo, tests, or commits.
+- The Flet API changes between versions — verify control arguments against the
+  installed version (currently 0.86.x) rather than older tutorials.
+
+## Cutting a release
+
+Releases are built automatically by GitHub Actions (`.github/workflows/release.yml`)
+whenever you push a version tag. To publish a new version:
+
+```bash
+git tag v0.1.0      # pick the next version number
+git push origin v0.1.0
+```
+
+The workflow builds the Windows app, macOS app, Android APK, and Python
+distributions on clean runners. It attaches the GUI artifacts to a new GitHub
+Release and publishes stable Python distributions to PyPI, which makes the new
+version available through `uvx intervalssync@latest`. Watch the workflow under
+the repository's **Actions** tab.
+
+PyPI publishing uses Trusted Publishing rather than an API-token secret. The
+repository owner must configure a PyPI publisher for this repository with:
+
+- owner: `jorge-huxley`
+- repository: `intervalssync`
+- workflow name: `release.yml` (PyPI wants only the filename, not the
+  `.github/workflows/` path)
+- environment: `pypi`
+- project: `intervalssync`
+
+Create the matching protected `pypi` environment in GitHub before the first
+stable package release. Existing PyPI versions are immutable, so retry a failed
+release with a new version after fixing the workflow.
+
+### Pre-releases (test a build before shipping)
+
+Tag with a hyphen, e.g. `v0.3.0-rc1`, to publish a **pre-release**. It still
+builds installable artifacts you can test on a device, but GitHub keeps the last
+stable as **Latest** and the in-app update check ignores it — so users on the
+stable version aren't notified. Pre-releases are not published to PyPI. Once
+it's good, tag the final `v0.3.0`.
+
+### Urgent hotfix while `master` has unreleased work
+
+`master` only ever contains finished, merged PRs, so usually you can just merge
+the fix and tag a patch. If `master` already has work you're not ready to ship,
+branch the fix from the **last released tag** instead, so only the fix goes out:
+
+```bash
+# 1. Branch from the last released tag (NOT master):
+git switch -c hotfix/v0.2.5 v0.2.4
+# 2. Commit the fix on this branch, then push it:
+git push -u origin hotfix/v0.2.5
+# 3. Tag this branch's fix commit -> builds & publishes only the fix:
+git tag v0.2.5 && git push origin v0.2.5
+# 4. Open a PR from hotfix/v0.2.5 into master and merge it, so the fix is
+#    also in master for future work (master is protected, so use a PR).
+```
+
+The tag points at the hotfix commit, so the build contains just the fix — none
+of master's unreleased work. The merge into master (step 4) is separate and
+happens *after* tagging.

intervalssync-0.9.3/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jorge Silva
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.