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

docs/superpowers/plans/2026-08-17-panama-cohesion.md

@@ -34,7 +34,7 @@ correctness bug in shipped behavior and does not depend on any of the
 architecture below.
 
 **Files:** Modify `config/dot/quickshell/services/SystemSettings.qml`;
-Test `tests/quickshell/settings-hyprland-write-contract.sh`
+Test `tests/quickshell/settings-hyprland-write-contract`
 
 - [x] Write a contract that sets a display policy through `SystemSettings`, then
       asserts via `hyprctl getoption` that the compositor value actually changed —
@@ -58,9 +58,9 @@ holds the group/key/option path and allow-list per option, so the UI never names
 an option or supplies an unchecked value. Policy is applied as one batch, so the
 shell cannot come up half-configured.
 
-New: `tests/quickshell/settings-hyprland-write-contract.sh` — flips each policy
+New: `tests/quickshell/settings-hyprland-write-contract` — flips each policy
 to a value it does not hold and reads it back, so a no-op write cannot pass.
-The pre-existing `settings-system-contract.sh` re-applied the values already in
+The pre-existing `settings-system-contract` re-applied the values already in
 place, which is why it passed throughout the outage.
 
 ---
@@ -70,7 +70,7 @@ place, which is why it passed throughout the outage.
 **Files:** Create `config/dot/quickshell/config/PreferenceSchema.qml`;
 Modify `config/dot/quickshell/config/DesktopPreferences.qml`,
 `config/dot/quickshell/config/Settings.qml`;
-Test `tests/quickshell/preference-schema-contract.sh`
+Test `tests/quickshell/preference-schema-contract`
 
 Schema entry shape:
 
@@ -93,8 +93,8 @@ Schema entry shape:
       file from `Quickshell.stateDir` on first run if present.
 - [x] Keep `Settings.qml` as the stable public read surface; existing consumers
       must not change.
-- [x] Run the new contract plus `settings-preferences-contract.sh` and
-      `settings-pages-contract.sh` to green.
+- [x] Run the new contract plus `settings-preferences-contract` and
+      `settings-pages-contract` to green.
 
 **Exit criteria:** adding a setting is one schema line; reset is complete by
 construction; the store lives at a stable, user-visible path.
@@ -116,7 +116,7 @@ absent, and never deletes the original. Verified live: the running shell adopted
 all 17 values into `~/.config/panama/settings.json` with the legacy files intact.
 
 New: `config/PreferenceSchema.qml`, `preference-schema-harness.qml`,
-`tests/quickshell/preference-schema-contract.sh`. Full suite green — 6 settings
+`tests/quickshell/preference-schema-contract`. Full suite green — 6 settings
 contracts, 22 other Quickshell contracts, 3 Python bridge tests.
 
 ---
@@ -125,7 +125,7 @@ contracts, 22 other Quickshell contracts, 3 Python bridge tests.
 
 **Files:** Create `config/dot/hypr/prefs.lua`;
 Modify `config/dot/hypr/hyprland.lua`, `looks.lua`, `input.lua`, `monitors.lua`;
-Test `tests/hypr/prefs-fallback-contract.sh`
+Test `tests/hypr/prefs-fallback-contract`
 
 - [x] Write a contract that verifies `Hyprland --verify-config` passes with the
       file absent, empty, truncated mid-object, and containing wrong-typed values —
@@ -228,7 +228,7 @@ Four things found by building it:
   what getoption answers with, not what the setting means, and getting it wrong
   does not fail loudly — it makes every write to that key look rejected. The user
   saw "Hyprland did not apply Hide pointer after" for a change that worked.
-  `tests/quickshell/schema-hypr-shape-contract.sh` now asks the compositor for
+  `tests/quickshell/schema-hypr-shape-contract` now asks the compositor for
   the real shape of all 23 mapped options.
 * The Settings window is a normal tiled window, so `implicitWidth: 1120` is only
   a hint and rows must survive ~400px. `SliderRow` stacks its control under the
@@ -244,7 +244,7 @@ Four things found by building it:
 ## Stage 4 — Shortcuts from the compositor
 
 **Files:** Create `services/Keybinds.qml`; Modify `modules/settings/ShortcutsPage.qml`,
-`config/dot/hypr/keybinds.lua`; Test `tests/quickshell/keybinds-contract.sh`
+`config/dot/hypr/keybinds.lua`; Test `tests/quickshell/keybinds-contract`
 
 - [x] Write a contract asserting the page's bind count matches `hyprctl binds -j`
       exactly, so it can never drift again.
@@ -266,7 +266,7 @@ Grouping is derived from each bind's own description rather than a table here, s
 adding a bind puts it in the right section automatically. Hyprland reports
 Lua-defined binds with dispatcher `__lua` and a bytecode offset as the argument,
 so a bind without a description has nothing readable beside its chord; the
-service drops those, and `tests/quickshell/keybinds-contract.sh` fails if any
+service drops those, and `tests/quickshell/keybinds-contract` fails if any
 exist so that dropping can never be silent.
 
 Input settings are on the same page and are now real controls: keyboard repeat,