Add GET /v1/runs/status (keep /runs/status as an alias)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript, yaml
- Domain
- api
Research direction
Start with docs/reference/change-policy.md (PR #506) for the /v1 decision, then find the route table in the server code and the existing GET /runs/status handler. Add GET /v1/runs/status while keeping /runs/status and /run-leaf/status as aliases, and update docs/api/harness-openapi.yaml. Update docs/reference/http-api.md and docs/reference/leaf-and-envelope.md, then run the contract test. Done when both paths respond, the OpenAPI spec lists the new path, and the contract test passes.
Written by the indexing model from the issue text.
Description
Follow-up from the change policy (docs/reference/change-policy.md, PR #506).
Decision: put the whole client surface under /v1. GET /runs/status is canonical today with no /v1 form.
To do: add GET /v1/runs/status to the route table and docs/api/harness-openapi.yaml, keep /runs/status (and the deprecated /run-leaf/status) as aliases, update the docs that name the old path (docs/reference/http-api.md, docs/reference/leaf-and-envelope.md), keep the contract test green. Additive, so no deprecation needed.
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 9
- Avg merge
- 9h 10m
- Merged PRs (30d)
- 137
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rossoctl/moca
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rossoctl/moca#421 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
outline/outline#14348 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
[Bug]: Agent import retains quotes in .env API keys followed by inline commentsPossibly taken @yxr-2025 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
elie222/rakazo#2322 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
awslabs/visual-asset-management-system#804 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
dsh-market/dsh-market#1027 · 1 comment ·
Maintainers usually reply within 1 day