Commit Graph
2900 Commits
Author SHA1 Message Date
LGUG2Z ae9ee327f9 build(nix): one root flake for Windows, KDE Plasma and macOS
One flake.nix and one flake.lock replace the root flake that re-exported two nested flakes.
The inputs are one nixpkgs (the revision the KDE flake was locked to, f05535a0: the VM suites
run against its Plasma and KWin 6.8.2), one crane, rust-overlay (19ecdd08, rustc 1.99.1),
flake-parts, treefmt-nix and git-hooks-nix, all the KDE flake revisions, plus asc. A second
nixpkgs, nixpkgs-x86_64-darwin (16c7794d, the macOS flake pin), serves the x86_64-darwin
outputs only: evaluating that system with the unified pin throws (nixpkgs 26.11 dropped it).

Layout: nix/common.nix (systems, pkgs, treefmt, pre-commit, dev shells default and native,
default overlay), nix/lib.nix, nix/workspace-src.nix (one source per platform from the one Cargo
workspace: the platform members, its files of the shared crates told apart by name, the data
files, and stubs for the other members, which cargo needs), nix/{windows,linux,macos}/
{build,flake-module}.nix. The dependency derivations use a manifests-only dummy source, a plain
path, so crane reads nothing built at evaluation and the Darwin outputs evaluate on Linux.

Names: unprefixed outputs are the native build (Linux: KDE; Darwin: macOS); Windows cross
outputs are windows-*; checks are windows-*, linux-*, macos-* and vm-NAME; table in docs/dev/flake.md
(next revision). One deny.toml, one format-all and one version (workspace) are used by all.
PLACEHOLDER for the agent that owns the check sets: the checks that evaluate a NixOS system
or a VM (vm-*, linux-nixos-module-eval, linux-plasma-guests-eval, linux-run-kde*) are
legacyPackages.<system>.heavyChecks.<name>, not checks, because evaluating them needs more
memory than nix flake check --all-systems can use. The Plasma guests got a stub root file system
and boot loader (mkDefault, replaced by their vmVariant) so that nix flake check can evaluate
their toplevel.

Verified: nix flake check --no-build --all-systems passes (42 s, rc 0); nix flake check
--no-build passes. Not verified: any build (next revisions record them).
2026-11-05 15:03:27 -08:00
LGUG2Z 05698a34ba fix(nix): the nix files read the final directories
The pure moves put the KDE and macOS nix files under nix/linux and nix/macos but left the
relative paths they read: the JSON schema (now schemas/linux and schemas/macos), the example
configurations and key binding samples (docs/linux, docs/macos), the key binding fixtures
(komorebi-hotkeys at the top level), the wsl2 probe script (scripts/linux). Each path now
names the file in the final directory, one more directory up because the files are one level
deeper.

Not touched: flake.nix and the nested flakes (next revisions), which still name the old paths.

