Link payment-review example and clarify App Kit task-grant status
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- node.js, python
- Domain
- documentation
Research direction
Start by reviewing products/casework/README.md:99-106, products/casework/TASK_GRANTS.md:66-77 and 90-99, and searching docs/site/ for the relevant Casework page. Confirm App Kit's support for unified review-task task grants from the available project context, then link the payment-review example and document the current UI status; done means both reader gaps are addressed without changing the route documentation.
Written by the indexing model from the issue text.
Description
The source-independent payment-review example is only documented from the product README, not from the docs site, and TASK_GRANTS.md dropped its App Kit UI statement without saying what replaces it for unified review tasks. As of PR #1189, products/casework/examples/payment-review is described in products/casework/README.md:99-106, but a search of docs/site/ finds no link to it. Separately, products/casework/TASK_GRANTS.md:90 now reads "The unified Node/Python Casework clients expose these operations. Credentials stay on the server...", where it previously also said "App Kit's source-item view provides review, approval, retry, listing, and revocation." The new /v1/review-tasks/{taskId}/task-grants routes are documented elsewhere in the same file (lines 66-77, 99), so the gap is specifically about App Kit's UI support for unified review tasks, not about the routes themselves.
Failure scenario: a reader following the docs site to understand Casework review options never discovers the payment-review example, which is the only example showing source-independent (non-BReg) approval; and a reader of TASK_GRANTS.md who remembers the App Kit UI reference has no way to tell whether App Kit still supports task grants for the new unified review-task routes or only for the retained work-item routes.
Suggested fix:
- Link
examples/payment-reviewfrom the relevant docs-site page (or its README index). - Add a sentence to
TASK_GRANTS.mdstating App Kit's current support (or lack of it) for the/v1/review-tasks/.../task-grantsroutes.
Filed from the review of #1189; not merge-blocking.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 3h 45m
- Merged PRs (30d)
- 134
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
registrystack/registry-stack#1239 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
registrystack/registry-stack#1235 ·
-
area:breg bug good first issue rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
registrystack/registry-stack#1227 ·
-
area:breg documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
registrystack/registry-stack#1213 ·
-
area:breg bug rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
registrystack/registry-stack#1211 ·
All issues in registrystack/registry-stack
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100