Metadata

• Update number: 4
• Update type: bugfix
• Date: 2026-05-05
• Author: Ryan Kamp
• Commit hash: 9bb710562208ab053536b4bd6f49411b2174a595
• Commit timestamp: 2026-05-05T15:59:55-04:00
• GitHub push timestamp: 2026-05-05T20:00:06Z
• App version: 1.2.0 → 1.2.1

Summary

This update is a reliability patch for scheduled Routines firing while the resmon window is closed. It closes three coupled defects: (i) routine ↔ APScheduler-jobstore lifecycle integrity (deleted routines no longer leave ghost apscheduler_jobs rows, daemon startup reconciles any pre-existing ghosts, and routine jobs are registered with a 1-hour misfire_grace_time so a fire whose nominal moment briefly passed still runs); (ii) the dual-backend race in which the Electron main process raced a launchd-bootstrapping daemon and silently spawned a competing backend with its own scheduler against the shared SQLite jobstore (now: pingHealth waits ~3 s with retry/backoff, lock-file presence forces a wait rather than a spawn, and even a legitimate fallback spawn honors RESMON_DISABLE_SCHEDULER=1 so the renderer-spawned backend never owns a scheduler); and (iii) Advanced-tab honesty — the “Run resmon in the background” status block now reads daemon.lock and probes the daemon’s actual port through a new GET /api/service/daemon-status route, so the displayed pid / version / last_started reflect the real daemon and any future dual-backend race surfaces immediately rather than being masked. App version bumps 1.2.0 → 1.2.1.

Motivation

All five fixes originated in a diagnostic session after the user observed in Update 3’s tutorial-recording flow that, having used the Settings → Advanced Danger Zone to wipe data and re-enable “Run resmon in the background,” scheduled Routines no longer fired when the app window was closed even though the Advanced tab reported the daemon as Installed and “up.” The full diagnosis lives in resmon_update_4_overview.md; the change inventory and batching plan live in update_5_5_26_workflow.md. The five items map back to the workflow doc as Fixes A–E:

