Take the catalogue's composition rules into the node-engine

ADR 0593 §7: the composer with its refusals leaves mesh-sdk, so mesh-sdk
carries no composition rule. The catalogue functions only the
node-engine's composition reaches (Resolve, Resolution's Compose,
Declaration, DataItems, LeftOut, Rules and the rest, the settings,
placeholder and template refusals, the rendering helpers) are copied
with their tests into internal/compose/resolution; a method of a
mesh-sdk shape becomes a function taking it first. The composition
calls its own copies, and the captured catalogue its tests read lives
here now, shared by mesh-compose's tests.

Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
This commit is contained in:
2026-11-02 19:15:55 +01:00
parent be0226b624
commit d68e241724
686 changed files with 35703 additions and 80 deletions
@@ -0,0 +1,38 @@
# picom, the X compositor (module picom, novox/hq ADR 0208). Owned by the mesh: this file is
# replaced at every push. Adopted from the two workstations' file of 2026-10-04 and moved to
# picom's window rules, which supersede opacity-rule, inactive-opacity and inactive-dim.
# The backend and damage tracking are each machine's settings (backend, use-damage; novox/hq research
# 037, issue 345): the right ones depend on the machine's graphics driver. The defaults are what every
# machine ran before: glx, and picom's own default of repainting only what changed. xrender, or
# use-damage false (repaint the whole screen each frame), is what to try on a machine where a window is
# left unpainted or stale.
backend = "${config:backend}";
use-damage = ${config:use-damage};
vsync = true;
fading = true;
fade-in-step = 0.05;
fade-out-step = 0.05;
# Tiled windows hide their shadows and corners, so neither is drawn.
shadow = false;
corner-radius = 0;
blur-method = "none";
# "Focused" is i3's _NET_ACTIVE_WINDOW, not X focus events: under i3 those do not reliably reach
# the toplevel picom tracks, and a terminal then never lifts to its focused opacity.
use-ewmh-active-win = true;
# Window rules are applied in order, and a later match wins. Only terminals are translucent:
# nothing else on screen (browsers, video, games) is touched. A terminal is matched by its class;
# the node's terminal emulator today is xterm (class XTerm). A window's own opacity property is
# used wherever no rule sets one, which is what the window-opacity tool sets.
rules = (
{ match = "window_type = 'tooltip'"; fade = false; opacity = 0.95; },
{ match = "window_type = 'dock' || window_type = 'desktop'"; fade = false; },
{ match = "class_g = 'XTerm' && focused"; opacity = 0.95; },
{ match = "class_g = 'XTerm' && !focused"; opacity = 0.75; },
# A full-screen window is opaque, a terminal included: a video or a game is never see-through.
{ match = "fullscreen"; opacity = 1; }
);
@@ -0,0 +1,90 @@
{
"module": "picom",
"version": "1",
"capabilities": [
"package-manager"
],
"requires": [
"x11-display"
],
"claims": [
{
"name": "node-compositor",
"scope": "node"
}
],
"config": {
"backend": {
"type": "string",
"description": "How picom draws: glx with the graphics card, which has served every machine so far, or xrender on the CPU where glx leaves a window unpainted or stale on the machine's driver (novox/hq research 037, issue 345); xr_glx_hybrid and egl are picom's other backends.",
"enum": [
"glx",
"xrender",
"xr_glx_hybrid",
"egl"
],
"trusted": true,
"default": "glx"
},
"use-damage": {
"type": "boolean",
"description": "Whether picom repaints only what changed (true, picom's own default) or the whole screen each frame (false), which costs work and cures a window left stale or unpainted on some drivers (novox/hq issue 345).",
"trusted": true,
"default": true
}
},
"tools": [
"picom_restart",
"picom_rules",
"picom_window_opacity",
"picom_toggle"
],
"resources": [
{
"id": "package",
"type": "package",
"package": "picom"
},
{
"id": "window-properties",
"type": "package",
"package": "xorg-xprop"
},
{
"id": "configuration-dir",
"type": "directory",
"path": "${machine:account-home}/.config/picom",
"owner": "${machine:account}",
"mode": "0755",
"unknown": "move-out"
},
{
"id": "configuration",
"type": "file",
"path": "${machine:account-home}/.config/picom/picom.conf",
"owner": "${machine:account}",
"mode": "0644",
"template": "files/picom.conf"
}
],
"build": {
"artifacts": [
{
"name": "tools",
"kind": "bundle",
"language": "go",
"system": "arch",
"from": "cmd/picom-tools",
"binary": "picom-tools",
"loads": [
"picom-tools"
]
},
{
"name": "files",
"kind": "archive",
"from": "files"
}
]
}
}