# Tlamatini 1.92.4 **Latest released version: 1.92.4.** English and Spanish use this same release number throughout the application documentation, manifest, self-knowledge, PDF dossiers and PowerPoint deck. ## What changed | Area | Behavior in 1.92.4 | Reference | |---|---|---| | Matching release versions | Before starting a complete build, the combined launcher calls each edition's own version resolver and previews its actual emitter in memory. It compares the version that the executable will report, rather than requiring a tag on the current commit. Both workers receive the matching number explicitly. | [Combined builder](../combined-release-builder.md), [versioning](../../VERSIONING.md) | | Parallel release generation | `BuildTlamatinis.cmd --build_type private` or `public` launches the corresponding complete-release wrapper for both editions concurrently, with `--self-modify`. Successful ZIPs are checked and moved into separate edition/type/date folders with SHA-256 sidecars. Failed or stale ZIPs are not presented as new releases. | [Commands and output layout](../combined-release-builder.md) | | Release identity in logs | Complete-release wrappers embed `release_type` in the generated version module. The first application-log banners identify the version and Private/Public build type. Development and unspecified builds are labeled honestly; directory names, environment variables and credentials do not guess the package type. | [Application log banners](../combined-release-builder.md#first-lines-of-the-application-log) | | Isolated dependency recovery | Standalone builds use application-owned `Temp/build-env`; the combined builder gives each edition its own cache under the release root. A failed dependency bootstrap stops if no healthy isolated environment is available, instead of falling through to the machine Python's NumPy cleanup or `pip --user`. Existing healthy isolated caches remain reusable. | `build_env.py`, `Tlamatini/agent/test_build_env.py` | | Markdown and text canvas | Readable files such as `README.md` remain editable when they contain occasional control characters introduced by shell escaping. Strict BOM-aware decoding preserves the original text and bytes. A decoded NUL, control-dominated payload or malformed encoding is still refused. | [Canvas editing](../canvas-editing.md), [Markdown](../markdown-canvas.md) | | Documentation and self-knowledge | English and Spanish guides, `Tlamatini.md`, current version banners, maintainer instructions and generated PDF/PPTX assets agree on 1.92.4. Generators carry the new behavior so future refreshes retain it. | [Full guide](../../BookOfTlamatini.md), [self-knowledge](../../Tlamatini/agent/Tlamatini.md) | The catalog remains **87 workflow agents, 68 wrapped chat agents, 111 built-in tools, 29 skills and 221 migrations**. This release adds no agent, migration or dependency solely for the combined launcher or the log banner. ## Build both editions Run from a visible Command Prompt in the developer's `C:\Development\XAIHT` workspace: ```bat BuildTlamatinis.cmd --build_type private --check BuildTlamatinis.cmd --build_type private BuildTlamatinis.cmd --build_type public --check BuildTlamatinis.cmd --build_type public ``` `--check` only previews the emitted versions and commands. Use `--Override_versioning 1.92.4` when deliberately selecting that common number; the bare override flag adopts the English resolver's number for both. Ordinary mismatch diagnostics show both predictions and their version provenance before any long build starts. The complete wrappers still perform their existing packaging and privacy checks. The workstation launcher and its sibling files live outside the two repositories; they are developer tools, not installed application services. Results go to: ```text Tlamatinis-Releases/ Tlamatini/{Private|Public}/YYYY-MM-DD_HH-mm/ Tlamatini-Spanish/{Private|Public}/YYYY-MM-DD_HH-mm/ ``` Each pair shares its start-minute folder name; collisions receive a numbered suffix. Logs and receipts live under `.runs/`. Each successful edition keeps its ZIP even if the other edition fails, and the overall command then returns failure. Private keyed ZIPs contain private data and belong only with their intended recipients. ## Carried behavior Torrenter retains queued metadata inspection when all four slots are occupied, signed-in-account ownership, full activity details and optional waiting for the verified download manifest. It publishes verified files to Windows Downloads, with the edition's `content_generated/Torrenter/` fallback when necessary; always use the actual manifest destination. Executer retains `PLAYWRIGHT_BROWSERS_PATH` shell assignments. Updates carry the verified uninstaller and preserve the existing vault; uninstall handles literal Windows browser-cache names. See [1.92.3 history](2026-11-01-v1.92.3.md), [Torrenter](../torrenter.md) and [self-management carriage](../self-management-carriage.md). ## Dated verification On **8 November 2026**, the preceding complete-build campaign produced all four real English/Spanish Private/Public ZIPs. All four executables extracted from those archives reported **1.92.3** and their correct release type. Package integrity, public-data audits, frozen-runtime checks, **26 build-isolation tests**, and focused lint passed. These are the actual archived results; they have not been relabeled as 1.92.4 binaries. See the [dated build record](../combined-release-builder.md#complete-private-and-public-builds--2026-11-08). The 1.92.4 documentation refresh regenerates and checks documents; it does not run a new executable build, replace an installed application, or claim clean-install/reboot/live-model acceptance. Git commits, tags and pushes remain separate maintainer actions.