Tasker-worker marked code-writing kanban cards done without filing Forgejo issues #107

New issue

Closed

opened 2026-07-30 00:21:34 +00:00 by Mark · 1 comment

Mark commented

2026-07-30 00:21:34 +00:00

Owner

Gap: tasker-worker has no instruction/skill to file Forgejo issues

What happened (2026-07-29)

A photo-segmentation Vikunja milestone (project 3, tasks 59-63) was created and the kanban tasker-worker picked each one up, ran it, marked the kanban cards done. Result: code written to /home/b/Projects/easystitch/src/segmentation/ and /tests/segmentation/, but zero Forgejo issues filed for any of the work. The work is uncommitted, untracked in the issue system, and the kanban cards are done without any review-required handoff.

Root cause

The tasker-worker is an agentic lane worker. Per kanban-worker skill:

Reads the full card body and uses judgment
Has no deterministic instruction to file Forgejo issues for code changes
Per the skill itself: "Coding task that needs human review (review-required)" — should block with review-required: reason and post structured metadata as a comment, not complete

The worker chose complete over block(review-required) despite writing actual code. That's a discipline gap.

What needs to change

The tasker-worker's profile (~/.hermes/profiles/tasker-worker/SOUL.md and/or skill loading) should instruct: any code-writing task must block(review-required: ...) not complete, with structured metadata (changed_files, tests_run, tests_passed, diff_path) posted as a comment first.
The tasker-worker profile should load a skill or instruction that says: when implementation lands, file a Forgejo issue with the diff/work as the body so the issue system tracks the work.
The kanban-worker's existing review-required guidance is correct — it just needs to be in the tasker-worker's loaded context, not just available in a skill someone has to load.

Evidence

Vikunja milestone 59-63 (project 3 = org_mode) ran tasker-board cards t_fb25b6b9, t_7e4bf156, t_fe3f8f50, t_1533d9e9, t_ff5ac64d
All marked done
No Forgejo issues created in window 2026-07-29T20:41-21:25 UTC
19 files written to easystitch repo (uncommitted)

Files involved

~/.hermes/profiles/tasker-worker/SOUL.md (or equivalent)
~/.hermes/profiles/tasker-worker/profile.yaml
~/.hermes/scripts/forgejo-api.sh (path used to file issues — needs to be reachable from worker)

## Gap: tasker-worker has no instruction/skill to file Forgejo issues ### What happened (2026-07-29) A photo-segmentation Vikunja milestone (project 3, tasks 59-63) was created and the kanban tasker-worker picked each one up, ran it, marked the kanban cards done. Result: code written to `/home/b/Projects/easystitch/src/segmentation/` and `/tests/segmentation/`, but **zero Forgejo issues filed** for any of the work. The work is uncommitted, untracked in the issue system, and the kanban cards are done without any review-required handoff. ### Root cause The tasker-worker is an agentic lane worker. Per `kanban-worker` skill: - Reads the full card body and uses judgment - Has no deterministic instruction to file Forgejo issues for code changes - Per the skill itself: "Coding task that needs human review (review-required)" — should block with `review-required:` reason and post structured metadata as a comment, not `complete` The worker chose `complete` over `block(review-required)` despite writing actual code. That's a discipline gap. ### What needs to change 1. The tasker-worker's profile (`~/.hermes/profiles/tasker-worker/SOUL.md` and/or skill loading) should instruct: **any code-writing task must `block(review-required: ...)` not `complete`**, with structured metadata (changed_files, tests_run, tests_passed, diff_path) posted as a comment first. 2. The tasker-worker profile should load a skill or instruction that says: **when implementation lands, file a Forgejo issue with the diff/work as the body** so the issue system tracks the work. 3. The kanban-worker's existing `review-required` guidance is correct — it just needs to be in the tasker-worker's loaded context, not just available in a skill someone has to load. ### Evidence - Vikunja milestone 59-63 (project 3 = org_mode) ran tasker-board cards t_fb25b6b9, t_7e4bf156, t_fe3f8f50, t_1533d9e9, t_ff5ac64d - All marked done - No Forgejo issues created in window 2026-07-29T20:41-21:25 UTC - 19 files written to easystitch repo (uncommitted) ### Files involved - `~/.hermes/profiles/tasker-worker/SOUL.md` (or equivalent) - `~/.hermes/profiles/tasker-worker/profile.yaml` - `~/.hermes/scripts/forgejo-api.sh` (path used to file issues — needs to be reachable from worker)

Mark

2026-07-30 00:21:34 +00:00

closed this issue
added the
bug

triage-approved
labels

Mark commented

2026-07-30 00:25:05 +00:00

Author

Owner

Closing as misrouted. These are org-mode process / config issues, not easystitch code issues.

Re-filed on Mark/org_mode as the correct repo. The tasker-worker profile lives in ~/.hermes/profiles/tasker-worker/ and the chat-agent framing rules apply to all features routed through Vikunja, not to easystitch specifically.

Closing as misrouted. These are org-mode process / config issues, not easystitch code issues. Re-filed on Mark/org_mode as the correct repo. The tasker-worker profile lives in `~/.hermes/profiles/tasker-worker/` and the chat-agent framing rules apply to all features routed through Vikunja, not to easystitch specifically.