Repository navigation
Fix bounded progress generation and review recovery diagnostics - #938
Conversation
…anged-domus-evaluations: generate bounded complete progress facts (#937)
|
To preview the documentation for this pull request, visit the following URL:
|
Bugbot: review complete
|
Copilot approval · Human review neededStatus: This pull request is outside the configured approval scope. Technical evidenceRevision: |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #938 +/- ##
===========================================
+ Coverage 95.25% 96.09% +0.84%
===========================================
Files 1172 1526 +354
Lines 39236 47472 +8236
Branches 11685 14772 +3087
===========================================
+ Hits 37373 45618 +8245
+ Misses 698 697 -1
+ Partials 1165 1157 -8
🚀 New features to boost your workflow:
|
…a-diagnostic-reason: retain bounded Bugbot response diagnostics (#920)
…anged-domus-evaluations: complete prompt delivery before native fixture exit (#937)
…thout-a-diagnostic-reason into bugfix/937-released-acceptance-recovery-exhausts-on-r11-in-three-unchanged-domus-evaluations
Branch synchronized
The fixer resolved 7 conflicted files. 6 verification checks passed. |
…anged-domus-evaluations: diagnose freshness failures and ineligible sync conflicts
…anged-domus-evaluations: wait for canonical catalog read completion
…anged-domus-evaluations: serialize all catalog recovery reads
Closes #937. Closes #920. Closes #870. Closes #911.
Large progress comparisons now allocate exact JSON UTF-8 quotas per field in both framed profiles. Final multi-batch assessments use closed semantic decisions and complete host-rendered labels within the original requirement and text bounds. Unicode and byte failures share the existing single replacement; exhausted generation stops with a nonretryable diagnostic. Source identity, locale, receipts, freshness and publication checks remain enforced.
Bugbot preserves a finite diagnostic reason after its existing three unusable completed responses. Freshness failures identify the trusted read operation and known HTTP metadata, distinguish before/after publication and reject malformed heads. Recovery rechecks the current head and reconciles persisted findings without duplicate publication. Protected-path and over-limit synchronization refusals preserve their policy and expose safe counts and complete English/Spanish actions.
Related operational fixes cover the native fixture stdin race, CRLF extraction, checksum-bound downloads of the same reviewed JDK/driver archives, and explicit generated-artifact conflicts so rebuilding finishes before synchronization verification. The Action published the verified combination with #939; normal contributor changes prepared the reviewed workflow while preserving bot credentials and Action-owned merging.
Validation: 920 root suites / 18,293 passing tests (35 existing platform skips); 385 extension suites / 5,289 passing tests at 100% on every metric. All coverage/acceptance budgets, types, lint, specification/catalog, documentation/workflow contracts, build, typed package/CLI/API/web smoke and normal hooks pass. The actual-base local diff audit covers all 260 changed executable lines with zero misses or partial branches; new freshness policies/helpers have 100% on every metric.
Native consumer qualification and the 18-issue audit are recorded in #937 and Domus PR #29. Merge gates apply to the exact final head: applicable CI, official Codecov, native consumer verification and zero active review findings. Domus feature completion and merge remain separate from SDK qualification.