Verified: not verified (nothing evaluates until the flake is rewritten; the new flake checks
these paths).
2026-11-05 15:03:27 -08:00
LGUG2Z bf300de007 docs(dev): the plan records the sponsor-only FEAT policy and the end of the root schema files
What: CUTOVER-PLAN.md follows two owner decisions. R6: one sponsor-only [FEAT] policy and one licence apply to all three platforms; section 2.2a is the concrete list of texts to rewrite (feature-check.yaml message, ISSUE_TEMPLATE feature_request, bug_report and config, README and docs index sponsorship sections, the macOS README paragraph about a private repository, licence consistency), found with git grep. R5: no root schema*.json copies and no freshness test; section 2.2b states the consequence (the old master/ raw URLs, including the one komorebic quickstart wrote into users' applications.json, stop resolving), the repository tasks, and the wording for the README and the release notes. The per-platform published file names stay an open release question with a recommendation.

How verified: sources read, nothing executed; the lists come from git grep on the tip 59b01fdb. Earlier revisions are not rewritten.
2026-11-05 15:03:27 -08:00
LGUG2Z ae4e7af9f4 chore(repo): the workspace version is 0.2.0-dev
The unified line starts the 0.2.0 development cycle and is not released yet, so the one
workspace version (every package takes it through version.workspace = true) is the
pre-release 0.2.0-dev instead of 0.2.0. The release revision sets it to 0.2.0.

Cargo.lock only changes the version of the workspace's own packages. The schema
descriptions and the macOS schema links keep naming v0.2.0: they document the schema of
the release this line leads to. The update widget of the bar compares version strings, so
a dev build never offers the 0.1.x releases as an update.

Verified: cargo metadata --offline succeeds; cargo test -p komorebi --test linux_version
passes; komorebic --version prints 0.2.0-dev. The other gates were not re-run for this
one-line change.
2026-11-05 15:03:27 -08:00
LGUG2Z 551d325bfc docs(dev): the 0.2.0-dev landing and the 0.2.0 release are separate phases in the plan
What: CUTOVER-PLAN.md follows three owner decisions. (1) No private sponsors repository: the mirror option and sponsor wording are removed, R1 is answered, only the confirmation of the push stays a gate (L3). (2) Schemas are per-platform files under schemas/: R5 states the fact and keeps two sub-questions (root schema*.json copies for old master/ URLs; published file names). (3) The workspace is 0.2.0-dev: section 4 and 5 split the DEV-LINE LANDING (L0-L6: komomono to master, no tag, no artefacts, CI on, nightly publish off) from the RELEASE (E0-E8: version 0.2.0, tag, artefacts, announcement); the go/no-go lists are split the same way, and the macOS hand-check (R2) gates the release only.

R6 (FEAT policy, licence) stays open with the changed premise. R3, R4, R7-R12 are unchanged.

How verified: sources read, nothing executed; the version 0.2.0-dev is as told by the coordinator and not re-read from the tree.
2026-11-05 15:03:27 -08:00
LGUG2Z ff5aeba752 docs(dev): the plan to land the consolidated repository (0.2.0)
What: docs/dev/CUTOVER-PLAN.md, a plan (not an execution) for landing the consolidated repository as LGUG2Z/komorebi and releasing 0.2.0. It covers branch and history mechanics (fast-forward master, the divergence with komomono on origin, PRs, forks, Scoop/WinGet/nixpkgs users, protection, the old-hashes check), what happens to komorebi-for-kde and komorebi-for-mac, the one CI (jobs, runners, triggers, e2e and VM tiers, caching, dependabot, secrets, with draft workflow files in an appendix), the 0.2.0 release (tags, artefact matrix, notes, schemas, docs, Homebrew), the order of the irreversible steps with go/no-go lists and the exact git and jj commands for the user, and twelve open decisions with recommendations.

Why: the cutover stack (wip-cutover, wip-cutover-docs) leaves the publication, CI and release decisions open (MIGRATION-SUMMARY.md section 7); several of them are irreversible (publishing the private KDE history, a published tag) and need the owner's answers first.

How verified: sources read, nothing executed. Facts come from the repository at 2185556efba6, the three old clones, the plan, decisions and progress logs, and read-only gh api/list calls; every inference is marked in the text, and what could not be determined is listed at the end of section 6. The flake outputs are placeholders until the flake-one stack lands. No file under .github/ was created.
2026-11-05 15:03:27 -08:00
LGUG2Z 05a7c0b6fe docs(windows): cargo install names the daemon package directory
docs/installation.md (the Windows build-from-source guide, published on the site) installed the
daemon with `cargo install --path komorebi`. The `komorebi` binary is built by the package in
komorebi-daemon/ (komorebi-windows is the library behind it, and has no binary), so the command
names `--path komorebi-daemon`. This was already wrong when the daemon became its own package; the
directory rename made it visible.

Verified: komorebi-daemon/Cargo.toml has `name = "komorebi"` and a main.rs; the command itself was
not run (Windows only).
2026-11-05 15:03:27 -08:00
LGUG2Z 920a3d1268 docs(comments): comments name the Linux docs and nix files where they are
Comment-only edits (no code changed): the module docs of komorebi-linux/src/kwin/mod.rs and
hotkeys.rs pointed at docs/dev/PLATFORM.md and docs/dev/DESIGN.md (now docs/linux/dev/...) and at
nix/tests/vm/suites/kwin-events (now nix/linux/...); the comment in komorebic/Cargo.toml named the
deleted shim komorebi-client-linux and now names the keys that exist (komorebi-linux, komorebi-macos).

Left alone on purpose: the same stale doc paths in comments under nix/ (not mine to edit),
fixture names (kfde-tiled), URLs, and the runtime default PathBuf::from("docs/cli") of docgen
(behaviour).

Not verified by a build: only comments changed. These files are inputs of the KDE nix derivations,
so they will rebuild.
2026-11-05 15:03:27 -08:00
LGUG2Z e0e0f49714 docs(dev): old paths in the analysis notes carry the new ones
seam, core-model, settings, rule-matching, bar-unification, e2e-to-unit and known-issues are
measurements and decision logs written for the old directories. They keep their history; each
gets a "Paths (cutover stack)" note under the title that maps the old names (komorebi/,
komorebi-for-kde/komorebi/, komorebi-for-mac/komorebi/, nix/, docs/, schema files) to the new
ones and says the 0.1.x numbers are history. The seam.md tree table, the test file paths in
e2e-to-unit.md and known-issues.md (files that exist and are named as current) and the
bar-e2e.md schema path now name the files where they are.

Not rewritten: the line numbers, measurements and "at the time" statements. Not touched:
backend-switch.md (no old paths), build-and-test.md and flake.md (flake-one).

Verified: the files named as current exist (komorebi-linux/tests/*.rs); relative links resolve.
2026-11-05 15:03:27 -08:00
LGUG2Z 4ca58a08ab docs(dev): the Mac runbook names the consolidated packages, paths and version
macos-hand-check-plan.md: a note at the top says the text was changed for the cutover stack
and not run; the build command also names komorebi-client and komorebi-macos; the line
about never mixing -p komorebic-macos with -p komorebic is replaced by a line saying the
shims are gone; the example config is docs/macos/komorebi.example.json, the schemas are
schemas/macos/schema.json and schemas/macos/schema.bar.json, and the expected version is
`komorebi 0.2.0` from crates/komorebi-version.
macos-handcheck.md (the older list): a paragraph at the top maps the old names to the
current ones and points at the plan; the Mini run and the bar file path get a "now" note.

The runbook has no flake attributes, so none are left for flake-one. Not run: nothing in
this revision was executed, on a Mac or elsewhere; the package names were checked against
the workspace manifests (komorebi is komorebi-daemon, komorebi-macos is the library).
2026-11-05 15:03:27 -08:00
LGUG2Z 1b3178cede docs(dev): the cutover account in the map, the summary and the unified-binaries note
ARCHITECTURE-UNIFIED.md: the status line, section 1 (a table of where each platform is now),
the package paragraph (shims gone, version crate), the oracle paths (schemas/*, docs/*/cli),
section 6 (now "done / still open" instead of "what is still the old layout"), the tier-0 row,
and the helper tools paragraph (tools/ is committed now).
MIGRATION-SUMMARY.md: status line, the three-trees paragraph, the oracle paths, the known
issues paragraph, and section 7, which was "Cutover list (not done)" and is now a table of what
the cutover stack did and what is open; item 7 of "How to continue".
unified-binaries.md: the status banner (with a map from the old directory names to the new
ones), the Mac Mini commands (the shim line removed, schema.bar.json under schemas/macos,
`komorebi 0.2.0`), and "What is left for the cutover" is now a done / still open list.

Still open, as stated in the three: the one flake (flake-one is writing it), CI and release
workflows (the old ones are archived in docs/dev/old-ci), the site and repository URLs,
COMPARE.md. The 0.1.42 / 0.1.0 / 0.1.1 numbers and the old directory names that stay in
narrative sections are history and are marked as such. Not touched: build-and-test.md and
flake.md (owned by flake-one).

Verified: the relative links of the three files resolve. The statements about what the stack
did are taken from the revision descriptions of wip-cutover, not re-measured.
2026-11-05 15:03:27 -08:00
LGUG2Z f82fe692fc build(docs): the Windows site does not publish docs/linux, docs/macos or docs/dev
mkdocs builds docs_dir: docs, which now also holds docs/linux, docs/macos (each with its own
index.md, README.md and cli/ pages) and docs/dev. Without a change they were all built into
the Windows site (692 files instead of the Windows ones) and 250 warnings appeared for their
links to sources outside docs/. exclude_docs lists /linux/, /macos/ and /dev/; the nav is
not touched.

Verified: mkdocs 1.6.1 with material 9.7.6 and mkdocs-macros 1.3.9 (a nix python env):
`mkdocs build --strict` passes with the change; the file set of the site is exactly the one
of the build without the change minus linux/, macos/ and dev/, and the other files are
byte-identical (search index and sitemap differ because they listed the extra pages).
2026-11-05 15:03:27 -08:00
LGUG2Z 629cb19580 docs(readme): a Platforms section, the SocketMessage link, the guides of the ports
README.md: the note "komorebi for Mac lives here" (a link to the old repository) is replaced
by a "Platforms" section: the three platforms with their daemon library, documentation
(docs/linux/README.md, docs/macos/README.md) and schemas directory, and a sentence that
where the repository is published and where the releases and sites live is not decided
yet. The SocketMessage link pointed at komorebi/src/core/mod.rs#L37 of the old upstream
repository; it is now a relative link to crates/komorebi-protocol/src/message.rs, where the
enum lives. CONTRIBUTING.md: a first line links the contribution guides of the Linux and
macOS ports.

The link to the old komorebi-for-mac repository is kept as history; nothing else of the
README (it is the Windows README) was changed.

Verified: the relative links resolve (link checker over the repository markdown).
2026-11-05 15:03:27 -08:00
LGUG2Z 1afac08af5 fix(scripts): the Linux scripts find the repository from scripts/linux/
The scripts were written for a KDE-only repository root (komorebi-for-kde/, scripts/ one
level below it). They now live in scripts/linux/ of the consolidated repository:
- run-kde looks for the repository two directories above itself (flake.nix at the root) and
  no longer knows the komorebi-for-kde/ subdirectory; its comments name nix/linux and docs/linux
- vm-mac cd`s two levels up, usage and comments name scripts/linux/vm-mac
- sync-e2e-core and scenario-status read nix/linux/tests/vm/lib, and usage lines name the new
  paths (scenario-status resolves the library with parents[2])
- wsl2-probe.sh names docs/linux/dev/wsl2-probe.md and prints "komorebi (KDE Plasma)" instead of
  komorebi-for-kde in its report header
- compare-gen.py is stale by design: the docstring now says so a second time (layout) and
  names the new path of COMPARE.md; the logic is not repaired

Flake attribute names the scripts call (nix run .#run-kde, .#wsl2-probe, legacyPackages.*.vm.NAME
in vm-mac) are left for the one-flake revision.

Verified: bash -n and shellcheck -S warning pass on the four shell scripts; the two Python
scripts parse (ast); `bash run-kde --dry-run` run from /tmp prints KOMOREBI_REPO as this
checkout; `sync-e2e-core --check e2e/lib` prints "in step"; `scenario-status --help` runs.
Not run: the VM, vm-mac, wsl2-probe.
2026-11-05 15:03:27 -08:00
LGUG2Z a7b78cc7e4 docs(linux): paths and links name the consolidated layout
The KDE docs were moved from komorebi-for-kde/ to docs/linux/ and the sources, nix files,
scripts and schemas to komorebi-linux/, nix/linux/, scripts/linux/ and schemas/linux/, so
every relative link that left docs/ (to sources, nix files, scripts, schemas, .envrc,
rust-toolchain.toml, the old CI file) was broken, and the text named the old paths.

Links were rewritten mechanically by resolving each broken target against the old
location and mapping it to the new one; link texts and code-span paths were updated to
the new paths (komorebi/src -> komorebi-linux/src, nix/ -> nix/linux/, scripts/ ->
scripts/linux/, docs/ -> docs/linux/, schema.json -> schemas/linux/schema.json). The
crate list of the README names komorebi-linux, komorebi-daemon and komorebi-version;
`cargo install --path komorebi` becomes komorebi-daemon; the comparison paragraph of
CONTRIBUTING.md says compare-gen.py is stale (it looks for the old sibling trees).

URLs of the old GitHub repositories are left as they are (a release decision).
COMPARE.md is left as it is (already marked stale).

Verified: a link checker over every markdown file (outside cli/, nix/, tools/, old-ci)
reports no broken link in docs/linux. Nothing was built.
2026-11-05 15:03:27 -08:00
LGUG2Z 5b2381efb4 docs(macos): cargo install names the daemon package directory
The macOS installation guide built the daemon with `cargo install --path komorebi`. The
`komorebi` binary is now the package in komorebi-daemon (komorebi-macos is the library
behind it), so the command names `--path komorebi-daemon`.

Verified: the directory exists and its package is named komorebi; the command itself was
not run (macOS only).
2026-11-05 15:03:27 -08:00
LGUG2Z 4653986f0e refactor(repo): move the platform READMEs, contributing guides and old CI files under docs/ (pure move)
komorebi-for-kde/README.md, CONTRIBUTING.md      -> docs/linux/
komorebi-for-mac/README.md, CONTRIBUTING.md      -> docs/macos/
komorebi-for-kde/.github/*                       -> docs/dev/old-ci/linux/
komorebi-for-mac/.github/*, mkdocs.yml, check_schema_docs.py, dependencies.json,
formula.template.rb                              -> docs/dev/old-ci/macos/

The CI workflows, dependabot files, issue templates, the macOS Homebrew formula template and
docs-site configuration of the two old repositories are kept for the CI and release plan
that follows (one workflow set, one release); under docs/ GitHub ignores them, as it did
under the subdirectories, so no KDE or macOS workflow runs on this branch. Renames only (19
files); the Windows .github and files at the root are untouched.
2026-11-05 15:03:27 -08:00
LGUG2Z 73c43239b5 chore(repo): one rustfmt, toolchain, gitignore and licence; format-all checks one group
komorebi-for-kde and komorebi-for-mac each had a rustfmt.toml (the root one minus
newline_style), a rust-toolchain.toml and .envrc (identical to the root's), a .gitignore and
a LICENSE.md; they are deleted, and the root .gitignore gains the KDE entries (/.vm,
__pycache__/, *.pyc). tools/format-all now has one group: every .rs file of the repository,
file by file with skip_children, with the root rustfmt.toml and the dev shell's nightly
(the --tree option is gone).

Verified: tools/format-all --check passes on the whole tree (the formatting of the six
files edited in the path-fix revision was applied to that revision).
2026-11-05 15:03:27 -08:00
LGUG2Z d726ec8ddb build(just): one justfile for the three platforms
The root justfile now has the recipes of all three: the Windows ones (PowerShell loops
through [windows] recipes, as before) and unix variants of install, build and schemapub,
the KDE ones (lint, check-js, the VM recipes, run-kde, wsl2-probe, nixgen-linux), the
macOS nixgen, and jsonschema/docgen-local that write schemas/<platform> and
docs/<platform>/cli for the platform they run on. Package names are the unified ones (one
komorebic, komorebi, komorebi-bar everywhere) and all paths are the final directories.
komorebi-for-kde/justfile and komorebi-for-mac/justfile are deleted. The KDE
`just check` recipe (cargo test --workspace) is dropped: on Linux it builds the Windows crates;
the commands in docs/dev/build-and-test.md replace it.

Verified: just --list parses; just --dry-run jsonschema prints the right commands on Linux.
The recipes themselves were not run.
2026-11-05 15:03:27 -08:00
LGUG2Z 138a97e95c build(deny): one deny.toml for the three platforms
The root deny.toml now covers every platform: the graph targets are the three Windows
targets plus x86_64 and aarch64 Linux and aarch64 macOS; the advisory ignores gain the
KDE ones (zbus family, RUSTSEC-2026-0370..0372) and the macOS ones (git2 through shadow-rs,
RUSTSEC-2026-0183/0184; quick-xml, RUSTSEC-2026-0194/0195); the licence allow list was
already a superset of both trees' lists; clarify entries are added for komorebi-linux,
komorebi-macos, komorebi-hotkeys and komorebi-version; quickxml_to_serde joins the allowed
git sources. komorebi-for-kde/deny.toml and komorebi-for-mac/deny.toml are deleted.

The reasons of ignores that exist in more than one file keep the root text.

Not verified: cargo deny was not run here (it is not installed; the nix check of the root
flake runs it in the flake revision of this stack).
2026-11-05 15:03:27 -08:00
LGUG2Z fa4752a514 fix(repo): sources and tests read files from the final directories
The include_str! and test paths of komorebic (Linux and macOS modules and tests),
komorebi-bar (macOS), komorebi-linux, komorebi-macos, komorebic-core, komorebi-config and
komorebi-bar-core named the old trees (komorebi-for-kde/docs, komorebi-for-mac/docs, the
schema.json files at the roots of the trees, komorebic/fixtures of the macOS tree). They
now read docs/linux, docs/macos, schemas/{windows,linux,macos} and the byte-identical
komorebic/fixtures at the root; the macOS pan tests point at the root fixtures, and
komorebi-linux's config_parity test takes the example config from docs/linux. Comments
that named the old paths were updated with them.

Not touched: markdown docs, justfiles, scripts, tools and nix files that name the old
paths (next revisions of the stack).

Verified: Windows clippy --locked --all-targets -D warnings (default members) passes; on
Linux cargo test -p komorebi -p komorebic -p komorebi-client -p komorebi-linux -p
komorebi-hotkeys -p komorebi-config -p komorebi-bar-core -p komorebic-core -p
komorebi-protocol (one test thread) passes, 96 test binaries ok after config_parity was
fixed; macOS cargo check --target aarch64-apple-darwin (fake CC) passes. Nix not run.
2026-11-05 15:03:27 -08:00
LGUG2Z f661493793 refactor(repo): one schemas/ directory with a subdirectory per platform (pure move)
schema.json, schema.asc.json, schema.bar.json                -> schemas/windows/
komorebi-for-kde/schema.json, schema.asc.json                -> schemas/linux/
komorebi-for-mac/schema.json, schema.asc.json, schema.bar.json -> schemas/macos/

The generated schemas of the three platforms are checked in side by side instead of at the
root and in two subtrees. Renames only; the tests, the justfile, the nix checks and the
docs that read them by path are updated in the path-fixing revision of this stack.
2026-11-05 15:03:27 -08:00
LGUG2Z 70010996da refactor(repo): move the KDE scripts and spikes to the top level (pure move)
komorebi-for-kde/scripts/ -> scripts/linux/
komorebi-for-kde/spikes/  -> spikes/

Renames only. The scripts' own references to the old directories (and to komorebi/src of
the old trees) are fixed in the path-fixing revision of this stack.
2026-11-05 15:03:27 -08:00
LGUG2Z f01853ceca refactor(repo): move the KDE and macOS nix files under nix/ (pure move)
komorebi-for-kde/nix/ -> nix/linux/
komorebi-for-mac/nix/ -> nix/macos/

The nix expressions of the platforms (modules, option files, VM test suites, kwin effects,
the darwin module) sit next to the existing nix/workspace-src.nix. Renames only (252
files); the flakes that import them are replaced by one root flake later in this stack, so
nix does not evaluate at this revision.
2026-11-05 15:03:27 -08:00
LGUG2Z d781028a2a refactor(repo): move the KDE and macOS docs under docs/ (pure move)
komorebi-for-kde/docs/ -> docs/linux/
komorebi-for-mac/docs/ -> docs/macos/

The Windows docs stay where they are (docs/). Renames only, so links and include paths
that named the old directories are broken at this revision; they are fixed in the revision
that fixes the paths of the whole layout move.
2026-11-05 15:03:27 -08:00
LGUG2Z 348cb7ae96 build(repo): cargo manifests use the final directories
The workspace members and the path dependencies of komorebi-client, komorebic,
komorebi-daemon, komorebi-linux, komorebi-macos and komorebi-hotkeys name the directories
of the previous revision (komorebi-windows, komorebi-linux, komorebi-macos,
komorebi-hotkeys at the top level); the dependencies of the moved crates on the shared
crates are one directory shorter. cargo metadata --offline succeeds with an unchanged
Cargo.lock. Source files that include files by relative path are fixed later in this
stack.
2026-11-05 15:03:27 -08:00
LGUG2Z cd3892de76 refactor(repo): move the platform libraries to their final directories (pure move)
komorebi/                          -> komorebi-windows/
komorebi-for-kde/komorebi/         -> komorebi-linux/
komorebi-for-mac/komorebi/         -> komorebi-macos/
komorebi-for-kde/komorebi-hotkeys/ -> komorebi-hotkeys/

The directories now carry the names of their packages (komorebi-windows, komorebi-linux,
komorebi-macos). Renames only: every file is a 100% rename (270 files); nothing is edited,
so the workspace does not build at this revision. The next revision fixes the paths.
2026-11-05 15:03:27 -08:00
LGUG2Z 170952596f refactor(repo): delete the shim packages
komorebic-linux, komorebi-client-linux, komorebic-macos, komorebi-client-macos and
komorebi-bar-macos were #[path] includes of the unified komorebic, komorebi-client and
komorebi-bar modules, kept only so the old package names kept building. The unified
packages are the only ones now, so the five directories and their workspace members are
gone (Cargo.lock loses their dependency entries).

Things that named the old packages follow: the clarify entries of the two per-tree
deny.toml files, tools/fast-check, tools/mac-check.sh and tools/kde-closure-check (it now
walks komorebic and komorebi-client), and the doc comment of komorebic/src/main.rs.
komorebi-for-kde/nix/root-crates.json gains komorebic, komorebi-client and
crates/komorebi-version, because those are root crates the KDE build depends on now.
komorebi-for-mac/komorebi/src/pan.rs read its transcripts from the deleted
komorebic/fixtures; they are byte-identical to the root komorebic/fixtures, so the three
paths point there.

Not touched here (done in the flake and justfile revisions of this stack): the nix
flakes and justfiles of the trees, which still name the removed packages, and docs/dev.

Verified: Windows cargo clippy --locked --all-targets -D warnings (default members) passes;
KDE cargo test -p komorebi -p komorebic -p komorebi-client -p komorebi-linux passes; macOS
cargo check --target aarch64-apple-darwin (fake CC) of komorebi, komorebi-macos, komorebic,
komorebi-client, komorebi-bar passes; tools/kde-closure-check passes. The nix flakes were
not run.
2026-11-05 15:03:27 -08:00
LGUG2Z cce2886622 refactor(version): one komorebi-version crate for Linux and macOS
version-linux (komorebi-for-kde/version, shadow-rs 2) and version-macos
(komorebi-for-mac/version, shadow-rs 1) had the same build.rs and the same lib.rs. They
are now one package, crates/komorebi-version (lib name version, shadow-rs from the
workspace), and the KDE and macOS daemons, their command lines and the unified komorebic
depend on it under the key version. The extern crate lines of komorebic/src/main.rs that
renamed the two crates are gone, and the two deny.toml clarify entries name the new
package.

komorebi-daemon/tests/linux_version.rs read the version out of the old crate's Cargo.toml
text, which no longer has a number (it is inherited); it now expects the package version,
which is the workspace version.

Verified: cargo test -p komorebi -p komorebic -p komorebi-client -p komorebi-linux (KDE
side, native Linux) all pass, including the version test; cargo check --target
aarch64-apple-darwin of the macOS packages with the fake C compiler passes. Windows and
nix were not run for this revision (Windows does not use the crate; nix runs at the end of
the stack).
2026-11-05 15:03:27 -08:00
LGUG2Z 0180d80fa6 docs(schema): the schema descriptions name v0.2.0
The doc comments that become the description of schema.json and schema.bar.json said
v0.1.42 (Windows), and the macOS views of the schemas said v0.1.0 and linked
komorebi.0.1.0.schema.json. They now say v0.2.0 (the unified release) and link the
0.2.0 file. The macOS site domain in those links is not touched: where the schemas are
published is a release decision.

The checked-in schema.json and schema.bar.json of the Windows tree and of
komorebi-for-mac were edited to match, and the size and hash pins of
crates/komorebi-bar-core/tests/schema_oracle.rs were updated for the two bar schemas
(Windows 248,539 bytes, FNV-1a aaa0fabfb45967b7; macOS 116,925 bytes, a042f6ac063a0cfd).
The KDE schemas carry no version text.

Verified: cargo test -p komorebi-config -p komorebi-bar-core -p komorebi-protocol and
-p komorebi-linux --test schemas pass. The komorebi-config doctest fails to link in
the nix dev shell (it cross-compiles to windows-msvc); that is not caused by this change.
2026-11-05 15:03:27 -08:00
LGUG2Z 87fb8340d0 chore(repo): one workspace version, 0.2.0
Every package of the workspace now takes its version from [workspace.package]
(version.workspace = true) instead of its own number. The numbers before were
0.1.42 (Windows libraries and packages), 0.1.0 (KDE, the macOS version crate,
komorebi-shortcuts and the e2e guest crates) and 0.1.1 (macOS libraries); the
unified release is 0.2.0 for all of them.

Cargo.lock only changes the version of the workspace's own packages.

Not changed here: the version text in schema doc comments and the generated
schemas (next revision), and the shim packages, which are deleted later and
only pick up the number meanwhile.

Verified: cargo metadata --offline --locked succeeds.
2026-11-05 15:03:27 -08:00
LGUG2Z e1fc1499d4 test(e2e): the bar scenario lists processes with plain tasklist
The bar scenario counted komorebi-bar.exe processes through 'tasklist /fi "imagename eq komorebi-bar.exe" /fo csv /nh' run via the guest agent, which exits with status 1 there (quoting of the filter), so the process checks failed even though the bar was running and drawing (wgpu). 'tasklist /fo csv /nh' lists the process and the existing filter on lines starting with komorebi-bar.exe keeps the result the same. Found by the candidate 8 Windows gate (gate-cand8.md, bar-fix8.diff: with it the scenario ran 23/0). The file is also reflowed by ruff format (the CONFIG dict), which is formatting only. Verified: ruff format and ruff check on the file; the e2e run in the gate with the one-line change.
2026-11-05 15:03:27 -08:00
LGUG2Z 0ae08e823e chore(repo): candidate 9: the extra shared commands, the macOS wm2 batch and the docs on top of candidate 8, plus the KDE nix check fixes
Candidate 9 (final): wip-cand9draft (wip-u-cmd2 with the router gate_message hook and 12 more shared arms, wip-u-mac-wm2, wip-u-docs2) merged with wip-u-kdenix (KDE deny --config order, intra-doc links, two KDE manifests formatted with taplo, KDE fmt check through tools/format-all with the flake's own nightly). Conflicts, if any, are resolved here.
2026-11-05 15:03:27 -08:00
LGUG2Z 9a20844146 chore(repo): combine the extra shared commands, the macOS wm2 batch and the final docs (candidate 9 draft)
Candidate 9 (draft): wip-u-cmd2 (router gate_message hook + 12 more arms through komorebi_core::command; stacked on wip-u-wm2) with wip-u-mac-wm2 (shared push_simple_rule, macOS ignore-rule fix, Minimize/Close/DebugWindow methods) and wip-u-docs2 (MIGRATION-SUMMARY.md, macos-hand-check-plan.md), all on wip-cand8. Conflicts, if any, are resolved here.
2026-11-05 15:03:27 -08:00
LGUG2Z 2544012c2e fix(nix): check the KDE formatting file by file with the flake's nightly rustfmt
The kfde fmt check ran `cargo fmt -p ...` and failed with `failed to resolve
mod windows` for komorebic and komorebi-client: rustfmt follows the
cfg_select! branches of the shared entry files into files the KDE source does
not have. It is now a runCommand running tools/format-all --tree kde with the
rustfmt of the flake's own nightly (fmtToolchain, the toolchain craneLibFmt
already used) over komorebi-for-kde/**/*.rs and the linux modules of the
shared crates, file by file with skip_children and komorebi-for-kde/rustfmt.toml.
tools/format-all now takes the rustfmt of the root dev shell first (the same
pinned nightly) before a nightly on PATH, because a different nightly may
format differently or not follow cfg_select.

Verified: with the rustfmt of that very nightly (rust-overlay 19ecdd08,
rustfmt 1.11.0-nightly 2026-10-27, built from the flake's pins)
tools/format-all --check passes for kde, mac and windows on this tree, so the
only failure was the module resolution, not different formatting. The nix
attribute evaluates; not built.
2026-11-05 15:03:27 -08:00
LGUG2Z 2447f7c94b docs(core): section 26, the command seam after D-coord-17 (28 arms moved, what is next)
Records the twelve arms moved in wip-u-cmd2 (28 with the earlier 16), the
two host traits added, and the clusters whose text is identical on all
three routers but still per daemon (rules and padding, animation, lock/save/
load, overrides and work-area offsets, queries) as the next candidates.
Docs only; the list of identical arms comes from comparing the three routers
at wip-cand8.
2026-11-05 15:03:27 -08:00
LGUG2Z 85f8e2af2b docs(core): section 23, the macOS side of the shared router and WindowManagerPlatform
Records, while kfde's gate_message hook and WindowManagerPlatform trait did not exist yet:
macOS gates every message with the same call at the same place as KDE (so the default
gate_message needs no macOS override), the macOS entry points as hooks with their size and
seam note (focus_workspace keeps the pre-existing main-queue dispatch under the lock, no
hook adds one), what was done meanwhile (Minimize, Close, DebugWindow as methods;
push_simple_rule), and that update stays macOS's (D-coord-15).

Verified: documentation only.
2026-11-05 15:03:27 -08:00
LGUG2Z f53060833f docs: macos-hand-check-plan.md, one prioritised runbook for the Mac pass
macos-handcheck.md grew by appending sections from several authors (A-H, the
review checks H1-H12, deep-dedup rows, bar clicks, settings rows), so the owner
had to merge them by hand. The new runbook orders every item by what could
make the daemon unusable first: prerequisites, startup and the command path
(shared transport, shared SocketMessage, lock order), hiding and restoring
(shared Container/Workspace/Monitor, HideSpot), the window registry and leaks,
the pointer preamble, settings reload, the rest of the walk-through, the bar,
then the known issues that are expected to misbehave. Each item has steps, the
expected result, how to stop or roll back, the revision that introduced it, a
mark where a second display, trackpad or cables are needed, and a time
estimate per block (about 5 hours in all).

It opens with the list of commands that must not be run on a Mac that has a
live komorebi (stop, start, quickstart, autostart, pkill, state-changing
komorebic commands, SIGSTOP on pids not just started), with the reasons read
from the code: a second daemon exits when a process named komorebi exists, and
a daemon deletes the socket in the user data directory on exit. The original
document is kept as the source.

Commands were checked against the checked-in macOS docs/cli page list; nothing
was run on a Mac. Not built.
2026-11-05 15:03:27 -08:00
LGUG2Z 87f34317d0 style(kde): format the two KDE manifests with taplo
Pure formatting, no other change: taplo fmt (default configuration) of
komorebi-for-kde/komorebi/Cargo.toml and komorebi-for-kde/komorebic/Cargo.toml,
the two files the kfde toml-fmt check reported. The earlier taplo sweep covered
the Windows and macOS sources only.

Verified: taplo fmt --check over the check's file set (the root Cargo.toml,
every .toml of komorebi-for-kde and of the nine to eleven root crates in
komorebi-for-kde/nix/root-crates.json) passes, it failed on exactly these two.
These two manifests change the KDE derivations (deps included, once); the
Windows and macOS ones do not read them.
2026-11-05 15:03:27 -08:00
LGUG2Z 491707469b refactor(windows): Windows router arms call the shared window, named-workspace and toggle commands
The arms MoveWindow, FocusWindow, CycleFocusWindow, PreselectDirection,
CancelPreselect, PromoteWindow, FocusNamedWorkspace,
MoveContainerToNamedWorkspace, SendContainerToNamedWorkspace,
ToggleWindowContainerBehaviour, ToggleCrossMonitorMoveBehaviour and
ToggleMonocleFocusBehaviour are one call each into komorebi_core::command
(12 arms; the 16 of the earlier batch are already there). The Windows
WindowManager implements WindowCommandHost (thin forwards to its own
direction functions, and Workspace::update) and BehaviourCommandHost (its
three settings). The arm text was identical on all three daemons, so the
same functions are called in the same order. Two small differences: a
missing workspace is reported as "there is no workspace" by the shared
code, and the named lookup is a shared function instead of
WindowManager::monitor_workspace_index_by_name (which stays for its other
callers).

BEHAVIOUR (expected none; marked because arms moved): Windows e2e commands, workspaces, focus, stacking and monocle scenarios (the gated functions are called as before).
Verified: cargo clippy -p komorebi-windows --all-targets -D warnings passes; tools/format-all --check clean. Windows tests and e2e cannot run on Linux.
2026-11-05 15:03:27 -08:00
LGUG2Z 59c19da785 refactor(mac): Minimize, Close and DebugWindow are methods
BEHAVIOUR (a pure move; type-checked and clippy-clean with the fake CC).

The three inline router arms of process_command.rs become minimize_foreground_window,
close_foreground_window and debug_window(window_id, reply), with the bodies the arms had (the
foreground element through AdhocWindow, the CoreGraphics window list walked for the id); the
arms are the same text as KDE's now. The bodies stay macOS's: there is no way to share
them without a window abstraction that hides the element, which is the registry work
of a later step. This is the part of the owner's item (4) that can be done without
changing behaviour.

Verified: fast-check macOS PASS; fake-CC cargo clippy -p komorebi-macos --all-targets -D
warnings clean; tools/format-all --check --tree mac clean. Not verified: any macOS run.
Verified on the Mini: not yet. Hand check row added.
2026-11-05 15:03:27 -08:00
LGUG2Z 5e553a7da4 docs: MIGRATION-SUMMARY.md, the final state of the consolidation
A maintainer who was not here had no one place that says what the repository
is now, what was shared and how, what was kept per platform on purpose, how it
was verified and what was not, what is still open, and how to go on. The page
gives: the four unified packages and how cfg(target_os) selects the platform;
the three trees; the shared crates (protocol, config with the one rule matcher,
collections, transport, backend, core with Container/Workspace/Monitor/
update_shared/command, settings, bar-core, komorebic-core) and the way each was
moved; what stays per platform (WindowManager, router, events, macOS update,
borders and other subsystems, bar rendering) with links into core-model.md,
seam.md, settings.md, bar-unification.md and unified-binaries.md; the oracles
and the gate results per candidate (Windows e2e, KDE VM, Mac Mini compile,
unit and nix) with the flake summary; what is not verified (macOS never ran as
a daemon, bar runtime under software rendering, the KDE slow tier, candidate 8
gates still running at the time of writing); known issues; the cutover list
(shims, version crates, flakes, workflows, docs, tools) with a CI and release
proposal that is not decided; how to continue; and a table of 26 decisions
rewritten without agent names.

Facts were taken from the progress and decisions logs, the revision list
wip-cand4..wip-cand8 and the docs in docs/dev; no host or personal paths are
included. Not built. Gate results are as recorded, not re-run.
2026-11-05 15:03:27 -08:00
LGUG2Z 161ed77f4d docs(kde): fix the intra-doc links that cargo doc -D warnings rejects
The kfde doc check failed (rustdoc exit 101) on eleven links: Backend::hide,
restore, cursor_pos, set_rect, focus, center_cursor_in, current_workspaces and
window_workspace are not items of the trait Backend that the links resolve to
here, [`Window`] and [`TRANSPARENCY_ALPHA`] are not in scope in their modules,
and the public Workspace alias links to the private WorkspaceScrolling. The
brackets are removed (the names stay as code), and the two link definitions in
desktop.rs. Documentation text only, no code change.

Verified: RUSTDOCFLAGS='-D warnings' cargo doc --locked -p komorebi -p
komorebi-linux -p komorebic -p komorebi-client -p komorebi-hotkeys --no-deps
(the flake's package set) finishes without errors, before it reproduced
exactly these eleven; local stable rustc is 1.99.1, the toolchain of the flake.
2026-11-05 15:03:27 -08:00
LGUG2Z 596271c38b refactor(mac): macOS router arms call the shared window, named-workspace and toggle commands
The arms MoveWindow, FocusWindow, CycleFocusWindow, PreselectDirection,
CancelPreselect, PromoteWindow, FocusNamedWorkspace,
MoveContainerToNamedWorkspace, SendContainerToNamedWorkspace,
ToggleWindowContainerBehaviour, ToggleCrossMonitorMoveBehaviour and
ToggleMonocleFocusBehaviour are one call each into komorebi_core::command
(12 arms; the 16 of the earlier batch are already there). The macOS
WindowManager implements WindowCommandHost (thin forwards to its own
direction functions, and Workspace::update) and BehaviourCommandHost (its
three settings). The arm text was identical on all three daemons, so the
same functions are called in the same order. Two small differences: a
missing workspace is reported as "there is no workspace" by the shared
code, and the named lookup is a shared function instead of
WindowManager::monitor_workspace_index_by_name (which stays for its other
callers).

BEHAVIOUR (expected none; marked because arms moved): macOS hand check: focus, move and promote by direction, named workspaces, the three toggles.
Verified: fake-CC cargo clippy --all-targets -D warnings for the four macOS packages passes; tools/format-all --check clean. Nothing ran on a Mac.
2026-11-05 15:03:27 -08:00
LGUG2Z 4811a056e9 refactor(kde): Minimize, Close and DebugWindow are methods with the macOS names
The inline router arms become minimize_foreground_window, close_foreground_window and
debug_window(window_id, reply) with the bodies they had, so that the three arms are the
same text as macOS's (the bodies differ by the platform: the backend and Window::from here,
the foreground element and the Accessibility window list there). Pure move, no behaviour
change.

Verified: KDE cargo check --all-targets and lib tests PASS; tools/format-all --apply
--tree kde ran.
2026-11-05 15:03:27 -08:00
LGUG2Z 2ba338347c style(mac): format with the project's rustfmt settings (tools/format-all --apply --tree mac)
Pure formatting by the same nightly rustfmt invocation the nix fmt check uses (tools/format-all, edition 2024, the tree's rustfmt.toml). No code change. Applied last on the candidate because it touches many files other agents were editing. Verified: tools/format-all --check --tree mac passes afterwards; light gates (fast-check) after all three.
2026-11-05 15:03:27 -08:00
LGUG2Z 1fe07c6736 fix(nix): pass --config before check in the KDE deny check
The KDE deny check failed with `error: unexpected argument '--config'
found`: the flake wrote `cargo deny ... check --config <deny.toml> bans
licenses sources`, and in cargo-deny 0.20.2 (the one of the pinned
kfde-nixpkgs) --config is an option of `cargo deny` itself, not of
`check`. It now goes into cargoDenyExtraArgs, before `check`.

Verified: cargo deny 0.20.2 from nixpkgs f05535a0 (the flake's pin) with the
flake's --exclude list, `--config komorebi-for-kde/deny.toml check bans
licenses sources`: bans ok, licenses ok, sources ok (the clarify entries
and the komorebi-bar-core exclusion of the previous fix are enough, also for
komorebi-daemon, komorebi-settings and the wgpu stack). Not built in nix.
2026-11-05 15:03:27 -08:00
LGUG2Z 4c5396a435 refactor(kde): KDE router arms call the shared window, named-workspace and toggle commands
The arms MoveWindow, FocusWindow, CycleFocusWindow, PreselectDirection,
CancelPreselect, PromoteWindow, FocusNamedWorkspace,
MoveContainerToNamedWorkspace, SendContainerToNamedWorkspace,
ToggleWindowContainerBehaviour, ToggleCrossMonitorMoveBehaviour and
ToggleMonocleFocusBehaviour are one call each into komorebi_core::command
(12 arms; the 16 of the earlier batch are already there). The KDE
WindowManager implements WindowCommandHost (thin forwards to its own
direction functions, and Workspace::update) and BehaviourCommandHost (its
three settings). The arm text was identical on all three daemons, so the
same functions are called in the same order. Two small differences: a
missing workspace is reported as "there is no workspace" by the shared
code, and the named lookup is a shared function instead of
WindowManager::monitor_workspace_index_by_name (which stays for its other
callers).

BEHAVIOUR (expected none; marked because arms moved): KDE VM commands and focus/move scenarios.
Verified: cargo clippy -p komorebi-linux --all-targets -D warnings passes; cargo test -p komorebi-linux 670 passed, 0 failed; tools/format-all --check clean.
2026-11-05 15:03:27 -08:00
LGUG2Z fe65256659 refactor(kde): the ignore and manage rules use the shared push_simple_rule
The KDE copy of push_simple_rule and its test moved to komorebi_config::matching (the
config revision of this stack); the daemon imports it. No behaviour change: the function is
the same text.

Verified: KDE cargo check --all-targets and lib tests (fast-check) PASS; native
cargo test -p komorebi-config has the moved test; tools/format-all --apply --tree kde ran.
2026-11-05 15:03:27 -08:00
LGUG2Z 6e9800751b style(kde): format with the project's rustfmt settings (tools/format-all --apply --tree kde)
Pure formatting by the same nightly rustfmt invocation the nix fmt check uses (tools/format-all, edition 2024, the tree's rustfmt.toml). No code change. Applied last on the candidate because it touches many files other agents were editing. Verified: tools/format-all --check --tree kde passes afterwards; light gates (fast-check) after all three.
2026-11-05 15:03:27 -08:00