mirror of
https://github.com/lobehub/lobehub
synced 2026-04-21 09:37:28 +00:00
8b3c871d08
* ♻️ refactor(onboarding): add OnboardingContextInjector and wire context engine Made-with: Cursor * 🔧 refactor(onboarding): update tool call references to use `lobe-user-interaction________builtin` Modified onboarding documentation and utility functions to standardize the use of the `lobe-user-interaction________builtin` tool call for structured input collection, enhancing clarity and consistency across the codebase. Signed-off-by: Innei <tukon479@gmail.com> * 🔧 refactor(onboarding): standardize tool call references to `lobe-user-interaction____askUserQuestion____builtin` Updated documentation and utility functions to replace instances of the `lobe-user-interaction________builtin` tool call with `lobe-user-interaction____askUserQuestion____builtin`, ensuring consistency in structured input collection across the onboarding process. Signed-off-by: Innei <tukon479@gmail.com> * ♻️ refactor(onboarding): move onboarding context before first user * ♻️ refactor(context-engine): add virtual last user provider * update v3 * 🐛 fix(onboarding): add early exit escape hatch for boundary cases The `<next_actions>` directive only prompted finishOnboarding in the summary phase, but phase transition required all fields + 5 discovery exchanges — a condition extreme cases rarely meet. This left the model stuck in discovery, never calling finishOnboarding. - Add EARLY EXIT hint in discovery phase next_actions - Add universal completion-signal REMINDER across all phases - Add minimum-viable discovery fallback in systemRole - Add explicit completion signal list in Early Exit section - Add off-topic redirect limit in Boundaries - Add CRITICAL persistence rule in toolSystemRole * ✅ test(context-engine): fix OnboardingContextInjector tests to match BaseFirstUserContentProvider Remove brittle MessagesEngine onboarding test that hardcoded XML content. --------- Signed-off-by: Innei <tukon479@gmail.com>
8.3 KiB
8.3 KiB
Team Assignment Guide
Quick Reference by Name
- @arvinxx: Last resort only, mention for priority:high issues, tool calling, mcp, database
- @canisminor1990: Design, UI components, editor, markdown rendering
- @tjx666: Image/video generation, vision, cloud version, documentation, TTS, auth, login/register, database
- @ONLY-yours: Performance, streaming, settings, general bugs, web platform, marketplace, agent builder, schedule task
- @Innei: Knowledge base, files (KB-related), group chat, Electron, desktop client, build system
- @nekomeowww: Memory, backend, deployment, DevOps, database
- @sudongyuer: Mobile app (React Native)
- @sxjeru: Model providers and configuration
- @rdmclin2: Team workspace, IM and bot integration
- @tcmonster: Subscription, refund, recharge, business cooperation
Quick reference for assigning issues based on labels.
Label to Team Member Mapping
Provider Labels (provider:*)
| Label | Owner | Notes |
|---|---|---|
All provider:* |
@sxjeru | Model configuration and provider integration |
Platform Labels (platform:*)
| Label | Owner | Notes |
|---|---|---|
platform:mobile |
@sudongyuer | React Native mobile app |
platform:desktop |
@Innei | Electron desktop client, build system |
platform:web |
@ONLY-yours | Web platform (unless specific feature) |
Feature Labels (feature:*)
| Label | Owner | Notes |
|---|---|---|
feature:image |
@tjx666 | AI image generation |
feature:dalle |
@tjx666 | DALL-E related |
feature:vision |
@tjx666 | Vision/multimodal generation |
feature:knowledge-base |
@Innei | Knowledge base and RAG |
feature:files |
@Innei | File upload/management (when KB-related) @ONLY-yours (general files) |
feature:editor |
@canisminor1990 | Lobe Editor |
feature:markdown |
@canisminor1990 | Markdown rendering |
feature:auth |
@tjx666 | Authentication/authorization |
feature:login |
@tjx666 | Login issues |
feature:register |
@tjx666 | Registration issues |
feature:api |
@nekomeowww | Backend API |
feature:streaming |
@arvinxx | Streaming response |
feature:settings |
@ONLY-yours | Settings and configuration |
feature:agent |
@ONLY-yours | Agent/Assistant |
feature:topic |
@ONLY-yours | Topic/Conversation management |
feature:thread |
@arvinxx | Thread/Subtopic |
feature:marketplace |
@ONLY-yours | Agent marketplace |
feature:tool |
@arvinxx | Tool calling |
feature:mcp |
@arvinxx | MCP integration |
feature:search |
@ONLY-yours | Search functionality |
feature:tts |
@tjx666 | Text-to-speech |
feature:export |
@ONLY-yours | Export functionality |
feature:group-chat |
@arvinxx | Group chat functionality |
feature:memory |
@nekomeowww | Memory feature |
feature:team-workspace |
@rdmclin2 | Team workspace application |
feature:im-integration |
@rdmclin2 | IM and bot integration (Slack, Discord, etc.) |
feature:agent-builder |
@ONLY-yours | Agent builder |
feature:schedule-task |
@ONLY-yours | Schedule task |
feature:subscription |
@tcmonster | Subscription and billing |
feature:refund |
@tcmonster | Refund requests |
feature:recharge |
@tcmonster | Recharge and payment |
feature:business |
@tcmonster | Business cooperation and partnership |
Deployment Labels (deployment:*)
| Label | Owner | Notes |
|---|---|---|
All deployment:* |
@nekomeowww | Server/client/pglite modes |
Hosting Labels (hosting:*)
| Label | Owner | Notes |
|---|---|---|
hosting:cloud |
@tjx666 | Official LobeHub Cloud |
hosting:self-host |
@nekomeowww | Self-hosting issues |
hosting:vercel |
@nekomeowww | Vercel deployment |
hosting:zeabur |
@nekomeowww | Zeabur deployment |
hosting:railway |
@nekomeowww | Railway deployment |
Issue Type Labels
| Label | Owner | Notes |
|---|---|---|
| 💄 Design | @canisminor1990 | Design and styling |
| 📝 Documentation | @canisminor1990 / @tjx666 | Official docs website issues |
| ⚡️ Performance | @ONLY-yours | Performance optimization |
| 🐛 Bug | (depends on feature) | Assign based on other labels |
| 🌠 Feature Request | (depends on feature) | Assign based on other labels |
Assignment Rules
Priority Order (apply in order)
- Specific feature owner - e.g.,
feature:knowledge-base→ @RiverTwilight - Platform owner - e.g.,
platform:mobile→ @sudongyuer - Provider owner - e.g.,
provider:*→ @sxjeru - Component owner - e.g., 💄 Design → @canisminor1990
- Infrastructure owner - e.g.,
deployment:*→ @nekomeowww - General maintainer - @ONLY-yours for general bugs/issues
- Last resort - @arvinxx (only if no clear owner)
Special Cases
Multiple labels with different owners:
- Mention the most specific feature owner first
- Mention secondary owners if their input is valuable
- Example:
feature:knowledge-base+deployment:server→ @RiverTwilight (primary), @nekomeowww (secondary)
Priority:high issues:
- Mention feature owner + @arvinxx
- Example:
priority:high+feature:image→ @tjx666 @arvinxx
No clear owner:
- Assign to @ONLY-yours for general issues
- Only mention @arvinxx if critical and truly unclear
Comment Templates
Single owner:
@username - This is a [feature/component] issue. Please take a look.
Multiple owners:
@primary @secondary - This involves [features]. Please coordinate.
High priority:
@owner @arvinxx - High priority [feature] issue.