Skip to content

list_bots marks a Bot whose send waits for approval - #588

Closed
HugoXK wants to merge 1 commit into
ThinkFlowLab:mainfrom
HugoXK:feat/list-bots-approvals
Closed

HugoXK wants to merge 1 commit into
ThinkFlowLab:mainfrom
HugoXK:feat/list-bots-approvals

Conversation

@HugoXK

@HugoXK HugoXK commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

list_bots marks a Bot whose send waits for approval

A Bot whose outbound message is held for the owner's approval looked idle to a coordinator. list_bots now marks such a Bot with a count (for example Chief (Boss, 1 to approve, Main Bot, you)), so a Main Bot can see who is blocked on the owner. The tag is a count only — never the held message text.

Ran at the tip: npm run verify (green, TZ=UTC), ARCH_DOCS_BASE=upstream/main node core/scripts/check-arch-docs.mjs. Not run: smoke, Desktop, real-model steward.

…follow-up)

A Bot with an outbound send held for the owner's decision is marked in
list_bots with a count (1 to approve), so a coordinator can see who is
blocked; the tag is a count only, never the held text.
@Birfy

Birfy commented Oct 21, 2026

Copy link
Copy Markdown
Collaborator

Closed by the maintenance round against the owner's admission line (2026-10-21): a PR is opened and merged only for (1) a fix of a reproducible real defect, or (2) something the routine work itself needs. Pure UX work, new configuration keys and design proposals are not queued at all.

This surfaces a signal (a count of held sends in list_bots). It is useful, but it is not a fix: the held send is already reported through the approval card and the task state, and the coordinator seeing a count is a comfort improvement rather than a reproducible defect. No routine depends on the count.

Kept as a record; the branch stays, and the change is small enough to re-open unchanged if the line widens.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants