Repository navigation
Conversation
timeline/alerts (read-only) folds the current window into an alert set: a
Bot that fails most of its turns (errors), a request left unanswered
(waiting) or a handoff waiting too long (stuck) opens ONE alert, not one
per poll, and the alert resolves when the condition clears. The answer is
{ open, resolved, changed }, so a panel or a routine sees what is wrong
and since when without re-deriving it every request.
Collaborator
|
Closed by the maintenance round against the owner's admission line (2026-10-21): a PR is opened and merged only for (1) a fix of a reproducible real defect, or (2) something the routine work itself needs. Pure UX work, new configuration keys and design proposals are not queued at all. Durable alert state is a new capability of the timeline (a new endpoint with its own open/resolve bookkeeping), not a fix for a reproducible defect: the panel and a routine could already derive the current condition from the window, and nothing misbehaves today. No routine depends on it. Kept as a record; the branch stays. If the owner wants an alerting layer, say so and it can come back as one of the two admitted kinds. |
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
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.
Timeline: durable alerts (open once, resolve when cleared)
The timeline drew failures and waits, but nothing kept state, so a routine or a panel re-derived "is something wrong" on every request and could not say since when.
timeline/alerts(read-only) now folds the current window into a durable alert set: a Bot that fails most of its turns (errors), a sent request left unanswered (waiting) or a handoff waiting too long (stuck) opens ONE alert — not one per poll — and the alert resolves when the condition clears. The answer is{ open, resolved, changed }.Ran at the tip:
npm run verify(green,TZ=UTC),node scripts/lint-plugins.mjs timeline(0 errors). Not run: smoke, Desktop, real-model steward.