Repository navigation
Alert tracer: Bot work failures reuse the configured management route #1041
Description
Parent
What to build
A Human enables PersonaBot work-failure alerts on the existing named management route and receives an honest automatic alert after a canonical failure.
Shared routing boundary
Use the same explicit management destination and checked delivery lifecycle as formal questions/approvals under #1019. Route visibility and decision authority remain separate: a failure alert grants no Answer, Approve or rule-saving capability. Do not create a separate destination registry, permission system or Profile settings surface. Source community X need not be the alert destination Y; public chats receive no private operational detail implicitly.
#1029 is the delivered prerequisite. #1034 qualifies Lark group targets; #1042/#1046 qualify additional providers. This alert slice does not claim unqualified group/provider support or implement native non-blocking waits (#1036–#1039).
Acceptance criteria
- Provide an explicit event-type control, test send and delivery state in the existing Bot DM Channel sidebar management surface (Spec: Profile shows shareable identity and activity; Bot and Group configuration moves into the Channel sidebar #1083); the model cannot change the route.
- Notify from the owning committed failure fact with stable identity, not generic token stream/output or aggregate attention counts.
- Reuse finite known-unsent retry, duplicate suppression and Unknown Outcome inspection without granting approval or blocking unrelated work.
- Respect route disable/unbind, provider identity replacement and content visibility; do not include credentials or private payloads in public alerts.
- Demonstrate an actual isolated Bot work failure, notification receipt and unavailable destination through the real UI.
- Host/VPS-down monitoring remains independently owned and outside this slice; never borrow another Bot’s sender credentials.
- Test through checked Provider and authenticated management/owning service boundaries; keep existing canonical persistence and no parallel content/decision authority.
- Retain real sanitized screenshots/step evidence and maintain the affected English/Chinese tutorial section; UI changes include matched baseline/changed light/dark evidence and no private secrets.
- Provide the exact-version runnable review path and focused behavioral coverage; pause for Human QA before expansion, without automatic merge/deployment.
Delivery evidence
Human accepted the first private-Lark slice. Native negative checks for event-off and destination-off passed; restoring the route/model produced a healthy fresh reply without notice replay. The task receiver is stopped and QA1 window released.
- PR: feat: notify committed Bot work failures on management DM #1468 (merged as
def31a2ee80e487105d36d2dcea198a4b25c5688from accepted source8b64c81eb8fad3c94e14fbc362043eb9cd186cfe; exact-head CI passed). - Complete QA path, canonical correlation and limits.
- Matched base/head light/dark and short-screen UI, genuine failure/unavailable state, real Lark notices and accepted/disabled sidebar screenshots are embedded in the PR body. The final 11 embedded images were verified loaded in GitHub through the restored native preview. Human accepted the revised wide two-column UI.
- Focused automated coverage includes actual deadline expiry, Provider replacement, unknown outcome and persisted restart recovery. These fault races are automated coverage, not a claim of native Lark fault injection.
- Spec/Standards review: no findings; final merge preserves Alert tracer: Bot work failures reuse the configured management route #1041 implementation. Generation 83 rollback needs a compatible writer or pre-upgrade backup. PR merged after explicit Human authorization; no deployment or qualification of group/other providers/Host-down monitoring.
Activity
[-]Alert tracer: PersonaBot work failures use the configured management route[/-][+]Alert tracer: Bot work failures reuse the configured management route[/+]DoodleBears commentedon Oct 12, 2026
Agent work claim
codex/local/01a12734-8226-7ae3-8d1b-db08bde64d76(not a DSH Session)codex/1041-work-failure-alerts29 remaining items
DoodleBears commentedon Oct 12, 2026
Agent work claim — final notification UI evidence and main conflict resolution
codex/local/01a12734-8226-7ae3-8d1b-db08bde64d76(not a DSH Session).codex/1041-work-failure-alerts.Merge current main while preserving notification and file-open ledgers
docs: publish final notification modal captures and provenance
docs: record exact-head CI and explainer inspection for 1468
docs: crop empty history evidence and record GitHub rendering check
DoodleBears commentedon Oct 12, 2026
Agent work handoff — final UI ready for Human feedback
codex/local/01a12734-8226-7ae3-8d1b-db08bde64d76.8b64c81eb8fad3c94e14fbc362043eb9cd186cfe.docs: record Human acceptance of notification modal revision
DoodleBears commentedon Oct 12, 2026
Human acceptance — revised notification modal ready for review
Task:
codex/local/01a12734-8226-7ae3-8d1b-db08bde64d76; PR #1468 head8b64c81eb8fad3c94e14fbc362043eb9cd186cfe.Human accepted the new wide two-column notification layout and interaction after the final screenshots and runtime UI verification. This closes the revised-UI feedback gate; the earlier accepted native private-Lark checks retain their original ad7c204 provenance.
PR #1468 is now ready for review. Exact-head CI passed; mergeability and current checks were rechecked. No merge or deployment was performed. Issue remains open / Project In Progress until merge, and QA1 receiver/window remains stopped/released.
Updated head-bound public HTML · Final verification and accepted feedback. This refresh supersedes the prior pending-feedback wording; only acceptance status changed, and the previously inspected page structure is preserved.
The preserved mobile observer/desktop-marker limitation and soft desktop raster remain disclosed. Current notification delivery supports one qualified Lark management DM; #1492 remains the unclaimed native-blocked multi-target follow-up.
DoodleBears commentedon Oct 12, 2026
Agent work completed — merged after Human authorization
codex/local/01a12734-8226-7ae3-8d1b-db08bde64d76.def31a2ee80e487105d36d2dcea198a4b25c5688; reviewed source head8b64c81eb8fad3c94e14fbc362043eb9cd186cfe.