Skip to content

fix(heads): surface LoadReport quarantine warnings on every head (USE-P1-3 / #30) - #71

Merged
CryptoJones merged 1 commit into
mainfrom
fix/surface-load-report
Sep 15, 2026
Merged

CryptoJones merged 1 commit into
mainfrom
fix/surface-load-report

Conversation

@CryptoJones

Copy link
Copy Markdown
Owner

Description

Resolves #30 (USE-P1-3 / Codeberg #142).

A partially-quarantined artifact used to load silently as a reduced model. Now:

  • LoadReport::warning(source) returns a one-line summary of what was dropped or truncated (None when clean).
  • cli (load_session and diff), tui, lsp, mcp, http, graphql, and rpc-serve print it to stderr after load.
  • wasm scylla_info JSON carries load_warning (null when clean).
  • Unit tests cover the clean and dirty cases. --strict from the review is not in this PR.
  • Updated BACKLOG.md and ARCHITECTURE_REVIEW.md; bumped to 0.7.12 with a CHANGELOG entry.

Verification Results

  • cargo fmt --all -- --check: Passed
  • cargo clippy --workspace --all-targets -- -D warnings: Passed
  • cargo test --workspace: Passed (54 suites ok)
  • cargo audit: Passed (0 vulnerabilities, 6 allowed warnings)
  • ./scripts/check-wasm.sh: Passed
  • node crates/scylla-wasm/web/verify.mjs: Passed

🤖 Generated with Claude Code

…-P1-3 / #30)

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@CryptoJones
CryptoJones merged commit ba7eebb into main Sep 15, 2026
@CryptoJones
CryptoJones deleted the fix/surface-load-report branch September 15, 2026 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[USE-P1-3] LoadReport quarantine warnings are silently dropped on every head — "never silently wrong" violated

1 participant