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
85 lines
3.2 KiB
Bash
Executable File
85 lines
3.2 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
set -euo pipefail
|
|
|
|
fail() {
|
|
printf 'calendar agenda contract: %s\n' "$1" >&2
|
|
exit 1
|
|
}
|
|
|
|
cleanup() {
|
|
qs ipc call focus end >/dev/null 2>&1 || true
|
|
qs ipc call activity clear >/dev/null 2>&1 || true
|
|
qs ipc call calendar-agenda reset >/dev/null 2>&1 || true
|
|
qs ipc call calendar-agenda close >/dev/null 2>&1 || true
|
|
}
|
|
trap cleanup EXIT
|
|
|
|
qs ipc show | rg -q '^target calendar-agenda$' \
|
|
|| fail 'calendar IPC target is missing'
|
|
|
|
qs ipc call calendar-agenda fixture daybook >/dev/null
|
|
status="$(qs ipc call calendar-agenda status)"
|
|
jq -e '
|
|
.fixture == true and
|
|
.sourceCount == 3 and
|
|
.eventCount == 5 and
|
|
.selectedDate == "2026-08-17"
|
|
' <<<"$status" >/dev/null || fail 'daybook fixture state is malformed'
|
|
|
|
qs ipc call calendar-agenda select 2026-08-18 >/dev/null
|
|
jq -e '.selectedDate == "2026-08-18" and .selectedEventCount == 1' \
|
|
<<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'date selection did not update events'
|
|
|
|
qs ipc call calendar-agenda open >/dev/null
|
|
jq -e '.open == true and .page == "agenda"' \
|
|
<<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'calendar open did not route to Agenda'
|
|
|
|
qs ipc call notifications open >/dev/null
|
|
jq -e '.open == true and .page == "notifications"' \
|
|
<<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'notification open did not route to Notifications'
|
|
|
|
qs ipc call activity fixture microphone-on >/dev/null
|
|
qs ipc call calendar-agenda page ongoing >/dev/null
|
|
jq -e '.open == true and .page == "ongoing" and .ongoingCount >= 1' \
|
|
<<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'persistent activity did not route to Ongoing'
|
|
|
|
qs ipc call activity fixture all-on >/dev/null
|
|
qs ipc call focus start >/dev/null
|
|
jq -e '.ongoingCount == 5 and .ongoingFits == true' \
|
|
<<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'crowded Ongoing activity does not fit the Daybook'
|
|
|
|
hyprctl layers | rg -q 'namespace: qs-popover-datemenu' \
|
|
|| fail 'Daybook layer did not map'
|
|
rg -q 'implicitWidth: 760' config/dot/quickshell/modules/datemenu/DateMenu.qml \
|
|
|| fail 'Daybook is not the approved width'
|
|
for component in AgendaPane AgendaEvent NotificationSummary; do
|
|
rg -q "${component} 1.0 ${component}.qml" config/dot/quickshell/modules/datemenu/qmldir \
|
|
|| fail "$component is not registered"
|
|
done
|
|
rg -q 'gnome-calendar.*--date.*toISOString' config/dot/quickshell/services/CalendarAgenda.qml \
|
|
|| fail 'GNOME Calendar date handoff is not a complete ISO-8601 timestamp'
|
|
|
|
qs ipc call calendar-agenda fixture upcoming >/dev/null
|
|
jq -e '.capsuleVisible == true and .capsuleText == "12m"' \
|
|
<<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'upcoming capsule window is wrong'
|
|
|
|
qs ipc call calendar-agenda fixture outside-window >/dev/null
|
|
jq -e '.capsuleVisible == false' \
|
|
<<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'capsule appears outside the quiet window'
|
|
|
|
qs ipc call calendar-agenda reset >/dev/null
|
|
jq -e '.fixture == false' <<<"$(qs ipc call calendar-agenda status)" >/dev/null \
|
|
|| fail 'fixture reset did not restore live mode'
|
|
|
|
trap - EXIT
|
|
cleanup
|
|
printf 'calendar agenda contract: PASS\n'
|