Casework mark-uncertain: settle wording in its refusal and an incomplete history entry type
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python, rust, typescript
- Domain
- backend-api-design, documentation
Research direction
Find the refusal message for the mark-uncertain action in the casework lifecycle-audit code. Update its wording to be distinct from 'settled'. Then locate the TypeScript type AttemptUncertainHistoryEntry and add the missing operator keys (who decided and why). Check the Python and Rust equivalents for the same type and update them if needed. Run any existing tests for these types to ensure they still compile and describe the payload accurately.
Written by the indexing model from the issue text.
Description
Two small follow-ups to the Casework operator command that marks an expired pending attempt uncertain (lifecycle-audit changes, not yet merged):
- The refusal shared with settle says "the work item is X; only a work item awaiting its source outcome can be settled". For mark-uncertain, "settled" is the wrong verb. Give each action its own wording.
- The TypeScript
AttemptUncertainHistoryEntrydetail type does not list the new operator keys (who decided and why). Its generic JSON object type tolerates them, so nothing breaks, but the published type under-describes the payload. Update the type and the Python and Rust equivalents if they have the same gap.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 4h 26m
- Merged PRs (30d)
- 152
Contributor 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 registrystack/registry-stack
-
bug github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1393 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1383 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
registrystack/registry-stack#1380 ·
-
area:breg enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
registrystack/registry-stack#1379 ·
-
area:casework documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
registrystack/registry-stack#1369 ·
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
TheLarkInn/aipm#2413 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
alexgorbatchev/simple-ptt#15 ·
-
tooling
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
todo:ticket
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
taikoxyz/taiko-mono#22168 · 1 comment ·