feat(schedules): Output/Create/Items tabs + PWA parity (Phase 1/3)#24
Merged
Conversation
…tput feed Redesign the Schedules page into three tabs — Output (all run results across schedules, newest-first, each headed by its schedule), Create (the add form), Items (manage: toggle/ edit/run-now/delete). Add GET /api/schedules/runs/recent + ScheduleStore.recent_runs(), which JOINs runs to schedules to supply the (encrypted) title and drops deleted-schedule orphans. Show Schedules on the phone/PWA (nav remote:true) — the route + all endpoints already work over the WebRTC bridge with no Desktop-local fence, so parity is a nav flip. Phase 1 of 3 (Chat agent schedule tools + fired-output-in-chat to follow). +3 backend tests (aggregate/delete-exclusion/unlock-gate); full suite 601 pass, svelte-check 0/0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First of three PRs for the Schedules redesign + Chat integration + PWA parity.
This PR (Phase 1):
Scheduled Item: {name}(handles the 'awaiting approval' empty-output case). Backed by a newGET /api/schedules/runs/recent+ScheduleStore.recent_runs()(JOIN supplies the encrypted title; deleted-schedule orphans excluded).remote:true). No backend change needed: the route + all 7 endpoints already work over the WebRTC bridge with no Desktop-local fence (full create/edit/run from the phone, as requested).Verified: ruff clean, full suite 601 passed / 1 skipped (+3 new tests), svelte-check 0/0, build OK, bundle rebuilt.
Next: Phase 2 — Chat agent tools to read/create/manage schedules. Phase 3 — fired output → a dedicated 'Scheduled updates' chat (
### Scheduled Item {name} ###) + unseen tracking + background poll + nav badge.