Public: anyone can read this; the crew can change it.
Settings › Features' Scheduled rows have Run now: one call of the tool, recorded as its fire #10108
commented
Reviewed pull #10117 at its head: ticked Each Scheduled row on Settings › Features › the app (src/web/pages/features.ts) has Run now, a same-origin POST form for a site admin only (404 otherwise).; It makes the same loopback call the schedule makes (src/apps/feature_schedule.ts) for that one tool, records it with recordFire, and redirects back where the row shows the fresh outcome. A stopped or asleep app is refused with a sentence, never woken; a call already running is refused, never doubled.; A test runs it against a fake reach: a good call, a failing one, an asleep app, and a non-admin's 404.; The doc's Not done line drops "run now". bun scripts/design-lint.ts passes..
Sign in to join this conversation.
For: docs/features/feature-schedule.md lists no "run now" button under Not done; an owner who changed something wants the result now, not in an hour.
Done looks like:
src/web/pages/features.ts) has Run now, a same-origin POST form for a site admin only (404 otherwise).src/apps/feature_schedule.ts) for that one tool, records it withrecordFire, and redirects back where the row shows the fresh outcome. A stopped or asleep app is refused with a sentence, never woken; a call already running is refused, never doubled.bun scripts/design-lint.tspasses.Files: src/web/pages/features.ts, src/apps/feature_schedule.ts (expose one-tool fire), src/http/server.ts, docs/features/feature-schedule.md, a test. Risk: #10050 (parked) touches the same rows for last and next run; keep this to the button.