Uh oh!
There was an error while loading. Please reload this page.
fix: Correct OPENSPEC frontmatter and add document footers - #1711
Conversation
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>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>
✅ Template check passed after update. Thanks for fixing the PR description. |
⏱️ Aging and SLA annotation
Maintained by project-meta-sync workflow. |
Warning Review limit reached
Next review available in:16 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
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>
🔍 Reviewer Summary for PR #1711CI Status: ✅ Recommendations
|
Co-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>
Uh oh!
There was an error while loading. Please reload this page.
…1712) * fix: Make confidence-status assertions deterministic in handle-needs-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> * 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>
Summary
Fixes frontmatter validation and footer formatting issues in OPENSPEC specification documents for active projects. These were validation issues discovered after PR #1703 merged, plus version bumps to satisfy freshness validation.
Changes
Frontmatter Validation: Corrected invalid status values and missing required fields
Document Footers: Added proper footer sections to all OPENSPEC files
Version Bumps: Updated document versions to reflect body changes
Files Modified
.github/projects/active/github-actions-v7-upgrade-2026-08-09/OPENSPEC_ANALYSIS.md.github/projects/active/badges-workflow-integration-2026-08-08/OPENSPEC_ANALYSIS.md.github/projects/active/issue-metadata-triage-expansion/OPENSPEC.mdLinked issues
Closes#1709
Relates to #1672
Relates to #1673
Relates to #1679
Changelog
Fixed
Checklist (Global DoD / PR)