• Fix A — Routine ↔ jobstore lifecycle integrity (workflow item #1, Batch 1). delete_routine did not remove the matching apscheduler_jobs row; the dispatcher kept trying to fire ghost jobs whose owning routine was gone, and a Danger-Zone wipe could leave ghosts behind that no UI surface could reach. Coupled with Fix B in Batch 1 because both touch scheduler.py / database.py / the FastAPI startup wiring and are exercised by the same scheduler verification suite.
• Fix B — Default misfire_grace_time for routine jobs (workflow item #2, Batch 1). APScheduler’s default misfire_grace_time of 1 second silently dropped any fire whose nominal moment had passed by even a brief window — exactly the failure mode produced by a daemon restart, a scheduler reattach, or the app’s own scheduler dying without a clean shutdown().
• Fix C — Robust daemon attach in the Electron main process (workflow item #3, Batch 2). The 500 ms /api/health timeout returned false during the launchd daemon’s bootstrap window; the renderer then silently spawned its own backend with its own scheduler against the same SQLite jobstore, and once the spawned backend died at app close every queued fire was marked “missed by N hours.”
• Fix D — Renderer-spawn never owns a scheduler (workflow item #4, Batch 2). Defense in depth for Fix C: even when a renderer-spawned fallback is legitimate (no daemon installed at all), the spawned backend must not start a ResmonScheduler against the shared jobstore. Implemented as a RESMON_DISABLE_SCHEDULER=1 env var that main.ts sets on the spawned child and the FastAPI startup hook honors.
• Fix E — Advanced tab daemon-status truthfulness (workflow item #5, Batch 3). The Advanced tab populated its daemon-status line from GET /api/health against whichever backend the renderer was attached to, so a renderer-spawned fallback masqueraded as the daemon and the dual-backend race was invisible to the user. The fix reads daemon.lock server-side and probes the daemon’s actual port through a new endpoint.

Changes

Batch 1 — Fixes A + B (scheduler / jobstore lifecycle cluster)

• resmon_scripts/implementation_scripts/scheduler.py — add_routine registers each routine job with misfire_grace_time=3600; new reconcile_jobstore_with_routines method drops every apscheduler_jobs row whose id has no matching routines.id with is_active=1; called once from the FastAPI startup hook before active routines are re-registered. (Fix B + Fix A reconciliation.)
• resmon_scripts/implementation_scripts/database.py — delete_routine removes the matching apscheduler_jobs row in the same transaction as the routines delete (idempotent against APScheduler-side removals; deletion-time job removal is tolerant of an already-gone row). (Fix A cascade.)
• resmon_scripts/resmon.py — startup hook calls scheduler.reconcile_jobstore_with_routines() before re-registering active routines so any pre-existing ghosts are dropped on first boot of the patched daemon. (Fix A startup wiring.)
• resmon_scripts/verification_scripts/test_scheduler_reconciliation.py (new) — regression: seeds an orphan apscheduler_jobs row, runs reconciliation, asserts removal; seeds a job whose owning routine is is_active=0, asserts removal; seeds a job whose owning routine is active, asserts retention.
• resmon_scripts/verification_scripts/test_routine_scheduler_sync.py (new) — regression: inserts a routine, registers its job, calls delete_routine, asserts no orphan apscheduler_jobs row remains.
• resmon_scripts/verification_scripts/test_scheduler_lifecycle.py (new) — regression: asserts new routine jobs are added with misfire_grace_time=3600.
• resmon_scripts/verification_scripts/test_scheduler_wiring.py (new) — verifies the FastAPI startup hook invokes reconcile_jobstore_with_routines before re-registration.

Batch 2 — Fixes C + D (dual-backend race cluster)

• resmon_scripts/frontend/electron/main.ts — pingHealth AbortController timeout raised from 500 ms to ~3 s; the lock-file → health-probe sequence is wrapped in a 2–3 attempt retry loop with brief backoff (hard ceiling ~4.5 s wall); when read_lock() returns a payload but the health probe has not yet responded, the main process waits for the daemon rather than falling through to the spawn branch; the spawn branch sets RESMON_DISABLE_SCHEDULER=1 on the child env so a legitimate renderer-spawned fallback never owns a scheduler.
• resmon_scripts/resmon.py — FastAPI startup hook gates ResmonScheduler instantiation and set_dispatcher on os.environ.get("RESMON_DISABLE_SCHEDULER") being unset / falsy; default behavior preserved for direct python resmon.py <port> invocations and for create_app() test calls.
• resmon_scripts/frontend/dist/electron/main.js — rebuilt from main.ts via tsc --project tsconfig.electron.json.
• resmon_scripts/verification_scripts/test_scheduler_disable_env.py (new) — regression: with RESMON_DISABLE_SCHEDULER=1 set, create_app() startup must not instantiate ResmonScheduler and must not call set_dispatcher; with the env var unset / falsy, scheduler startup proceeds normally.

Batch 3 — Fix E (Advanced tab daemon-status truthfulness)

• resmon_scripts/resmon.py — new GET /api/service/daemon-status route that calls daemon.read_lock(), probes http://127.0.0.1:<lock_port>/api/health via httpx (1.5 s timeout), and returns { lock_present, running, pid, port, version, started_at, lock_pid, lock_port, lock_version, error, is_self }; the is_self flag is set when the probed pid equals the current process pid so the renderer can render the distinction between “daemon is the current backend” and “daemon is a separate process.”
• resmon_scripts/frontend/src/components/Settings/AdvancedSettings.tsx — added DaemonStatusResponse type; refresh() polls /api/service/daemon-status alongside the existing /api/service/status and /api/health calls; status block rewritten to render three explicit states (“daemon up” with pid/version and an , this process tag when is_self; “lock present but unreachable” with the diagnostic error; “no daemon running”); the renderer-attached backend’s identity is shown separately as · this window → pid …, v… so any divergence between the two is immediately visible. Last started is now sourced from the daemon-status response rather than /api/health.
• resmon_scripts/frontend/dist/bundle.js — rebuilt from the renderer source via webpack --mode production.
• resmon_scripts/verification_scripts/test_daemon_status_endpoint.py (new) — three regression tests: (a) no lock file → lock_present=False, running=False; (b) stale lock pointing at a closed port → lock_present=True, running=False, error populated; (c) valid lock + monkey-patched httpx.Client returning a healthy response → running=True with daemon identity surfaced.

T-UPD-3 documentation pass (this step)

• resmon_scripts/implementation_scripts/config.py — APP_VERSION = "1.2.0" → "1.2.1".
• resmon_scripts/frontend/package.json — "version": "1.2.0" → "1.2.1".
• resmon_scripts/frontend/src/components/AboutResmon/AboutAppTab.tsx — backendVersion initial fallback bumped 1.0.0 → 1.2.1; “Recent Update” card rewritten to summarize Update 4 (replacing the Update 3 copy).
• resmon_reports/info_docs/settings_info.md — Advanced panel description now documents the new GET /api/service/daemon-status endpoint and the three-state status block; endpoint table gains the new route.
• resmon_reports/info_docs/system_info.md — “headless daemon split” paragraph now documents the raised pingHealth timeout / retry+backoff, the lock-file-aware wait, and the RESMON_DISABLE_SCHEDULER env gate that ensures only the daemon ever owns a scheduler.
• resmon_reports/info_docs/routines_info.md — Delete-a-routine flow now documents the delete_routine cascade into apscheduler_jobs, the daemon-startup reconciliation, and the misfire_grace_time=3600 registration default.
• .ai/updates/update_5_5_26/update_5_5_26.md — this log.
• .ai/updates/updates.csv — appended Update 4 row (commit_hash / commit_timestamp / github_push_timestamp = pending; T-UPD-4 will overwrite).

Verification

Per-batch test command and results (verification suite at resmon_scripts/verification_scripts/):

• Batch 1 — python -m pytest resmon_scripts/verification_scripts/test_scheduler_disable_env.py resmon_scripts/verification_scripts/test_scheduler_lifecycle.py resmon_scripts/verification_scripts/test_scheduler_wiring.py resmon_scripts/verification_scripts/test_scheduler_reconciliation.py resmon_scripts/verification_scripts/test_routine_scheduler_sync.py resmon_scripts/verification_scripts/test_daemon.py — all passing (this superset is the same command used for the post-Batch-3 sanity run; per-batch counts were captured at the time of each batch report).
• Batch 2 — Python regression test_scheduler_disable_env.py covers Fix D’s RESMON_DISABLE_SCHEDULER env gate; Fix C’s Electron main-process retry/backoff is exercised by manual UI verification (the project does not currently host a JS-side Electron main test harness — same posture documented in Updates 2 and 3).
• Batch 3 — python -m pytest resmon_scripts/verification_scripts/test_daemon_status_endpoint.py resmon_scripts/verification_scripts/test_daemon.py resmon_scripts/verification_scripts/test_service_units.py → 21/21 passing, 0 skipped.
• Frontend build — cd resmon_scripts/frontend && npm run build succeeded after the Batch 2 / Batch 3 edits (webpack production renderer bundle clean; tsc --project tsconfig.electron.json for dist/electron/main.js clean).
• Manual UI smoke — daemon was restarted via launchctl kickstart -k gui/$UID/com.resmon.daemon to reload the patched Python; resmon.app launched and attached to the daemon on port 8742 (no fallback backend spawned); GET /api/service/daemon-status returns the documented shape with is_self=true when the renderer is attached to the daemon.

Concatenated counts string (for the CSV row): backend: 21/21 passing, 0 skipped on the targeted batch-3 suite (test_daemon_status_endpoint.py + test_daemon.py + test_service_units.py); batch-1 suite (test_scheduler_disable_env.py + test_scheduler_lifecycle.py + test_scheduler_wiring.py + test_scheduler_reconciliation.py + test_routine_scheduler_sync.py + test_daemon.py) all passing; platform-gated Linux systemd --user and Windows Task Scheduler tests remain skipped on macOS via their existing skipif guards (no daemon / service-unit code path on those platforms changed in this update); frontend: webpack production build clean after every batch; manual UI smoke confirmed daemon attach via launchd, no fallback backend spawn, /api/service/daemon-status three-state rendering, and that scheduled Routines now fire from the daemon's scheduler with the new misfire grace.

Follow-ups

• Stale-daemon caveat for upgrading users. As with Updates 2 and 3, an existing resmon-daemon started before this update is still running the old scheduler.py / database.py / resmon.py and therefore still has the 1-second misfire grace, the delete_routine cascade gap, and the missing /api/service/daemon-status route. Users upgrading from 1.2.0 should restart the daemon (launchctl kickstart -k gui/$UID/com.resmon.daemon on macOS, systemctl --user restart resmon-daemon on Linux, or unregister/re-register the Task Scheduler entry on Windows) so the renderer attaches to a fresh backend.
• Electron main-process test harness. Fix C’s retry/backoff / lock-file-aware wait is currently covered only by manual UI verification. A future update could introduce a focused JS-side test harness for frontend/electron/main.ts (mocking fetch and the lock-file reader) so Fix C’s branches are regression-protected the same way Fix D is.
• Scheduler-diagnostics surface. The Advanced tab’s /api/scheduler/jobs panel now reflects the daemon’s jobstore truthfully (since only the daemon owns a scheduler). A small follow-up could surface misfire_grace_time and the most-recent reconciliation pass timestamp on each row for operator transparency.

Metadata

• Update number: 3
• Update type: mixed (bugfix + feature)
• Date: 2026-04-27
• Author: Ryan Kamp
• Commit hash: 0570bc5ac416b42b774b3e1609e1602d6c8adc27
• Commit timestamp: 2026-04-30T17:35:25-04:00
• GitHub push timestamp: 2026-04-30T21:35:39Z
• App version: 1.1.0 → 1.2.0

Summary

This update lands two Calendar bugs, one small deep-link feature, and one large feature — a brand-new top-level About resmon page — together with eleven out-of-band additions that emerged mid-flight and were folded into the same change set per the T-UPD-ADD rule. The Calendar’s scheduled-routine times no longer drift by ~4 hours and Custom-cadence first-fire / interval anomalies (every-N-months, every-5-hours, every-5-days, every-3-weeks, every-1-year) all expand correctly; the 30-minute “orange-bar” cosmetic bug is fixed; and the expansion window now extends to a full 12 months with a user-facing notice when the FullCalendar viewport is navigated past the horizon. The Repositories & API Keys page gains a “Looking for AI API key settings?” deep-link button to Settings → AI. A new top-level About resmon page hosts four tabs — Tutorials (eighteen embedded YouTube walk-throughs covering the full app, every page, and every Settings sub-tab), Issues (a credentials-free mailto: + GitHub-issue-deep-link form), Blog (an in-app reader fed by the new GitHub Pages site at https://ryanjosephkamp.github.io/resmon/), and About App (relocated out of Settings); a shared TutorialLinkButton is rendered next to every page header and every Settings sub-panel header so any user can deep-link straight into the matching tutorial section. App version bumps 1.1.0 → 1.2.0.

Motivation

All items in this update originated in the user’s third-after-release feedback session and map back to the change inventory in .ai/updates/update_4_27_26/update_4_27_26_workflow.md.

• Bug 1 — Calendar scheduled-routine times incorrect (workflow item #1, batch 1). Daily / weekday / weekly / monthly cron expansions on the Calendar page rendered 4 hours earlier than they actually fired (UTC vs. local-time mismatch), and several Custom cadences exhibited first-fire / interval anomalies. The Calendar’s 90-day expansion window also silently truncated upcoming fires for high-frequency cadences with no user-facing notice.
• Bug 2 — Cosmetic 30-minute routines render as multi-day orange bars (workflow item #2, batch 1). Same Calendar subsystem; FullCalendar event mapping was treating short-duration routine fires as all-day events.
• Feature 3 — “Looking for AI API key settings?” deep-link button (workflow item #3, batch 2). Users repeatedly looked for AI provider keys (OpenAI, Anthropic, etc.) on the Repositories & API Keys page even though those keys live on Settings → AI. A small inline button between the page intro paragraph and the scope selector now routes them directly to /settings/ai.
• Feature 4 — New About resmon top-level page (workflow item #4, batch 3). Users had no in-app place to learn how each page worked, no credentials-free way to file a bug or request a feature, and no surfaced channel for per-update release notes. The About App tab was also crowding the Settings page. Update 3 introduces the new top-level page with Tutorials, Issues, Blog, and the relocated About App tab, plus a shared TutorialLinkButton next to every page and every Settings sub-panel header.
• Out-of-band additions (T-UPD-ADD). Eleven user-requested additions emerged after T-UPD-1 was scaffolded and during T-UPD-2 execution; they were folded into the active batches per the workflow’s T-UPD-ADD rule. They are listed under Changes below and motivated individually in update_4_27_26_workflow.md (OOB-1 … OOB-11).

Changes

Batch 1 — Calendar bug cluster (Bug 1 + Bug 2 + window extension + horizon notice)

• resmon_scripts/resmon.py — /api/calendar/events cron expansion now resolves trigger fire times in the local timezone rather than UTC (fixes the ~4-hour shift); Custom-cadence first-fire arithmetic is reworked to honor IntervalTrigger start-date semantics for every-N-hours / every-N-days / every-N-weeks / every-N-months / every-N-years schedules so first-fires and intervals are correct; the expansion window is extended from 90 days to a full 12 months and MAX_PER_ROUTINE is raised proportionally so high-frequency cadences (every 5 hours) are not truncated; the response now carries a horizon_end timestamp the frontend can compare against the FullCalendar viewport.
• resmon_scripts/frontend/src/pages/CalendarPage.tsx — FullCalendar event mapping now sets allDay: false and a real end derived from the routine duration so 30-minute routines render as a tight bar rather than a full-width orange band; renders a user-facing notice when the FullCalendar viewport is navigated past the 12-month horizon explaining that the calendar only projects scheduled fires up to 12 months ahead.

Batch 2 — Repositories & API Keys deep-link button

• resmon_scripts/frontend/src/pages/RepositoriesPage.tsx — adds a “Looking for AI API key settings?” inline button between the page intro paragraph and the scope selector that routes to /settings/ai.

Batch 3 — About resmon page + tutorial deep-link buttons + Settings → About App relocation

• New top-level page and routes.
  • resmon_scripts/frontend/src/pages/AboutResmonPage.tsx (new) — top-level page with the tab strip and nested router; final tab order Tutorials → Issues → Blog → About App (Issues and Blog were added under OOB-5 / OOB-6).
  • resmon_scripts/frontend/src/components/AboutResmon/TutorialsTab.tsx (new) — eighteen tutorial sections (one full-app overview + ten page sections + seven Settings sub-tab sections), each with an embedded youtube-nocookie.com/embed/<id> iframe, a TOC, and prev / next navigation; deep-link hash drives smooth-scroll into view.
  • resmon_scripts/frontend/src/components/AboutResmon/AboutAppTab.tsx (new — relocated content) — the previous Settings → About App panel content, now mounted under /about-resmon/about-app.
  • resmon_scripts/frontend/src/App.tsx — adds the /about-resmon/* route and the sidebar nav entry appended after Settings.
• Shared TutorialLinkButton next to every page header and every Settings sub-panel header.
  • resmon_scripts/frontend/src/components/AboutResmon/TutorialLinkButton.tsx (new) — single shared component navigating to /about-resmon/tutorials#<anchor>.
  • All ten page components (DashboardPage, DeepDivePage, DeepSweepPage, RoutinesPage, CalendarPage, ResultsPage, ConfigurationsPage, MonitorPage, RepositoriesPage, SettingsPage) plus all seven Settings sub-panels (EmailSettings, CloudAccountSettings, CloudSettings, AISettings, StorageSettings, NotificationSettings, AdvancedSettings) render TutorialLinkButton next to their <h1> / <h2> headers.
• Settings → About App removal.
  • resmon_scripts/frontend/src/pages/SettingsPage.tsx — removes the About App NavLink and nested <Route>; removes the AboutAppSettings import; tab count goes 8 → 7. The Settings index redirect to /settings/email is unchanged.
  • resmon_scripts/frontend/src/components/Settings/AboutAppSettings.tsx — deleted (content relocated to AboutResmon/AboutAppTab.tsx).

Out-of-band additions (T-UPD-ADD)

• OOB-1 — Calendar Routines: x of y dropdown filters to active-only. resmon_scripts/frontend/src/pages/CalendarPage.tsx — fetchData seeds visibleRoutines from the active subset and a derived activeRoutines constant drives the Select all action and the rendered checkbox list.
• OOB-2 — Calendar event popover shows Name: and Cron Schedule: info lines. resmon_scripts/frontend/src/pages/CalendarPage.tsx — popover renders two new event-popover-meta lines for the matching active routine.
• OOB-3 — Edit Routine button on Calendar popover + shared RoutineEditModal + cross-page sync.
  • resmon_scripts/frontend/src/lib/routinesBus.ts (new) — pub/sub bus mirroring configurationsBus.ts with notifyRoutinesChanged() + useRoutinesVersion().
  • resmon_scripts/frontend/src/components/Routines/RoutineEditModal.tsx (new) — extracted reusable create/edit modal that broadcasts on both routinesBus and configurationsBus on save.
  • resmon_scripts/frontend/src/pages/RoutinesPage.tsx — refactored to consume the shared modal; subscribes to useRoutinesVersion().
  • resmon_scripts/frontend/src/pages/CalendarPage.tsx — adds the Edit Routine popover button; subscribes to useRoutinesVersion() and re-runs fetchData() on save without closing the popover.
• OOB-4 — .modal-overlay z-index above the Calendar event popover. resmon_scripts/frontend/src/styles/global.css — bumps .modal-overlay from z-index: 1000 → 1100.
• OOB-5 — About resmon → Issues tab + GitHub issue templates.
  • resmon_scripts/frontend/src/components/AboutResmon/IssuesTab.tsx (new) — credentials-free form with two read-only submit paths (mailto: link + GitHub-issue deep link); both routed through window.resmonAPI.openPath (falls back to window.location.href / window.open when the preload bridge is unavailable).
  • .github/ISSUE_TEMPLATE/bug.yml, feature.yml, question.yml, config.yml (new) — typed GitHub issue forms whose IDs match the slugs the Issues tab generates.
  • resmon_scripts/frontend/src/pages/AboutResmonPage.tsx — mounts the new tab between Tutorials and About App.
• OOB-6 — About resmon → Blog tab + GitHub Pages publishing infrastructure.
  • resmon_scripts/frontend/src/components/AboutResmon/BlogTab.tsx (new) — fetches the Atom feed at https://ryanjosephkamp.github.io/resmon/feed.xml, parses client-side via DOMParser, renders a two-pane layout with an origin-locked Electron <webview>; off-origin links open in the user’s default browser.
  • resmon_scripts/frontend/electron/main.ts — enables webPreferences.webviewTag: true and adds a will-attach-webview hardening hook that scrubs nodeIntegration, preload, and any non-https src.
  • resmon_scripts/frontend/src/index.html — widens the CSP <meta> to permit https://ryanjosephkamp.github.io for frame-src / child-src / connect-src, plus https://www.youtube-nocookie.com and https://www.youtube.com for the Tutorials embeds.
  • docs/_config.yml, docs/Gemfile, docs/index.md, docs/README.md, docs/_posts/2026-04-23-welcome-to-the-resmon-blog.md (new — Jekyll site scaffolding). The two republished update posts (docs/_posts/2026-04-24-resmon-update-1.md, docs/_posts/2026-04-25-resmon-update-2.md) shipped in a separate 7f1ea24 commit on 2026-04-29 ahead of T-UPD-4 and are noted here for the record; they are not staged as part of the Update 3 commit.
  • resmon_scripts/frontend/src/pages/AboutResmonPage.tsx — mounts the new tab between Issues and About App.
• OOB-7 — New T-UPD-5 prompt template in update_prompts.md. .ai/updates/update_prompts.md — adds a T-UPD-5 — Publish Update as Blog Post prompt template formalizing the seven-step per-post procedure, bumps the document to version 1.3, extends the usage / TOC / hard rules to reflect the new five-prompt sequence, and adds a “Push before publish” hard rule.
• OOB-8 — saved_configuration_id linkage on the executions table.
  • resmon_scripts/implementation_scripts/database.py — adds a nullable saved_configuration_id INTEGER REFERENCES saved_configurations(id) ON DELETE SET NULL column to the executions table via an idempotent ALTER TABLE … ADD COLUMN migration.
  • resmon_scripts/resmon.py — _enrich_execution_row LEFT JOINs saved_configurations and projects saved_configuration_id + saved_configuration_name onto every execution-returning endpoint; extends DiveRequest and SweepRequest with an optional saved_configuration_id; adds PATCH /api/executions/{id} accepting { saved_configuration_id: int }.
  • resmon_scripts/frontend/src/pages/DeepDivePage.tsx, resmon_scripts/frontend/src/pages/DeepSweepPage.tsx — track the loaded id in a loadedConfigIdRef populated by ConfigLoader.applyConfig; user edits clear the ref via a dirtyRef guard.
  • resmon_scripts/frontend/src/components/Save/SaveConfigButton.tsx, resmon_scripts/frontend/src/pages/CalendarPage.tsx — PATCH the originating execution row with the new id after a successful Save Config.
• OOB-9 — Saved as <name> badge + Name column wiring. resmon_scripts/frontend/src/pages/DashboardPage.tsx, resmon_scripts/frontend/src/components/Results/ResultsList.tsx, resmon_scripts/frontend/src/pages/CalendarPage.tsx, resmon_scripts/frontend/src/components/Save/SaveConfigButton.tsx — adds a Name column (with saved_configuration_name → routine_name → Execution #{id} fallback chain) and a Saved as <name> badge that reconciles in place after a save broadcast.
• OOB-10 — Configurations page View JSON per-row read-only modal. resmon_scripts/frontend/src/pages/ConfigurationsPage.tsx — adds a per-row View JSON button next to Edit that opens a read-only modal with a Copy-to-clipboard button.
• OOB-11 — Settings → Advanced **Danger Zone (16 destructive actions, two-tier confirmation).**
  • resmon_scripts/frontend/src/components/Settings/ConfirmDangerModal.tsx (new) — typed-CONFIRM confirmation gate for the six destructive data/settings actions.
  • resmon_scripts/frontend/src/components/Settings/AdvancedSettings.tsx — appends a Danger Zone section with two columns (Local / Cloud) of 8 buttons each; broadcasts on configurationsBus, routinesBus, and the resmon:execution-completed window event on success; the cloud column is rendered disabled with a Coming soon muted note.
  • resmon_scripts/resmon.py — adds 8 admin route handlers under POST /api/admin/...; the two API-key wipes accept an empty body, the six data/settings destructions require { "confirm": "CONFIRM" }.
  • resmon_scripts/implementation_scripts/database.py — helpers for whole-table truncates with FK cascade.
  • resmon_scripts/implementation_scripts/credential_manager.py — bulk-wipe helpers for the API-key categories.

Documentation, version, and About App tab

• resmon_reports/info_docs/about_resmon_info.md, settings_info.md, calendar_info.md, configs_info.md, dashboard_info.md, results_and_logs_info.md, repos_and_api_keys_info.md, system_info.md, deep_dive_info.md, deep_sweep_info.md — refreshed in T-UPD-3 sub-tranche 1 to reflect Update 3 changes (routines_info.md and monitor_info.md were verified up-to-date and left as-is).
• resmon_scripts/implementation_scripts/config.py — bumps APP_VERSION from 1.1.0 to 1.2.0.
• resmon_scripts/frontend/package.json — bumps version from 1.1.0 to 1.2.0.
• resmon_scripts/frontend/src/components/AboutResmon/AboutAppTab.tsx — version banner now reads 1.2.0 and the Recent Update card is rewritten with this update’s number, name, and summary.
• README.md — adds an #/about-resmon/* row to the routes table, an About resmon bullet under Key Features describing all four tabs, a short Blog subsection linking the GitHub Pages site, a note in the existing Reporting Issues subsection that issues can be filed via the in-app form, and a brief Maintenance / Danger Zone subsection pointing readers at Settings → Advanced.

Verification

Test results from each batch and from the OOB additions, run from the project root with the .venv virtualenv active and the frontend tooling under resmon_scripts/frontend/.

• Batch 1 (Calendar bug cluster):
  • pytest resmon_scripts/verification_scripts/ -q → all green; the Calendar timezone-shift and IntervalTrigger first-fire fixes are exercised by the existing scheduler / cron expansion suites.
  • Frontend: webpack 5.106.2 compiled successfully; manual UI verification of every cron expression enumerated in the bug report (8 AM daily, midnight daily, Mon 9 AM, weekday 8 AM, first-of-month, every-2-months, every-5-hours, every-5-days, every-3-weeks, every-1-year, plus a 30-minute routine) on month / week / day views.
• Batch 2 (AI-key deep-link button): webpack 5.106.2 compiled successfully; manual click-through on the Repositories & API Keys page → lands on #/settings/ai.
• Batch 3 (About resmon page + tutorial deep-link buttons + Settings relocation):
  • cd resmon_scripts/frontend && npm run typecheck → clean.
  • webpack 5.106.2 compiled successfully; renderer bundle.js ~1.06 MiB after the YouTube embed pivot.
  • Manual nav to /about-resmon confirmed all four tabs; manual click-through on every TutorialLinkButton instance (10 page headers + 7 Settings sub-panel headers) confirmed correct deep-link behavior; Settings tab count is 7 with no stranded /settings/about references.
• OOB-1 / OOB-2 / OOB-3 / OOB-4 (Calendar polish + RoutineEditModal + z-index fix): webpack build clean; manual UI smoke confirmed the Routines dropdown now shows active-only routines, the popover surfaces the Name: and Cron Schedule: lines, the Edit Routine button opens the modal above the popover and updates both Calendar and Routines without a manual reload.
• OOB-5 (Issues tab + GitHub issue templates): webpack build clean; manual click-through on Open in Email opened the default mail client with the correct subject / body / diagnostic block, and File on GitHub opened the GitHub new-issue page with the correct template auto-selected and the form fields pre-populated.
• OOB-6 (Blog tab + GitHub Pages): webpack build clean; the GitHub Pages site is live at https://ryanjosephkamp.github.io/resmon/; the in-app Blog tab successfully fetches feed.xml, lists the three published posts, and renders each post in the embedded <webview>. Off-origin links route to the user’s default browser.
• OOB-7 (T-UPD-5 prompt template): documentation-only change; no test suite applies. Verified by re-reading the document end-to-end after the edit.
• OOB-8 (saved_configuration_id linkage): pytest resmon_scripts/verification_scripts/ -q → green (idempotent migration covered by the existing schema-migration suite); manual UI verification of the round-trip on Deep Dive → Save Config → Dashboard / Results & Logs / Calendar popover.
• OOB-9 (Saved as <name> badge + Name column): webpack build clean; manual UI verification of the fallback chain (saved_configuration_name → routine_name → Execution #{id}) and of the in-place reconciliation when a save originates on a different page.
• OOB-10 (View JSON modal): webpack build clean; manual UI verification of the read-only modal across all three config types (manual_dive, manual_sweep, routine); Copy-to-clipboard succeeded under both navigator.clipboard.writeText and the document.execCommand('copy') fallback path.
• OOB-11 (Danger Zone): pytest resmon_scripts/verification_scripts/ -q → green for the new admin-route tests (typed-CONFIRM gate enforced server-side, FK cascades verified). Manual UI verification of all 8 local actions (the two API-key wipes through the simple modal, the six data/settings destructions through the typed-CONFIRM modal); cloud column rendered disabled with the Coming soon note as designed.

Skipped tests: platform-gated Linux systemd --user and Windows Task Scheduler tests remain skipped on macOS via their existing skipif guards (these were exercised under Update 2’s manual verification matrix and are not re-exercised here because no notification-dispatch code changed in this update). No new dependencies; the executions.saved_configuration_id ALTER is idempotent and forward-compatible with installs that already migrated.

Commands:

# Backend
source .venv/bin/activate && pytest resmon_scripts/verification_scripts/ -q

# Frontend
cd resmon_scripts/frontend
npm run typecheck
npm run build
npm start  # full Electron + backend smoke

Follow-ups

• Tutorials full-app overview video — the full-app overview entry currently embeds a placeholder video; the user has reserved the final replacement recording for Update 4 so the rest of the app can be bug-tested first. The placeholder is functional and replaceable by a single youtubeId change.
• Cloud-side Danger Zone column — the eight cloud-mirror buttons in the Settings → Advanced Danger Zone are intentionally rendered disabled (Coming soon). They will activate when the Cloud Account feature lands and the matching /api/admin/cloud/... routes are added.
• Stale-daemon caveat (carried forward from Update 2’s settings-allowlist) — users upgrading should kill any running resmon-daemon process so the renderer attaches to a fresh backend that has loaded the new admin endpoints and the executions.saved_configuration_id migration.

Metadata

• Update number: 2
• Update type: mixed (bugfix + feature)
• Date: 2026-04-25
• Author: Ryan Kamp
• Commit hash: 023d7abc176f50a5eddac35d04bf86e288ac13a8
• Commit timestamp: 2026-04-26T18:06:13-04:00
• GitHub push timestamp: 2026-04-26T22:06:23Z
• App version: 1.0.0 → 1.1.0

Summary

This update lands two bug fixes and three feature clusters, plus eleven out-of-band additions that emerged mid-update and were folded back into the same change set per the workflow’s T-UPD-ADD rule. The Calendar week/day views are switched to the readable dot+text rendering already used on the month view; desktop completion notifications now fire on macOS, Linux, and Windows for both manual and routine executions (including app-closed routines under the headless-daemon path); the AI summarization stack is reworked to store one API key per provider with transparent migration of any pre-existing global key, and the Deep Dive / Deep Sweep / Routines pages gain a single shared full-parity AI override panel (Provider + Model + Length + Tone + Temperature + Extraction Goals) with per-field merge semantics. The Settings → AI panel is rebuilt around a four-column Stored API Keys table backed by a new ai_default_models per-provider default-model map; the Configurations page gains a per-row Edit action with three config-type-aware modal variants and a stale-link 404 fallback; and the configuration-import endpoint now auto-materializes a deactivated routine for every imported routine config, restoring the bidirectional Routines ↔ routine-configs invariant.

Motivation

All items in this update originated in the user’s second-after-release feedback session and map back to the change inventory in .ai/updates/update_4_25_26/update_4_25_26_workflow.md.

• Bug A — Calendar week/day event readability (workflow item #1, batch 1). The timeGridWeek and timeGridDay views rendered each event as a status-colored background block with type-colored text on top; the two color channels collided and the text was unreadable. The month view already used a status-dot + type-colored-text pattern that worked, so the fix was to extend that pattern down into week and day.
• Bug B — Desktop notifications not firing on any platform (workflow item #2, batch 2). Notifications enabled in Settings → Notifications were silently dropped for both manual completions and routine fires, on all three supported platforms. Routine notifications additionally needed to fire when the app window was closed under headless-daemon / background-execution mode (the launchd / systemd --user / Task Scheduler service path). Per the user, cross-platform parity was required inside this same update — not deferred.
• Feature 1 — Multi-provider AI API key storage (workflow item #3, batch 3). The previous design supported exactly one stored AI key at a time, forcing users to delete one provider’s key to test another. The user requested concurrent per-provider key slots with a transparent one-shot migration of any pre-existing global key on first launch.
• Feature 2 — Full per-execution AI override parity (workflow item #4, batch 4). The Dive/Sweep override block exposed only Length / Tone / free-text Model and was missing entirely from Routines. The user requested full parity with the Settings → AI panel (Provider + Model + Length + Tone + Temperature + Extraction Goals) on all three pages, wired to the multi-provider credentials introduced in Feature 1, with per-field merge semantics (empty/blank = use app default; populated = override).
• Feature 3 — Settings → AI tooltips (workflow item #5, batch 4). The Length / Tone / Temperature / Extraction Goals labels on Settings → AI had no in-app explanation. The user requested an InfoTooltip “?” hover on each of the four labels.
• Out-of-band additions OOB-1..OOB-11. Eleven follow-on requests landed mid-update after T-UPD-1: a richer Stored API Keys table on Settings → AI (OOB-1, -2, -7, -8); a Model dropdown + Load-models button + inline missing-key entry + Save-as-default-model action on the override panel (OOB-3, -4); a new ai_default_models per-provider default-model map (OOB-5); race-safe writers in AISettings.tsx to stop two writers from clobbering the map (OOB-6); a per-row Edit action on the Configurations page with three modal variants (OOB-9); a stale linked_routine_id 404 fallback (OOB-10); and an import-side fix that auto-materializes a deactivated routine for every imported routine config so the bidirectional Routines ↔ routine-configs invariant holds (OOB-11). All eleven are part of this same Update 2 per workflow direction; this log is the single source of truth.

Changes

Batch 1 — Bug A: Calendar week/day event readability

• resmon_scripts/frontend/src/pages/CalendarPage.tsx — wired the FullCalendar eventContent / eventClassNames / eventDidMount hooks for the timeGridWeek and timeGridDay views to the same dot+type-colored-text rendering already used on the dayGridMonth view; week and day events no longer paint a status-colored background block under type-colored text.
• resmon_scripts/frontend/src/styles/global.css (or the calendar-scoped styles file actually used) — removed the background-color rules from the calendar-type-* / fc-event-* classes when the active view is timeGridWeek or timeGridDay; the status dot is now the sole status channel in those views.

Batch 2 — Bug B: Desktop notifications across macOS, Linux, and Windows

• In-process notification dispatcher (the module reachable via notify_on_complete) — repaired the dispatch path that swallowed notifications when the renderer was the active window and when the headless daemon fired routines with no attached renderer.
• resmon_scripts/implementation_scripts/daemon.py and resmon_scripts/implementation_scripts/service_manager.py — wired the headless-daemon execution path into the notification dispatcher so routine completions raised by the launchd / systemd --user / Task Scheduler service path emit a desktop notification even when no renderer is attached.
• resmon_scripts/service_units/ (launchd plist, systemd --user unit, Task Scheduler XML) — verified per-platform notification permissions are not blocked by the service template; documented the per-platform manual-verification checklist where the dev machine could not natively exercise both Linux and Windows.
• No new runtime dependency was added; the existing notifier surface covers all three platforms once the dispatcher is reached.

Batch 3 — Feature 1: Multi-provider AI API key storage with transparent migration

• resmon_scripts/implementation_scripts/credential_manager.py — added a per-provider credential-naming scheme (ai_api_key__<provider_slug>) and a one-shot, idempotent migration helper invoked at backend startup that re-keys any pre-existing legacy global AI credential under the per-provider name corresponding to the user’s currently selected provider. The legacy entry is only removed after the new entry is confirmed written.
• resmon_scripts/resmon.py — surfaced per-provider presence on GET /api/credentials, accepted per-provider names on PUT /api/credentials/{name} and DELETE /api/credentials/{name}, and updated the AI factory / provider-resolution path so the correct stored key is selected at execution time based on the active provider.
• resmon_scripts/frontend/src/components/Settings/AISettings.tsx — replaced the single-key form with a presence map keyed by provider; this is the foundation OOB-1..OOB-8 build on.

Batch 4 — Feature 2 + Feature 3: Per-execution AI override parity and Settings → AI tooltips

• resmon_scripts/frontend/src/components/AIOverridePanel.tsx (new) — single shared override panel rendering the full Settings → AI control set (Provider + Model + Length + Tone + Temperature + Extraction Goals). Empty values are dropped via a buildAIOverridePayload helper before posting so they cannot clobber persisted defaults during the backend per-field merge.
• resmon_scripts/frontend/src/pages/DeepDivePage.tsx, resmon_scripts/frontend/src/pages/DeepSweepPage.tsx, resmon_scripts/frontend/src/pages/RoutinesPage.tsx — mounted AIOverridePanel inside the form / create-edit modal; replaced the previous Length/Tone/free-text-Model trio with the shared panel (Routines previously had no override block at all).
• resmon_scripts/resmon.py (AI execution-settings merge) — extended the per-execution merge to accept Provider + Model + Length + Tone + Temperature + Extraction Goals as per-field overrides; per-execution overrides never write back to the persisted app_settings row.
• resmon_scripts/frontend/src/components/Settings/AISettings.tsx — added InfoTooltip “?” hovers next to the Length, Tone, Temperature, and Extraction Goals labels (Feature 3).

Out-of-Band Additions

• OOB-1, OOB-2, OOB-7, OOB-8 — Settings → AI Stored API Keys table. resmon_scripts/frontend/src/components/Settings/AISettings.tsx now renders a four-column Stored API Keys table (Provider / Status / Default Model / Actions). The Provider name (only — not the row) is the click target for setting the app default; Status carries a Default badge for the active provider; per-row Actions expose Clear default model and Clear API key. The table is lifted out of the .settings-form 480 px-capped container into its own min(960px, 100%) wrapper with non-stacking horizontal Actions buttons. (global.css minor tweak from OOB-1 only; OOB-7/-8 stayed inline so the shared .settings-form rule is not perturbed.)
• OOB-3, OOB-4 — Override panel: provider-aware Model dropdown + missing-key inline entry + Save-as-default-model. resmon_scripts/frontend/src/components/AIOverridePanel.tsx replaced the override-panel free-text Model input with a dropdown populated by POST /api/ai/models for the chosen Provider, behind a Load models button. When the chosen Provider has no stored key, the panel renders an inline API-key input that POSTs to /api/credentials/{name} (re-using the Settings → AI endpoint). A Save as default model button persists the chosen model into ai_default_models[provider] without leaving the page; after save, the panel emits the live-update event so other surfaces refresh. No backend route additions.
• OOB-5 — ai_default_models per-provider default-model map. resmon_scripts/resmon.py added ai_default_models (JSON-encoded {provider: model_id} dict) to _SETTINGS_GROUPS["ai"]. All read/write paths (Settings → AI panel, override panel, the AIDefaultsInfo strip on Dive/Sweep/Routines) consult the map keyed by the active provider, falling back to the legacy global ai_model / ai_local_model only for the active provider’s row when the map has no entry. Non-breaking, additive — no schema migration. Operational caveat: existing daemons started before this allowlist entry existed silently dropped ai_default_models writes; users upgrading past this update must restart the daemon (kill the existing resmon-daemon process and let the renderer attach to a fresh one).
• OOB-6 — Race-safe writers in AISettings.tsx. handleClearDefaultModel, handleSetDefaultProvider, and handleSave in resmon_scripts/frontend/src/components/Settings/AISettings.tsx each GET /api/settings/ai immediately before each PUT, merge the fresh ai_default_models map with their intended delta, and PUT only the narrow set of keys they need to change; the override panel already used a similarly narrow PUT. This stops the two writers (Settings panel + override panel) from clobbering each other.
• OOB-9 — Configurations page per-row Edit action. resmon_scripts/frontend/src/pages/ConfigurationsPage.tsx gained an Edit button on every row’s Actions column with a config-type-aware modal: routine → full Routines-style editor (cron + multi-repo + date range + keywords + max-results + AI/Email/Email-AI/Notify toggles + Execution-Location radio + shared AIOverridePanel) saving via PUT /api/routines/{linked_routine_id}; manual_sweep → same form minus cron and the routine-only toggles, saving via PUT /api/configurations/{id}; manual_dive → same as manual_sweep but with RepositorySelector mode="single". No new backend routes.
• OOB-10 — Stale linked_routine_id 404 fallback. handleEditSave in resmon_scripts/frontend/src/pages/ConfigurationsPage.tsx now tries PUT /api/routines/{linked_routine_id} first and, on 404, falls back to PUT /api/configurations/{id} with the full routine payload (and linked_routine_id cleared). Defense-in-depth retained for any non-import path that could leave a config row orphaned; for the import path itself, OOB-11 makes the fallback unnecessary by always materializing the routine.
• OOB-11 — Import ↔ Routines bidirectional invariant. resmon_scripts/resmon.py’s import_configurations endpoint post-processes each imported row: for every config_type == 'routine' config it parses the inner parameters JSON, builds a routine insert payload, forces is_active=0 (imported routines are deactivated by default so bulk imports never auto-fire), calls insert_routine, captures the new id, and rewrites the just-imported config row’s parameters JSON so linked_routine_id points at the new routine and is_active=False. The response gains a routines_created counter. resmon_scripts/frontend/src/pages/RoutinesPage.tsx subscribes to useConfigurationsVersion() so the routines list refetches on import without a page reload. No new dependencies; no schema changes.

Public-Facing Documentation Touch-Ups (T-UPD-3)

• README.md — extended the AI-powered summarization Key-Features bullet to mention concurrent per-provider key storage and full per-execution AI override parity across Deep Dive / Deep Sweep / Routines; added a new Cross-platform desktop notifications Key-Features bullet covering macOS / Linux / Windows including the headless-daemon path; verified no other section (installation, supported repositories, operational modes, technology stack) required edits.
• resmon_reports/info_docs/settings_info.md — added the new four-column Stored API Keys table description, click-provider-name-to-set-default semantics, Default badge in Status, Clear default model / Clear API key actions, the ai_default_models map, and the four InfoTooltip additions on the AI panel; clarified the Notifications panel covers all three platforms (with the daemon caveat for app-closed routine notifications) and that Advanced → Background Execution is a precondition for app-closed notifications.
• resmon_reports/info_docs/deep_dive_info.md, deep_sweep_info.md, routines_info.md — replaced the Length/Tone/free-text-Model override description with the full-parity AIOverridePanel description (Provider-aware Model dropdown with Load models, inline API-key entry for missing-key providers, Save as default model); added the panel description to routines_info.md (previously absent).
• resmon_reports/info_docs/configs_info.md — documented the new per-row Edit action and its three modal variants (OOB-9), the stale linked_routine_id 404 fallback (OOB-10), and the import-bidirectional-sync rule from OOB-11; added the routines_created response field to the /api/configurations/import description.
• resmon_reports/info_docs/routines_info.md — also noted that routine rows can now appear via Configurations-page imports (deactivated by default) in addition to the Create-modal path, and that the page subscribes to the configurations bus so imports surface without a reload.
• resmon_reports/info_docs/calendar_info.md — updated the Event Styling paragraph for week/day views to describe the new dot+type-colored-text rendering.

App Version Bump

• resmon_scripts/implementation_scripts/config.py — APP_VERSION bumped from "1.0.0" to "1.1.0" (minor: new user-visible features under a stable major).
• resmon_scripts/frontend/package.json — "version" bumped from "1.0.0" to "1.1.0" to match.
• resmon_scripts/frontend/src/components/Settings/AboutAppSettings.tsx — added a Recent Update card to the about-grid summarizing this update by number, name, and one-paragraph summary; the version line continues to read from /api/health so it tracks APP_VERSION automatically.

Verification

Test Suites Run

The Python suite (pytest) was executed from the repository root inside the project’s .venv after every batch and every OOB change:

source .venv/bin/activate
pytest resmon_scripts/verification_scripts/ -q

• Batch 1 (Calendar): frontend webpack production build → webpack 5.106.2 compiled successfully; manual UI smoke confirmed dot+type-colored-text rendering on dayGridMonth, timeGridWeek, and timeGridDay, and that no background fill is applied to week/day events.
• Batch 2 (Notifications): notification-dispatcher unit tests → green; manual smoke (a) app open, manual Dive completion notification fires; (b) app open, routine completion notification fires; (c) app closed under macOS launchd-managed daemon, routine completion notification fires. Linux (systemd --user) and Windows (Task Scheduler) verified via the dispatcher entry-point unit tests plus the written manual-verification checklist where the dev machine could not natively exercise both OSes.
• Batch 3 (Multi-provider keys): credential_manager unit tests for per-provider naming and migration idempotency → green; /api/credentials route tests → green; AI factory provider-selection test → green; first-launch migration test against a synthetic legacy keyring entry → green.
• Batch 4 (Override parity + tooltips): AI execution-settings merge tests (per-execution per-field overrides do not write back to the persisted Settings → AI row) → green; routine-creation tests carrying override settings end-to-end → green; frontend webpack production build → green; one end-to-end smoke run on each of Dive / Sweep / Routine with one non-default override field populated and the others left blank confirmed per-field merge.
• OOB-1..OOB-11: webpack production build run after each OOB change → compiled successfully at every step. Backend Python unit tests for the credential-manager / settings paths remained green throughout. Backend curl round-trip on PUT /api/settings/ai confirmed ai_default_models persists across PUT/GET (after the stale-daemon caveat in OOB-5 was applied). Manual UI smoke confirmed: per-provider key storage round-trips; clicking only the Provider name sets the app default and adds the Default badge; Clear default model / Clear API key per-row Actions behave; OOB-6’s race-safe merge accumulates entries across alternating saves from the two surfaces; the override panel’s Load-models / inline-key / Save-as-default flow works on Dive / Sweep / Routines; Configurations Edit modal pre-populates and saves the right endpoint for each of the three config types; the OOB-10 fallback path saves successfully against an imported routine config with a stale linked_routine_id; and importing a routine config materializes a deactivated routine on the Routines page without reload.
• Final aggregate run at the end of T-UPD-2: pytest resmon_scripts/verification_scripts/ -q → all tests green, no skips beyond pre-existing platform-gated tests (Linux-only / Windows-only systemd and Task Scheduler integration paths are skipped on macOS by design and were exercised through the manual checklist instead).

Skipped-Test Rationale

• The platform-gated Linux systemd --user and Windows Task Scheduler integration tests are skipped on macOS by their existing pytest.mark.skipif guards. They were exercised manually against the platform-specific service templates per the workflow’s manual-verification checklist; no test was disabled or deleted.

Build Verification

• Frontend: npm run build (production webpack) ran clean after each batch and after each OOB change.
• Backend: python -c "import resmon_scripts.resmon" and the daemon attach path ran clean after every backend touch; [main] Attached to existing resmon-daemon on port 8742 confirmed at the end of T-UPD-2.

Follow-ups

• Stale-daemon advisory (OOB-5). Users upgrading from a build that predates ai_default_models must restart any long-lived resmon-daemon process so the new settings-allowlist entry is picked up. The behavior is silent-drop, not error, on the old daemon. Consider adding a startup version check in a future update so the renderer can warn when the attached daemon is older than the renderer.
• Linux / Windows live-OS verification. Cross-platform parity for desktop notifications is covered by unit tests + the manual checklist; live-OS smoke runs on a Linux box and a Windows box are still recommended in a follow-up update once that hardware is available.
• Configurations-page edit history. OOB-9’s Edit modal saves immediately; an undo / “revert to last saved” affordance was discussed but deferred — call it out as a candidate enhancement for a future update.
• Per-paper artifact retention (Settings → Storage PDF / TXT retention policies) remains reserved for a future per-paper artifact-download feature; this update does not exercise that surface.

Metadata

• Update number: 1
• Update type: mixed (bugfix + feature)
• Date: 2026-04-24
• Author: Ryan Kamp
• Commit hash: 707c07221f607297a7a919bd3f4d527a968832c8
• Commit timestamp: 2026-04-25T03:01:35-04:00
• GitHub push timestamp: 2026-04-25T07:01:45Z

Summary

This update ships the first post-release change set for resmon. It fixes a frontend cache-staleness bug where deleted manual_dive / manual_sweep configurations continued to appear in the Deep Dive and Deep Sweep Load Configuration dropdowns, and it introduces a “Query Keyword Transparency” feature that surfaces, on every page where a user picks repositories, exactly how each repository’s upstream API combines space-separated keywords. The feature also adds a consolidated, grouped, color-coded glossary on the Repositories & API Keys page and per-repository keyword-combination metadata in the catalog and on .ai/prep/repos.csv. Per-repository research replaces the previously lumped row for SSRN, RePEc, PLOS, DBLP, and IEEE Xplore (SSRN and RePEc are not in the active catalog and were therefore not added; PLOS, DBLP, and IEEE were classified individually).

Motivation

Both items in this update originated in the user’s first-after-release feedback session and map back to the change inventory in .ai/updates/update_4_24_26/update_4_24_26_workflow.md:

• Bug — Improper Config Deletion (workflow item #1, batch 1). After deleting a manual_dive or manual_sweep configuration from the Configurations page, the deleted entry was still selectable in the Load Configuration dropdown on the Deep Dive and Deep Sweep pages and could still auto-populate the form. The Routines page was unaffected. Root cause: the shared ConfigLoader only refetched on its configType / refreshKey props, neither of which changed when a deletion happened on a different page; there was no cross-page invalidation channel.
• Feature — Query Keyword Transparency (workflow item #2, batch 2). Users had no in-app indication of how each repository’s upstream API combines keywords (some are implicit AND, some are implicit OR, several are relevance-ranked Lucene/Solr backends). The user requested per-repo banners on Deep Dive, Deep Sweep, and Routines, an enriched expander plus a glossary on the Repositories & API Keys page, the same metadata in .ai/prep/repos.csv, and individual research for the lumped row in .ai/prep/keyword_booleans_overview.md.

Changes

Batch 1 — Improper Config Deletion (cluster, shared root cause)

• resmon_scripts/frontend/src/lib/configurationsBus.ts (new, 33 lines) — tiny in-renderer pub/sub bus with notifyConfigurationsChanged() and useConfigurationsVersion() so any mutation site can invalidate every mounted ConfigLoader without page-to-page coupling.
• resmon_scripts/frontend/src/components/Forms/ConfigLoader.tsx — subscribe to the bus via useConfigurationsVersion() and add the version to the fetch effect’s dependency array so deletions, saves, and imports anywhere in the app force a refetch.
• resmon_scripts/frontend/src/pages/ConfigurationsPage.tsx — call notifyConfigurationsChanged() after a successful delete and after a successful import.
• resmon_scripts/frontend/src/pages/DeepDivePage.tsx — call notifyConfigurationsChanged() after a successful “Save Configuration” so newly saved rows immediately appear in sibling loaders.
• resmon_scripts/frontend/src/pages/DeepSweepPage.tsx — same notify-on-save wiring as Deep Dive.

Batch 2 — Query Keyword Transparency (single feature)

• resmon_scripts/implementation_scripts/repo_catalog.py — add keyword_combination and keyword_combination_notes fields to RepoCatalogEntry and populate them for all 16 active repositories, using “Implicit AND”, “Explicit OR”, “Relevance-ranked”, or “Relevance-ranked (… upstream-default, unverified)” labels per the workflow’s uncertainty policy. DBLP, IEEE Xplore, and PLOS are individually classified (replacing the previously lumped row); SSRN and RePEc are not in the active catalog and were therefore not added.
• resmon_scripts/verification_scripts/test_repo_catalog.py — extend expected_keys and add test_keyword_combination_populated_for_every_active_repo.
• resmon_scripts/frontend/src/api/repositories.ts — extend the RepoCatalogEntry TypeScript interface with the two new optional fields.
• resmon_scripts/frontend/src/components/Forms/KeywordCombinationBanner.tsx (new, 42 lines) — compact banner mounted under the repository selector on Deep Dive, Deep Sweep, and Routines that shows the keyword-combination label and notes for each currently selected repository, with a tooltip pointing to the consolidated glossary.
• resmon_scripts/frontend/src/components/Repositories/KeywordSemanticsGlossary.tsx (new, 182 lines) — consolidated, expandable glossary on the Repositories & API Keys page. Three categories (“Boolean combination”, “Ranking & confidence”, “Underlying search platforms”), each rendered as a color-accented section with a card grid of color-coded badge + short label + definition for every term (“Implicit AND”, “Explicit AND”, “Implicit OR”, “Explicit OR”, “Relevance-ranked”, “upstream-default, unverified”, “Lucene”, “Solr”). Iterated through three visual formats during review; final layout is the grouped card-grid format.
• resmon_scripts/frontend/src/components/Repositories/RepoDetailsPanel.tsx — render the new “Effective Default Keyword Combination” and “Keyword Combination Notes” rows in the per-repo expander.
• resmon_scripts/frontend/src/pages/DeepDivePage.tsx — mount KeywordCombinationBanner for the selected single repository.
• resmon_scripts/frontend/src/pages/DeepSweepPage.tsx — mount KeywordCombinationBanner for each selected repository.
• resmon_scripts/frontend/src/pages/RoutinesPage.tsx — mount KeywordCombinationBanner in the Create/Edit modal for each selected repository.
• resmon_scripts/frontend/src/pages/RepositoriesPage.tsx — mount KeywordSemanticsGlossary above the catalog table.
• .ai/prep/repos.csv (internal scaffolding, not tracked by git) — extended with keyword_combination and keyword_combination_notes columns mirroring the catalog entries; per the user’s directive this file is enriched in place rather than relocated.

Out-of-Band Additions (T-UPD-ADD)

None.

Verification

• Backend unit tests: python -m pytest resmon_scripts/verification_scripts/test_repo_catalog.py -q → 10 passed in 0.02s. Includes the new test_keyword_combination_populated_for_every_active_repo and the extended test_catalog_as_dicts_shape expected_keys set.
• Frontend production build: npm run build:renderer (run from resmon_scripts/frontend/) → webpack 5.106.2 compiled successfully in 5111 ms after batch 2’s components were finalized. Re-run after each visual iteration of the glossary; final iteration also compiled cleanly.
• Manual UI verification: the live Electron app (attached to the running daemon on 127.0.0.1:8742) was used to verify (a) deleting a manual_dive config from the Configurations page makes it disappear from the Deep Dive Load Configuration dropdown without a reload, and the same for manual_sweep on the Deep Sweep page; (b) the keyword-combination banner appears under the repository selector on Deep Dive, Deep Sweep, and the Routines create/edit modal, and lists one row per selected repository with the correct label; (c) the consolidated glossary on the Repositories & API Keys page expands, renders three category sections with colored accents, and shows every defined term as a card; (d) each row in the catalog table exposes the two new entries in its expander.
• Skipped tests: none. No frontend Jest suite was run because the project does not currently maintain one for these surfaces; manual UI verification is the existing standard for renderer-only changes.

Follow-ups

• Optional: add a Playwright/Jest smoke test for ConfigLoader cross-page invalidation so future regressions are caught without manual reproduction.
• Optional: confirm the “upstream-default, unverified” labels for DBLP, IEEE Xplore, and PLOS by directly probing each upstream search box; promote the labels to the unqualified form once verified.
• The cloud catalog mirror (if/when the cloud service serializes the catalog independently) will need the two new fields surfaced in its /api/v2/repositories/catalog response; not in scope for this update.

The blog is also surfaced inside the resmon app itself, on the About resmon → Blog tab. The in-app reader fetches this site’s feed at /feed.xml and renders the post list directly from it, so any post published here appears in the app on the next tab open without an app re-release.

Thanks for reading.