gib/Panama
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ba4e5e6677fc925b206d62684d5aac7d58939876
Panama/docs/superpowers/plans/2026-08-17-contextual-signal-glass.md
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

4.4 KiB
Raw Blame History

Contextual Signal Glass 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: Build a curated event broker, quiet shared Signal Glass host, and persistent privacy/activity indicators.

Architecture: Producers publish structured events to one bounded broker. A single per-screen host renders transient events ahead of existing focus controls, while persistent privacy state renders independently in the bar.

Tech Stack: Quickshell QML, QtQuick, Quickshell PipeWire/Bluetooth/Io APIs, Hyprland, Bash contract tests

Spec: docs/superpowers/specs/2026-08-17-contextual-signal-glass-design.md

Global Constraints

  • Initial discovery must not emit user-visible events.
  • DND suppresses ambient events but never persistent privacy state.
  • No idle visual animation or unbounded queue/process loop.
  • Existing Focus behavior and tests must remain compatible.

Task 1: Status event broker

Files:

  • Create: config/dot/quickshell/services/StatusEvents.qml
  • Modify: config/dot/quickshell/shell.qml
  • Test: tests/quickshell/status-events-contract

Interfaces:

  • Produces: publish(event: var), dismiss(): void, invoke(): void, activeEvent, active, and IPC diagnostics.

  • Write an IPC contract that publishes ambient and critical fixtures, verifies replacement and DND filtering, and dismisses cleanly.

  • Run the contract and verify it fails because the IPC target is absent.

  • Implement broker normalization, priority, four-entry queue, stable-key replacement, expiry, and action routing.

  • Wire a diagnostics-only IPC target and run the contract to green.

Task 2: Shared Signal Glass host

Files:

  • Create: config/dot/quickshell/modules/signals/SignalGlass.qml
  • Create: config/dot/quickshell/modules/signals/EventCard.qml
  • Create: config/dot/quickshell/modules/signals/FocusCard.qml
  • Create: config/dot/quickshell/modules/signals/qmldir
  • Modify: config/dot/quickshell/shell.qml
  • Retire: config/dot/quickshell/modules/focus/FocusCapsule.qml

Interfaces:

  • Consumes: StatusEvents.activeEvent, FocusSession.active, and FocusSession.capsuleVisible.

  • Produces: one qs-signal-glass layer surface per monitor.

  • Add a static source contract proving only one Signal Glass host is instantiated.

  • Extract the existing focus presentation without changing its actions.

  • Implement the compact event presentation and event-first/focus-second arbitration.

  • Verify focus contracts and QML construction.

Task 3: Event producers and persistent activity

Files:

  • Create: config/dot/quickshell/services/PrivacyState.qml
  • Create: config/dot/quickshell/services/DeviceEvents.qml
  • Modify: config/dot/quickshell/services/Capture.qml
  • Modify: config/dot/quickshell/services/NightLight.qml
  • Modify: config/dot/quickshell/services/FocusSession.qml
  • Test: tests/quickshell/activity-state-contract

Interfaces:

  • Produces: PrivacyState.microphoneActive, cameraActive, screenSharingActive, recordingActive, activeKinds, and transition events.

  • Write contracts for capture events and independent persistent-state reporting.

  • Instrument Panama-owned capture, Night Light, and focus completion transitions.

  • Add initialized transition monitoring for output, Bluetooth, KDE Connect, and privacy activity.

  • Run the contracts and verify missing optional integrations fail quietly.

Task 4: Bar indicator and detail panel

Files:

  • Create: config/dot/quickshell/modules/bar/ActivityIndicator.qml
  • Create: config/dot/quickshell/modules/bar/ActivityPanel.qml
  • Modify: config/dot/quickshell/modules/bar/Bar.qml
  • Modify: config/dot/quickshell/services/ShellState.qml

Interfaces:

  • Consumes: PrivacyState booleans and Capture.stopRecording().

  • Add the indicator beside Focus with semantic icon/color selection.

  • Add a compact details popover and safe Stop action for Panama recording.

  • Verify overlay exclusivity, click targets, and all active-state combinations.

Task 5: System verification

  • Run all Quickshell contract tests.
  • Run QML/runtime diagnostics and inspect logs for warnings.
  • Capture ambient, privacy, recording, and focus-restoration states.
  • Restart the live Quickshell instance and repeat the smoke contract.
Reference in New Issue View Git Blame Copy Permalink