slow4cyl 3cd8feb63c docs(kanban): worker-lifecycle + events table reflect the bounded protocol-violation retry ... Fold in kevinb361's suggested lifecycle wording (#61817 conceded in favor of this PR) and update the second stale site his sweep didn't cover: the task-events table still said the dispatcher 'auto-blocks immediately instead of retrying'. Both now describe the violation-only streak: protocol_violation fires on every violation (its payload marker feeds the budget), below-budget runs return the task to ready, and gave_up + auto-block happen only when the consecutive streak reaches _PROTOCOL_VIOLATION_FAILURE_LIMIT (default 3, per-task max_retries overriding).		2026-07-14 16:47:33 +05:30
..
developer-guide	Merge pull request #61885 from embwl0x/agent/tui-secret-overlay-expiry	2026-07-12 05:50:24 -05:00
getting-started	fix(providers): align Fireworks integration with project policy	2026-07-11 05:43:35 -07:00
guides	fix(skills): bind bundles to exact files and origins	2026-07-12 02:59:27 -07:00
integrations	fix(providers): align Fireworks integration with project policy	2026-07-11 05:43:35 -07:00
reference	fix(skills): bind bundles to exact files and origins	2026-07-12 02:59:27 -07:00
user-guide	docs(kanban): worker-lifecycle + events table reflect the bounded protocol-violation retry	2026-07-14 16:47:33 +05:30
index.mdx	feat(docs): clarify platform support	2026-06-26 11:37:56 -07:00
user-stories.mdx	docs(website): add User Stories and Use Cases collage page (#18282)	2026-04-30 23:56:59 -07:00