admin/orchestrator
1
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

fix(pipeline): description+name to analyst, status-only analyst comment with doc links #13

Merged
admin merged 3 commits from fix/taskmd-description into main 2026-06-03 22:45:17 +03:00
Conversation 0 Commits 3 Files Changed 6 +320 -30
admin commented 2026-06-03 22:43:22 +03:00
Owner
Copy Link

Three fixes, one PR (see DEV_TASK_TASKMD_DESCRIPTION.md).

  • Bug A: append resolved description to analyst task_desc (.task.md was Title-only ~101B).
  • Bug B: fetch_issue_fields() single issue-detail GET returns (name, description); name pulled above slug build so branch is no longer feature/-untitled.
  • Bug C: analyst ready-comment rewritten for status-only model (ask Approved status, not :approved:/In Progress) + clickable Gitea links to docs that actually exist.

Tests: 207 passed + 9 pre-existing failed (baseline 204 + 3 new). New: test_taskdesc_includes_description, test_name_fetched_when_payload_empty, test_analyst_comment_asks_approved_with_links.

NOT deployed, NOT merged — merge after live check + prod run.

Three fixes, one PR (see DEV_TASK_TASKMD_DESCRIPTION.md). - **Bug A**: append resolved description to analyst task_desc (.task.md was Title-only ~101B). - **Bug B**: fetch_issue_fields() single issue-detail GET returns (name, description); name pulled above slug build so branch is no longer feature/<id>-untitled. - **Bug C**: analyst ready-comment rewritten for status-only model (ask Approved status, not :approved:/In Progress) + clickable Gitea links to docs that actually exist. Tests: 207 passed + 9 pre-existing failed (baseline 204 + 3 new). New: test_taskdesc_includes_description, test_name_fetched_when_payload_empty, test_analyst_comment_asks_approved_with_links. NOT deployed, NOT merged — merge after live check + prod run.
admin added 3 commits 2026-06-03 22:43:22 +03:00
fix(pipeline): pass issue description to analyst task file b91be74692 
start_pipeline built the analyst .task.md with only the Title, so the analyst received a ~101-byte file and reported the business request as empty even though the description was already fetched. Append the resolved description to task_desc.
fix(pipeline): fetch issue name from Plane API on status-trigger start 96c5e6b2f9 
issue.updated ships only the changed fields, so name was absent and the branch slug became feature/<id>-untitled. Add fetch_issue_fields (single issue-detail GET returning name+description, reusing the endpoint/token of fetch_issue_description) and pull the name above the slug build. Empty name still falls back to untitled.
feat(plane): analyst comment asks for Approved status + links docs a9cdb17614 
The analyst ready-comment used the obsolete :approved: wording (comment-based approve was removed in PR #12). Rewrite it for the status-only model: ask the stakeholder to move the issue to Approved (reject = reason comment + Rejected), and add clickable Gitea links to the analyst docs that actually exist in the worktree.
admin merged commit dce9ac806b into main 2026-06-03 22:45:17 +03:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/orchestrator#13
Delete Branch "fix/taskmd-description"

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?