Versionsverlauf

Das Code-Repository listet 104 Commit-Titel in 5 Gruppen auf, unter Unreleased. Diese Seite wird aus seiner Datei CHANGELOG.md erzeugt und nie von Hand nachbearbeitet; die Titel sind so zitiert, wie das Repository sie schreibt. Sie richtet sich an alle, die sehen wollen, was sich im Hub und in seinen Brücken geändert hat.

Unveröffentlicht

Neu

Port the Hub core to Windows
Add the manual pages of the two commands and the package paths to the guides
Add the Spanish guides: the five application modules and the model guide
Add the German guides: the five application modules and the model guide
Add the French guides: the five application modules and the model guide
Add the cold recipe: the real binary through init and a session of four calls
Add the dependency, repository, server and README invariants
Write the README and the guide for the model
Add the licence, the security policy, the changelog generator and CI
Add the test that drives a real LibreOffice through the generated bridge
Add libremodular-launch libreoffice: start LibreOffice and its bridge, or stop the bridge
Add the Hub module that serves Writer, Calc and Impress through one bridge
Add the LibreOffice adapter and its generated bridge
Add the Inkscape module of the cli mode
Add private work file helpers and a reader of passed variables
Add the Krita adapter and its generated bridge
Add the Blender adapter and its generated bridge
Add the GIMP adapter and generate the single-file GIMP bridge
Add the common core of the Python bridges
Add a reference bridge and test the bridge client against it
Add the bridge client, the module registry and the two-tool MCP server

Korrekturen

Fix the bridge dropping a client that reconnects as soon as it sees the close
Fix the Inkscape module answering before the killed process group has vanished
Fix the French README: link the French guides, set the non-breaking spaces

Documentation

Document the contribution checks and link them from the four READMEs
Describe the tool parameters in English for the MCP client
Document the one package Inkscape’s inkex needs on a clean Debian 13
Document the build prerequisites in the READMEs: a C toolchain and Rust 1.97
Document the website pages Quickstart, Installation, Architecture and Security in the READMEs
Document the Fedora, openSUSE Leap and Arch Linux packages in the README and the manual pages
Describe two test doubles by the defect they stand for
Record the corrections, the public files and the cold recipe in the journal
Record the LibreOffice run on 25.2.3.2 and the mode a fresh clone gives the bridge file
Document the LibreOffice module and record this work in the journal
Record the Krita, Blender and Inkscape work in the journal
Document the GIMP bridge and record this work in the journal
Record the Hub, its protocol details and its decisions in the journal

Tests

Test that the bridge frees its place before the client sees the close
Test the cold start of the LibreOffice bridge against a real LibreOffice
Test Inkscape through the MCP server
Check that only the Inkscape module starts processes, through its trait
Check mechanically that bridge security stays in the bridge core
Check the single output point and network confinement mechanically
Test both tools end to end, in memory and on the real binary over stdio

Änderungen

Module guides: Blender cannot reopen a file from a script, has no denoiser here and draws Workbench solids; Krita export waits on a dialog and has no stroke call, in four languages
README: version, licence, continuous integration and package badges, as the published projects have them
Spanish manual page: say man pages where the English says manual pages
LibreOffice guide: drop the remark about a bridge file from before a change, in four languages
README translations: credits as in English, the guide link names its own language, the Spanish guard sentence and reporting verb, the German Linux condition and Calc sentence
Credits: the two free models of the Windows trial and of the first-contact test, and the packages, website and translations of Claude Code
SECURITY.md: the supported versions are the latest release and the latest commit; drop the note about the repository settings
Guides: name the five guard categories, say that the guard refuses writes and only reports reads, describe the MCP framing and the answer to an unknown target
Format the English-description test
README: point to the model guide, define content_origin, accept hub in get_state, and say what a capture leaks
README translations: the presentation formula reads as on the site in French, German and Spanish
README invariant: Windows is a published platform, AI and macOS stay out
Cite Windows 11 on the READMEs and the manual pages, at the level reached
Windows installer: recipe, validation script and on-demand workflow
Tests on Windows: the volatile directory of the binary under test is never the user’s profile
Leave the changelog’s own regeneration commits out of the changelog
Say in the Blender guide that the default view transform changes colours
Say in the GIMP guide that layer.fill ignores the selection
Say in the GIMP guide that GIMP needs an X display even without its interface
Say in the Blender guide that the first render of a new profile takes about 30 seconds
Read the bridge file as UTF-8 in the console commands of the guides
Move the product journal to the website
Make the Inkscape tests take turns when they write a fake program or start a process
Flag an Inkscape output cut at the limit as truncated
Name the installed bridge path without tying it to one package format
Split the two configuration paths of the libremodular-launch manual page into two entries
Give the installed bridge path of libremodular-launch its own line in the manual pages
Name the installed bridge file in the refusal of libremodular-launch
Print the help of the subcommands in English
Trust a bridge file owned by root, so the file the Debian package installs is accepted
GIMP bridge: serve_main_thread() turns GLib’s main loop so the bridge outlives a -b command
Blender guide: the render hang from the bridge thread is intermittent, measured over 23 runs
Blender bridge: serve_main_thread() hands the main thread to the bridge in background mode, so bpy.ops.render.render runs there
Invariants: the PNG files of logo/ are the published identity, any other PNG stays a capture
Logo: PNG sizes and mono variants, source scripts; .gitignore keeps logo PNGs
Credits: Muse Spark 1.3 in the French, German and Spanish READMEs
Credits: Muse Spark 1.3 as graphic designer (logo and favicons)
Module guides: GIMP 3.0 renamed calls, inkex 1.4 traps, Blender background render limit and Workbench pitfalls; charter moved out of the public repository
Logo piste A adoptee (graphiste muse-spark-1.3-contributor, 20/10/2026): favicon.svg and favicon.ico
Commentaires et docstrings en français ; ponts regénérés
README : plateforme Debian citée, traductions en français, allemand et espagnol
Crédits : section Credits du README et CONTRIBUTORS.md
Open the README with the presentation line
Make the launcher tests take turns when they write a program or start a process
Generate the changelog from the commit titles
Make the version tests wait for the bridge to free its place
Run a LibreOffice script when no document is open
Read the application version again while it is unknown
Let the bridge core hand a request’s family to adapters that serve several
Make the second attempt of execute wait before it connects
Give Module::state the work directory so Inkscape reads its document after a restart
Keep numpy from starting a thread per core in the Inkscape module
Drive the Krita and Blender bridges end to end with the tcp module
Wait before the tcp module connects a second time
Call GIMP directly when the process is not GIMP, and record the first real run
Run the bridge tests from cargo and drive the GIMP bridge with the Hub
Purge the captures when the Hub is stopped by SIGTERM or SIGINT
Refuse a bridge that announces another application than its port’s
Extend the security foundation for captures, journal probes and the home directory
Initial commit: Rust security foundation of the Hub

WeiterÜber das Projekt →