Files
Panama/tests/quickshell/adwaita-accent-contract
T
Gabriel Brown e1faaf7a76 Drop the extension, and give the test suite a front door
Phase 6, the last of the fresh-install spec.

159 scripts lose their .sh: 110 contracts, 47 Vicinae commands, 2 compositor
contracts. A shebang and the executable bit already select the interpreter. The
extension only ever added something that had to stay in sync, and the rename
proved the point twice over in the space of an hour.

The spec's stated risk was Vicinae's script discovery. One script was renamed and
reloaded on its own before the other 46 followed; it came back as
scripts:panama.capture and all 47 resolve. What the probe turned up instead is
that the extension was never only a filename: Vicinae's command IDs embed it, so
every ID changed. Nothing in this repository refers to them, so nothing breaks.
The only trace is Vicinae's metadata.json, whose visited map had two Panama
entries that are now orphaned -- two commands lost their usage ranking and will
earn it back. Worth knowing before anyone renames these again on a machine that
has a keybind pointing at one.

Rewriting the references by exact filename missed two things it structurally
could not see: a name built from a variable, settings-$page.sh, and a glob,
-name '*.sh'. Both were in the contract that counts the generated commands, which
promptly reported 47 expected and 0 found. The mechanical part of a rename is the
part that looks finished.

The three subcommands. panama doctor fronts a health check that already existed
and already ran at the end of every install but could not be reached from a
terminal. panama upgrade re-runs the installer from anywhere. panama test runs
the suite, which had no entry point at all -- 121 files that were the main safety
net in this repository and were invisible in it.

Writing that runner found three tests nothing was running.
calendar_agenda_bridge_test, home_assistant_bridge_test and kdeconnect_bridge_test
are unittest suites without the executable bit, so no contract invoked them and
the first draft of the runner skipped them silently. All three pass, and have
passed unobserved for weeks. The runner collects *_test.py as well now, because a
runner with a blind spot is worse than no runner for the same reason a dependency
checker with one is: it reports PASS.

Six worktrees pruned. Each was re-checked rather than trusted to the spec's list,
and two needed it: panama-commands is not on feat/panama-commands but on
feat/gnome-tweaks-parity, and fix/panama-displays-review reads [ahead 3] -- ahead
of its remote, not of main, with every commit patch-equivalent to landed work.
roadmap-completion stays; it has five commits that are genuinely unlanded. The
branches are left alone: pruning a worktree costs nothing, deleting a branch is a
decision.

121 contracts pass.

Claude-Session: https://claude.ai/code/session_01NvgBuSWB5sE43yWmg21ozj
2026-08-20 21:55:55 -04:00

116 lines
5.4 KiB
Bash
Executable File

