docs(agents): verify the issue dependency API #26
No reviewers
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wontfix
needs-info
needs-triage
ready-for-agent
ready-for-human
review/merge-ready
review/needs-fix
review/needs-human
review/needs-review
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
olympus/infra-forge!26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/agent-tracker-dependency-api"
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?
Follow-up to #17 (the forgejo-mcp split). The tracker note in
docs/agents/issue-tracker.mdsaid the issue-dependency endpoints were"unverified against this instance" and told agents to rely on a
Blocked by:body line alone. They are verified, and the body line isnow optional.
What changed
docs/agents/issue-tracker.mdonly. ADependenciesentry underConventions, plus a line in Wayfinding that keeps the body line as the
fallback for a caller with only the tracker UI. No code, no manifest
change: this file is listed under
exclude, so it never reaches thewiki.
Verified live (15.0.9, 2026-10-06)
GET /issues/{n}/dependenciesandGET /issues/{n}/blocksreturnbare
IssueMetaarrays. Both 200; absent blockers is[], not 404.POST /issues/{n}/dependenciesadds an edge,201. The body must bea full
IssueMeta(owner,repo,index);indexalone is404 IsErrRepoNotExist, which reads as a missing repo.201), andDELETEof anedge that is not there still answers
201./issues/{n}/sub_issuesis404.Context
Prose only -- no behaviour changes. Reverting it costs nothing if the
body-line convention is preferred after all.
29c1782ae7tob0a42ff508