mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[COORD-000] Create coordinator bot user in Gitea #156

New Issue
Closed
opened 2026-01-31 21:27:31 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-31 21:27:31 +00:00
Owner
Copy Link

Objective

Create the bot user in Gitea that will be assigned to issues to trigger coordinator work.

Implementation Details

  1. Access Gitea admin panel
  2. Create new user:
    • Username: mosaic
    • Email: mosaic@mosaicstack.dev
    • Type: Bot account
    • Permissions: Can comment on issues, close issues, push commits
  3. Generate API token for coordinator to use
  4. Document credentials in secrets vault

Context Estimate

  • Files to modify: 0 (Gitea UI configuration)
  • Implementation complexity: low (5000 tokens)
  • Test requirements: low (5000 tokens)
  • Documentation: light (2000 tokens)
  • Total estimated: 15000 tokens
  • Recommended agent: haiku

Difficulty

low

Dependencies

  • Blocked by: None (foundation task)
  • Blocks: COORD-001 (webhook setup needs bot user)

Acceptance Criteria

  • Bot user exists in Gitea
  • API token generated and stored securely
  • Bot user can be assigned to issues
  • Bot user can comment on issues
  • Bot user can close issues
  • Documented in coordinator.yml.example

Testing Requirements

  • Manual test: Assign issue to @mosaic, verify assignment works
  • Manual test: Comment as @mosaic via API
## Objective Create the bot user in Gitea that will be assigned to issues to trigger coordinator work. ## Implementation Details 1. Access Gitea admin panel 2. Create new user: - Username: mosaic - Email: mosaic@mosaicstack.dev - Type: Bot account - Permissions: Can comment on issues, close issues, push commits 3. Generate API token for coordinator to use 4. Document credentials in secrets vault ## Context Estimate - Files to modify: 0 (Gitea UI configuration) - Implementation complexity: low (5000 tokens) - Test requirements: low (5000 tokens) - Documentation: light (2000 tokens) - **Total estimated: 15000 tokens** - **Recommended agent: haiku** ## Difficulty low ## Dependencies - Blocked by: None (foundation task) - Blocks: COORD-001 (webhook setup needs bot user) ## Acceptance Criteria - [ ] Bot user exists in Gitea - [ ] API token generated and stored securely - [ ] Bot user can be assigned to issues - [ ] Bot user can comment on issues - [ ] Bot user can close issues - [ ] Documented in coordinator.yml.example ## Testing Requirements - Manual test: Assign issue to @mosaic, verify assignment works - Manual test: Comment as @mosaic via API
jason.woltje added the setupp0 labels 2026-01-31 21:27:32 +00:00
jason.woltje added this to the M4.1-Coordinator (0.0.4) milestone 2026-01-31 21:28:42 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label p0 setup
Milestone
No items
No Milestone M4.1-Coordinator (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#156
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?