Skip to content

Releases: VooZ2/terento

Terento v1.0.0-beta.7

Terento v1.0.0-beta.7 Pre-release
Pre-release

Choose a tag to compare

@VooZ2 VooZ2 released this 26 Aug 20:24
Immutable release. Only release title and notes can be modified.
dd46156

Terento v1.0.0-beta.7

Release date: 2026-08-26

Beta.7 keeps the complete validated Freizeitkarte catalog visible while
separating catalog membership from Terento's map-acquisition policy. Downloads
for Crimea and canonical Russian Federation regions are withheld before any
temporary workspace or network request is created. Other regions, including
Ukraine, Belarus and unknown non-Russian identities, remain available under
the normal validation rules.

This remains a pre-MVP beta for hardware validation. Freizeitkarte remains the
only map provider, and model eligibility is not a claim that every exact watch
has been independently verified.

Highlights

  • Crimea remains listed under its canonical provider identity and is presented
    as part of Ukraine and temporarily occupied by russia.
  • Canonical Russian Federation packages remain searchable and visible, but
    Terento does not offer their downloads while russia's war of aggression
    against Ukraine continues.
  • Withheld rows show a neutral Unavailable state, policy explanation and no
    checkbox-like control, size, update action or storage impact.
  • Ukraine and all other non-withheld packages retain the normal selectable map
    control and acquisition flow.
  • Install and Safe Update use one acquisition-policy gate. A withheld package
    fails before creating temporary files or making an HTTP request.
  • Existing Terento-owned maps are not reclassified. Backup and Remove remain
    available, while Update is hidden for a currently withheld region.

Application updates

  • Terento performs one non-blocking HTTPS metadata check per launch after the
    first window becomes usable. Startup failures remain silent.
  • About retains the manual update check and persistent result state.
  • A user-confirmed Download action opens only a strictly validated official
    Terento distribution URL. The app does not download, mount or replace itself.

Safety and privacy

  • Garmin-owned, unknown and manually managed files remain read-only.
  • New installs never overwrite an existing target. Safe Update still follows
    write-new → verify → remove-old and never deletes the working map first.
  • Device manifests and physical-watch ownership keys remain local. There is no
    account, login, cloud device profile or server-side Garmin identifier storage.
  • Catalog filtering and acquisition policy do not add telemetry or map proxying;
    available maps still download directly from Freizeitkarte infrastructure.

Validation status

  • Automated policy tests cover canonical Crimea and Russian identities,
    Freizeitkarte RUS* alias mapping, non-Russian controls, stale selections,
    accessibility labels, Manage actions and fail-before-workspace/network order.
  • The full native shell regression matrix and signed arm64 Release dry-run pass
    on the beta.7 candidate tree, including bundled-library and runtime-path
    verification.
  • Owner hardware evidence on the connected fēnix 8 confirms the 63-package
    catalog view, withheld Russia/Crimea presentation and normal Ukraine row.
  • No install, update or remove operation was performed as part of that visual
    hardware check. Safe Update's real-device newer-map gate remains pending.

Known limitations

  • Map-capable means eligible for a guarded beta attempt, not independently
    verified compatibility.
  • Safe Update has not yet passed its real-device newer-map gate.
  • Freizeitkarte is the only supported map provider. Terento does not host,
    mirror or proxy map binaries.
  • macOS 13 or later on Apple Silicon is required. Intel Macs, App Store, PKG,
    Windows and Linux distributions are not included.

Release artifacts

The release pipeline completed successfully and Apple notarization was
accepted with no issues.

Terento-1.0.0-beta.7-macOS-arm64.dmg  6a74b7613a81c68b9e0e3995dd0e00c6a7778957fc039b40a113731573e95faa
Terento-1.0.0-beta.7-macOS-arm64.zip  f9940254242935843e7fdd340d5962961e4cdaf8f6752dcf2cef9d3fef248203

Terento v1.0.0-beta.6

Terento v1.0.0-beta.6 Pre-release
Pre-release

Choose a tag to compare

@VooZ2 VooZ2 released this 26 Aug 11:56
Immutable release. Only release title and notes can be modified.
c279e91

