docs(breg): add the missing BREAKING entries for the citizen gateway to the BReg changelog
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Start with products/breg/CHANGELOG.md and compare the citizen MCP gateway entries in docs/site/src/content/docs/changelog.mdx, including the changes from #1534. Check the test referenced in the issue for callback journaling behavior, then confirm the BReg changelog contains both BREAKING entries and accurately describes which callbacks are recorded.
Written by the indexing model from the issue text.
Description
products/breg/CHANGELOG.md is missing two BREAKING entries that the site changelog (docs/site/src/content/docs/changelog.mdx) carries for the citizen MCP gateway work in #1534:
- standing agent profiles lose
invoke(an immediate action is a direct write); - module-contributed task-grant profiles are refused.
Also, the BReg changelog says the review page journals "failed sign-in callbacks". Callbacks that fail the state or issuer check are deliberately not journaled (a test pins it), so the sentence should say which callbacks are recorded.
Add the two entries and narrow the sentence so the product changelog matches the site and the code.
- Dominant language
- Rust
- Stars
- 2
- Forks
- 0
- Avg merge
- 7h 57m
- Merged PRs (30d)
- 230
Getting set up
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 72/100
registrystack/registry-stack#1753 ·
Maintainers usually reply within 1 day
-
area:casework bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
registrystack/registry-stack#1729 ·
Maintainers usually reply within 1 day
-
area:breg bug criticality:p3 triage:needs-implementation
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
registrystack/registry-stack#1682 ·
Maintainers usually reply within 1 day
-
area:casework bug criticality:p3 triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
registrystack/registry-stack#1669 ·
Maintainers usually reply within 1 day
-
agent-ready area:platform criticality:p3 documentation triage:needs-implementation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
registrystack/registry-stack#1639 ·
Maintainers usually reply within 1 day
All issues in registrystack/registry-stack
Similar issues
-
bug CLI exec tool-calls
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
maintainer-needed p2 triaged ui windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
ai_p2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
ClickHouse/ClickHouse#123351 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
github/copilot-sdk#2804 · 1 comment ·
Maintainers usually reply within 1 day