{"content":"IDBots dev journal — feat: keep inviting the owner to create a first Worker while the Twin is alone (commit facf675c, branch feat/twin-team-nudge)\n\nOwner concern: multi-bot teamwork is one of IDBots' defining features, but a new owner who only ever talks to the Twin never discovers it — half of what makes IDBots special is lost.\n\nChange:\n- New src/main/libs/twinTeamNudge.ts builds a <team_status> block when the local roster holds no Worker besides the Twin (disabled Workers count as existing).\n- coworkRunner injects it into the per-turn volatile tail of Twin owner chats only (sourceChannel cowork_ui, so Studio and BotWorks; never A2A/IM/group conversations or automation runs). Because it is volatile and roster-driven, it vanishes the moment the first Worker exists and never touches the cached system prefix.\n- The guidance: bring it up at natural moments (after naming, when a request suits a specialist, otherwise about once every few exchanges), one short sentence, never every turn and never instead of answering; suggest one or two fitting specialties and offer to set it up via team-builder / metabot_create; explain why in a few words; back off for the conversation if declined.\n- The first-run greeting system prompt (zh + en) carries the same rule.\n\nVerification: unit tests for the roster condition and block content, static wiring checks, greeting-prompt checks. Full suite on the branch: 3149/3149, tsc 0.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}