[ Bounty $4k ] [ Metrics ] Reject non-finite gauge values — numeric safety

[alex-huma-orch]

Bug Details

• Affected component: codebase/src/common/metrics.py MetricsCollector.gauge
• Trigger: A caller records NaN or infinity as a gauge.
• Observed behavior: The snapshot emits a non-finite number.
• Expected behavior: Gauge values should be finite for JSON compatibility.
• Impact: Exporters can fail or drop batches.

Fix

• Use math.isfinite for gauge validation.

Acceptance Criteria

• A regression test covers this Metrics case.
• The changed behavior is documented or asserted by the relevant test.

🚀 Bounty Gate — Star First

You must star orchestration-agent/AgentOrchestration before submitting work. No star, no bounty. Simple.

# Star via API
curl -L -X PUT -H "Accept: application/vnd.github+json" \
  -H "Authorization: Bearer <YOUR_TOKEN>" -H "Content-Length: 0" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  https://api.github.com/user/starred/orchestration-agent/AgentOrchestration

# Or via CLI
gh repo star orchestration-agent/AgentOrchestration

We verify at submission time:

gh repo view orchestration-agent/AgentOrchestration --json viewerHasStarred --jq '.viewerHasStarred'

⚡ Star Priority

The more stars you have on this repo, the higher your submission sits in the review queue. Star count is checked live — no history, no gimmicks. More stars = faster review + better adoption odds.

📋 Bounty Rules

• Submit a working fix with proof (test output, screenshot, or demo).
• No secrets, no tokens, no hidden context in your code.
• We accept multiple entries per issue. Best implementation wins the pot.
• PR must reference this issue number.
• Low effort submissions get closed without review.

/bounty $4000

[nguyenlnp]

/claim #3873

[neuralmint]

/claim #3873 via #3902