#!/usr/bin/env bash
# Choosing an accent must recolor libadwaita applications too.
#
# Files, Papers and Loupe read their accent from the Settings portal, so an
# accent that never reaches GNOME's accent-color key leaves half the desktop in
# GNOME blue while the other half wears the chosen color. That is invisible from
# inside Panama's own surfaces, which look correct either way.
#
# Three things have to line up, and none of them share a source:
# - config/Theme.qml carries the accent table with its `gnome` member
# - scripts/panama-theme-apps maps the same names in shell
# - the portal routes Settings to a backend that can serve accent-color
#
# Read-only apart from a gsettings *read*; it never sets an accent.
set -uo pipefail
repo_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
theme="$repo_dir/config/dot/quickshell/config/Theme.qml"
script="$repo_dir/config/dot/quickshell/scripts/panama-theme-apps"
portals="$repo_dir/config/dot/xdg-desktop-portal/hyprland-portals.conf"
fail() {
printf 'adwaita accent contract: %s\n' "$1" >&2
exit 1
}
for path in "$theme" "$script" "$portals"; do
[[ -r "$path" ]] || fail "missing $path"
done
# ── The accent table ─────────────────────────────────────────────────────────
mapping="$(python3 - "$theme" <<'PYTHON'
import re, sys
source = open(sys.argv[1]).read()
table = re.search(r"readonly property var accents: \(\{(.*?)\n \}\)", source, re.S)
if not table:
raise SystemExit("accents table not found")
for line in table.group(1).splitlines():
name = re.search(r'"([a-z]+)":', line)
if not name:
continue
member = re.search(r'gnome: "([a-z]+)"', line)
print(name.group(1) + "\t" + (member.group(1) if member else ""))
PYTHON
)" || fail 'could not read the accent table from Theme.qml'
[[ -n "$mapping" ]] || fail 'the accent table is empty'
while IFS=$'\t' read -r name member; do
[[ -n "$name" ]] || continue
[[ -n "$member" ]] \
|| fail "the \"$name\" accent has no gnome member, so libadwaita applications keep the previous accent when it is chosen"
done <<<"$mapping"
# ── Every member must exist in GNOME's enum ──────────────────────────────────
# The enum is read from the system rather than hardcoded here: a hardcoded copy
# would still pass on a machine whose GNOME dropped or renamed a member, which
# is the case where gsettings silently refuses the write.
if command -v gsettings >/dev/null 2>&1; then
enum="$(gsettings range org.gnome.desktop.interface accent-color 2>/dev/null | tail -n +2 | tr -d "'")"
if [[ -n "$enum" ]]; then
while IFS=$'\t' read -r name member; do
[[ -n "$member" ]] || continue
grep -qx "$member" <<<"$enum" \
|| fail "the \"$name\" accent maps to \"$member\", which GNOME's accent-color enum does not publish"
done <<<"$mapping"
fi
fi
# ── The shell helper must agree with the table ───────────────────────────────
# panama-theme-apps carries its own copy of this mapping because a shell script
# cannot read a QML object. A copy that drifts is exactly how an accent ends up
# correct in Panama's own surfaces and wrong everywhere else.
shell_member() {
local name="$1" body
body="$(sed -n '/^gnome_accent() {/,/^}/p' "$script")"
[[ -n "$body" ]] || fail 'gnome_accent() is missing from panama-theme-apps'
local line
line="$(grep -E "^\s+${name}\)" <<<"$body" | head -1)"
if [[ -z "$line" ]]; then
# Not listed means it falls through to the default branch.
line="$(grep -E '^\s+\*\)' <<<"$body" | head -1)"
fi
sed -E "s/.*printf '([a-z]+)'.*/\1/" <<<"$line"
}
while IFS=$'\t' read -r name member; do
[[ -n "$name" ]] || continue
actual="$(shell_member "$name")"
[[ "$actual" == "$member" ]] \
|| fail "Theme.qml maps \"$name\" to \"$member\" but panama-theme-apps maps it to \"$actual\""
done <<<"$mapping"
# The helper also validates the accent name it is handed; an accent the table
# knows but the helper rejects silently degrades to blue.
accepted="$(grep -oE '^\s+blue\|[a-z|]+\)' "$script" | head -1 | tr -d ' )' )"
while IFS=$'\t' read -r name member; do
[[ -n "$name" ]] || continue
grep -qE "(^|\|)$name(\||$)" <<<"$accepted" \
|| fail "panama-theme-apps does not accept the \"$name\" accent, so choosing it falls back to blue"
done <<<"$mapping"
# ── The portal has to be able to serve it ────────────────────────────────────
# xdg-desktop-portal-gtk cannot serve accent-color, so routing Settings to gtk
# alone makes every mapping above inert -- correct on paper, invisible in use.
settings_line="$(grep -E '^org\.freedesktop\.impl\.portal\.Settings=' "$portals")" \
|| fail 'the portal config does not route Settings at all, so accent-color has no backend'
[[ "$settings_line" == *gnome* ]] \
|| fail "Settings is routed to \"${settings_line#*=}\", and only the gnome backend serves accent-color"
[[ "${settings_line#*=}" == gnome* ]] \
|| fail "the gnome backend must come first in \"${settings_line#*=}\" or gtk answers Settings and accent-color is never published"
printf 'adwaita accent contract: PASS (%d accents mapped)\n' "$(grep -c . <<<"$mapping")"