azimut 0.2.2__tar.gz → 0.2.4__tar.gz

{azimut-0.2.2 → azimut-0.2.4}/.github/workflows/release.yml

@@ -11,8 +11,37 @@ permissions:
   id-token: write   # PyPI Trusted Publishing (OIDC) — no token secret needed
 
 jobs:
+  guard:
+    name: Version + release gate
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      # Install the app (editable) + dev tools, like the CI backend job, so the
+      # gate can import azimut and run its tests. No frontend build: these tests
+      # don't touch the built UI, and the app tolerates a missing static dir.
+      - run: uv sync --frozen --extra dev
+      # The pushed tag must equal the version baked into the code. When it
+      # didn't (0.2.2 shipped a stale __version__), the binary's self-update
+      # check nagged every user about the very release they were running. This
+      # is the check the release used to lack — it runs before anything builds.
+      - name: Tag matches the code version
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: |
+          tag="${GITHUB_REF_NAME#v}"
+          ver="$(uv run --no-sync python -c 'import azimut; print(azimut.__version__)')"
+          echo "tag=$tag  __version__=$ver"
+          [ "$tag" = "$ver" ] || { echo "::error::tag v$tag != __version__ $ver — bump src/azimut/__init__.py"; exit 1; }
+      # The version-parity gate the release workflow used to skip: pyproject's
+      # single-sourced version and the extension manifest must line up.
+      - name: Release gate + version parity
+        run: uv run --no-sync pytest tests/test_release_gate.py tests/test_updates.py -q
+
   dist:
     name: Build wheel + sdist
+    needs: guard
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
@@ -45,6 +74,7 @@ jobs:
 
   binaries:
     name: Binary (${{ matrix.os }})
+    needs: guard
     runs-on: ${{ matrix.os }}
     strategy:
       fail-fast: false
@@ -52,13 +82,15 @@ jobs:
         include:
           - os: ubuntu-latest
             asset: azimut-linux-x86_64
+            ffmpeg_target: linux-x86_64
           - os: windows-latest
             asset: azimut-windows-x86_64.exe
+            ffmpeg_target: windows-x86_64
           - os: macos-latest
             asset: azimut-macos-arm64
-          # macos-latest is Apple Silicon. We don't ship an Intel binary: the
-          # last Intel runner (macos-13) is deprecated and its queue stalls
-          # releases. Intel Macs are covered by `pip install azimut` instead.
+            ffmpeg_target: macos-arm64
+          # macos-latest is Apple Silicon. Intel remains a documented Python
+          # package install rather than a standalone release asset.
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-node@v4
@@ -76,40 +108,13 @@ jobs:
         run: |
           uv sync --frozen --no-dev --group release --no-install-project
           uv sync --frozen --no-dev --group release --no-build-isolation --no-editable
-      # ffmpeg is a native program, not a Python dep, so it isn't in the wheel.
-      # Vendor a static ffmpeg + ffprobe per-OS so the binary works out of the
-      # box (packaging/azimut.spec picks them up; engine/ffmpeg.py finds them at
-      # runtime). One host, one arch per runner; each zip holds a single binary.
+      # ffmpeg is a native program, not a Python dep. The helper pins and hashes
+      # each upstream archive, then extracts only the expected tools.
       - name: Vendor static ffmpeg + ffprobe into the binary