Terento v1.0.0-beta.6

Release date: 2026-08-26

Beta.6 broadens the Garmin smartwatch beta from one tested USB identity to
reviewed Garmin Map Manager model families, while strengthening the checks
that protect the connected watch and Terento-managed maps. It also adds
privacy-minimised failure diagnostics so unsuccessful beta installations can
be investigated without asking users to send raw logs.

This remains a pre-MVP beta for hardware validation. A model being listed by
Garmin as map-capable allows a guarded beta installation attempt; it is not a
claim that Terento has already verified that exact model. Freizeitkarte
remains the only map provider.

Highlights

  • Map installation is no longer limited to the fēnix 8 USB PID used by the
    original hardware test. Reviewed map-capable smartwatch families, including
    fēnix, epix, Forerunner, Enduro, tactix, quatix, MARQ, Descent, D2 Mach and
    Venu X1 families, may enter the guarded beta installation flow.
  • Every production write is bound to the live MTP session. The native layer
    verifies the connected Garmin VID/PID, manufacturer, raw MTP model and one
    unambiguous /GARMIN target before writing. The laboratory Write Test and
    Interruption Test remain restricted to their validated 0x51b8 identity.
  • fēnix 8 and fēnix 8 Pro are now separate identities in the app, private
    diagnostics and compatibility data. Case size alone never guesses AMOLED,
    Solar or MicroLED.
  • Watches without a stable MTP serial can use the Garmin Unit ID from one
    bounded /GARMIN/GarminDevice.xml read for local ownership. The serial and
    Unit ID values are never uploaded, logged or stored in the manifest.
  • Terento-managed maps can be recovered after moving the same watch to a new
    Mac or losing the previous local manifest. Recovery verifies the complete
    map before adopting it and cannot transfer ownership to a different watch.
  • Remove refreshes the live device inventory and resolves current-session MTP
    handles before deletion. It still removes only a verified Terento-managed
    map. Backup remains an explicit user choice and is not run automatically.

Installation diagnostics and compatibility evidence

  • The visible compatibility-sharing choice remains selected by default and
    can be turned off without limiting installation or removal.
  • Opted-in reports now include one random operation ID per Install action,
    exact Terento beta/build, a controlled failure stage and code, whether a
    write or cleanup started, and a coarse transfer-progress range.
  • Download, extraction, validation and preflight failures can be diagnosed but
    do not reduce a watch model's installation compatibility rate when device
    writing never started.
  • Multiple selected maps share one operation ID while retaining individual map
    results. Reports for the same exact model/variant aggregate into one evidence
    row instead of creating duplicate model rows.
  • Private admin diagnostics show only the sanitized raw MTP model label and
    whether local identity came from an MTP serial, Garmin Unit ID or was
    unavailable. They never receive the identifier value, local path, MTP object
    ID, manifest, map hash, raw error text or log file.
  • The three legacy Swiss-map failures from issue #32 were retained for private
    investigation but quarantined from the incorrect base fēnix 8 identity.

Catalog, UI and offline behavior

  • The app consumes the canonical API compatibility status instead of deriving
    Testing, Tested, Supported or Verified locally.
  • The bundled Freizeitkarte fallback contains the complete current 63-package
    metadata set, including measured final IMG installation sizes. It is used
    only when the live catalog is unavailable and is presented as potentially
    stale; it does not limit the remote catalog.
  • Verification wording now distinguishes sampled transfer verification from a
    complete file proof.
  • App metadata and compatibility reports carry the exact
    1.0.0-beta.6 / build 5 identity.

Safety and privacy

  • Garmin-owned, unknown and manually managed files remain read-only.
  • New installs never overwrite an existing target. Update still follows
    write-new → verify → remove-old and never deletes the working map first.
  • Safe Update behavior is unchanged in beta.6. Its automated suite passes, but
    the real-device update gate remains pending a genuinely newer Freizeitkarte
    release.
  • Device manifests and physical-watch ownership keys remain local. There is no
    account, login, cloud device profile, required email or server-side Garmin
    identifier storage.

