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
63 lines
2.1 KiB
Bash
Executable File
63 lines
2.1 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
set -euo pipefail
|
|
|
|
fail() {
|
|
printf 'focus-session expiry: %s\n' "$1" >&2
|
|
exit 1
|
|
}
|
|
|
|
cleanup() {
|
|
qs ipc call focus end >/dev/null 2>&1 || true
|
|
}
|
|
trap cleanup EXIT
|
|
|
|
qs ipc call focus end >/dev/null 2>&1 || true
|
|
|
|
# focus start records the caffeine state it found so end() can hand it back, and
|
|
# the assertion below requires caffeine to finish off. Both are only true if
|
|
# caffeine starts off.
|
|
#
|
|
# This test kills and restarts the live shell, so an interrupted run leaves
|
|
# caffeine on with nothing to turn it back off. The next run then records
|
|
# "previously on", faithfully restores it, and fails -- and every run after
|
|
# that fails identically, with the desktop quietly unable to idle or lock the
|
|
# whole time. Refuse to start from that state rather than latching it in.
|
|
if [[ "$(qs ipc call caffeine status 2>/dev/null)" != "false" ]]; then
|
|
fail 'caffeine is on before the session starts -- this test cannot distinguish "restored correctly" from "never released". Turn it off first: qs ipc call caffeine toggle'
|
|
fi
|
|
|
|
qs ipc call focus start >/dev/null
|
|
|
|
state_file=$(find "${XDG_STATE_HOME:-$HOME/.local/state}/quickshell/by-shell" -name focus-session.json -print -quit)
|
|
[[ -n "$state_file" ]] || fail 'persistent state file was not created'
|
|
|
|
expired=$(mktemp "${state_file}.expired.XXXXXX")
|
|
jq '.paused = false | .deadlineMs = 1' "$state_file" >"$expired"
|
|
chmod --reference="$state_file" "$expired"
|
|
mv "$expired" "$state_file"
|
|
|
|
qs kill >/dev/null
|
|
for _ in $(seq 1 50); do
|
|
qs list 2>&1 | rg -q '^Instance ' || break
|
|
sleep 0.1
|
|
done
|
|
if qs list 2>&1 | rg -q '^Instance '; then
|
|
fail 'shell did not stop before restart'
|
|
fi
|
|
quickshell --daemonize >/dev/null
|
|
|
|
status=""
|
|
for _ in $(seq 1 60); do
|
|
status=$(qs ipc call focus status 2>/dev/null || true)
|
|
if jq -e '.active == false' <<<"$status" >/dev/null 2>&1; then
|
|
break
|
|
fi
|
|
sleep 0.2
|
|
done
|
|
|
|
jq -e '.active == false and .caffeine == false and .doNotDisturb == false' <<<"$status" >/dev/null || fail 'expired session was not completed and released'
|
|
|
|
trap - EXIT
|
|
printf 'focus-session expiry: PASS\n'
|