-        shell: bash
-        run: |
-          mkdir -p packaging/vendor
-          if [ "${{ runner.os }}" = "Windows" ]; then
-            # martin-riedl.de stopped publishing Windows builds; BtbN's
-            # "latest" release tag always points at the newest static win64
-            # build, so pull ffmpeg.exe/ffprobe.exe out of its nested bin/.
-            curl -fL "https://github.com/BtbN/FFmpeg-Builds/releases/download/latest/ffmpeg-master-latest-win64-gpl.zip" -o ffmpeg.zip
-            uv run --no-sync python -c "
-          import zipfile
-          zf = zipfile.ZipFile('ffmpeg.zip')
-          for n in zf.namelist():
-              tail = n.rsplit('/', 1)[-1]
-              if tail in ('ffmpeg.exe', 'ffprobe.exe'):
-                  open('packaging/vendor/' + tail, 'wb').write(zf.read(n))
-          "
-          else
-            case "${{ runner.os }}" in
-              Linux) plat=linux/amd64 ;;
-              macOS) plat=macos/arm64 ;;
-            esac
-            base="https://ffmpeg.martin-riedl.de/redirect/latest/$plat/release"
-            for tool in ffmpeg ffprobe; do
-              curl -fL "$base/$tool.zip" -o "$tool.zip"
-              uv run --no-sync python -c "import sys, zipfile; zipfile.ZipFile(sys.argv[1]).extractall('packaging/vendor')" "$tool.zip"
-            done
-          fi
-          chmod +x packaging/vendor/* 2>/dev/null || true
-          ls -l packaging/vendor
+        run: >-
+          uv run --no-sync python scripts/vendor_ffmpeg.py
+          "${{ matrix.ffmpeg_target }}"
+          --output packaging/vendor
       - name: Build single-file binary
         run: uv run --no-sync pyinstaller packaging/azimut.spec --distpath dist-bin --workpath build-bin
       - name: Smoke-test the binary

{azimut-0.2.2 → azimut-0.2.4}/.gitignore

@@ -48,6 +48,7 @@ CLAUDE.md
 .claude/
 AGENTS.md
 .codex/
+.agents/
 .cheatsheet
 
 # PyInstaller local output

{azimut-0.2.2 → azimut-0.2.4}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: azimut
-Version: 0.2.2
+Version: 0.2.4
 Summary: A local OSINT workspace for media, geolocation proofs and case management.
 Project-URL: Homepage, https://github.com/OsintMeThat/azimut
 Author: OsintMeThat
 License: AGPL-3.0-only
 License-File: LICENSE
 Keywords: geoint,geolocation,investigation,osint,verification
-Classifier: Development Status :: 3 - Alpha
+Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Web Environment
 Classifier: Intended Audience :: Other Audience
 Classifier: Operating System :: OS Independent
@@ -47,7 +47,7 @@ case is a plain folder that can be reopened, archived or shared.
 *The name is the French word for azimuth, the compass bearing you sight along
 to fix a point on the map.*
 
-## v0.2.2: Login-walled downloads
+## v0.2.4: Saved work and scalable browsing
 
 | Tool | What it does |
 |------|--------------|
@@ -67,15 +67,18 @@ extension, and cross-platform binaries with a bundled ffmpeg.
 Every tool works one-shot (a scratch session, no setup) or inside a case, a
 plain directory holding the whole investigation.
 
-New in v0.2.2:
+New in v0.2.4:
 
-- Downloads now handle login-walled media. The first attempt is always
-  cookie-less; only when a post turns out to need an account does Media offer to
-  borrow a signed-in browser's session or an exported `cookies.txt`. The session
-  is used for that download, kept 0600 in the workspace, and never leaves the
-  machine. Chromium on Windows can't be read, so it points you to the file route.
-- The Geo Proof toolbar reflows to fit narrow screens instead of overflowing,
-  and remembers the color and stroke width you last drew with.
+- Saved places, captures, filed screenshots and proofs are easier to find,
+  preview and place on the map.
+- The case sidebar and Files now support search, filters, folder browsing,
+  multi-select filing and a details list.
+- Media and Files use bounded SQLite queries, including complete category
+  counts and search results beyond the first page.
+- Inspect, Geo Proof and Geo Report use named saves. Their pickers can search
+  and browse folders.
+- Release binaries now fetch pinned, SHA-256-verified ffmpeg archives. Images
+  above 100 MP are rejected before decode.
 
 ## Install & run
 
@@ -101,12 +104,9 @@ opens Azimut in your browser.
 |----|-------|
 | Windows | `azimut-windows-x86_64.exe` |
 | macOS (Apple Silicon) | `azimut-macos-arm64` |
-| macOS (Intel) | No standalone binary; install with `pipx` or `pip` |
+| macOS (Intel, 14+) | No standalone binary; install with `pipx` or `pip` |
 | Linux | `azimut-linux-x86_64` |
 
-Intel Macs are supported through the Python package. They do not have a
-downloadable standalone binary.
-
 First run, the binaries are **unsigned**, so the OS warns before letting them
 open:
 - **macOS**: right-click the file → **Open** → **Open** (Gatekeeper only
@@ -116,10 +116,10 @@ open:
   info** → **Run anyway**.
 - **Linux**: mark it executable with `chmod +x azimut-linux-x86_64`.
 
-To update, **Settings → About → Check for updates** tells you when a newer
-release is out and links the download; replace the old file with the new one.
-To uninstall, delete the file. Either way `~/Azimut` stays put, so your cases
-open unchanged in the new version.
+Azimut checks for a newer release on startup by default and links the download.
+Settings can disable that check, and **Settings → About → Check for updates**
+runs it manually. Replace the old binary with the new one. To uninstall, delete
+the binary. Either way `~/Azimut` stays put, so cases open unchanged.
 
 The downloadable binaries bundle a static **ffmpeg** (and ffprobe), so video
 thumbnails, frame scans, video enhancement, and downloads that merge separate
@@ -235,7 +235,7 @@ wheel + Windows/Linux/macOS binaries, attaches them to a GitHub release, and
 publishes to PyPI. **Don't publish by hand.**
 
 ```bash
-git tag v0.2.2 && git push origin v0.2.2
+git tag v0.2.4 && git push origin v0.2.4
 ```
 
 One-time setup: register the repo as a
@@ -244,17 +244,14 @@ One-time setup: register the repo as a
 
 ## Principles
 
-1. **Local-first, privacy-first.** No account, no telemetry, no upload; the
-   server binds to `127.0.0.1` only, and Azimut never posts anywhere on your
-   behalf.
-2. **The case is the product.** Media and notes stay as files and the graph lives
-   in per-case SQLite. A closed case folder is complete and portable; a ZIP
-   import/export workflow is planned.
+1. No account, telemetry or automatic upload. The server binds to
+   `127.0.0.1`, and Azimut never posts on your behalf.
+2. A case contains the investigation's files and SQLite graph. A closed case
+   folder is complete and portable; ZIP import/export is planned.
 3. One tab = one tool, useful in 30 seconds.
-4. **Orchestrator, not replacer.** Integrate specialized services rather than
-   cloning them.
-5. Tools emit facts; the analyst decides. No automated "magic button".
-6. **Honest output.** Every artifact records how it was produced.
+4. Azimut integrates specialized services instead of recreating them.
+5. The analyst decides; tools do not produce automated verdicts.
+6. Every artifact records how it was produced.
 7. Free and open source. No paid key is ever required; bring your own for
    more basemaps.
 

{azimut-0.2.2 → azimut-0.2.4}/README.md

@@ -9,7 +9,7 @@ case is a plain folder that can be reopened, archived or shared.
 *The name is the French word for azimuth, the compass bearing you sight along
 to fix a point on the map.*
 
-## v0.2.2: Login-walled downloads
+## v0.2.4: Saved work and scalable browsing
 
 | Tool | What it does |
 |------|--------------|
@@ -29,15 +29,18 @@ extension, and cross-platform binaries with a bundled ffmpeg.
 Every tool works one-shot (a scratch session, no setup) or inside a case, a
 plain directory holding the whole investigation.
 
-New in v0.2.2:
+New in v0.2.4:
 
-- Downloads now handle login-walled media. The first attempt is always
-  cookie-less; only when a post turns out to need an account does Media offer to
-  borrow a signed-in browser's session or an exported `cookies.txt`. The session
-  is used for that download, kept 0600 in the workspace, and never leaves the
-  machine. Chromium on Windows can't be read, so it points you to the file route.
-- The Geo Proof toolbar reflows to fit narrow screens instead of overflowing,
-  and remembers the color and stroke width you last drew with.
+- Saved places, captures, filed screenshots and proofs are easier to find,
+  preview and place on the map.
+- The case sidebar and Files now support search, filters, folder browsing,
+  multi-select filing and a details list.
+- Media and Files use bounded SQLite queries, including complete category
+  counts and search results beyond the first page.
+- Inspect, Geo Proof and Geo Report use named saves. Their pickers can search
+  and browse folders.
+- Release binaries now fetch pinned, SHA-256-verified ffmpeg archives. Images
+  above 100 MP are rejected before decode.
 
 ## Install & run
 
@@ -63,12 +66,9 @@ opens Azimut in your browser.
 |----|-------|
 | Windows | `azimut-windows-x86_64.exe` |
 | macOS (Apple Silicon) | `azimut-macos-arm64` |
-| macOS (Intel) | No standalone binary; install with `pipx` or `pip` |
+| macOS (Intel, 14+) | No standalone binary; install with `pipx` or `pip` |
 | Linux | `azimut-linux-x86_64` |
 
-Intel Macs are supported through the Python package. They do not have a
-downloadable standalone binary.
-
 First run, the binaries are **unsigned**, so the OS warns before letting them
 open:
 - **macOS**: right-click the file → **Open** → **Open** (Gatekeeper only
@@ -78,10 +78,10 @@ open:
   info** → **Run anyway**.
 - **Linux**: mark it executable with `chmod +x azimut-linux-x86_64`.
 
-To update, **Settings → About → Check for updates** tells you when a newer
-release is out and links the download; replace the old file with the new one.
-To uninstall, delete the file. Either way `~/Azimut` stays put, so your cases
-open unchanged in the new version.
+Azimut checks for a newer release on startup by default and links the download.
+Settings can disable that check, and **Settings → About → Check for updates**
+runs it manually. Replace the old binary with the new one. To uninstall, delete
+the binary. Either way `~/Azimut` stays put, so cases open unchanged.
 
 The downloadable binaries bundle a static **ffmpeg** (and ffprobe), so video
 thumbnails, frame scans, video enhancement, and downloads that merge separate
@@ -197,7 +197,7 @@ wheel + Windows/Linux/macOS binaries, attaches them to a GitHub release, and
 publishes to PyPI. **Don't publish by hand.**
 
 ```bash
-git tag v0.2.2 && git push origin v0.2.2
+git tag v0.2.4 && git push origin v0.2.4
 ```
 
 One-time setup: register the repo as a
@@ -206,17 +206,14 @@ One-time setup: register the repo as a
 
 ## Principles
 
-1. **Local-first, privacy-first.** No account, no telemetry, no upload; the
-   server binds to `127.0.0.1` only, and Azimut never posts anywhere on your
-   behalf.
-2. **The case is the product.** Media and notes stay as files and the graph lives
-   in per-case SQLite. A closed case folder is complete and portable; a ZIP
-   import/export workflow is planned.
+1. No account, telemetry or automatic upload. The server binds to
+   `127.0.0.1`, and Azimut never posts on your behalf.
+2. A case contains the investigation's files and SQLite graph. A closed case
+   folder is complete and portable; ZIP import/export is planned.
 3. One tab = one tool, useful in 30 seconds.
-4. **Orchestrator, not replacer.** Integrate specialized services rather than
-   cloning them.
-5. Tools emit facts; the analyst decides. No automated "magic button".
-6. **Honest output.** Every artifact records how it was produced.
+4. Azimut integrates specialized services instead of recreating them.
+5. The analyst decides; tools do not produce automated verdicts.
+6. Every artifact records how it was produced.
 7. Free and open source. No paid key is ever required; bring your own for
    more basemaps.
 

{azimut-0.2.2 → azimut-0.2.4}/docs/ONTOLOGY.md

@@ -7,7 +7,8 @@
 **Storage schema: `3`.** The manifest carries `{"azimut": {"schema": 3,
 "storage": "sqlite"}}`; schema 3 moved the graph from `case.json` to per-case
 `case.db`. The entity/link shape is unchanged since v1. Breaking changes require
-a schema bump and migration.
+a manifest schema bump and migration. The internal SQLite schema is version 4;
+it adds search and media browse indexes without changing this logical model.
 
 Legend: ✅ implemented in code · 🔶 machinery exists, unused · ⬜ proposed.
 
@@ -26,8 +27,9 @@ presents it as this logical shape:
 - **Links** are typed directed edges. Every save records its inputs; see §3. ✅
 - **Folders** are `/`-nested analyst buckets in `attrs.folder`, not semantic
   links. ✅
-- Media sidecars hold kind, size, uploader, duration and thumbnail data. Entities
-  retain only what the graph needs for identity, links and deduplication.
+- Media sidecars hold kind, size, uploader, duration and thumbnail data. A
+  SQLite browse index mirrors searchable fields. Entities retain only what the
+  graph needs for identity, links and deduplication.
 
 ## 2. Entity
 
@@ -43,13 +45,22 @@ presents it as this logical shape:
 `type` is extensible: unknown strings are stored but receive no custom renderer.
 `label` is editable and never defines identity.
 
+`geo` is the country a saved point falls in, resolved once and kept:
+`{state, country_code, country, region?, region_en?}` with `state` one of `ok`,
+`nocoords` (no position to look up), `nocountry` (open sea) or `failed` (the
+lookup did not answer — the only state a later pass retries). `country` and
+`region` are the local-language names; `region_en` is a second lookup in English
+and is absent when it failed or matched the native name. Continent and the
+English country name are *not* stored: both are derived from `country_code` at
+read time, so extending those tables repairs existing cases with no migration.
+
 ### Entity type registry
 
 | Type | State | Produced by | Key `attrs` | File-backed |
 |---|---|---|---|---|
 | `media` | ✅ | media-library | `path`, `sha256`, `source_url?` | yes (+ sidecar) |
-| `capture` | ✅ | satellite | `coords`, `lat`, `lon`, `plus_code`, `zoom`, `bearing`, `path` | yes (image) |
-| `place` | ✅ | satellite | `coords`, `lat`, `lon`, `plus_code`, `zoom`, `bearing`, `notes?` | no (a point) |
+| `capture` | ✅ | satellite | `coords`, `lat`, `lon`, `plus_code`, `zoom`, `bearing`, `path`, `geo?` | yes (image) |
+| `place` | ✅ | satellite, ingest | `coords`, `lat`, `lon`, `plus_code`, `zoom`, `bearing`, `notes?`, `geo?`, `source_url?`, `site?` | no (a point) |
 | `proof` | ✅ | proof-composer | `spec` (json), `path` (png) | yes |
 | `post` | ✅ | post-composer | `draft` (json) | yes |
 | `inspect-session` | ✅ | inspect | `spec` (json) | yes |
@@ -67,6 +78,11 @@ New types coming from the roadmap (declare here when built): `panorama`,
 Per-type attribute schemas remain open work. Today attribute keys are conventions,
 not a validated contract between tools.
 
+The file-backed pointers of `proof`, `post` and `inspect-session` (`spec`,
+`draft`, `path`) are not stable: the file's name follows the label, so renaming
+one in its tool rewrites the pointer on the same entity. Look these up by id, or
+re-read the pointer — never cache one across a save.
+
 ## 3. Link
 
 ```jsonc
@@ -106,6 +122,13 @@ A tool selects one of two deletion behaviours through its link type:
 
 - `derived-from` never cascades into an output. A post keeps its text when its
   proof is deleted; a frame keeps its pixels when its video is deleted.
+- It is also read backwards, as geography. The Saved panel counts the proofs
+  hanging off each saved point through this edge, and a proof with no point of
+  its own is placed at the point of every capture it composes, one hop back.
+  A proof does carry its own point first, though: `coordsText` (what the analyst
+  typed, in any supported format) then `coords` (what the panels gave it, frozen
+  at save). That is what keeps a proof on the map once its capture is deleted —
+  a tombstone records the path, the sha256 and the URL, never coordinates.
 - `attrs.lost_sources[]` stores `{label, type, path, sha256, source_url, at}`.
   Tombstones are keyed by path and never stacked.
 - Every UI deletion uses the same dependency-aware service. The confirmation
@@ -133,6 +156,9 @@ How it is wired (`engine/links.py`):
   resolves path → entity and emits the edge.
 - Every save restates sources through `sync`. Removing a panel removes its edge;
   repeated saves keep one edge per panel.
+- A proof's pasted images are read as decoration, not sources: they carry no case
+  path, so they file no entity and earn no edge. Only panels put a proof in a
+  chain.
 - A missing source path produces a tombstone instead of a link.
 - Media derivatives are all filed through one registration point, so any future
   tool producing imagery gets its chain for free. A derivative that **dedupes**

azimut-0.2.4/docs/RELEASE_NOTES.md

@@ -0,0 +1,61 @@
+# Azimut v0.2.4
+
+## OSINT toolkit at a glance
+
+- **Sources:** import or download media, use an existing login when a post
+  requires it, record hashes and provenance, inspect frames, crops, collages,
+  panoramas and ELA, then prepare reverse-image searches.
+- **Maps:** convert coordinates, geocode places, capture attributed imagery,
+  compare providers, rotate and measure maps, save references and review AOI
+  grids.
+- **Evidence:** organise media, places, proofs and notes in portable cases with
+  folders, links, Markdown notebooks and PDF output.
+- **Publishing:** build annotated Geo Proofs and prepare evidence-linked Geo
+  Reports for X, Bluesky or Mastodon without posting automatically.
+
+## What changed
+
+- **Saved work on the map.** Places, captures and filed screenshots can be
+  browsed by geography or case folder, searched in English or the local name,
+  previewed and shown on the map. Proofs appear at their own coordinates or at
+  the captures they use.
+- **Case organisation.** The sidebar adds search, type and status filters,
+  multi-select filing and a details drawer. Files adds Small, Large and List
+  views with sortable columns and complete folder browsing.
+- **Named work.** Inspect, Geo Proof and Geo Report name their documents in the
+  header and keep that name when saved or renamed. Inspect's save dialog can
+  name a batch and attach one note.
+- **Faster browsing.** Media and Files now query a SQLite browse index. Search,
+  folder filters and Media category counts cover the complete case instead of
+  only the first 200 items. Files requests thumbnail metadata only for paths it
+  can display.
+- **Better pickers and proofs.** Inspect, Reverse Search, Geo Proof and Notebook
+  pickers can search and browse folders. Geo Proof supports coloured panel
+  frames, layer controls and pasted overlays stored with that proof.
+- **Capture extension.** A map point can be saved as a place, and any page can
+  be saved as a bookmark. Map captures keep their source metadata and
+  attribution.
+- **Case-switch fix.** Saved Satellite items and Media thumbnail state are
+  cleared before a different case loads, so data from the previous case no
+  longer remains until refresh.
+- **Release and security hardening.** Release builds use pinned, SHA-256-checked
+  ffmpeg archives and extract only the expected tools. Images above 100 MP are
+  rejected before decode. SQLite schema 4 adds the media browse index and
+  upgrades existing cases automatically.
+
+The read-only GitHub release check still runs on startup by default. It can be
+disabled in Settings, and offline failures remain silent.
+
+## Install or upgrade
+
+Download the ready-to-run asset for Windows x86_64, Linux x86_64 or Apple
+Silicon macOS and run it. Each binary includes the browser UI, `ffmpeg` and
+`ffprobe`; no Python or system FFmpeg is needed.
+
+Intel Macs require macOS 14 or newer and the Python package:
+`pipx install azimut` or `pip install azimut`.
+
+The binaries are unsigned. Follow the operating system prompt described in the
+README on first launch.
+
+Existing cases upgrade in place. No manual export or import is required.