Validation status

  • Backend validation: 95 tests passed; backward-compatible migrations 017 and
    018 are deployed before the beta.6 client.
  • Full automated native Stage 2–7, Install, Recover, Remove, manifest,
    compatibility, privacy and unchanged Safe Update suites pass.
  • Swift/Xcode arm64 Release build, bundled libmtp/libusb checks, Developer ID
    signing verification and GitHub CI pass.
  • The owner hardware smoke gate passed on the available fēnix 8 watch using
    the final notarized build: exact model presentation, map installation,
    opted-in beta.6 report delivery and Remove all passed.
  • The fēnix 8 Pro issue #32 correction is based on the reported pre-write
    failure and automated regression coverage. Public beta evidence is still
    needed for that exact model.

Known limitations

  • Map-capable means eligible for a guarded beta attempt, not independently
    verified compatibility. Exact model status continues to be based on opted-in
    successful installations.
  • A watch that exposes neither a stable MTP serial nor a valid Garmin Unit ID
    remains read-only because Terento cannot safely separate two identical
    physical watches for ownership and later removal.
  • Safe Update has not yet passed its real-device newer-map gate.
  • Freizeitkarte is the only supported map provider. Terento does not host or
    mirror map binaries.
  • macOS 13 or later on Apple Silicon is required. Intel Macs, App Store, PKG,
    Windows and Linux distributions are not included.

Release checksums

Terento-1.0.0-beta.6-macOS-arm64.dmg  f206816fbee38fe2092cdfc91d58eb68e88c2b0f7ee0c909c327b4b1d455ccb5
Terento-1.0.0-beta.6-macOS-arm64.zip  b779086c1bad975b7275db34e44c6033eeaf04118881feca20b383fa82b960c7

Terento v1.0.0-beta.5

Terento v1.0.0-beta.5 Pre-release
Pre-release

Choose a tag to compare

@VooZ2 VooZ2 released this 25 Aug 22:16
Immutable release. Only release title and notes can be modified.
3674512

Terento v1.0.0-beta.5

Release date: 2026-08-26

Beta.5 synchronizes the native device compatibility presentation with the
canonical Terento API. Exact reviewed Garmin variants now retain their model,
case size, display type, public evidence status, and map capability without a
local hardcoded status or cross-variant cache inheritance.

For the reviewed fēnix 8 USB identity, the connected-device screen can now
show the exact 47 mm AMOLED variant even when the raw MTP model omits the
display token. Unreviewed size-only identities still fail closed rather than
guessing AMOLED or Solar.

This is a pre-MVP beta release for the Terento macOS application. It is
intended for development and hardware validation; it is not a stable
production release. Apple Silicon users can download the notarized ZIP or DMG
from the GitHub release assets. Freizeitkarte is the only map provider in this
beta.

Included

  • guarded Garmin smartwatch discovery, compatibility evaluation, map
    inventory, source acquisition, installation, backup, removal, and safe
    update foundations;
  • local manifest-backed ownership and fail-closed protection for unknown and
    Garmin-owned device files;
  • metadata-only Freizeitkarte catalog and Garmin device catalog services;
  • serialized MTP lifecycle handling and disconnect-safe map lifecycle UI;
  • a native macOS application target with bundled arm64 libmtp/libusb runtime;
  • catalog-driven Freizeitkarte installation for one or several selected maps,
    including split-header composite-region identity handling, fresh
    device-backed inventory on Install/Manage navigation, and bounded Finishing
    progress;
  • beta installation failures now save local operation diagnostics to
    ~/Library/Logs/Terento/log.txt, including the selected preflight map and
    latest scanned Freizeitkarte objects, with a Show log.txt action on the
    failure screen;
  • an About page with app version, update checking, support links, and local
    privacy statement;
  • API-backed Testing, Tested, Supported, and Verified compatibility status,
    exact AMOLED/Solar variant isolation, and a bounded exact-identity offline
    cache;
  • the public Terento landing page with English, German, French, Polish, Czech,
    and Italian indexable versions, translated metadata, reciprocal hreflang,
    sitemap entries, and a local language preference; and
  • production deployment of the multilingual public landing page at
    https://terento.app.

