assignToGroup cannot create new groups; reportTabs(ungrouped:true) returns 0

[ekroon]

Summary

assignToGroup appears unable to create a new group in the current browser session, returning Group not found, while assigning tabs to an existing group works.

Separately, reportTabs(ungrouped:true) returned zero tabs even when full-window snapshots clearly showed many ungrouped tabs.

Agent-created report: this issue was filed by a coding agent using @ekroon's account after reproducing the behavior during a live browser cleanup session.

Environment

• tabctl base version reported by tabctl ping --json: 0.6.0
• Browser session had multiple windows and both grouped + ungrouped tabs

Reproduction: new group creation fails

I tested with a currently ungrouped tab:

mutation {
  assignToGroup(
    tabIds: [1385025791]
    groupTitle: "🧪 tmp-group-test"
    color: "green"
    collapsed: false
  ) {
    groupId
    title
  }
}

Actual result

{
  "data": null,
  "errors": [
    {
      "message": "Group not found"
    }
  ]
}

Expected result

If groupTitle does not exist in that window, assignToGroup should create the group and assign the tab to it.

Control case: assigning to an existing group works

This succeeded during the same session:

mutation {
  assignToGroup(
    tabIds: [1385025890, 1385025755, 1385025893, 1385025885]
    groupTitle: "📋 Preprod"
    color: "pink"
    collapsed: false
  ) {
    title
  }
}

Reproduction: reportTabs(ungrouped:true) appears broken

At the same time, full-window snapshots from:

query {
  windows {
    windowId
    tabs {
      tabId
      groupTitle
    }
  }
}

showed many ungrouped tabs (groupTitle: null / groupId: -1).

But this query returned zero:

query {
  reportTabs(ungrouped: true) {
    totals {
      tabs
    }
  }
}

Actual result:

{
  "data": {
    "reportTabs": {
      "totals": {
        "tabs": 0
      }
    }
  }
}

Notes

This may be two separate bugs, but both showed up in the same workflow:

• inability to create new groups via assignToGroup
• reportTabs(ungrouped:true) not matching the actual browser state