huskies: accept 481_bug_scaffold_does_not_copy_agent_definitions_from_project_toml_to_new_projects

2026-04-07 15:11:57 +00:00
parent fa5885154b
commit 61a8f0edca
3 changed files with 0 additions and 68 deletions
@@ -1,34 +0,0 @@
---
-name: "Status traffic light dots use unsupported HTML colouring - switch to emoji"
---
-
-# Bug 495: Status traffic light dots use unsupported HTML colouring - switch to emoji
-
-## Description
-
-The status command uses Unicode dots (●, ◑, ✗, ○) with `<font data-mx-color>` HTML tags for colouring. Element X (and most modern Matrix clients) doesn't support inline text colouring via any HTML method — not `data-mx-color`, not `style="color:"`, nothing.
-
-Switch to coloured emoji which render natively in all clients:
- 🟢 running normally (was ● green)
- 🟠 throttled/rate limited (was ◑ orange)  
- 🔴 blocked (was ✗ red)
- ⚪ idle / no agent (was ○ grey)
-
-Remove the `build_pipeline_status_html` colour-wrapping logic since it's dead code with emoji.
-
-## How to Reproduce
-
-1. Run `@timmy status` in Element X
-2. Observe dots are not coloured
-
-## Actual Result
-
-Plain uncoloured Unicode dots.
-
-## Expected Result
-
-Coloured indicators visible in all Matrix clients.
-
-## Acceptance Criteria
-
- [ ] Bug is fixed and verified
@@ -1,34 +0,0 @@
---
-name: "Hard rate limit without reset_at never auto-schedules retry"
---
-
-# Bug 496: Hard rate limit without reset_at never auto-schedules retry
-
-## Description
-
-When the API returns a hard rate limit block (`status=rejected`) without a `reset_at` timestamp, `pty.rs` downgrades it to a `RateLimitWarning` instead of a `RateLimitHardBlock`. The auto-scheduler only listens for `RateLimitHardBlock` events, so no timer is set and the agent is never restarted. The agent sits idle until the 300s inactivity timeout kills it, and the story is stuck.
-
-In practice, most hard blocks come without `reset_at` (as seen in the logs: "no reset_at in rate_limit_info"). This means the auto-resume feature from story 423 almost never fires.
-
-Fix: when there's a hard block without `reset_at`, either:
-1. Send `RateLimitHardBlock` with a default backoff time (e.g. `Utc::now() + 5 minutes`)
-2. Or add a separate retry mechanism that doesn't depend on knowing the exact reset time
-
-## How to Reproduce
-
-1. Run an agent that hits the API rate limit
-2. Observe logs show "no reset_at in rate_limit_info"
-3. Agent gets killed by inactivity timeout
-4. Story sits in current with no agent, never restarted
-
-## Actual Result
-
-Hard block without reset_at is downgraded to RateLimitWarning. No timer set. Agent dies and story is stuck.
-
-## Expected Result
-
-Hard block without reset_at triggers a retry with a default backoff (e.g. 5 minutes). Agent is automatically restarted when the backoff expires.
-
-## Acceptance Criteria
-
- [ ] Bug is fixed and verified