Validation status

  • Full automated Stage 2–7 validation and Swift/Xcode Release builds pass.
  • The About → Updates flow checks a release metadata endpoint and opens the
    verified release download for user-confirmed installation. It does not
    silently replace the running app.
  • The application is Developer ID signed, notarized, stapled, Gatekeeper
    validated, and distributed as arm64 ZIP and DMG assets containing one
    Terento.app.
  • The harmless write/read/delete roundtrip has passed on one validated Garmin
    smartwatch profile, including after reconnect.
  • Read-only backup and safe-delete hardware gates have passed for the tested
    device and exact Terento-owned map.
  • Safe Update is implemented and covered by automated tests, but its physical
    real-device update gate remains pending a genuinely newer Freizeitkarte
    release.
  • The public beta release is v1.0.0-beta.5 with notarized arm64 ZIP and DMG
    assets published at the GitHub release page.

Known limitations

  • This beta does not claim universal Garmin smartwatch support. Hardware
    evidence is specific to one tested Garmin smartwatch profile and
    connectivity path.
  • The complete first real-product success condition is not declared passed
    until the end-to-end install/update flow is repeated and verified on real
    hardware without changing non-Terento files.
  • Freizeitkarte remains the only supported map provider in this phase.
  • The catalog contains metadata only; Terento does not host or mirror map
    binaries.
  • No PKG, App Store package, or universal Intel/Apple Silicon binary is
    included in this beta.

Privacy and safety

No account, login, cloud device profile, server-side Garmin Unit ID storage, or
required email is introduced by this checkpoint. Device manifests remain local
to the Mac. Terento modifies only files it can prove it owns and prefers a
safe failure over destructive guessing.

Release checksums

Terento-1.0.0-beta.5-macOS-arm64.dmg  a96326e73ebc453e2b46fad3c3e0759e0340a58e26415e3f8b2a85b07583c9c3
Terento-1.0.0-beta.5-macOS-arm64.zip  bdb807430e533f9ccb3f9f79929e21395844643f3079891cd057a957186a8707

Terento v1.0.0-beta.4

Terento v1.0.0-beta.4 Pre-release
Pre-release

Choose a tag to compare

@VooZ2 VooZ2 released this 25 Aug 15:57
Immutable release. Only release title and notes can be modified.

Beta.4 adds beta installation enrollment for Garmin map-capable watches, including newly connected models and sizes, while retaining the guarded /GARMIN target and transfer verification gates.

It also improves device artwork resolution through official Garmin product pages and keeps a neutral fallback image when artwork is unavailable.

Requires macOS 13+ on Apple Silicon. Freizeitkarte is the only map provider in this beta.

Checksums:

  • DMG: efa6574247eb9eaedb9b21853ead97a2743f05e4a5fcc2ead602530c5c4f17cf
  • ZIP: 568d0b6b687d6bc268fbfa75777c09391757dff64b21cb43e2058d6950ec8298

Terento v1.0.0-beta.3

Terento v1.0.0-beta.3 Pre-release
Pre-release

Choose a tag to compare

@VooZ2 VooZ2 released this 25 Aug 12:17
Immutable release. Only release title and notes can be modified.
5bb52e0

Terento v1.0.0-beta.3

Release date: 2026-08-25

This is a pre-MVP beta release for the Terento macOS application. It is
intended for development and hardware validation; it is not a stable
production release. Apple Silicon users can download the notarized ZIP or DMG
from the GitHub release assets.

Included

  • guarded Garmin smartwatch discovery, compatibility evaluation, map
    inventory, source acquisition, installation, backup, removal, and safe
    update foundations;
  • local manifest-backed ownership and fail-closed protection for unknown and
    Garmin-owned device files;
  • metadata-only Freizeitkarte catalog and Garmin device catalog services;
  • serialized MTP lifecycle handling and disconnect-safe map lifecycle UI;
  • a native macOS application target with bundled arm64 libmtp/libusb runtime;
  • catalog-driven Freizeitkarte installation for one or several selected maps,
    including split-header composite-region identity handling, fresh
    device-backed inventory on Install/Manage navigation, and bounded Finishing
    progress;
  • beta installation failures now save local operation diagnostics to
    ~/Library/Logs/Terento/log.txt, including the selected preflight map and
    latest scanned Freizeitkarte objects, with a Show log.txt action on the
    failure screen;
  • an About page with app version, update checking, support links, and local
    privacy statement;
  • the public Terento landing page with English, German, French, Polish, Czech,
    and Italian indexable versions, translated metadata, reciprocal hreflang,
    sitemap entries, and a local language preference; and
  • production deployment of the multilingual public landing page at
    https://terento.app.

Validation status

  • Full automated Stage 2–7 validation and Swift/Xcode Release builds pass.
  • The About → Updates flow checks a release metadata endpoint and opens the
    verified release download for user-confirmed installation. It does not
    silently replace the running app.
  • The application is Developer ID signed, notarized, stapled, Gatekeeper
    validated, and distributed as arm64 ZIP and DMG assets containing one
    Terento.app.
  • The harmless write/read/delete roundtrip has passed on one validated Garmin
    smartwatch profile, including after reconnect.
  • Read-only backup and safe-delete hardware gates have passed for the tested
    device and exact Terento-owned map.
  • Safe Update is implemented and covered by automated tests, but its physical
    real-device update gate remains pending a genuinely newer Freizeitkarte
    release.

Known limitations

  • This beta does not claim universal Garmin smartwatch support. Hardware
    evidence is specific to one tested Garmin smartwatch profile and
    connectivity path.
  • The complete first real-product success condition is not declared passed
    until the end-to-end install/update flow is repeated and verified on real
    hardware without changing non-Terento files.
  • Freizeitkarte remains the only supported map provider in this phase.
  • The catalog contains metadata only; Terento does not host or mirror map
    binaries.
  • No PKG, App Store package, or universal Intel/Apple Silicon binary is
    included in this beta.

Privacy and safety

No account, login, cloud device profile, server-side Garmin Unit ID storage, or
required email is introduced by this checkpoint. Device manifests remain local
to the Mac. Terento modifies only files it can prove it owns and prefers a
safe failure over destructive guessing.

Release checksums

Terento-1.0.0-beta.3-macOS-arm64.zip  8307e6ce8abff93475ccf21fe135e730ff8b4a6d4a67b615c90f0a0939e0e46d
Terento-1.0.0-beta.3-macOS-arm64.dmg  eeb56bdf247c870a69b8ae3205052a028fe7c97c4ec28975ac4fea8eb87b91d9

Terento v1.0.0-beta.2

Terento v1.0.0-beta.2 Pre-release
Pre-release

Choose a tag to compare

@VooZ2 VooZ2 released this 24 Aug 20:31
Immutable release. Only release title and notes can be modified.
70b59d8

Terento v1.0.0-beta.2

Release date: 2026-08-24

This is a pre-MVP beta release for the Terento macOS application. It is
intended for development and hardware validation; it is not a stable
production release. Apple Silicon users can download the notarized ZIP or DMG
from the GitHub release assets.

Included

  • guarded Garmin smartwatch discovery, compatibility evaluation, map
    inventory, source acquisition, installation, backup, removal, and safe
    update foundations;
  • local manifest-backed ownership and fail-closed protection for unknown and
    Garmin-owned device files;
  • metadata-only Freizeitkarte catalog and Garmin device catalog services;
  • serialized MTP lifecycle handling and disconnect-safe map lifecycle UI;
  • a native macOS application target with bundled arm64 libmtp/libusb runtime;
  • catalog-driven Freizeitkarte installation for one or several selected maps,
    including split-header composite-region identity handling, fresh
    device-backed inventory on Install/Manage navigation, and bounded Finishing
    progress;
  • beta installation failures now save local operation diagnostics to
    ~/Library/Logs/Terento/log.txt, including the selected preflight map and
    latest scanned Freizeitkarte objects, with a Show log.txt action on the
    failure screen;
  • an About page with app version, update placeholder, support links, and local
    privacy statement;
  • the public Terento landing page with English, German, French, Polish, Czech,
    and Italian indexable versions, translated metadata, reciprocal hreflang,
    sitemap entries, and a local language preference; and
  • production deployment of the multilingual public landing page at
    https://terento.app.

Validation status

  • Full automated Stage 2–7 validation and Swift/Xcode Release builds pass.
  • The application is Developer ID signed, notarized, stapled, Gatekeeper
    validated, and distributed as arm64 ZIP and DMG assets containing one
    Terento.app.
  • The harmless write/read/delete roundtrip has passed on one validated Garmin
    smartwatch profile, including after reconnect.
  • Read-only backup and safe-delete hardware gates have passed for the tested
    device and exact Terento-owned map.
  • Safe Update is implemented and covered by automated tests, but its physical
    real-device update gate remains pending a genuinely newer Freizeitkarte
    release.

Known limitations

  • This beta does not claim universal Garmin smartwatch support. Hardware
    evidence is specific to one tested Garmin smartwatch profile and
    connectivity path.
  • The complete first real-product success condition is not declared passed
    until the end-to-end install/update flow is repeated and verified on real
    hardware without changing non-Terento files.
  • Freizeitkarte remains the only supported map provider in this phase.
  • The catalog contains metadata only; Terento does not host or mirror map
    binaries.
  • No PKG, App Store package, or universal Intel/Apple Silicon binary is
    included in this beta.

Privacy and safety

No account, login, cloud device profile, server-side Garmin Unit ID storage, or
required email is introduced by this checkpoint. Device manifests remain local
to the Mac. Terento modifies only files it can prove it owns and prefers a
safe failure over destructive guessing.

Terento v0.1.0-beta.1

Terento v0.1.0-beta.1 Pre-release
Pre-release

Choose a tag to compare

@VooZ2 VooZ2 released this 23 Aug 20:53

Terento v0.1.0-beta.1

Release date: 2026-08-23

This is a pre-MVP beta checkpoint for the Terento macOS proof of concept. It
is intended to make the current implementation reproducible for development
and hardware validation; it is not a stable production release and does not
include a notarized DMG or PKG.

Included

  • guarded Garmin smartwatch discovery, compatibility evaluation, map
    inventory, source acquisition, installation, backup, removal, and safe
    update foundations;
  • local manifest-backed ownership and fail-closed protection for unknown and
    Garmin-owned device files;
  • metadata-only Freizeitkarte catalog and Garmin device catalog services;
  • serialized MTP lifecycle handling and disconnect-safe map lifecycle UI;
  • the public Terento landing page with English, German, French, Polish, Czech,
    and Italian indexable versions, translated metadata, reciprocal hreflang,
    sitemap entries, and a local language preference; and
  • production deployment of the multilingual public landing page at
    https://terento.app.

Validation status

  • Automated Stage 2–5 validation and Swift build are the release validation
    baseline.
  • The harmless write/read/delete roundtrip has passed on the validated Garmin
    fēnix 8 profile, including after reconnect.
  • Read-only backup and safe-delete hardware gates have passed for the tested
    device and exact Terento-owned map.
  • Safe Update is implemented and covered by automated tests, but its physical
    real-device update gate remains pending a genuinely newer Freizeitkarte
    release.

Known limitations

  • This beta does not claim universal Garmin smartwatch support. Hardware
    evidence is specific to the tested fēnix 8 profile and connectivity path.
  • The complete first real-product success condition is not declared passed
    until the end-to-end install/update flow is repeated and verified on real
    hardware without changing non-Terento files.
  • Freizeitkarte remains the only supported map provider in this phase.
  • The catalog contains metadata only; Terento does not host or mirror map
    binaries.
  • The macOS app is a development proof of concept. Distribution, notarization,
    and App Store packaging are outside this checkpoint.

Privacy and safety

No account, login, cloud device profile, server-side Garmin Unit ID storage, or
required email is introduced by this checkpoint. Device manifests remain local
to the Mac. Terento modifies only files it can prove it owns and prefers a
safe failure over destructive guessing.