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

config/dot/quickshell/migrations-harness.qml

@@ -1,5 +1,5 @@
 // Exercises Migrations.applyWith against fixture steps and prints a verdict per
-// case. Run by tests/quickshell/migrations-contract.sh.
+// case. Run by tests/quickshell/migrations-contract.
 //
 // Fixture steps rather than the real list: the real one is empty until the
 // first breaking schema change, and a mechanism that has never been run against

config/dot/quickshell/modules/settings/README.md

@@ -91,7 +91,7 @@ layout.
 
 Mirrors must remain the same schema-backed control, never a second preference
 or a copied default. Additions to this table require a concrete discoverability
-reason and an update to `tests/quickshell/settings-ownership-contract.sh`.
+reason and an update to `tests/quickshell/settings-ownership-contract`.
 
 Window border color follows the same ownership rule. The inactive border is a
 **scheme-relative role** owned by `ColorScheme.qml`: it changes only to retain
@@ -127,7 +127,7 @@ store. A row never needs to know which kind it holds.
 the value in a different JSON field per type — `int`, `bool`, `float`, `str`,
 and `css` for gaps (a four-value box). Declaring the wrong one does not fail
 loudly: it makes every write to that key look *rejected*, and the user sees an
-error for a change that worked. `tests/quickshell/schema-hypr-shape-contract.sh`
+error for a change that worked. `tests/quickshell/schema-hypr-shape-contract`
 asks the compositor for the real shape of every mapped option.
 
 **Never trust an exit code from `hyprctl`.** `keyword` refuses to work on a

config/dot/quickshell/scripts/panama-settings-commands

@@ -150,12 +150,12 @@ def build() -> dict[Path, str]:
     files: dict[Path, str] = {}
     for page, label in pages():
         words = keywords_for(page, routing, schema, extras)
-        files[OUTPUT_DIR / f"settings-{page}.sh"] = command_for(page, label, words)
+        files[OUTPUT_DIR / f"settings-{page}"] = command_for(page, label, words)
     return files
 
 
 def existing() -> set[Path]:
-    return {path for path in OUTPUT_DIR.glob("settings-*.sh")}
+    return {path for path in OUTPUT_DIR.glob("settings-*")}
 
 
 def main(arguments: list[str]) -> int:

config/dot/quickshell/services/Keybinds.qml

@@ -226,7 +226,7 @@ Singleton {
                 // A bind with no description cannot be presented usefully --
                 // the dispatcher is "__lua" and the argument is a bytecode
                 // offset. Showing the chord alone would be worse than omitting
-                // it, and tests/quickshell/keybinds-contract.sh fails the build
+                // it, and tests/quickshell/keybinds-contract fails the build
                 // if any exist, so this should never be reached in practice.
                 if (description === "")
                     continue;