release: prepare v0.1.3

CHANGELOG.md

@@ -1,6 +1,6 @@
 # Changelog
 
-## Unreleased — 0.1.3
+## 0.1.3 — 2026-09-20
 
 - Decoupled the Android full-generation request from the strict legacy V3
   compatibility signal. One explicit intent now publishes the dedicated

README.md

@@ -52,9 +52,9 @@ Each published stable release provides:
 - SHA-256 checksums.
 
 Both mirrors publish the same Trainlog product version and release assets. The
-current development version is **0.1.3** on Android and desktop; this is one
+latest stable version is **0.1.3** on Android and desktop; this is one shared
-shared Trainlog version, not separate interface versions. Version 0.1.2 is the
+Trainlog version, not separate interface versions. Version 0.1.2 is the
-latest stable release.
+previous stable release.
 
 Trainlog presents French by default, with English selectable
 from **Settings → Language** on Android and the desktop TUI. The selection is
@@ -157,7 +157,7 @@ updates; generating a replacement key is not a normal release procedure.
 
 ### Linux runtime dependencies
 
-The published v0.1.2 x86-64 desktop runtime is dynamically linked. Its tagged
+The published v0.1.3 x86-64 desktop runtime is dynamically linked. Its tagged
 source directly requires compatible versions of:
 
 - glibc and the GCC support runtime;
@@ -169,7 +169,7 @@ source directly requires compatible versions of:
 - Notcurses Core;
 - the standard math library.
 
-Version 0.1.2 additionally links GNU libmicrohttpd and yyjson for the local Web
+Version 0.1.3 additionally links GNU libmicrohttpd and yyjson for the local Web
 adapter and Dashboard layout configuration. Those are not retroactive
 requirements of the pre-Web v0.1.1 tagged source.
 

docs/current_state.md

@@ -60,8 +60,8 @@ the private `Trainlog/Sync/v1` namespace is configured as a verified mirror and
 fallback, independently from `Trainlog/AI`. Cross-transport replay is
 idempotent and neither transport carries SQLite.
 
-The public Android release chain advances from v0.1.1 versionCode 2 to v0.1.2
+The public Android release chain advances from v0.1.1 versionCode 2 through
-versionCode 3 under certificate SHA-256
+v0.1.2 versionCode 3 to v0.1.3 versionCode 4 under certificate SHA-256
 `5ef41117da107c9805ae3215c5ec823cff06216610e6e4f7542a754161c71bd2`.
 Higher-numbered private validation builds used a separate Android Debug
 certificate and are not members of the public update-signature chain.
@@ -111,7 +111,7 @@ parallel implementation of its rules.
 | Android SQLite | schema v25 |
 | Mobile snapshot | V3 active; V1/V2 readable legacy inputs; explicit V4 codec staged, not selected by transport |
 | Desktop terminal backend | Notcurses only |
-| Trainlog product version | `0.1.3` development, synchronized across Android and desktop; latest stable release: `v0.1.2` |
+| Trainlog product version | `0.1.3` stable, synchronized across Android and desktop; latest stable release: `v0.1.3` |
 | Interface language | `TRAINLOG_I18N_V0_1_1=PASS`: French default; English selectable in Settings → Language on both surfaces |
 | AI history export | `TRAINLOG_AI_EXPORT_V1` active |
 | AI session proposals | `TRAINLOG_AI_SESSION_DRAFT_V1=VALIDATION_PENDING` |

docs/releases/README.md

@@ -6,5 +6,6 @@ than later development. GitHub and Forgejo publication must preserve the
 existing release, tag, status, and assets while keeping their note bodies equal
 to the corresponding source file.
 
+- [Trainlog v0.1.3](v0.1.3.md)
 - [Trainlog v0.1.2](v0.1.2.md)
 - [Trainlog v0.1.1](v0.1.1.md)

docs/releases/v0.1.3.md

@@ -0,0 +1,24 @@
+Trainlog v0.1.3 improves the local-first capture, planning, history, and
+synchronization experience without changing the published data formats.
+
+## Highlights
+
+- The Android interface is more compact while preserving durable capture.
+- Programs and their execution state are available across the supported local
+  workflows.
+- Sessions and durable drafts are clearer to inspect and resume.
+- The Web exercise catalogue supports bounded administration workflows.
+- Causal deletion prevents retired data from being resurrected by replay.
+- Full-generation synchronization carries the complete supported state.
+- Direct MTP exchange is more robust and reports bounded failures precisely.
+- Foreground and background synchronization have explicit conversation
+  ownership.
+- Full-generation requests use a dedicated trigger while legacy V3 signalling
+  remains separate and strict.
+
+## Assets
+
+- `trainlog-android-v0.1.3.apk`: signed public Android APK.
+- `trainlog-tui-linux-x86_64-v0.1.3`: Linux x86-64 runtime bundle containing
+  the TUI, local Web adapter, synchronization helpers, and required catalogs.
+- `SHA256SUMS`: SHA-256 checksums for both artifacts.