Skip to content

Tree reorg must MOVE/reparent bots; never rename to 归档- and recreate #452

Closed

Description

@Birfy

Environment

Steps to reproduce

  1. Install / update to main with Tree organizes itself by role: groups under leads, merge, daily tidy, undo #448 (tree self-organization by role).
  2. Have a FlyBot specialist set under Chief (e.g. FlyBot 开发 / 维护 / 测试 / 仓管).
  3. Let reorganization or a Main-Bot "archive" attempt run (full level / tidy / LLM update_bot).
  4. Open the Bot sidebar.

Actual

  • Sidebar shows both FlyBot 开发 and 归档-FlyBot 开发 (same for 维护 / 测试 / 仓管).
  • Reorg / "archive" path effectively renames the old Bot to 归档-… and creates a new Bot with the original name, instead of reparenting the existing Bot.
  • Archived (or 归档-*) Bots still appear in the main Bot list under Chief (tagged or prefixed), so the list doubles.

Expected

  • Tree reorganization moves / reparents existing Bots (set parent); it never renames a Bot to 归档-… and never recreates a same-role Bot to achieve grouping.
  • Archive = tree field archived (+ hide from the default sidebar); chat/memory kept; delete stays the owner's click.
  • Archived Bots (and leftover 归档-* names from tonight) do not show in the main Bot list.
  • One-shot repair restores tonight's 归档-* Bots (strip prefix when the bare name is free; otherwise properly archive+hide the 归档-* duplicate).

Where it sits

Suggested direction

  1. Keep grouping as reparent only (set parent); tests assert Bot names never change during a reorg run.
  2. On archive: set archived and hide from the default sidebar (core hidden / structure include).
  3. One-shot repair for names matching 归档- / Archive- prefixes.
  4. Docs: tree.md Self-organization — move never rename+recreate; archived hidden from main list.

Owner decision (2026-10-19 22:23 Asia/Shanghai)

Reorg must reparent existing bots; never rename-old-to-归档- + create new; archived must not show in the main bot list; repair tonight's 归档-* bots.

Activity

  1. added
    bugSomething isn't working
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    area:automationScheduled tasks and automation
    on Oct 19, 2026
  2. Birfy commented on Oct 19, 2026

    @Birfy
    CollaboratorAuthor

    Owner decision (2026-10-19 22:23 Asia/Shanghai): recorded.

    Tree reorganization must MOVE / reparent existing Bots (change parent only). It must never:

    1. rename an old Bot to 归档-… / Archive-…, then
    2. create a new Bot with the original name.

    Archive means the tree field archived (chat and memory kept; delete stays the owner's click). Archived Bots must not appear in the main Bot list. Repair tonight's leftover 归档-* names in the same change.

    Implements the sidebar-hide piece that #450 item 4 deferred. Labels: bug + area:automation + agent-ready.

  3. removed
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    on Oct 21, 2026
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 automationbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions