Gaps per app
The MUSTs each app still misses, then the SHOULDs open in several apps. Every row was read against an audit of the
app’s MUSTs on 2026-11-10, at the head of the app’s default branch that day, and Editora’s against the rules that cite
it. A part an app lacks is listed once, under the rule that requires it, and the rules about how that part behaves
follow as links on the same clause: a missing find bar is FIND-01’s, and
FIND-02, FIND-06 and
FIND-07 follow it. Five rules say in their References that no app has been read
through for them yet (OS-04, PERF-01,
PERF-02, PERF-03,
PERF-08): a row holds what was found so far, and a row with no clause for one of them
is not a pass. A command id, catalog key, chord, command-line flag, environment variable, property in pom.xml or
pauta.json, or file the repository must carry that a rule’s statement names is required as spelled; a class,
method, style class, branch or workflow file there is Editora’s, and an app’s equivalent meets the rule
(Coding agents).
Missing MUSTs
Section titled “Missing MUSTs”Six MUSTs are open across the family. The rows leave OS-02, WIN-11, WIN-12 and ACC-01 out, and say for MENU-16 and
CLI-12 what each app lacks. No app has the one Os class that alone reads os.name
(OS-02): 51 files read it in Editora, 20 in Termina, 19 in Torrenta, 15 in Mirada, 4
in nux and 3 in Modula, and eight more of Editora’s tell Windows apart by File.separatorChar or
File.pathSeparatorChar instead. No app fixes the order of a dialog’s buttons (WIN-11):
none calls setButtonOrder, so Editora, Torrenta, Termina, Mirada and nux draw theirs in JavaFX’s order for the OS,
and Modula’s one dialog has a single button. No app has a UI zoom (WIN-12): Editora,
Termina and Mirada zoom their content only (the text, the terminal’s font, the image), and Torrenta, Modula and nux
have no zoom. So no app’s menus follow one either (MENU-16): Editora’s and Mirada’s, the two
that set the font on .context-menu, write 14 px as a fixed size. And no app meets all of
CLI-12: the template comes nearest, and refuses a launcher’s JVM options with every
other unknown one. And no app has the test that sweeps every window for a control with no name
(ACC-01): Termina’s sweeps icon-only buttons, Editora’s and Mirada’s each check a few
named sets of buttons, and Torrenta, Modula and nux have none. Editora’s in-window menu rows carry no accessible text;
Torrenta sets one in a single helper, which names every button of its main toolbar and the Search view’s Clear button
and not its ”···” button, and Modula sets none.
| App | Missing MUSTs |
|---|---|
The Pauta edition and conformance in About, pauta.json and the Pauta window, in the README’s badge and “Built to” line and in a section on Pauta in AGENTS.md: nothing in its repository names Pauta (PAUTA-01, PAUTA-02, PAUTA-04, PAUTA-09, PAUTA-10, PAUTA-15, PAUTA-17, ABOUT-05, ABOUT-06, ABOUT-08, ABOUT-09, PWIN-01, PWIN-02, PWIN-03, PWIN-04); a follow-the-system theme: its picker lists named themes only (ICON-16); AI keys only in the keychain, written off the FX thread: Settings keeps the key fields as the fallback for a session in which no keychain answers, and a key typed in Settings is put in the keychain from the field’s own handler (SET-13); plugin signature checking off the Settings UI: Require registry signature is a Settings check box and a palette command (SET-16); no fixed color in a component rule: .recent-remove, .view-mode-bar and others still carry hexes, .overlay-backdrop, the diff and merge tints and 19 shadows, among others, an rgba(), and .breakpoint-condition-mark a fixed white (ICON-08); its state colors taken from the -state-* tokens in every rule: 78 declarations in its component rules name -color-danger-fg, -color-warning-fg or -color-success-fg themselves (ICON-07); @Tag("fx") on every FX test: 33 of its *FxTest classes carry none (QUAL-06); no waiting on the common pool: DapManager.reportJavaExit waits up to three seconds for an exit code inside a supplyAsync with no executor (PERF-05); accessible names on the main toolbar’s buttons and on the floating buttons that leave Zen and Expert mode and bring the toolbar back, which get a tooltip only, and the chord in a stripe button’s accessible name, as in its tooltip (TBAR-01); its toolbars’ buttons out of the Tab order: among them, those of the main toolbar, the stripes, the Test Results panel’s toolbar and the Git Log panel’s toolbar, and the float, maximize and close buttons in every tool window’s header, take focus (TBAR-02); Shift+Enter in the editor’s find bar: its field steps forward on Enter and has no key of its own for the previous match (FIND-06); a previous-tab command: it registers buffer.next alone (TABS-01); the tab’s right-click menu, a tooltip with the file’s full path and a place in Reopen Closed Tab for its image, hex and PDF viewer tabs: they are opened with no menu and no tooltip, and a closed one is not remembered (TABS-01, TABS-02, TABS-06); the tab’s right-click menu on its diff and pull-request review tabs, which are opened with none too (TABS-01); stripe buttons that run their panels’ tool.<id> commands, and commands that hide a panel as well as show it: each stripe button calls the manager’s own toggle, so it skips what a command does first (tool.remote refreshes its panel, tool.project tests that projects are on), and tool.gitLog and the build tools’ tool.<id> commands only open their panel (TABS-13); a palette command for every setting: terminalNotifications, for one, is a Settings row alone (SET-06); an echo message for an uncaught error: its handler writes the trace to the Debug Log and posts nothing (DIAG-04); an icon on every menu row: a command with no fitting glyph gets none, by a test of its own (MENU-14); chords in right-click menus and drop-downs: a row there is a plain MenuItem (MENU-15); a right-click menu on every tree, list and read-only console, each of its rows a command: among those with none are the trees of the Hierarchy and References panels, the Find in Files results tree, the Undo History list, the Message Log’s list, the External Tools console and the text of its Debug Log window, and the Customize Toolbar… row of the toolbar’s menu turns on a mode that no command does (MENU-05); menus whose sizes follow a UI zoom: it sets Inter 14 px on .context-menu and its rows’ labels and 11 px on the chords as fixed pixels, and has no UI zoom to scale them by (MENU-16); Cancel as the default button of its Git confirmations and Local History purges, where Enter runs the red action, and of the questions that leave the stock OK as the default, deleting to the trash, Revert and overwriting a file from Save As among them, and a default button at all in its unsaved-changes and Quit questions (CONF-13); the menu bar in the title bar by default on Windows and Linux: its setting starts off (WIN-03); About in the macOS application menu (ABOUT-01), and macOS’s own Quit run through its quit method: MacOpenFiles hands Glass’s quit action on to JavaFX, which asks each window to close (WIN-13); the buttons of every dialog with two or more buttons worded from the catalog: 26 of its 64 CONFIRMATION alerts keep JavaFX’s stock OK and Cancel, and 22 more name the action beside the stock ButtonType.CANCEL, the helper every destructive Git action asks through among them, and its warnings that ask do the same, the four trust questions beside a stock Cancel and the question before its MCP server is enabled with the stock OK and Cancel, and so do its prompts and forms, among them the Create on GitHub prompt, the picks of a reset mode and of a settings backup and the Java cleanups form with the stock OK and Cancel, and the login form and the forms that export and import the configuration beside a stock Cancel (CONF-14); the action’s own verb, in red, on every question before a destructive action: deleting a file in the Project panel, a project, a note or a macro, and Replace in Files, among others, are answered with OK, and deleting a remote site or a TODO pattern, resetting the settings, discarding recovery records and removing a plugin, among others, name the action with no red (CONF-03); a find bar in its Debug Log window and in three of its four consoles, and with it what every find bar does (the search as it is typed, Enter and Shift+Enter, Escape): the build console has one, and the Run, External Tools and Debug consoles are read-only text areas with none (FIND-01, FIND-02, FIND-06, FIND-07); a console launcher on Windows (CLI-11); the packaged app launched on every OS before a release: only the notarized macOS app is (REL-29); a pull-request workflow that never cancels a run on master: terminal-image.yml sets cancel-in-progress: true and can be started by hand, so a second run started on master cancels the first (REL-31); its “Save as administrator” row disabled on Windows, where it does nothing, and the other differences between OSes listed on Same on every OS: its Windows delete reaches no Recycle Bin, a key rebound on one OS is not rebound on another, and its WSL targets are registered on Windows only (OS-01, OS-04); a settings summary in its problem report (DIAG-06); a bold one-line summary opening every changelog entry, under Keep a Changelog’s headings: 369 of its 2,173 don’t have one, and some sections carry headings of its own (### Performance, ### Internal, ### Packaging) (REPO-02); an unknown command-line option refused: it skips one without a word (CLI-12); no disk access on the FX thread: renaming a file and creating a folder check and change the disk inside their handlers (MainController, ProjectPanel), and start(), before the first window is shown, opens the Debug Log’s session file, takes the lock on a file in the config folder, and reads the ledger of the processes it started, a stale mcp-endpoint.json and the user themes’ folders (PERF-01); a pause before the work typing starts: the debugger’s completion asks the debug adapter again on every change of its field while its list is open, and the file finder starts reading a folder as soon as the typed path names another one, neither behind a timer (PERF-23); only what the first window shows built with it: the shared Output console, an empty tab pane, is made in a field of the main controller and handed to its tool window already built (PERF-14); a virtualized control for every list the data can grow without limit: the crontab preview builds a node for every job, and the pull-request checks card a row for every check run (PERF-08); release notes written for users: the GitHub release’s are its commit list (DOCS-05); its pages for the app’s user on the website alone: docs/plugins.md, a page for plugin authors, has a section that tells the user the three ways to install a plugin and one on troubleshooting plugins (DOCS-02); readable text out of the subtle color everywhere: two rules still set it (.encryption-locked-hint, .pom-version-unknown), and its contrast test checks six named selectors (ICON-09); toolbar tooltips built from the commands’ titles: the main toolbar’s come from tooltip.* keys of their own, and eight differ from the titles (six give another name, Clear Recent’s reads “Clear recent files” for “Clear Recent Files”, and the tail’s Stop button, set up with no command, reads “Stop the running program” and shows no chord) (TBAR-03); every toolbar icon’s command in a menu too: tool.todo, tool.bookmarks and view.toggleZen, three of the icons a user can add, are in the palette and in no menu (TBAR-08); the system’s region kept for dates and numbers: it sets the bare language as the locale (INTL-14); --dev winning over the config-folder environment variable (SET-07); a command and a keyboard path for every button: the Message Log’s Clear button and the build console’s Previous Run and Save Output buttons are out of the Tab order and do their work in their own handlers, with no command and no key behind them (KBD-01, KBD-15); a command for every button of its Debug Log: Refresh, Copy, Clear and Export do their work in handlers of their own, with no command behind them (KBD-01); a failed notification logged: its notifier drops the failure in an empty catch (TRAY-09); a build on a JDK newer than 25: its formatter-needs-jdk25 profile, which turns itself on for JDK 26 and newer, holds an enforcer rule with the range [25,26), so a plain build there stops unless it is told to skip the format check (PLAT-01). | |
the command ids the rules name, help.about and app.quit (it registers about and quit: ABOUT-01, WIN-14), a palette.show command (a menu row, a toolbar button and a key action named palette open the palette, and no command does, so the toolbar’s palette button runs none: PAL-01, TBAR-08) and tool.<id> for its panels (it registers toggle-sidebar and toggle-detail: TABS-13), and each command’s title under command.<id> with a description under command.<id>.desc: its titles are under keys of another spelling (command.addFile for add-file, menu.file.quit for quit) and it has no descriptions (KBD-03); Help → Documentation: it has no help.documentation command and no such row (DOCS-06); docs/README.md (DOCS-12); Keep-a-Changelog format: its changelog opens with ## Unreleased, not ## [Unreleased], heads its numbered sections without brackets too, and one of its 155 entries opens without a bold summary (REPO-02); AGENTS.md (only CLAUDE.md is committed, 131 KB of it, where a few lines that point to AGENTS.md belong: REPO-05, DOCS-14, DOCS-17); CONTRIBUTING.md (REPO-06); attestations (REL-18); a methods floor in the coverage gate: it checks lines only (PLAT-12); the Pauta edition and conformance in About, pauta.json and the Pauta window, in the README’s badge and “Built to” line and in a section on Pauta in AGENTS.md: nothing in its repository names Pauta (PAUTA-01, PAUTA-02, PAUTA-04, PAUTA-09, PAUTA-10, PAUTA-15, PAUTA-17, ABOUT-05, ABOUT-06, ABOUT-08, ABOUT-09, PWIN-01, PWIN-02, PWIN-03, PWIN-04); a follow-the-system theme: its picker lists six named themes (ICON-16); a config file that can’t be read kept as a backup, never stopping startup (SET-11); proxy, Torznab, remote-profile and HTTPS-certificate secrets in the keychain: they are written to its config files as typed (SET-13); its uncaught-exception handler installed at the start of main, and an echo message for an uncaught error: DebugLog.install() runs after the arguments, the config folder and the instance lock are handled, and the handler logs the trace and posts nothing (DIAG-04); an icon on every menu row: none on the rows of the RSS, priority, Set Category and saved-view menus, nor on the File menu’s New Torrent…, Run RSS Rules Now and Switch engine profile… rows (MENU-14); the chords of its right-click rows in the keyboard color: the torrent list’s menu shows each command’s chord as a native accelerator in the theme’s color, and -state-key colors the palette’s chords only (MENU-15); the menus’ font set on .context-menu, never inherited (MENU-16); menu-bar rows with no KeyCombination accelerator: Command.menuItem builds each row as a plain MenuItem and sets an accelerator on it, and the View menu’s hand-built rows do the same (MENU-02); every menu-bar row built from a command: the View menu’s Command Palette, Toolbar, Sidebar, Sidebar on the Right, Details Pane, Details Pane at the Bottom, Simple Mode and row-density rows and the Help menu’s two update rows are built by hand, with menu.* titles and handlers of their own (MENU-01); a command for every action: the Help menu’s Download and Skip Version rows, and every row of the RSS, search results, files, peers (Ban Peer among them) and saved-view right-click menus, run handlers that no command reaches, so the palette and the key bindings can’t either (KBD-01, MENU-05); a command for every button of its Debug Log: Refresh, Copy and Clear do their work in handlers of their own, with no command behind them (KBD-01); a right-click menu on its Message Log’s list, on the table of its Event Log window and on the text of its Debug Log, which the window shows in a read-only TextArea: none of the three has one (MENU-05); Cancel as the default button of its Remove questions, whose red button is the default, and of its four Settings questions, where OK is (CONF-13); Emacs and CUA keymaps as JSON resources, and with them a .mac.json variant that binds the same commands (KBD-09, KBD-21); Ctrl+Shift+P (Cmd+Shift+P on macOS) for the palette: its one key table opens it with Alt+X alone (KBD-05); a focus ring: it has no :focus-visible layer and no -focus-ring (KBD-16, ICON-12); tinted text at 4.5:1 on its own fill: its editora-light.css gives 3.80 to 4.26:1 for the accent, warning and success (ICON-10); the menu bar in the title bar by default on Windows and Linux: its setting starts off (WIN-03); About in the macOS application menu (ABOUT-01), and macOS’s own Quit caught and run through its quit path: it arrives as a close request, which with close-to-tray on hides the window (WIN-13, TRAY-04); --dev, and so its place between --config-dir and the config-folder environment variable (CLI-02, SET-07); Export in the Debug Log (DIAG-03), and a find bar in its Debug Log window, and with it what every find bar does (the search as it is typed, Enter and Shift+Enter, Escape) (FIND-01, FIND-02, FIND-06, FIND-07); a filter field over its Event Log window and over the Log tab of its detail pane: the window filters its table by level with three check boxes, and the tab lists a torrent’s events with no filter (FIND-03); a Format job in CI: Spotless’s check runs only inside ./mvnw verify (PLAT-10, REL-19); the full name in LICENSE’s copyright line (REPO-03); a build on a JDK newer than 25: its enforcer range is [25,26) (PLAT-01); Linux arm64 and macOS x64 builds (REL-01); the .AppImage and .tar.gz downloads (REL-11); actions pinned to commit SHAs (REL-22); Dependabot for maven (REL-23); permissions: contents: read at the top of ci.yml and engine-soak.yml (REL-24), timeout-minutes on their jobs (REL-26), and a ci.yml that never cancels a run on master: its cancel-in-progress is true for every run (REL-31); its “on metered connections” row shown on macOS, disabled, instead of hidden (OS-01); a settings summary in its problem report (DIAG-06); the update check held until a few seconds after the first frame: it starts as soon as the engine is ready (DIAG-05); notifications held back while its window is in front (TRAY-10); every failure of its notifier logged: it reports the first of a session and drops the ones after it (TRAY-09); contrast tests for readable, tinted and emphasis text and the focus ring (ICON-09 to ICON-12); test reports uploaded from CI whether or not the tests fail, the JaCoCo report, and the coverage totals in the job summary: it uploads only on failure and prints coverage to the log (REL-27); configuration export and import (SET-12); its four Settings questions answered by the action’s own verb, in red: disconnecting Settings Sync, Reset to Defaults, Reset All Shortcuts and taking a shortcut back from another command are CONFIRMATION alerts whose OK and Cancel are worded from the catalog, so the button that confirms says “OK” and isn’t red (CONF-03); a lone - and what follows -- taken for files, and a launcher’s JVM options skipped: it refuses them all (CLI-12); a schema version in each config file it reads back, and a migration step for each (SET-09, SET-10); a right-click menu closed by a press inside the control it was opened on: every one has the stock auto-hide alone (MENU-07); an accessible name on the detail pane’s ”···” button: it gets a tooltip and no accessible text (TBAR-01); every registered command in the palette, with its description: it lists only the commands that can run now, leaving out what the engine can’t run and what Simple mode puts away, and shows no descriptions (PAL-02); a Settings search that ranks a whole word above the start of one: SettingsWindow.rank matches by substring alone and ranks only by where the match is, title, description or keywords (SET-03); its state colors taken from its tokens in every rule, and no fixed color in a component rule: .speed-graph-up and .speed-graph-legend-up repeat -torrenta-up’s ladder(), with its two hexes, .palette-backdrop and two shadows write an rgba(), and 29 declarations in its component rules name -color-danger-fg, -color-warning-fg or -color-success-fg themselves (ICON-07, ICON-08); @Tag("fx") on its FX tests: no test carries a tag, and 26 test classes start the toolkit through @ExtendWith(FxToolkit.class) (QUAL-06); no disk access on the FX thread: a change of a Settings control writes the settings file from its listener (Settings.saveQuietly), the Set Location dialog asks the disk about the typed folder on every keystroke (FreeSpace.disk), Import from Another Client looks for the other clients’ folders inside its handler (ImportText.found), start() opens the Debug Log’s session file, the main window’s constructor reads six stores of the user’s before the window is shown (the profiles, the labels, the watch folders, the search providers, their definitions and the RSS feeds), and start() reads profiles.json again once the window is shown (PERF-01); redraws coalesced to one per pulse: Sparkline and SpeedGraph draw straight from their width listener and again from their height listener, with no pending flag, so a resize draws twice (PERF-06); log records sent to the FX thread in batches: the Event Log’s bridge posts one Platform.runLater for each warning or error that is logged (PERF-07); a size check before a picked .torrent is read: Session.resolve reads the whole file whatever its size, where its web API and its fetch of a link stop at 10 MB (PERF-12); only the first window built before the first frame: the main window’s constructor builds the Event Log, Statistics and Settings windows with it, and the Settings window’s constructor builds its content (PERF-14); a virtualized control for every list the user can grow without limit: the rule dialog builds a check box for every feed, and the tags dialog one for every tag (PERF-08); a short landing-page README.md with highlights, an install section and a command-line part: it has none of the three, and runs to 433 lines, with the keyboard, the engine, the remote engine and the layout written out where a link to the website belongs (REPO-01); a NOTICE that says “licensed under the MIT License”, lists every bundled component and ships in the installers: it has no such line and no entry for OpenJFX or Jackson, and nothing puts LICENSE or NOTICE into a package (REPO-04); the docs/ set: of the seven it has release.md alone (REPO-07); its user guides on the website alone: docs/headless.md, docs/webapi.md and docs/search-providers.md are user guides kept in the app’s repository (DOCS-02); the notarized macOS app launched once: its “Smoke-test the packaged app” step runs before the notarization, and “Notarize the dmg (macOS)” ends at spctl (REL-15); its messages formatted in the locale that formats its dates and numbers: Messages.tr formats every message in the bare language, so a number inside a sentence loses the region that Locale.setDefault keeps (INTL-14). | |
the command ids the rules name, help.about, palette.show and help.documentation (it registers about, commandPalette and documentation: ABOUT-01, PAL-01, DOCS-06), and find.show, which a SHOULD names (it registers find: FIND-04), with titles and descriptions under command.<id> and command.<id>.desc (it uses menu.<id>: KBD-03); the coverage floors on Windows too: its os-windows profile lowers them to 0.45 for lines and 0.47 for methods (PLAT-12); the conformance in About, pauta.json and the Pauta window (PAUTA-01, PAUTA-02, PAUTA-04, PAUTA-09, PAUTA-10, ABOUT-09, PWIN-01, PWIN-02, PWIN-03, PWIN-04); a “Built to” line in its README that names the edition and the conformance and links the docs page: the README has the Pauta badge alone, which names the edition and links the edition’s address (PAUTA-15); icons on the menu bar’s rows (MENU-14), chords in right-click menus, and a keyboard color for the menu bar’s chords, which are drawn in -color-fg-muted (MENU-15), and the menus’ font set on .context-menu, never inherited: it sets Inter on .root only (MENU-16); Cancel as the default button of its removal questions and of Import configuration, as it already is when closing a running program (CONF-13); the buttons of its text prompts worded from the catalog: Rename Tab keeps JavaFX’s stock Cancel, and the prompt its setting commands ask a value through and Create on GitHub are TextInputDialogs with the stock OK and Cancel (CONF-14); the menu bar in the title bar by default on Windows and Linux: its setting starts off (WIN-03); a status bar shown by default: its ui.showStatusBar setting starts off, by a decision record of its own (WIN-01); a console launcher on Windows (CLI-11); a find bar in its Debug Log window, and with it what every find bar does (the search as it is typed, Enter and Shift+Enter, Escape) (FIND-01, FIND-02, FIND-06, FIND-07); a filter over its Message Log, which is a list of entries: the window has no field to type in (FIND-03); its hideMenuBar command kept on macOS, disabled with its reason: it is removed there (OS-01); a tab’s folder taken from the same source on every OS, and the user’s key bindings synced as one set: a directory the shell reports is believed on Windows only, and on macOS and Linux the OS is asked instead, so the folder a new tab starts in can differ, and Settings Sync keeps the key bindings in one file for macOS and another for Windows and Linux (OS-04); a Quit: it has no app.quit command and no Quit row in its File menu (WIN-14); one quit method that macOS’s own Quit runs: it has none, so the application menu’s and the Dock’s Quit reach each window as its own close request, and each window asks for itself (WIN-13); a command for its find bar’s regex toggle, which is out of the Tab order and has no key either (FIND-16, KBD-15); its find bar’s arrows named by their commands’ titles, each with its own command’s chord: they are named “Previous match, up (Enter)” and “Next match, down (Shift+Enter)” from strings of their own, and each shows the chord of the command that steps the other way (the up arrow steps to an older match, as findNext does, and shows findPrevious’s chord) (TBAR-03); --report written to a file in the current folder: it only prints the report (CLI-05); contrast tests for readable, tinted and emphasis text and the focus ring (ICON-09 to ICON-12); a launcher’s JVM options skipped by name: it refuses them with any other unknown option (CLI-12); the UI font on every scene: four of its dialogs get no ui-font.css, the Rename Tab prompt, the two alerts of its terminal window and the Settings window’s repository-name prompt (ICON-01); --dev winning over the config-folder environment variable (SET-07); its tab menus closed by a press inside the tab strip, as the terminal’s menu is (MENU-07); an About that names an edition it meets: it says “Built to Pauta 2.0.2”, which already required the find bar in the Debug Log, the UI font on every scene and the command ids it lacks (ABOUT-07); links to its source code and its releases in About: it links its website and not its repository, and its releases only when an update is available (ABOUT-02); a link to the release in the status bar’s notice of a newer version: the notice names the version and links nothing (DIAG-09); the paste hint in the issue form’s report field when the report is too long for the link: past 7,500 characters its link leaves that field out, and only its own window says to paste (DIAG-13); blocking work off the common pool: SingleInstance.handOff connects to the first instance’s socket, writes to it and reads its answer inside a supplyAsync with no executor (PERF-05); no file or socket work on the FX thread: once the first window is shown, start() deletes a stale socket file and binds the socket for later launches (serve in instance/SingleInstance.java), and Fonts.loadRest reads and registers the bundled font families the first window didn’t need, two pulses after it is shown (PERF-01); a command for every button: Clear in the Message Log, Refresh, Copy, Export and Clear in the Debug Log and Import theme in Settings, among others, do their work in handlers of their own, with no command behind them (KBD-01); every menu-bar row a command: the bar’s model holds rows that are no command id, the New Tab With Profile submenu, whose rows carry each profile’s name and open the tab from a handler of their own, and, off macOS, the zoom row, one row of buttons for its four zoom commands (MENU-01); a right-click menu on its Message Log’s list and on the text of its Debug Log: neither has one (MENU-05); its pages for the app’s user on the website alone: docs/reference/installing.md tells the person installing it which download to take, how to install each and how to check its signature (DOCS-02); every failure of its notifier logged: it logs an exception only, and nothing when it finds no tool to run, kills the tool at the timeout or the tool exits with an error (TRAY-09); a schema version in the color schemes it imports, and with it a way to tell a newer one: each is a file it writes whole and reads back at start, with no version (SET-09, SET-10). | |
the command ids the rules name, help.about (it registers about: ABOUT-01) and a palette.show command (a key filter opens the palette: PAL-01); user docs on a website, with its Pauta conformance page: the README is all it has, and it names no website (DOCS-01, DOCS-02, PAUTA-13); a help.documentation command that opens the user docs from the palette: it registers none, and has no Help menu for a row (DOCS-06); docs/README.md (DOCS-12, DOCS-17); JaCoCo and its coverage floors (PLAT-12), with the report uploaded from CI and the coverage totals in the job summary: it uploads the surefire reports alone (REL-27); headless FX tests: surefire sets no glass.platform, and no test starts the toolkit (PLAT-11); i18n: it has no message catalogs, and its commands’ titles are literals in the code, with no descriptions (INTL-01, INTL-08, KBD-03); Inter, bundled and on every scene: it bundles IBM Plex Mono and sets it on .root in its stylesheet (ICON-01, ICON-02); a status bar with an echo area: its status line has one fault style and no warning style, and a click on it opens nothing (WIN-01); Settings search, and the sidebar of pages it searches: Settings is one column of rows (SET-02, SET-03); a Message Log and a Debug Log with its window and the window’s find bar, and an uncaught-exception handler set in main to feed them: it logs to java.util.logging and keeps nothing to show (DIAG-01, DIAG-02, DIAG-03, DIAG-04, FIND-01, FIND-02, FIND-06, FIND-07); Report a Problem, as a command, a window and --report (DIAG-06, DIAG-11, DIAG-12, DIAG-13, CLI-05); AGENTS.md, with its section on Pauta, and a short CLAUDE.md that points to it: its CLAUDE.md is 878 lines and the only guide (REPO-05, PAUTA-17, DOCS-14); CONTRIBUTING.md (REPO-06); bug_report.yml (REPO-09); JReleaser: softprops/action-gh-release creates its release (REL-03); attestations (REL-18); a Linux arm64 build (REL-01); the Pauta edition and conformance in About, the README, pauta.json and the Pauta window, with an exception recorded for each rule it does not meet: nothing in its repository names Pauta (PAUTA-01, PAUTA-02, PAUTA-04, PAUTA-09, PAUTA-10, PAUTA-15, ABOUT-05, ABOUT-06, ABOUT-08, ABOUT-09, PWIN-01, PWIN-02, PWIN-03, PWIN-04); a follow-the-system theme: its theme is one Daylight switch (ICON-16); a config file that can’t be read kept as a backup: it logs a warning and loads the defaults (SET-11); icons on its menu rows (MENU-14), and the menus’ font set on .context-menu, never inherited: its stylesheet gives the rows’ labels 12 px and no family (MENU-16); Emacs and CUA keymaps as JSON resources, with the user’s own bindings applied over them: its keys are fixed in one key filter (KBD-09, KBD-11, KBD-21); Cmd+Shift+P for the palette on macOS: its key filter tests for Ctrl on every OS, so the chord is Ctrl+Shift+P there too (KBD-05); a focus ring: it has no :focus-visible layer and no -focus-ring (KBD-16, ICON-12); --help, --version, --config-dir and --dev: it reads no arguments, so it refuses no unknown one either (CLI-01, CLI-02, CLI-12); an environment variable for the config folder: ConfigStore.userDefault is ~/.modula and reads no MODULA_CONFIG_DIR (SET-07); one instance per config folder (CLI-07); a console launcher on Windows (CLI-11); a Check for Updates command (DIAG-10); the update check held until a few seconds after the first frame: start() runs it straight after stage.show(), with no delay (DIAG-05, PERF-15); the release linked where the status line says a newer version exists: it names the version alone (DIAG-09); configuration export and import (SET-12); About in the macOS application menu (ABOUT-01), and macOS’s own Quit caught and run through its quit path: it reaches the window as a close request, which the close handler takes for a close and, with the tray on, answers by hiding the window (WIN-13, TRAY-04); a Linux tray with no AWT fallback: its Trays.create tries AWT’s when the StatusNotifierItem fails (TRAY-01); a Format job in CI: Spotless’s check runs only inside ./mvnw verify, and its build has no coverage gate either (PLAT-10, REL-19); the docs/ set (REPO-07); the full name in LICENSE’s copyright line (REPO-03); actions pinned to commit SHAs (REL-22); the packaged app launched on every OS before a release: only the notarized macOS app is (REL-29); an app.quit command: it quits from its tray and its window’s close button only (WIN-14); a bold one-line summary opening every changelog entry, under Keep a Changelog’s headings: 11 of its 79 don’t have one, and some sections carry headings of its own (### Radio, ### Recording, ### Hardware and five more) (REPO-02); contrast tests for readable, tinted and emphasis text and the focus ring (ICON-09 to ICON-12); timeout-minutes on the jobs of build.yml, release.yml and notify-catalog.yml: the one timeout in the three is on a step, the notarization (REL-26); the .rpm and .AppImage downloads (REL-11); Dependabot weekly for github-actions: it is monthly (REL-23); an accessible name on its icon-only buttons: none sets one, and the four transport buttons, Settings, Record and the save-preset button carry a tooltip only (TBAR-01); tooltips built from the commands’ titles and chords: each is a string typed for the button (“Seek up to the next station” for seek.up, whose title is “Seek up” and whose chord the tooltip leaves out) (TBAR-03); a question or an undo when a preset is removed: the right-click menu’s Remove deletes it at once (CONF-01); a schema version in each config file it reads back, and a migration step for each (SET-09, SET-10); release notes written for users: they are generated from the commits (DOCS-05); a concurrency group on build.yml that cancels superseded pull-request runs (REL-31); its preset chips’ menus closed by a press inside the bar, as the pane’s menu is (MENU-07); one right-click menu at a time: a preset chip’s menu opens beside the pane’s, which nothing closes (MENU-06); a keyboard path to a preset’s Rename and Remove: it takes every control of its main window out of the Tab order, which its keys and its palette make up for everywhere but on the preset chips, whose right-click menu no key opens (KBD-15, MENU-09); a command for every action: a preset’s Rename and Remove are rows of its chip’s menu alone, and the volume and the typed frequency are keys alone, none of them among the commands its palette lists (KBD-01, MENU-05); Ctrl+, (Cmd+, on macOS) for Settings: its settings command has no chord (SET-01); a palette command for every setting: only Daylight has one (theme), and the recording folder and format, the encoder’s path, the tray’s two switches and the update check are Settings rows alone (SET-06); the Java runtime, a link to its releases and the result of the last update check in About: it shows no Java version, links its repository alone, and shows an update line only when a newer version was found (ABOUT-02); every command in the palette, with its description: its commands have none, and stereo is left out while its control is disabled (PAL-02); its colors taken from the theme’s roles: modula.css uses no -color-* token, and its whole palette, the state colors -lock and -fault among them, is fixed hexes on .root and again on .root.daylight, chained to no role, and .palette-backdrop and two shadows write an rgba() in component rules (ICON-07, ICON-08); no disk access and no wait for a process on the FX thread: the pane’s constructor reads presets.txt and schedules.txt before the window is shown, saving, renaming and removing a preset, Stop, and every change of a Settings row write the config file inside their handlers, and opening Settings starts ffmpeg -version and waits up to five seconds for it (PERF-01); a README.md that is a short landing page: its 364 lines have no highlights and no command-line part, link no website, and carry the detail themselves (the dongle’s drivers, signing, recording, the source layout, the roadmap) (REPO-01); a capture hook or a headless fixture that builds its real window: it has neither (QUAL-09); a virtualized control for its presets, a list the user can grow without limit: the preset bar builds a chip for every one of them, in a row that scrolls (PERF-08). | |
Its settings in ~/.mirada on every OS, and --config-dir winning over --dev: on macOS and Windows it uses the OS’s own folder, and of the two flags the one typed last wins, so --config-dir X --dev gives ~/.mirada-dev (SET-07); the command ids the rules name, tool.<id> for its panels, and M-1 and M-2 for them in its Emacs keymap (it registers view.properties and view.thumbnails, and binds them to i and t: TABS-13); a find bar in its Debug Log window, and with it what every find bar does (the search as it is typed, Enter and Shift+Enter, Escape) (FIND-01, FIND-02, FIND-06, FIND-07); the conformance in About, the README, pauta.json and the Pauta window: it names its edition and states no conformance anywhere (PAUTA-01, PAUTA-02, PAUTA-04, PAUTA-09, PAUTA-10, PAUTA-15, ABOUT-09, PWIN-01, PWIN-02, PWIN-03, PWIN-04); Cancel as the default button of its Confirm questions (CONF-13); the buttons of its Rename prompt worded from the catalog: it is a TextInputDialog with JavaFX’s stock OK and Cancel (CONF-14); an About that names an edition it meets: it says “Built to Pauta 4.0.1”, and the settings folder was a MUST in that edition too (ABOUT-07); a link to its releases in About: it links its repository and the running build’s release notes, and its releases only when an update is available (ABOUT-02); Escape, the OS’s accent color, the title’s place and its menus the same on every OS: Escape closes the window on Linux only, the accent is followed on macOS and Windows only, the title is on the left on Windows only, and it has a menu bar on macOS only (OS-04); a Quit: it has no app.quit command and its ☰ menu ends with Close (WIN-14); --report written to a file in the current folder: it writes beside the settings (CLI-05); a contrast test that walks every rule for readable text in the subtle color: its StyleContrastTest holds ICON-10 to ICON-12 (ICON-09); a single-dash option refused: anything that doesn’t start with -- is taken for a file (CLI-12); the system’s region kept for dates and numbers: it sets the bare language as the locale, and its catalog formats its messages with the bare language too (INTL-14); the chord in an icon button’s accessible name, as in its tooltip (TBAR-01); its About and Documentation rows inside its Help menu: in the ☰ menu both sit beside the Help submenu, and the Help menu of its macOS menu bar lists Documentation and no About (ABOUT-01, DOCS-06); --help, --version and --report shown to print in the Windows console: its one executable is the native image, with no console launcher and no AttachConsole, and no Windows run has confirmed what it does (CLI-11); its menus’ sizes scaled by a UI zoom: ui-font.css sets Inter on .context-menu and its rows’ labels, and writes the titles’ 14 px and the chords’ 11 px there as fixed pixels, with no UI zoom to scale them by (MENU-16); its state colors named as tokens: it has none for them, and four of its component rules name -color-danger-fg and -color-warning-fg themselves (ICON-07); a right-click menu on its Message Log’s list and on the text of its Debug Log: neither has one (MENU-05); a command for Refresh in its Debug Log: the button, and F5 in that window, call the window’s own refresh, with no command behind them (KBD-01); no disk access on the FX thread: on macOS, started with a file, it compares the first file the OS hands over with the one on its command line through Files.isSameFile there (PERF-01). | |
the command ids the rules name, help.about (it registers app.about: ABOUT-01) and a palette.show command (a shortcut opens the palette: PAL-01), with titles and descriptions under command.<id> and command.<id>.desc: its titles drop the id’s prefix, command.connect for app.connect, and it has no descriptions (KBD-03); user docs on a website, with its Pauta conformance page: nothing in its repository or its About names one (DOCS-01, DOCS-02, PAUTA-13); a help.documentation command, which the palette lists: it registers none (DOCS-06); docs/README.md, the index that says the code wins (DOCS-12, DOCS-17); NullAway, with every package @NullMarked (PLAT-09); Spotless (PLAT-10), and a format check and a build that runs verify in CI: its one test job runs ./mvnw test (REL-19); JaCoCo, with the 0.90 floors for lines and methods (PLAT-12); Inter, bundled and on every scene (ICON-01, ICON-02); a status bar: a found update is a button in its toolbar (WIN-01, DIAG-09); a Settings window with a sidebar of pages and a search field: its pages are the tabs of a TabPane, with no search (SET-02, SET-03); settings that apply live, with no Save button: its Settings window writes nothing until its Save button is pressed, and has a Cancel beside it (SET-04); a palette command for every setting: its palette changes three, the tray’s metric, a UPS’s notification rule and start at login (SET-06); a Message Log, a Debug Log with its window and the window’s find bar, and a handler for an uncaught error (DIAG-01, DIAG-02, DIAG-03, DIAG-04, FIND-01, FIND-02, FIND-06, FIND-07); Report a Problem, in the app and as --report (DIAG-06, DIAG-11, DIAG-12, DIAG-13, CLI-05); CONTRIBUTING.md, which points into docs/ (REPO-06, DOCS-14); bug_report.yml (REPO-09); Linux signatures (REL-16); JReleaser: its release job attaches the files with softprops/action-gh-release (REL-03); attestations (REL-18); the Pauta edition and conformance in About, pauta.json, the Pauta window, the README and AGENTS.md: nothing in the repository names Pauta (PAUTA-01, PAUTA-02, PAUTA-04, PAUTA-09, PAUTA-10, PAUTA-15, PAUTA-17, ABOUT-05, ABOUT-06, ABOUT-08, ABOUT-09, PWIN-01, PWIN-02, PWIN-03, PWIN-04); a config file that can’t be read kept as a backup, never stopping startup, and every value clamped on load (SET-11); icons on its menu buttons’ rows (MENU-14), and the menus’ font set on .context-menu, never inherited (MENU-16); Emacs and CUA keymaps as JSON resources, with the user’s own bindings over them and the macOS variant: its chords are written into App.start (KBD-09, KBD-11, KBD-21); a focus ring: it has no :focus-visible layer and no -focus-ring (KBD-16, ICON-12); --help, --version, --config-dir and --dev: it reads --minimized and --screenshot only, and ignores any other (CLI-01, CLI-02, CLI-12); the NUX_CONFIG_DIR environment variable: its config folder is fixed at ~/.nux (SET-07); a console launcher on Windows (CLI-11); configuration export and import (SET-12); About in the macOS application menu (ABOUT-01), and macOS’s own Quit caught and run through its quit path: it comes as a close request, which hides the window to the tray (WIN-13, TRAY-04); notifications that need no tray on Windows, where they are the tray icon’s balloon, whose text is no part of the script on macOS, and whose failures are logged: it logs none (TRAY-09); a Linux tray with no AWT fallback: its Trays.create tries AWT’s when the StatusNotifierItem fails (TRAY-01); the docs/ set (REPO-07); actions pinned to commit SHAs (REL-22); the packaged app launched on every OS before a release: only the notarized macOS app is (REL-29); a switch for each notified event, where it has one for all and a rule per UPS, and notifications held back while its window is in front (TRAY-10); its risky-command question’s Run button in red: it has no style of its own (CONF-03); the buttons of its four dialogs of two buttons worded from the catalog: the risky-command question names Run beside JavaFX’s stock ButtonType.CANCEL, the question before a harmless command is a CONFIRMATION alert with the stock OK and Cancel, the credentials form adds the stock OK and Cancel, and the Save Profile prompt is a TextInputDialog with the same pair (CONF-14); a question or an undo when a profile is deleted: Profiles → Delete profile removes it at once (CONF-01); a bold one-line summary opening every changelog entry, under Keep a Changelog’s headings: 90 of its 98 don’t have one, and one section carries a heading of its own (### Internal) (REPO-02); contrast tests for readable, tinted and emphasis text and the focus ring (ICON-09 to ICON-12); timeout-minutes on the jobs of ci.yml and release.yml (REL-26); the .AppImage download (REL-11); test reports and the JaCoCo report uploaded from CI, and the coverage totals in the job summary: its test job uploads nothing (REL-27); an AGENTS.md with the worktree-per-task rule and the change checklist, and a short CLAUDE.md that points to it: its AGENTS.md has neither, and its CLAUDE.md is a copy of it (REPO-05); a word to the user when no tray icon comes: it shows the window and says nothing (TRAY-02); a schema version it reads back: it writes schema=1 and never reads it, and has no migration (SET-09, SET-10); release notes written for users: they are generated from the commits (DOCS-05); a concurrency group on ci.yml that cancels superseded pull-request runs (REL-31); the system’s locale kept whole when no language is chosen and it has no catalog for the system’s: it sets bare English (INTL-14); a filter over its event log: the Events window is a TableView under a Refresh and an Export button, with no field to type in (FIND-03); the chord in its ”?” button’s accessible name, as in its tooltip: the tooltip is rebuilt as “About Nux (F1)” and the accessible text stays “About Nux” (TBAR-01); tooltips built from the commands’ titles, with chords from a keymap: its buttons’ tooltips are the button’s label and a chord written into App.start (“History” where the command’s title is “Show history charts…”) (TBAR-03); the update check started a few seconds after the first frame: start() runs it before it returns, with no delay (DIAG-05, PERF-15); a link to its releases and the result of the last update check in About, whatever it was: it adds the update’s line, and the link to the releases with it, only when a newer version was found (ABOUT-02); a command for every action: deleting a profile, and Refresh and Export in its Events and History windows, are reached by no command (KBD-01); its state colors named as tokens: nux.css has no .root block, and three of its rules name -color-warning-fg and -color-danger-fg themselves (ICON-07); no fixed color in a component rule: .status-pill and .update-badge set -fx-text-fill: white, .palette-backdrop an rgba() background and .palette-card an rgba() shadow (ICON-08); redraws coalesced to one per pulse: its history charts redraw at once from the width listener, the height listener and every mouse move, with no flag that one is queued (PERF-06); no wait and no file work on the FX thread: Settings’ Save, with the tray switched off, waits there up to two seconds for the tray icon’s removal, and --screenshot writes its PNG from an animation’s callback (PERF-01); background results applied under a generation guard: each Refresh of its Events window, and each load of the Energy and Outages tabs of its History window, is applied with no mark, beside a Charts tab that numbers its loads (PERF-03); the results of its network scan sent to the FX thread in batches: the scan hands over each server it finds in a Platform.runLater of its own (PERF-07); a virtualized control for its profiles and its UPSes, lists the user and the data can grow without limit: the dashboard builds a card for every saved profile but the one on screen, while the setting that watches the other profiles is on, and for every UPS, again as readings arrive (PERF-08); a README.md that is a short landing page: its 313 lines have no command-line or config-folder part and link no website (REPO-01); NOTICE inside its installers: nothing in pom.xml or release.yml packages it (REPO-04); each command’s description in the palette: its rows show the title and the command’s id, and its commands have no description (PAL-02); a second launch that hands its arguments to the running app, and --new-instance as the way to a second instance: a second launch only asks the running app to show its window, and a setting lets a second instance run on the folder (CLI-07). |
SHOULDs open in several apps
Section titled “SHOULDs open in several apps”- Windows
.msisigning (REL-17): no app signs its MSI yet; the certificate isn’t chosen. - Settings in the macOS application menu (WIN-15): only Mirada puts it there, with a key equivalent of its own where the rule asks for the active keymap’s chord in the row’s title. Editora, Termina, Torrenta, Modula and nux have no such row.
- Maven’s repository cached by every
setup-javastep (REL-25): Editora, Termina and Torrenta each have a step withoutcache: maven. - The same short flags (CLI-13): Termina and Torrenta take
-h,-vand-V. Editora has no-vand Mirada no short flags; Modula reads no arguments, and nux reads two long flags of its own,--minimizedand--screenshot, and no short one. - One tooltip delay (TBAR-14): no app sets 400 ms on every tooltip. Termina sets it on its icon buttons and leaves its palette’s at JavaFX’s second; Editora sets 300 to 400 ms on a few, Mirada 250 ms on one, and the rest set none.
- The find command finding the next match, and every match painted (FIND-04,
FIND-05): Editora’s terminal find bar refocuses its field and its console
bar has no command; Termina’s refocuses too. A Debug Log drawn in a
TextAreashows one match at a time. - Page Up and Page Down in the palette (PAL-06): Torrenta’s, Modula’s and nux’s palettes have neither.
- The config read begun before the toolkit (PERF-16): Editora starts it in
mainandstart()takes the result. Torrenta, Modula and nux load their settings insidestart(), Torrenta and nux after theirmainhas read the file once on the main thread; Termina reads them ininit(), after the toolkit is up; Mirada’s earlier read only happens in its native image. - A pinned toolbar tail (TBAR-15): Torrenta keeps Simple mode and Settings
inside its
ToolBar, so a narrow window overflows them before its icons. - Toolbar buttons that follow their command (TBAR-17): the buttons Editora adds from its catalog (Commit, Problems and the rest) stay enabled when their command can’t act.
- A stripe button’s tooltip that follows its tool window’s title (TBAR-12): Editora rebuilds the tooltip on a keymap switch only, so a title change (the Project window becoming “Current Folder”) reaches the button’s accessible text and the bottom stripe’s label, not its tooltip.
- Settings Sync (SYNC-01): Modula, Mirada and nux don’t have it.
- Copy in the Message Log on the keymap’s copy chord (MLOG-04): Editora’s, Torrenta’s, Termina’s, Mirada’s and the template’s each copy on the platform’s fixed chord alone.
- A tab’s Git status in its tooltip (TABS-08): Editora, the one app whose tabs hold files, shows the status by the title’s color alone; its tab tooltip is the file’s path.
- The Message Log as an in-scene card (MLOG-08): Termina’s is a separate window keeping 500 entries, and Torrenta’s card is 640 × 300, not 773 × 336.
- The Help menu’s rows in one order (DOCS-07): Mirada’s Help submenu holds Message Log, Debug Log, Report a Problem, then Check for Updates, with its Command Palette, Documentation, keyboard reference and About rows beside it in the main menu. Editora’s Welcome Page row is in its View menu, and so is Termina’s Command Palette row.
- A keyboard reference in the Help menu (DOCS-08): Editora’s keybinding editor is a page of Settings that no Help row opens, and Mirada’s keyboard-reference row sits beside its Help submenu.
- A help chord in the palette (PAL-08): only Editora’s palette opens the selected command’s page in the docs. Termina’s, Torrenta’s, Mirada’s, Modula’s and nux’s have no such chord.
- AWT headless unless a listed use needs it (CLI-09): Modula’s and nux’s
mainnever setjava.awt.headless, so AWT is headful on every OS, Linux included. - Screenshots rendered at 2× (DOCS-18): Termina’s, Torrenta’s and nux’s capture hooks write the scene at its own size. Editora has no capture hook, and its headless fixture writes a screenshot from three FX tests only, at the scene’s own size too.
- Docs links that open the running version’s docs (DOCS-03): Termina and Mirada
each open their site’s unversioned
/docs/. - Toolbar groups separated by spacing, not lines (TBAR-04): the separators of Editora’s Debug panel toolbar draw their line, and so do those of Torrenta’s main toolbar.
- A toggle that looks on while it is on (TBAR-07): Torrenta’s palette button carries no pseudo-class while the palette shows.
- A command that hides the tab bar (TABS-12): the nearest Termina has is a setting, toggled from the palette, that hides the strip only while a window has one tab.
Pauta 6.0.0 · · Changelog · This page in the latest edition