Skip to content

0.50 Findings

Status: Technical qualification complete; Sol review pending.

ID Severity Disposition
SOL-050-001 High resolved and covered by regression tests
SOL-050-002 High resolved by the normative baseline manifest
SOL-050-003 High resolved by the public canonical runner
SOL-050-004 High resolved by action-correlated native proof
SOL-050-005 High resolved by the complete backend campaign
SOL-050-006 High resolved by adaptive handoff scenarios
SOL-050-007 Medium resolved by release documentation
SOL-050-008 Low resolved by formatting verification
SOL-050-009 High resolved by action-level native evidence
SOL-050-010 Medium resolved by independent backend campaigns
SOL-050-011 High resolved by candidate evaluation evidence
SOL-050-012 Medium resolved by canonical digest and metadata checks
SOL-050-013 Medium resolved by source and artifact digest linkage
SOL-050-014 High resolved by fail-fast campaign execution
SOL-050-015 High resolved by action-correlated EXPLAIN evidence
SOL-050-016 High resolved by complete target-matrix candidate evaluation
SOL-050-017 Medium resolved by schema, digest, and ledger validation
SOL-050-018 High resolved by Spark protocol dispatch and error-semantics regression coverage
SOL-050-019 Medium resolved by focused Pyright validation
SOL-050-020 Medium resolved by non-recursive node-local adaptive selection
SOL-050-021 High resolved by truthful unsupported-action pushdown findings
SOL-050-022 High resolved by obligation-authoritative validation diagnostics
SOL-050-023 High resolved by complete pushdown outcome and lowering evidence
SOL-050-024 Medium resolved by authoritative findings-ledger enforcement

| SOL-050-025 | High | resolved by engine-bound finding provenance and native proof digest validation |

| SOL-050-026 | High | resolved by source-authoritative compiler targets and native proof commitments |

| FINAL-050-001 | High | resolved by obligation-authoritative feasibility checks | | FINAL-050-002 | High | resolved by nested support-payload validation | | FINAL-050-003 | High | resolved by value-free DuckDB EXPLAIN bindings | | FINAL-050-004 | Medium | resolved by complete unknown-category serialization | | FINAL-050-005 | Medium | resolved by the 0.50 release-surface update | | FINAL-050-006 | Medium | resolved by complete ledger verification | | FINAL-050-007 | High | resolved by finding-specific evidence serialization | | FINAL-050-008 | High | resolved by canonical and negative support reports | | FINAL-050-009 | High | resolved by graph constraint domain scenarios | | FINAL-050-010 | Medium | resolved by the CI-enforced scoped Pyright gate | | FINAL-050-011 | High | resolved by duplicate requirement/finding rejection | | FINAL-050-012 | High | resolved by static lowering-condition validation | | FINAL-050-013 | High | resolved by compiler implementation identity fingerprints | | FINAL-050-014 | Medium | resolved by release-candidate documentation status |

| FINAL-050-015 | High | resolved by complete pushdown finding and proof matrix validation |

| FINAL-REL-001 | High | resolved by typed-null boolean lowering and PostgreSQL null substring coverage | | FINAL-REL-002 | High | resolved by PostgreSQL half-even floating-point rounding | | FINAL-REL-003 | High | resolved by complete Unicode Case_Ignorable sigma context | | FINAL-REL-004 | High | resolved by fail-closed composed substring bound analysis | | FINAL-REL-005 | High | resolved by fail-closed composed replacement search analysis | | FINAL-REL-006 | High | resolved by public case_when arity validation | | FINAL-REL-007 | High | resolved by canonical normalization of null, boolean, numeric, and order semantics | | FINAL-REL-008 | Medium | resolved by complete stable finding ledger and checker coverage |

| SOL-REL-009 | High | resolved by SQLite boolean type preservation across unions and scoped parameters |

Implementation resolutions are complete; Sol re-review pending. The evidence index, source digest, and artifact digests are the release record for this disposition.