shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

feat: queue architecture Phase 1 & 2 + PM verbosity control #51

Closed
shoko wants to merge 0 commits from feature/queue-architecture-verbosity into main
pull from: feature/queue-architecture-verbosity
merge into: shoko:main
Conversation 1 Commits - Files Changed -
shoko commented 2026-03-31 17:10:19 +02:00
Owner
Copy Link

Summary

Phase 1 - Queue Infrastructure (#49)

  • queue.json - Queue storage with 3 tiers
  • enqueue - Add task to queue
  • dequeue - Remove and return next task (priority order)
  • queue-list - List pending tasks

Phase 2 - PM Polling Loop (#49)

  • pm-poll-loop - Continuous polling daemon
  • Priority: dev_followups > user_interrupts > background
  • Configurable poll interval (default 600s)

PM Verbosity Control (#46)

  • 3 modes: total (default), verbose, hybrid
  • Config via KUGETSU_VERBOSITY env var
  • PM v4

Bug Fix

  • kugetsu: fixed nohup command (use sh -c instead of bash -c)
## Summary ### Phase 1 - Queue Infrastructure (#49) - queue.json - Queue storage with 3 tiers - enqueue - Add task to queue - dequeue - Remove and return next task (priority order) - queue-list - List pending tasks ### Phase 2 - PM Polling Loop (#49) - pm-poll-loop - Continuous polling daemon - Priority: dev_followups > user_interrupts > background - Configurable poll interval (default 600s) ### PM Verbosity Control (#46) - 3 modes: total (default), verbose, hybrid - Config via KUGETSU_VERBOSITY env var - PM v4 ### Bug Fix - kugetsu: fixed nohup command (use sh -c instead of bash -c)
shoko added 1 commit 2026-03-31 17:10:19 +02:00
feat: queue architecture Phase 1 & 2 + PM verbosity control 214a31e4bd 
Phase 1 - Queue Infrastructure (#49):
- ~/.kugetsu/queue.json - Queue storage with 3 tiers
- ~/.kugetsu/scripts/enqueue - Add task to queue
- ~/.kugetsu/scripts/dequeue - Remove and return next task (priority order)
- ~/.kugetsu/scripts/queue-list - List pending tasks

Phase 2 - PM Polling Loop (#49):
- ~/.kugetsu/scripts/pm-poll-loop - Continuous polling daemon
- Priority: dev_followups > user_interrupts > background
- Configurable poll interval (default 600s)

PM Verbosity Control (#46):
- 3 modes: total (default), verbose, hybrid
- Config via KUGETSU_VERBOSITY env var
- PM v4

Other fixes:
- kugetsu: fixed nohup command (use sh -c instead of bash -c)
han commented 2026-04-01 10:11:33 +02:00
First-time contributor
Copy Link

KUGETSU_VERBOSITY should be in the config file as well, refer to #69

KUGETSU_VERBOSITY should be in the config file as well, refer to #69
shoko force-pushed feature/queue-architecture-verbosity from 214a31e4bd to 4d3205de86 2026-04-01 10:14:48 +02:00 Compare
shoko closed this pull request 2026-04-02 00:06:50 +02:00
shoko deleted branch feature/queue-architecture-verbosity 2026-04-02 00:06:50 +02:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#51
Delete Branch "feature/queue-architecture-verbosity"

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?