A chat-kind schedule posts to its chat, and a chat-spawned task posts its outcome back.
Evidence
KindChat (internal/domain/scheduling/jobspec.go:15) and NewChatCourier (crondelivery/runner.go:22) are unused; scheduling.go:77 registers only KindWorkflow.
Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run task check once at the end; if it fails twice on the same problem, comment on this bead and stop.
Stop when
Courier over the messaging contract registered.
Schedules editor offers chat.
Task outcome posted to the originating chat.
Then commit (Conventional Commits, scoped by package), bd close this bead and stop.
Notes
Courier is blocked on the delivery epic (Messaging Service Deliver RPC), not built here. Do the schedules editor chat option and task-origin tracking independently.
Close reason
Deliver RPC and chat schedules shipped in 463f4cd9; outcome post-back split into its own bead
Imported from beads archie-core-mqti.4 · GitHub #1400 · type feature · priority P1 · created 2026-10-05 · closed 2026-10-05
## Goal
A chat-kind schedule posts to its chat, and a chat-spawned task posts its outcome back.
## Evidence
KindChat (internal/domain/scheduling/jobspec.go:15) and NewChatCourier (crondelivery/runner.go:22) are unused; scheduling.go:77 registers only KindWorkflow.
## Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run `task check` once at the end; if it fails twice on the same problem, comment on this bead and stop.
## Stop when
- [ ] Courier over the messaging contract registered.
- [ ] Schedules editor offers chat.
- [ ] Task outcome posted to the originating chat.
Then commit (Conventional Commits, scoped by package), `bd close` this bead and stop.
### Notes
Courier is blocked on the delivery epic (Messaging Service Deliver RPC), not built here. Do the schedules editor chat option and task-origin tracking independently.
### Close reason
Deliver RPC and chat schedules shipped in 463f4cd9; outcome post-back split into its own bead
---
_Imported from beads `archie-core-mqti.4` · GitHub #1400 · type feature · priority P1 · created 2026-10-05 · closed 2026-10-05_
sam
added the highfeature labels 2026-10-27 13:36:05 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
A chat-kind schedule posts to its chat, and a chat-spawned task posts its outcome back.
Evidence
KindChat (internal/domain/scheduling/jobspec.go:15) and NewChatCourier (crondelivery/runner.go:22) are unused; scheduling.go:77 registers only KindWorkflow.
Rules
Read CLAUDE.md. Do only what the Goal and Stop when need. File anything else you notice as a bead; do not fix it. Run
task checkonce at the end; if it fails twice on the same problem, comment on this bead and stop.Stop when
Then commit (Conventional Commits, scoped by package),
bd closethis bead and stop.Notes
Courier is blocked on the delivery epic (Messaging Service Deliver RPC), not built here. Do the schedules editor chat option and task-origin tracking independently.
Close reason
Deliver RPC and chat schedules shipped in 463f4cd9; outcome post-back split into its own bead
Imported from beads
archie-core-mqti.4· GitHub #1400 · type feature · priority P1 · created 2026-10-05 · closed 2026-10-05