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

tests/quickshell/settings-jump-contract

@@ -0,0 +1,50 @@
+#!/usr/bin/env bash
+
+# Every "open the settings for this" jump must land somewhere real.
+#
+# ShellState.openSettings() validates its argument against an allow-list and
+# falls back to Home for anything unknown. That fallback is sensible and it is
+# also completely silent: a typo, or a page renamed later, turns a right-click
+# into "opens Settings on the wrong page" with nothing logged and no error.
+#
+# Before this, exactly four places in the entire shell could reach Settings, so
+# the risk was small. The bar now offers a jump on every widget, which makes the
+# fallback worth guarding.
+
+set -uo pipefail
+
+repo_dir="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
+shell_state="$repo_dir/config/dot/quickshell/services/ShellState.qml"
+modules="$repo_dir/config/dot/quickshell/modules"
+
+fail() {
+    printf 'settings jump contract: %s\n' "$1" >&2
+    exit 1
+}
+
+allowed_line="$(grep -m1 'const allowed = \[' "$shell_state")" \
+    || fail 'could not find the allow-list in ShellState'
+
+jumps="$(grep -rhoE 'openSettings\("[a-z-]+"\)' "$modules" 2>/dev/null \
+    | sed 's/openSettings("//; s/")//' | sort -u)"
+[[ -n "$jumps" ]] || fail 'found no settings jumps at all -- this contract is not reading the modules correctly'
+
+count=0
+while read -r page; do
+    [[ -n "$page" ]] || continue
+    grep -qF "\"$page\"" <<<"$allowed_line" \
+        || fail "a jump opens \"$page\", which ShellState does not allow -- openSettings falls back to Home silently, so this reads as a right-click that goes to the wrong page"
+    count=$((count + 1))
+done <<<"$jumps"
+
+# The bar is where a person looks first, and Pill has offered a right-click
+# signal all along that nothing connected -- so the gesture did nothing on every
+# widget in the bar. Anything built on Pill that can be configured should say so.
+for widget in Clock WeatherWidget VitalsWidget StatusCluster MediaWidget; do
+    file="$modules/bar/$widget.qml"
+    [[ -r "$file" ]] || continue
+    grep -q 'onSecondaryActivated' "$file" \
+        || fail "$widget has no right-click jump; Pill routes right-click to secondaryActivated, so leaving it unconnected makes the gesture silently inert"
+done
+
+printf 'settings jump contract: PASS (%d distinct destinations)\n' "$count"