3.2 KiB
Independent schedules and navigation — 2026-10-21
Saved schedules now pair a pinned workflow version with complete run information and an independent timer. Multiple topics/prompts reuse one workflow. Creation keys prevent duplicate timers after lost replies; revision CAS protects edits and deletion. Run-level write restrictions and explicit titles are preserved. Workflow publication remains separate, including on execution-only servers.
The scheduler dispatches external records only, records provenance before the first live run frame, preserves original input and workflow history, and skips missed/conflicting occurrences rather than replaying agent work. Legacy migration is idempotent; trusted runtime startup binds missing legacy workspaces instead of using an offline reader's directory. Deleted or paused schedules do not resurrect.
The web editor supports create/edit/pause/delete, interval/clock rules, timezones, advanced run options and Schedule this run. Pipeline filters mean configured schedules, including paused entries; run filters mean actual timer-origin runs. Manual runs on a configured workflow are not misclassified, and provenance survives deletion. The current-source authoring skill documents the external API instead of teaching embedded schedule blocks.
Run graph clicks now open exactly the Timeline visit pane, selecting the latest recorded visit. Earlier visits remain in Timeline; within-visit messages remain in Session audit. Definition remains an explicit pinned-version audit tab. Chat rows use a left-before-title harness mark, top-right star and bottom-right more control, with always-visible actions and shared button-state styling.
Verification and deployment
- Full Go race suite, build/vet, web/installer regressions and scratch installer smoke passed; Linux amd64/arm64 server cross-builds passed. Native Linux installation remains a host trial, not established by cross-builds.
- A real scratch Go server/browser verified independent items, both filters, CAS draft retention, run seeding with explicit title/write scope, genuine timer-first-frame provenance and immutable history/source after deletion. Only human stages, explicit titles and notify=off were used; fixture-only NextDue advancement initiated no provider turns or live-user work.
- A private copy of the current database migrated/reopened with its original workflow-version, run, step, legacy state and event row values unchanged.
- Browser captures cover 390/420/1100px chat layout/state/hit-tests, schedule dialogs and graph/Timeline equality; capture manifests remain in the approved OpenCode temporary directory rather than exposing private runtime content.
- Clean code
1e4654381e3b788259a8177b9378cc3dcb426dacwas deployed after active-work checks and a SQLite/binary rollback backup. Only Pipelines restarted; existing service arguments, credentials and other harness/notification services remained. - An authenticated live browser verified the saved-schedule API/projection fields, editor availability, requested chat-row geometry and actual run #19 graph/Timeline pane equality. It created no production schedules, runs, workflow versions or provider turns. Shell cache is v13.