Skip to content

task-drive claim/assign never posts the one-line group claim cue the room notice requires #1253

Closed

Description

@Birfy

Observed (prod tip 7fdb8082, 交付组 seq 3112–3171)

Room notice (214 chars) hard-requires one group line when a card is claimed:

接了 #1234,第一步是 <做什么>

In the last 60 messages: 0 lines match 接了\s*#….

Meanwhile bots do claim via track_tasks (cards show actors: claimed/working, notes like「看板卡已开并置 in-progress」) and Chief still @-dispatches in chat. Humans looking only at the room cannot tell who owns what without opening the board — the one public signal the notice asked for never appears.

Desired

When task-drive (or track_tasks claim/assign for a room-origin card) moves a card to claimed/working for a member:

  1. Post exactly one short room line in that member's voice (or as a system/room event), e.g. 接了 #1234,第一步是 … (title/note derived),
  2. Do not open a full group round for that line,
  3. Skip if an identical claim line for that issue/card was already posted recently.

Progress updates stay on the card (per #1205); this is only the public claim beacon.

Acceptance

Evidence

Prod room dump last80 + live tasks on u-682b8a (2026-10-26).

Activity

  1. added
    bugSomething isn't working
    area:socialFriends, invites, grants, Bot Social
    area:automationScheduled tasks and automation
    on Oct 26, 2026
  2. HugoXK commented on Oct 26, 2026

    @HugoXK
    Contributor

    Written-by: Dev-2

    Claimed-by: Dev-2
    Claimed-at: the GitHub created_at of this comment (the box clock runs ~28 minutes ahead)
    Branch: dev2/fix/1253-claim-cue-line
    Base: 0472c1683034d2184c51ec92165ea92e3dde7f36

    Taking #1253: task-drive claim/assign on a card that carries origin.roomId posts one short room line in the member's voice (接了 #1234,第一步是 …) without opening a group round, and does not repeat it on re-claim or progress ticks.

    Timeline read first: no linked pull request, no assignee, no earlier claim (only the three labels from 06:17:53Z). Failing test first, then the fix; I will post the PR number and head sha when it is open, and no PASS request until Dev Lead confirms the tip.

  3. HugoXK commented on Oct 26, 2026

    @HugoXK
    Contributor

    Written-by: Dev-2

    GitHub clock: this claim was posted 11:10:10Z; the Claimed-at: 2026-10-26T11:39:00Z line above is this box's local clock, ~28 min ahead of GitHub. The branch and base in that comment are the ones being worked.

    One more: agent-working cannot be set by this account (403 Must have admin rights to Repository, pull-only identity), so the claim text above is the record that the card is taken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:automationScheduled tasks and automationarea:socialFriends, invites, grants, Bot SocialbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions