chore(deps): relock capability_module onto the universal port (#179)

The url here is unpinned — github:logos-co/logos-capability-module — so it reads
as current, while the lock sat at 0cb33fb: the pre-#24 hand-written Qt plugin,
from 2026-08-11.

capability_module master is c670f7f, the `interface: "universal"` port from its
#24: a Qt-free impl over a host-granted trust root, declaring
metadata.json#host_services and failing CLOSED until the host grants them.

Safe here because this flake's own closure carries the granting side — the
loader resolves at acd07cf (logos-module-loader-qt#8, brought in by #178), which
stamps the hostServices property and calls logos_module_grant_host_services.
Verified in the lock rather than assumed.

This matters beyond one input: liblogos is what SHIPS capability_module —
nix/bin.nix copies its modules/ into the package and logos_core loads it through
initializeCapabilityModule(). So this lock is what consumers actually get,
whatever their own flake says. Both logos-basecamp and logos-logoscore-cli were
running the old Qt module through exactly this path, behind unpinned urls that
looked current.

`nix build .#default` and checks.tests both pass.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Dario Lipicar
2026-08-20 16:13:53 -03:00
committed by GitHub
co-authored by Claude Opus 5
parent b949212d6c
commit 6a16bfffd6
Generated
+22653 -11728
View File
File diff suppressed because it is too large Load Diff