This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+1 more
Summary
AI summarySummary now includes a "source" key indicating DB or JSON origin when all report directories are fully ingested.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Validation tests assert semantic equality between DB and JSON paths for summary, index counts, FTS results, and handle mixed/pre‑v9 fallback regressions. Validation tests assert semantic equality between DB and JSON paths for summary, index counts, FTS results, and handle mixed/pre‑v9 fallback regressions. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Refactor | Low |
`summarize_reports` now aggregates from DB when all report dirs are covered; falls back to JSON walk otherwise. `summarize_reports` now aggregates from DB when all report dirs are covered; falls back to JSON walk otherwise. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Refactor | Low |
`build_analysis_index` sources local reports from DB instead of re-parsing `analysis.json`. External report paths and pre-v9 dirs still use JSON read. `build_analysis_index` sources local reports from DB instead of re-parsing `analysis.json`. External report paths and pre-v9 dirs still use JSON read. Source: llm_adapter@2026-06-12 Confidence: high |
— |
Full changelog
The last JSON-fed readers now source from the DB-canonical analysis store. Consistency/perf hygiene, not a behavior change — the JSON export is lockstep with the DB, so this is shape-preserving by construction.
Changed
summarize_reportsaggregates from the DB (canonical blob + human overlay) when every report dir on disk is covered by an ingested clip row. Pre-v9 roots and mixed roots (some clips not ingested) fall back wholesale to the JSON walk — a partial DB view would silently under-report. The summary gains a"source": "db"|"json"observability key; the F1 provenance map (source_reports/missing_reports) is unchanged.build_analysis_indexsources local reports from the DB instead of re-parsing everyanalysis.json. Job-linked external report paths (their rows live under another project's DB) and pre-v9 dirs keep the JSON read. The FTS schema and the query surface are identical; the result gainsreport_sourcescounts.
Validation
- DB-vs-JSON parity tests assert semantic equality of both paths (summary, index counts, FTS query results, normalized ordering), plus wholesale-fallback regressions for mixed and pre-v9 roots.
- Live-validated on the sample analysis root: summary parity, index-count parity, and identical FTS results for both sources. Offline suite at 1177.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Related context
Beta — feedback welcome: [email protected]