Make the scaffold gates honest, then group the help
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 62/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- bash, python
- Domain
- documentation, testing, tooling
Research direction
Start by reading run-gates.sh, the README drift table, and the code that produces okl --help; identify the real commands before grouping them. Add or locate the gate test for a missing registry and confirm it expects SKIP; done means that test passes, the drift table labels its scaffold rows and has the correct count, and help groups only real commands.
Written by the indexing model from the issue text.
Description
Problem
run-gates.shprints ✓ when the tombstone and retraction registries are missing. That is the case in okl's own CI, so a gate that ran nothing reads as passed.- The README's drift table is miscounted. It says "Five mechanisms" but lists seven, and it doesn't separate the scaffold rows.
Proposal
- Make a missing registry say SKIP, not ✓.
- Fix the drift table: label its scaffold rows and correct the count.
- Group
okl --helpusing real commands only. - Not proposed: an environment-to-config migration.
Acceptance
- A missing registry prints SKIP, with a test.
From an unpublished 2026-10-10 multi-agent review of okl, in which two reviewer agents checked each recommendation, one against the code and one for value at its cost. R27, priority P2 (P0 highest). This issue describes the version they endorsed.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 119
Getting set up
- No 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 emeraldleaf/okl
-
enhancement loop-review
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
emeraldleaf/okl#190 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
emeraldleaf/okl#147 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 36/100
emeraldleaf/okl#365 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
emeraldleaf/okl#357 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
emeraldleaf/okl#349 ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
huggingface/deep-rl-class#723 ·
-
[tool] bug: Qwen3 XML tool parser raises on `...` argument values (Ellipsis is not JSON serializable)Possibly taken @super-yuki claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
verl-project/verl#8559 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TencentCloud/octop-harness#228 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
google/osv-scalibr#2585 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
NousResearch/hermes-agent#149323 ·
Maintainers usually reply within 1 day