Files

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

8.1 KiB

Raw Blame History

Panama Settings Completion Codex Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: Complete Codex's portion of Panama Settings with default-application and autostart management, shared page scaffolds, and real controls for every remaining hardcoded shell behavior value.

Architecture: DefaultApps.qml is the typed system boundary for freedesktop default handlers and user autostart entries; ApplicationsPage.qml binds reactively to DesktopEntries.applications.values and never snapshots the asynchronous model. Existing pages adopt SettingsPage; schema-bound values use ChoiceRow, SliderRow, and ToggleRow, while specialized controls and genuinely read-only facts remain specialized or use TextRow.

Tech Stack: Quickshell 0.3 QML, QtQuick, xdg-settings, xdg-mime, freedesktop .desktop files, Bash/Python contract tests, Hyprland.

Spec: docs/superpowers/specs/2026-08-17-panama-cohesion-design.md

Status: Implemented and independently reviewed on 2026-08-18. The combined verification gate is recorded in the integrating commit history.

Global Constraints

Claude owns and must be the only editor of PreferenceSchema.qml, SettingsSidebar.qml, SettingsShell.qml, qmldir, ShellState.qml, SystemSettings.qml, AppearancePage.qml, DesktopPage.qml, ShortcutsPage.qml, and config/dot/hypr/*.
Never use hyprctl keyword; every hl.bind requires a description.
Use DesktopEntries.applications.values in reactive bindings. Do not call byId() or heuristicLookup() in a one-time initialization path.
Use SettingRow.activatable for whole-row clicks. Nested Repeaters address outer models through explicit ids, never parent.modelData.
Only these verified GNOME panels may be opened: applications, background, bluetooth, color, display, keyboard, mouse, multitasking, network, notifications, online-accounts, power, printers, privacy, search, sharing, sound, system, universal-access, wacom, wellbeing, wifi, wwan.
No mock phase, new visual direction, color literals, or idle animation. Preserve page copy and behavior unless a dead read-only row is replaced by a real control.
Automated tests isolate XDG config/state, do not change live defaults or autostart entries, do not launch applications, and do not invoke Home actions.

Task 1: Applications, default handlers, and user autostart

Files:

Create: config/dot/quickshell/services/DefaultApps.qml
Create: config/dot/quickshell/modules/settings/ApplicationsPage.qml
Create only if needed for a safe parser/writer boundary: config/dot/quickshell/scripts/panama-default-apps
Create: tests/quickshell/default-apps-contract
Create: tests/quickshell/applications-settings-contract

Interfaces:

Consumes: DesktopEntries.applications.values, SettingsPage, SettingsCard, SettingRow.activatable, ActionRow, TextRow, and Claude-owned routing for page id applications.
Produces: a singleton DefaultApps with reactive handlers, autostartEntries, luaAutostartEntries, busy, lastError, refresh(), setDefault(role, desktopId), and setAutostart(desktopId, enabled).
Step 1: Write failing helper/service and page contracts

Cover seven roles: browser (xdg-settings default-web-browser), mail (x-scheme-handler/mailto), files (inode/directory), terminal (x-scheme-handler/terminal), music (audio/mpeg), images (image/png), and video (video/mp4). Use temporary XDG directories and fake xdg-settings/xdg-mime binaries; assert setters pass separate arguments and reject unknown roles or desktop ids. Fixture user autostart entries must expose id/name/enabled and toggle with standard Hidden= semantics; hl.exec_cmd entries parsed from config/dot/hypr/autostart.lua are read-only and identify their source.

The page contract must require DesktopEntries.applications.values, page id/object name, all seven role labels, user and compositor autostart sections, SettingRow.activatable, and must reject Component.onCompleted snapshots plus byId()/heuristicLookup().

Step 2: Run focused contracts to verify RED

tests/quickshell/default-apps-contract
tests/quickshell/applications-settings-contract

Expected: fail because the service/page and behavior do not exist.

Step 3: Implement the minimal typed boundary and page

All process commands use argument arrays. Validate roles against a fixed map and desktop ids against the reactive applications model or a strict freedesktop id pattern plus discovered entries. The page filters role choices from category/generic-name data, sorts by display name, keeps the current handler visible even when category metadata is sparse, and shows calm inline errors. Toggling applies only to files under $XDG_CONFIG_HOME/autostart; Lua entries remain read-only with explanatory copy.

Step 4: Verify and commit

tests/quickshell/default-apps-contract
tests/quickshell/applications-settings-contract
tests/quickshell/settings-pages-contract

Commit subject: Add application and autostart settings.

Task 2: Remaining page scaffolds and hardcoded behavior controls

Files:

Modify: config/dot/quickshell/config/Settings.qml
Modify: config/dot/quickshell/modules/settings/HomePage.qml
Modify: config/dot/quickshell/modules/settings/DisplaysPage.qml
Modify: config/dot/quickshell/modules/settings/ConnectivityPage.qml
Modify: config/dot/quickshell/modules/settings/SoundPage.qml
Modify: config/dot/quickshell/modules/settings/NotificationsPage.qml
Modify: config/dot/quickshell/modules/settings/ScreenIntelligencePage.qml
Modify: config/dot/quickshell/modules/settings/ServicesPage.qml
Modify: config/dot/quickshell/modules/settings/AboutPage.qml
Modify: tests/quickshell/settings-pages-contract
Create: tests/quickshell/settings-hardcoded-values-contract

Interfaces:

Consumes: Claude-owned schema keys temperatureUnit, weatherRefreshMinutes, vitalsIntervalMs, notificationTimeoutMs, notificationTimeoutCriticalMs, notificationHistoryLimit, maxVisibleToasts, screenshotDir, recordingDir, and recorderArgs; shared Settings rows; existing services and system handoffs.
Produces: the same public Settings.qml properties, now each reading DesktopPreferences.get("key"), and controls routed to weather/vitals, notifications, and capture pages.
Step 1: Write failing contracts

Require all ten Settings.qml properties to use DesktopPreferences.get() exactly. Require every listed page root to be SettingsPage and reject its copied root Flickable scaffold. Require weather/vitals controls on HomePage, notification controls on NotificationsPage, and capture directory/encoder controls on ScreenIntelligencePage; every schema-bound control uses a shared row and writes only through SystemSettings.commitPreference via that row.

Step 2: Run contracts to verify RED

tests/quickshell/settings-hardcoded-values-contract
tests/quickshell/settings-pages-contract

Expected: fail on hardcoded properties and copied page scaffolds.

Step 3: Implement controls and migrate scaffolds

Use ChoiceRow for temperatureUnit, screenshotDir, recordingDir, and recorderArgs; use SliderRow for numeric refresh, timeout, history, and toast limits. Give notificationTimeoutCriticalMs zeroLabel: "Never". Preserve all specialized buttons, service status rows, display diagnostics, permission/privacy explanations, and GNOME handoff actions. Convert genuinely read-only rows to TextRow; delete only rows superseded by working controls.

Step 4: Run focused and full suite, then commit

tests/quickshell/settings-hardcoded-values-contract
tests/quickshell/settings-pages-contract
tests/quickshell/settings-preferences-contract
tests/quickshell/settings-search-contract

Then run every tests/quickshell/*, every tests/hypr/*, and all three tests/quickshell/*_test.py files sequentially.

Commit subject: Complete Panama settings controls.

8.1 KiB Raw Blame History

Panama Settings Completion Codex Implementation Plan

Global Constraints

Task 1: Applications, default handlers, and user autostart

Task 2: Remaining page scaffolds and hardcoded behavior controls

8.1 KiB

Raw Blame History