Changelog

Changelog

Version history for Git Lora. Every release is signed, every installer carries a SHA-256 checksum, and the updater refuses to install anything it cannot verify.

---

3.0 — August 2026

Git Lora and gitlora.uz become one system. Until now the application was entirely self-contained. It now has a service layer — built so that being self-contained is not what gets lost.

• Installation registry using a random identifier generated on your own machine. No hardware fingerprinting: no MAC address, no machine name, no serial numbers.
• Update checks that verify publisher, signature and SHA-256 before installing. A build without a checksum is not offered at all.
• Support tickets from inside the app. Diagnostics are sent only with an explicit tick, and the server discards them if the tick was missing.
• A control panel with separated roles: Owner, Admin, Support, Release Manager, Analyst — enforced server-side, with every action and refusal audited.
• If gitlora.uz is unreachable, the app works exactly as before. It never depended on the website, and that deliberately did not change.

2.8 — August 2026

Sync and languages.

• Optional sync: you choose the destination — your own server or your own storage. gitlora.uz is not a place project content is stored under any configuration.
• Three interface languages: English, Russian, Simplified Chinese.
• Import of existing Markdown vaults without converting them to a private format.

2.6 — July 2026

Finalizer and branches.

• The Finalizer assembles a long artifact end to end — a manuscript, a document, a codebase — stage by stage under constraints set once.
• Preview of several possible developments before assembly: you approve one.
• Branches inside a project: alternative plot lines or implementation approaches, with no knowledge of Git required.

2.3 — July 2026

Autonomous Engine.

• Long-running processes: plan, execute, checkpoint, recover, QC, continue.
• Progress is checkpointed into memory, so a failure halfway through does not start everything over.
• Processing runs on your computer.

2.0 — June 2026

Agent OS, and the rule that AI never overwrites silently.

• A persistent runtime working through a queue of goals in the background, with its own memory scope per run.
• Every AI edit becomes a proposal: stored, shown as a diff, passed through a quality gate, and applied only once you agree.
• A QC agent that can refuse an edit.

1.5 — June 2026

A companion that remembers the project.

• A conversation with access to canonical memory: answers are grounded in what you have already written.
• Private companion memory that never becomes project canon.
• MCP server: an external AI client can ask about your project without receiving a copy of every file.

1.2 — May 2026

Graph and entities.

• Entity extraction from your own files: characters, locations, modules, decisions, events.
• A relationship graph, for answering "what breaks if I change this".
• Fact tiers: canon, working, sandbox. Contradictions between canonical facts are surfaced rather than averaged away.

1.0 — May 2026

Foundation.

• A local-first workspace: a project is an ordinary folder on your disk.
• Markdown editor with preview, and a file tree.
• The first version of canonical project memory, indexed locally.
• Your API key stays on your computer; model requests are not proxied through anyone else's servers.

---

How releases are published

Every installer is published with a SHA-256 checksum and a detached signature. Before installing an update, Git Lora verifies that the download is HTTPS, that the publisher is the expected one, that the signature is valid and that the checksum matches. A release without a checksum is not offered at all — an unverifiable installer is worse than no update.

Releases below minimum_version are told to reinstall from the website rather than upgrade in place, because a build too old to update safely should not try.