Finish now requires every mandatory answer, since a summary without locator, band and category could not be saved. Adds an optional step for antenna and power values that feed the path analysis.
Written-by: Claude Fable 5.2
Describes a first-start assistant for unconfigured operator profiles: what it asks, how it covers multi-operator and multi-station setups, and why it writes preferences.xml before the runtime is built instead of going through the settings draft.
Written-by: Claude Fable 5.2
Written-by: Codex (GPT-6.2 Sol)
Written-by: Gemini 4 Hydrogen (Antigravity)
Written-by: DeepSeek V4 Pro
Apply beacon checkbox changes at runtime and keep the aggregate status chip synchronized.
Improve explicit station-map navigation, spatial filter overlays, overlay legend, selected-path contrast, and the documented map screenshot.
* test: print all threads when a test times out
The rare CI hang in SelectedStationMessageUiVisualRenderingTest blocks on a
monitor in SnapshotStateObserver.observeReads (line 643 is the monitorenter
of observedScopeMapsLock in Compose 1.8.2). The timed-out thread's stack
shows where it waits but not which thread holds the lock. With the thread
dump enabled, JUnit prints every thread to the test's standard output, which
ends up in the XML report of the test-results artifact.
Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y
* test: render every ImageComposeScene on the AWT event thread
The rare CI hang is a lock-order deadlock in Compose Multiplatform 1.8.2,
shown by the thread dump of run 40299943329:
- the test thread renders the scene and holds the FlushCoroutineDispatcher
runLock while LazyListState.scrollToItem measures and wants the
SnapshotStateObserver's observedScopeMapsLock;
- the AWT event thread sends the global snapshot notifications and holds
observedScopeMapsLock in drainChanges while a re-read derived state wakes
the scene's snapshotFlow collector, whose dispatch wants runLock.
The application renders on the event thread, where both monitors are simply
re-entered. The tests now do the same: onEventThread builds, renders and
closes each scene there and rethrows what the block throws.
Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y
Strip HTML tags and XML comments until the text no longer changes, so that
nested input cannot reassemble a tag or comment after a single pass
(js/incomplete-multi-character-sanitization in website/.eleventy.js and
website/scripts/validate-version-info.js).
Limit the GITHUB_TOKEN of the PR compile check and the test version-XML
workflow to read access (actions/missing-workflow-permissions).
Claude-Session: https://claude.ai/code/session_01FJBfPYm6rCH4zD6T7bcC7Y
The kst4contest and kst4contest-git packages built jpackage's launcher
with Arch's openjdk, which links libapplauncher.so against the shared
libstdc++. That build aborts now and then on exit with "pure virtual
method called" in a static destructor (SIGABRT, core dump), the failure
Debian describes for non-static libstdc++ builds. Temurin links
libstdc++ statically, like the CI-built packages.
Both PKGBUILDs now fetch a pinned Temurin 21.0.13+9 through
source_x86_64, so aur-publish.yml's rewrite of the sha256sums= line
leaves it alone, and point the Gradle toolchain at it alone.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Nightly #303 named the hanging test, SelectedStationMessageUiVisual-
RenderingTest at scene.render(), but the short exception format showed
only that line, not the call that blocked below it. The job timeout
cancels the run, and the test reports were kept only on failure().
Failed tests now print their full stack, causes included, and the
reports are uploaded on cancelled() as well.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Nightly #302 and the PR check for #147 hung in :app-desktop:test for
over an hour, and the log named only the task. Thirteen reruns of the
same commit passed, so the hang is rare and still unidentified.
Every test now gets a two-minute JUnit timeout in a separate thread, so
even an uninterruptible hang fails with the test's name and the stack
where it stood. The test jobs are capped at 20 minutes for a hang
outside any test.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The cluster and QSO monitor split its two tables at half the height, fixed:
the Compose port had left the JavaFX SplitPane out until a splitter existed.
SplitterPane exists now, so the monitor uses it and reads and writes the same
profile value the SplitPane did (GUIpnl_directedMSGWin_dividerpositionDefault,
default 0.8), so a profile gets its old position back. Each heading now sits
in the pane of its table, and the "DX cluster" heading is translated
(monitor.dxCluster).
Fixes#144.
Claude-Session: https://claude.ai/code/session_01AaorTymXfkXPm8yb4Btva7
Co-authored-by: Claude <noreply@anthropic.com>
Material3's DropdownMenu clamps every popup to 48dp below the window's
top edge (MenuVerticalMargin in its position provider); the margin is
applied after the offset parameter and the provider is not replaceable,
so the in-window menu bar's menus all opened with a visible gap hanging
below the bar. Replace them with a plain focusable Popup in MenuDefaults
styling and an own position provider that puts the menu directly under
its anchor, flipping above only when there is no room below. The anchor
box takes the full bar height so the menu starts at the bar's bottom
edge, not at the centred title text.
Claude-Session: https://claude.ai/code/session_01BegdsGSNNxKR6VPNPNvfoc
Co-authored-by: Claude <noreply@anthropic.com>
* Move remaining references to the HamRadioOnline organisation
The repository moved from praktimarc/kst4contest to
HamRadioOnline/kst4contest. Document the move in the German and English
changelog, point manuals, README, website, AUR packaging and the
version-feed tooling at the new address, and keep accepting pre-move
release URLs in the update-feed validator because published feeds still
carry the old owner. Personal identities (Ko-Fi account, contact
e-mail) stay unchanged.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WFGQ7wkSPo21itLMHPi8Yw
* Lowercase the owner in the generated Flatpak Pages URL
GITHUB_REPOSITORY_OWNER is now the mixed-case HamRadioOnline, and the
next build would write that spelling into the published flatpakrepo and
flatpakref files. Hostnames are case-insensitive, but the published
metadata should match the documented lowercase address.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WFGQ7wkSPo21itLMHPi8Yw
* Build the Flatpak against org.freedesktop.Platform 25.08
Runtime branch 24.08 is end-of-life and no longer receives security
updates, so every flatpak update now prints an EOL warning. 25.08 is
the current supported branch on Flathub. The app bundles its own Java
runtime, so the platform bump only changes the base libraries.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WFGQ7wkSPo21itLMHPi8Yw
---------
Co-authored-by: Claude <noreply@anthropic.com>
Second slice of making MessageBusManagementThread testable. The CH (live)
and CR (history) chat-frame branches of processRXMessage23001 were near
copies; they are now one processChatFrame(fields, live), with behaviour
unchanged.
- InboundChatFrame, ChatRoute and classifyRoute: where a message belongs
(public, to me, from me, between others), pure.
- ChatMessageEffects and decideChatFrameEffects: what a message triggers
(sounds, //BELL, //VER reply, auto-answer, directional tick, in-angle
flag, DX cluster spot), pure. History frames trigger nothing but the flag.
- The four live/history differences are kept on purpose: frequency
detection before routing (live) or after publishing (history), effects
for messages to me, tick and spot between others, AirScout info on the
SERVER sender.
- MessageBusManagementThreadChatFrameTest pins both branches through the
real thread, including the frequency order on directed frames and the
spot entry; ChatFrameDecisionTest covers the pure functions.
- Spec: docs/superpowers/specs/2026-10-16-message-bus-second-slice-design.md
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Spec: SO2R with two radios in one instance (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Plan: SO2R implementation (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Move the rotator command rules into RotatorControl (#46)
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
* Store the SO2R switch, the second Win-Test station and rotator 2 (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Route frequency reports to radio 1 or 2 (#46)
Add the RadioSlot enum (FIRST, SECOND) with its QRG and QTF targets, and
the pure RadioSlotRouter that decides per RadioInfo packet and per
Win-Test station which radio a report belongs to.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Send RadioInfo of radio 2 to SECONDQRG when SO2R is on (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Send Win-Test STATUS of the second station to SECONDQRG when SO2R is on (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Run a second PSTRotator for radio 2 with SO2R (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Start rotator 2 only while an ON4KST session runs (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Settings for SO2R, the second Win-Test station and rotator 2 (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Turn antenna 2 and show QTF2 with SO2R (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Make the SO2R switches observable so Apply shows them (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Document SO2R (#46)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Refuse clashing PSTRotator ports in both directions (#46)
Writing either port now checks same-or-adjacent against the drafted value of
the other; rotor 1 is only checked while SO2R and rotor 2 are on. Also fixes
a misplaced Javadoc, stale WinTest parseStatus Javadoc, docs wording and
removes an unused import and dead comment.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Remove the executed SO2R plan (#46)
The plan's content lives on in the commits, the spec and PROJECT_CONTEXT.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Open secondary windows on the main window's screen (#59)
Every Compose window but the main one went to the platform's default
position, which on a multi-monitor desk is the primary screen - the
station map could open on a monitor that was switched off. They now open
centred on the screen the main window is on, with their size clamped to
that screen's usable area (insets considered). A window the operator
moved during the session reopens there, as long as its title bar can
still be grabbed on a connected screen; otherwise it falls back to the
main window's screen. The position lives only in the window's host and
is never persisted. ComposeAlert dialogs and the profile picker are
centred the same way once the main window exists.
The rule is a pure function (WindowPlacement) with 18 unit tests; the
AWT side (WindowPlacementOnScreen) only reads the screens and the main
window's bounds on the event thread. The clamped opening size of a
secondary window is not written back, so the stored size survives a
smaller screen.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Track window moves reliably and keep remembered windows on screen (#59)
Review fixes for the window placement:
- Once a window has left the tolerance around its opening position,
every later position is remembered. Before, the anchor was never
re-set, so dragging away and back to near the opening spot left the
stale far position remembered.
- A window the host did not place (opened before the main window
exists) only trusts its anchor once two consecutive reports lie
within the tolerance, so a provisional position followed by the
window manager's placement jump is no longer taken as the operator's
move.
- A remembered position is shifted the least distance that puts the
(clamped) window wholly inside the usable area of the screen holding
its title bar, as the KDoc promised.
The move rule moves into a pure MoveTracker with 5 tests; WindowPlacement
gains keptWithin and 2 more tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Keep window positions across restarts as an opt-in; fit windows to small screens (#59)
A new GUI tab option, off by default, keeps the position the operator last
moved each window to, the main window included. It is stored per window
with the bounds of the screen it was on, written by the layout autosave,
and restored only when a screen with exactly those bounds is connected
again; otherwise the session rule applies. Only operator moves are
stored, never window manager nudges, so a restored window cannot drift.
An open window that rests on a screen too small for it is now cut down
to that screen's usable area, and the station map's 900x600 minimum is
capped to the smallest connected screen, so 640x480 monitors stay usable.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Never store a size or position the host fitted a window to (#59)
The cut-down to a small screen was written back as the stored size
(main window via onResized, others via the tracker) and counted as an
operator move. The host now records its own fit: that size is not
written back, and that position re-anchors the move tracker instead of
being stored. A main window opened at a stored position skips its
opening size like the other windows, since it may be clamped too.
The opt-in gate moves into PreferencesWindowPositionMemory, with tests.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Match the fit echo with tolerance and consume it once (#59)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Restore the connection line in the main window title
While online, the title showed the connection manager's diagnostic
"ON4KST session is authenticated and synchronized" instead of the line
the JavaFX window carried: categories, call, name, locator, users online,
stations shown and messages total. The title now builds that line from
the login preferences and the live station and message tables, so it
follows every new station, filter change and message. The diagnostic
stays where it belongs, in the status bar.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Title: typed categories, no empty category, review fixes
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Path analysis: own ground height ASL and highest point of the remote square
Two new settings in the path-analysis section of the Station tab:
- Own ground height ASL (stn_pathAnalysisOwnHeightAslMeters). Empty keeps
the elevation model value at the own locator centre; a value from -500 to
9000 m replaces the elevation of the first profile sample. The antenna
height AGL is still added on top. The field commits on Enter or focus
loss into the settings draft and reports a refused entry; it keeps the
operator's spelling while that names the drafted number, because the
draft is Compose state and would otherwise swap "25" for "25.0" under
the cursor right after Enter.
- Target station on the highest point of its locator square
(stn_pathAnalysisDxHighestPointInSquare, on by default). The remote square
is sampled on a 5 x 5 grid of cell centres in one batched request against
the Open-Meteo provider, the highest sample becomes the path end with its
position and elevation. LocatorHighestPointResolver caches the result per
locator for the session and backs off five minutes after a failure
(failure list pruned and bounded); the analysis then falls back to the
square centre and that result is not kept.
Both settings are drafted like the other path-analysis settings and take
effect with Apply/Close or Save; the reachability service reads the stored
values only.
The lookup runs on the reachability thread only. Building a request peeks
the resolver cache without blocking, so a cached square moves the endpoint
right away. The calculation key now includes the own height and the remote
ground elevation at full precision, and the switch, so changing either
recalculates.
Also assign the result of sanitizeEffectiveEarthRadiusFactor in the
PathAnalysisRequest constructor; it was called and dropped. No behaviour
change: the sanitizer is the identity for valid factors, and the analysis
service sanitizes again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Document own ground height and highest-point setting of the path analysis
Changelog v1.50 (New), configuration and features pages in English and
German, and the terrain section of PROJECT_CONTEXT.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Add a minimum QRB filter to the station filter bar (#21)
Next to "Show only QRB [km] <=" the bar gets "Show only QRB [km] >": it
hides every station up to the entered distance. With both switched on the
list keeps a range, min < QRB <= max. The minimum is exclusive, as the
issue asks, so the two filters split the list without overlap at the same
value. A station without a known QRB is hidden while either is on, as the
maximum already did. The value lives in the bar for the running session
only, like the maximum, and the station map follows through activeFilters.
The distance check moves from the controller predicate into
StationFilterState.acceptsQrb so it can be tested; the maximum keeps its
behaviour (null or > max is hidden).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Document the minimum QRB filter (#21)
Changelog v1.50 under New, the filter tables of the user interface pages,
the distance filter section of the feature pages, and the station filter
page of the website.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Let the first filter bar row wrap instead of clipping (#21)
With both QRB filters the first row of the station filter bar no longer
fits a narrow station pane, and as a plain Row it cut the bearing buttons
off at the right edge. It is a FlowRow now. Reset, the QRB pair, the QTF
controls and the bearings each move to the next line as one group; the
QRB pair and the bearings only break up inside their group when even the
group is wider than the pane. Separators in the wrapping row have a fixed
height, because a flow row line has no intrinsic height to fill.
A screen test at 300 dp checks that every bearing button, both QRB labels
and fields and the QTF label are displayed and end inside the bar.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Refuse NaN, Infinity and negatives in the QRB filter fields (#21)
toDoubleOrNull also reads "NaN" and "Infinity": a pasted "Infinity" as
the minimum hid every station, "NaN" let every one through, and the
maximum field had the same hole before. Both QRB fields now go through
parseQrbKm, which takes only finite, non-negative distances; anything
else leaves the field at its last valid value.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Let the station map follow the station filters (#21)
The Compose map built its markers from all station rows, so no filter
reached it, although its status line reported "filtered view active".
The JavaFX map, up to beta-v1.50.0-beta-001, took the sorted, filtered
list (StationMapBridge.refreshNow), so this is a regression of the
Compose port that never shipped. The markers now come from the rows the
list shows, and the filter is a key of the remembered markers so a
filter change redraws them. A selected station that a filter hides gets
no marker, as in the JavaFX map.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Filter again on redraw; no path analysis for a hidden station (#21)
DataTableState.visibleRows caches the filtered rows, and forceRedraw only
bumped contentRevision. The filter reads fields that change in place
(QRB, worked and QRV flags, last activity), so a redraw could hand back
rows filtered before the change -- in the list and, since the map draws
the same rows, on the map. forceRedraw now drops the cache, and
visibleRows reads contentRevision so a reader recomputes after it. In the
running application the user-list refresh also sets a new row filter,
which dropped the cache before; this makes the redraw itself sufficient.
A selected station without a marker -- hidden by a filter, or without a
locator -- no longer starts a path analysis: the map used to set
"Loading" with an empty target and send the request. The analysis is
cleared instead, and the effect re-runs when the station's marker
appears or disappears.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Add a settings draft that holds edits until they are applied
The settings window is to stage its edits and apply them with Apply/Close
or Save instead of writing each one at once. SettingsDraft holds one
pending change per setting, reads through to the stored value, and on
apply writes everything first and then runs each effect key once, in the
order the settings were first changed. Form.committed registers its typed
entry with the draft so a click on Apply cannot lose it.
The spec explains the order and the settings that stay immediate.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Stage the settings tabs' edits and apply them with Apply/Close or Save
Every tab state now reads through the window's draft and stages its edits
there instead of writing ChatPreferences: Station (all but the login
credentials), Log synch, TRX synch, Airscout, Notification, Shortcuts,
Beacon, Message handling and GUI (all but the language). The lists stage
their roster, the committed fields stage what their rule accepts.
Effects stay attached to their settings. The Win-Test listener and the DX
cluster server share one effect for switch and port that brings the running
service in line with the applied state, so applying both restarts it once,
on the new port. The own-QRG follower runs once for both sources.
Apply/Close applies and closes, Save applies and writes, Connect applies
before it connects, so the session uses what the tabs show. A field that
refuses its entry on the way stops the button with the reason shown.
Immediate as before: the login credentials, the language, the colours, the
file chooser, the test spot and the profile and worked-database actions.
Number fields keep the typed text while the staged value comes back as
Compose state; otherwise "1" became "1.0" before the next key.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Ask about unapplied settings when the window is closed
Closing the settings window with its X, or through the Windows menu, while
edits wait in the draft now asks: apply them, discard them, or go back to
the window. Without pending edits the window closes as before. Fields and
list rows still holding a typed entry are committed first, so an entry
typed just before the X counts.
The request only sets Compose state; the window decides on its next frame,
so nothing waits on the event thread. A close from outside -- a profile
switch, the shutdown -- discards the draft: the preferences it belongs to
are about to be replaced.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Document that settings take effect with Apply
PROJECT_CONTEXT records the draft and what stays immediate, the changelog
gets one entry under v1.50, and the configuration manual no longer says
that settings take effect while they are edited.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Repair stored settings once before the settings window is built
The fallback band of the DX cluster was repaired to 144 inside a getter
that runs during composition, and the Win-Test broadcast address was
auto-detected in a tab state's constructor. Both wrote ChatPreferences
past the draft at a moment nobody could see. repairStoredSettings now does
both once, before any tab is built; the tab states only read.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Ask before a profile switch or exit, and check fields before applying
A profile switch and the exit dropped pending settings edits silently. They
now go through SettingsWindow.settleThen: with edits pending, the window is
raised and asks Apply / Discard / Back; Apply applies them to the profile
still in force, Back cancels the switch or the exit. The question is Compose
state and the continuation is posted from the dialog's callback, so the
event thread never waits. Without pending edits both go on at once.
Fields are checked before anything is applied: a field still showing text
that does not parse, or that its rule refuses, refuses the apply and is
named in the notice, so the valid edits stay pending and Discard is still
possible. This covers number fields and the guarded external-interface
fields, which used to let Apply go ahead with the last valid value.
Every write and effect of an apply now runs on its own; failures are
collected and reported, a failed write stays pending and skips its effect,
and Save still writes the file when only an effect failed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Check every drafted setting with a real draft, and rename write-through tests
DraftedSettingsTableTest walks every drafted setter of every tab with a
real SettingsDraft: unchanged after the edit, changed after apply,
unchanged after discard. The tab tests run with a draft that applies at
once and cannot tell a drafted setting from one that bypasses the draft.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Document the question on switch and exit, the field checks and the repairs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Decide the pending-settings question on the event thread, never trap
The question is now a SettingsQuestion decided in settle() on the calling
event thread instead of in the settings window's next frame, so an exit
from the main window does not depend on frames of a minimised settings
window; the window is raised and restored before the dialog is needed.
While a question is open, further requests are ignored: an X no longer
replaces the continuation of an exit or switch with a plain close. Each
continuation of settleThen runs at most once.
A field holding text it refuses no longer traps the operator: the X, the
switch and the exit show the question anyway, with the reason, Apply
disabled and Discard and Back available.
The apply-failure notice keeps the technical detail out of the sentence,
in parentheses after a translated one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The release body was built from direct commits on main and GitHub's
generated PR list only; whatever was written into the tag was lost. An
annotated tag's subject and body now open the notes, ahead of "What's
Changed", and so reach the in-app update feed too. The tag object is
fetched explicitly because actions/checkout can leave the triggering tag
as a lightweight ref; contents:subject/body leave the SSH signature out.
Lightweight tags contribute nothing, as before.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Three nightly macOS DMG builds on the Intel runner failed in a row after a
successful notarization: `xcrun stapler validate` lost its connection to
api.apple-cloudkit.com ("The network connection was lost.", exit 68). The
ticket was fine; the runner's connection to Apple was not. staple and
validate now get up to five attempts with growing pauses (20, 40, 80,
160 s) before the build fails.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Translate the interface texts that stage 9 left in English
The GUI tab checkboxes, the file chooser and dropdown placeholders, the
profile dialog's Apply, the settings notice's OK, the chat clear button,
the selected-station map button and "all", six column titles, the monitor
window's title and heading, and the refusal and hint texts of the profiles,
beacon and notification tab states now come from the translation files.
Column titles go through CurrentStrings in a lambda like the existing ones,
so the id stays untranslated and the stored layout keeps its keys. The tab
states read CurrentStrings as StatusIndicatorState already does. The
English values are unchanged, so the screen tests still find every control
by its old label; a new test switches to German and checks one sample per
path: a composed label, a column title and a tab-state refusal.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Translate the settings notices, profile labels and alert button too
Wires the settings.spot* and settings.write* keys that existed but were
never used, translates the settings window title and its notice titles,
the profile tab's "unknown", "Copy of" and database-mode labels, and lets
the shared alert use alert.ok instead of a literal. The German for
messages.qsoOfTheOther becomes "Fremd-QSOs", the word the menu already uses.
"Copy of" is only the suggested display name; the profile id is derived
from the entered name once at creation and stored, so a later language
switch does not touch it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>