Uh oh!
There was an error while loading. Please reload this page.
fix: Make confidence-status assertions deterministic in triage tests - #1712
Conversation
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe pull request updates two triage automation tests. The tests now assert ChangesTriage confidence tests
Estimated code review effort: 2 (Simple) | ~10 minutes ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow. |
✅ Template check passed after update. Thanks for fixing the PR description. |
🔍 Reviewer Summary for PR #1712CI Status: ✅ Recommendations
|
…triage tests Address CodeRabbit findings on PR #1703: 1. Assert result.status is specifically 'warning' for low-confidence, unlabeled fixture at 0.95 threshold (line 247) 2. Derive expected status from returned inference confidences instead of accepting all three statuses (lines 294-296) - Returns 'preview' if any inference meets 0.85 threshold - Returns 'warning' if no inference meets threshold All 27 handle-needs-triage tests passing. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
48bbfca to
1143387CompareCo-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Resolved multiple-footer validation errors by removing old footer text and keeping only the latest structured footer with document metadata. - badges-workflow-integration: v1.2.0 → v1.2.1 - github-actions-v7-upgrade: 1.1.1 (updated from 1.1) - issue-metadata-triage-expansion: 1.1.1 (updated from 1.1.0) Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
* fix: Correct frontmatter validation errors in project documentation
Fixed invalid status values and missing required fields in OPENSPEC analyses:
- Changed status from 'in-progress'/'implemented' to 'active' (valid enum)
- Changed version from number to string format ("1.1")
- Added missing description fields
- Added owners field to all specification documents
- Standardized frontmatter field formatting
All frontmatter validation now passes (4/4 files validated, 0 errors).
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
* fix: Add proper document footers to OPENSPEC files
Added footer sections to all OPENSPEC analysis and specification documents
with metadata and status information for maintainability and tracking.
Resolves footer validation errors in CI/CD checks.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
* fix: Bump OPENSPEC document versions to reflect footer additions
Updated version numbers to satisfy frontmatter freshness validation:
- badges-workflow-integration: v1.2.0 → v1.2.1
- github-actions-v7-upgrade: 1.1 → 1.1.1
- issue-metadata-triage-expansion: 1.1.0 → 1.1.1
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
* docs: Add changelog entries for PR #1711 and PR #1712
- OPENSPEC frontmatter/footer validation fixes (PR #1711)
- Confidence-status assertion determinism in handle-needs-triage tests (PR #1712)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
* docs: Update CHANGELOG.md last_updated to 2026-08-10
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
* fix: Remove duplicate footer sections from OPENSPEC files
Resolved multiple-footer validation errors by removing old footer text
and keeping only the latest structured footer with document metadata.
- badges-workflow-integration: v1.2.0 → v1.2.1
- github-actions-v7-upgrade: 1.1.1 (updated from 1.1)
- issue-metadata-triage-expansion: 1.1.1 (updated from 1.1.0)
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>Uh oh!
There was an error while loading. Please reload this page.
Summary
Addresses CodeRabbit findings from PR #1703 by making confidence-status assertions deterministic in the handle-needs-triage test suite. These were functional correctness issues flagged during code review of the merged Phase 5 work.
Changes
Line 247: Assert result.status is specifically 'warning' for low-confidence, unlabeled fixture at 0.95 threshold
Lines 294-296: Derive expected status from returned inference confidences
Test Results
✅ All 27 handle-needs-triage tests passing
✅ Linting and formatting automated fixes applied
Linked issues
Closes#1709
Relates to #1679
Changelog
Fixed
Checklist (Global DoD / PR)