peter/devclaw-gitea
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
14 Commits 1 Branch 0 Tags
8a79755e4c9f7c9e1fea448fe34991cb0d58af96
Commit Graph

4 Commits

Author SHA1 Message Date
Lauren ten Hoor
8a79755e4c feat: Implement GitLabProvider for issue management using glab CLI 
- Add GitLabProvider class for handling issue operations, label management, and MR checks.
- Implement methods for ensuring labels, creating issues, listing issues by label, and transitioning labels.
- Introduce a provider factory to auto-detect GitLab or GitHub based on the repository URL.
- Create project registration tool to validate repositories, create state labels, and log project entries.
- Enhance queue status and session health tools to support new session management features.
- Update task completion and task creation tools to support auto-chaining and improved session handling.
- Refactor task pickup tool to streamline model selection and session management.
 2026-02-09 12:54:50 +08:00
Lauren ten Hoor
d921b5c7bb Refine session management terminology and clarify plugin-controlled lifecycle in documentation 2026-02-08 20:49:44 +08:00
Lauren ten Hoor
e7e61987d4 Replace PM terminology with orchestrator/session model across docs 
- Add "Agents vs Sessions" explainer section to ARCHITECTURE.md
- Replace all "PM Agent" references with "Orchestrator" in sequence diagrams
- Fix ticket creation: agents create issues via glab, not humans
- Update scope boundaries to show sub-agent session responsibilities
- Clarify plugin returns instructions, agent executes session operations
- Update ONBOARDING.md issue creation to show agent-first workflow

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-02-08 16:30:22 +08:00
Lauren ten Hoor
9195c4be7f Add ONBOARDING.md and ARCHITECTURE.md docs 
ONBOARDING: Step-by-step setup guide — prerequisites, plugin install,
agent config, GitLab labels, project registration, first test.

ARCHITECTURE: Full component interaction — system overview diagram,
complete ticket lifecycle with sequence diagrams for every phase
(heartbeat → pickup → dev work → complete → QA → pass/fail/refine),
data flow map, scope boundaries, error recovery, file locations.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-02-08 16:12:23 +08:00