docs: record independent scheduling and navigation deployment

This commit is contained in:
2026-10-21 02:12:58 +01:00
parent 1e4654381e
commit de987555e9
2 changed files with 54 additions and 0 deletions
@@ -0,0 +1,49 @@
# 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 `1e4654381e3b788259a8177b9378cc3dcb426dac` was 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.
+5
View File
@@ -25,6 +25,8 @@ definition access. Captures: approved OpenCode temporary
`run-graph-visit-captures/`. `test/ui-stage-definition.mjs` retains its source,
missing/loading/error and keyboard checks through the now-explicit run audit.
This supersedes the older run-graph definition-popup default described below.
The deployed authenticated browser also compared run #19's actual graph and
Timeline pane contents successfully, without altering that run or its sessions.
### Independent schedules and provenance filters (2026-10-21)
@@ -52,6 +54,9 @@ human stages, explicit titles, notify=off and a fixture-only NextDue advancement
it initiates no provider turns or live-user runs. Captures:
`schedule-editor-captures/` and `schedule-integration-captures/` under the approved
OpenCode temporary directory. Shell cache v13 refreshes the new modules/styles.
After deployment, authenticated read-only checks verified the schedule API,
typed pipeline/run scheduling metadata and the actual editor. No production
schedule, workflow version or run was created for verification.
### Always-visible chat row actions (2026-10-21)