Decide explicit-zero semantics for ReportPlanOutcomeResponse.CommittedBudget
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Read the ReportPlanOutcomeResponse definition and the changes in PR #293 to understand how PlanSummary represents explicit zero values. Decide whether a zero CommittedBudget has distinct protocol meaning, then update the field and add migration and test coverage if needed. Done means the decision is reflected in the schema and tests, without changing unrelated response fields.
Written by the indexing model from the issue text.
Description
Context
PR #293 typed ReportPlanOutcomeResponse.PlanSummary and made its budget fields pointers so explicit zero plan totals marshal. ReportPlanOutcomeResponse.CommittedBudget remains float64,omitempty.
Current rationale: CommittedBudget is a per-outcome delta, so an omitted zero is not currently distinct from no committed budget, while PlanSummary.TotalCommitted and PlanSummary.BudgetRemaining are cumulative state where zero is meaningful.
Decision needed
Confirm this asymmetry is intentional. If governance needs an explicit "zero committed for this outcome" acknowledgement, change CommittedBudget to *float64 and add migration/test coverage.
Constraints
- Keep the decision schema-faithful.
- Preserve explicit-zero values where omission and zero have different protocol meaning.
- Avoid sweeping pointer changes across unrelated response fields.
- Dominant language
- Go
- Stars
- 4
- Forks
- 2
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 14
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 adcontextprotocol/adcp-go
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
adcontextprotocol/adcp-go#567 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
adcontextprotocol/adcp-go#562 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
adcontextprotocol/adcp-go#564 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
adcontextprotocol/adcp-go#556 ·
Maintainers usually reply within 1 day
-
claude-triaged cross-repo
Difficulty 5/5 Over a week Newbie friendliness 25/100
adcontextprotocol/adcp-go#548 · 2 comments ·
Maintainers usually reply within 1 day
All issues in adcontextprotocol/adcp-go
Similar issues
-
bug
Difficulty 2/5 Half a day Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
kubernetes-sigs/external-dns#6816 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ANSI translator ignores SGR 22/24 (and other attribute-off codes): bold and underline never turn offOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Named Tuple element with a space in its name fails to parsePossibly taken @spicysharkco claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ClickHouse/clickhouse-go#2073 ·
Maintainers usually reply within 1 day