Changelog

Solana ecosystem security integration shipped across product surfaces

• Security model: released a shared solana_security_profile structure to keep Solana framework interpretation consistent across dashboard and scanner outputs.
• Investigation flow: token bundle investigation now presents Solana Security Program context including tiering, pillar status, incident readiness, and recommended actions.
• Scanner analytics: added a Solana Security Program card for crypto-relevant scans with eligibility context and triage-oriented next steps.
• Dashboard-first messaging: CTA and role-mode guidance were prioritized in-product so users take action before reading supporting docs.
• Docs rollout: published public-facing Solana program documentation in Blockchain and Integrations docs, plus a direct Resources entry point.
• Validation: backend test checks and frontend syntax/lint validation completed before release notes publication.

Solana security system integration (framework + product surfaces)

• API model: introduced a structured solana_security_profile schema with framework references, tiering, pillars, incident workflow checklist, tooling coverage, and prioritized actions.
• Investigation flow: Solana bundle investigation now returns security-program guidance and supports optional tvl_usd context for eligibility interpretation.
• Scanner surface: shipped a Solana Security Program card in scan analytics for crypto-relevant scans, showing tier label, monitoring/formal-verification eligibility, incident priority, and action lists.
• Consistency: scanner and investigation now consume the same profile model to keep interpretation aligned across workflows.
• Resources docs: published Solana program documentation updates in Blockchain and Integrations docs, plus a direct card entry in Resources.

Scanner quality, diff tracking, and docs operations updates

• Scanner UX: completed guided onboarding, richer finding trust details, and false-positive feedback flow.
• UI cleanup: removed the Scanner Readiness panel from scanner view by product direction.
• Diff tracking: shipped recheck and scan diff flow with new, fixed, regressed, and improved states.
• Diff UX pass: Scan Diff now appears before the first run with a comparison explainer, first-run recheck CTA, and inline hints for each diff state.
• Readability: baseline comparison time is now shown in human-readable format; Fixed/Regressed/Improved values are visually emphasized for faster triage.
• Workflow focus: removed GitHub issue integration controls to keep scanner output and remediation flow streamlined in-console.
• API: scan responses now include structured diff payloads for same-target historical comparison.
• Hardening: tightened same-target diff matching and added safer UI handling for malformed diff sections.
• Validation: scan-diff test suite passed and same-target repeat scans validated baseline/diff behavior.
• Docs ops: launched this daily changelog format and added a direct changelog entry point under Resources.

Detailed release notes

• Discoverability: users no longer need to finish an initial scan to discover the diff feature; comparison mechanics are visible at scan setup time.
• First-run behavior: explicit baseline guidance now explains why diff buckets may be empty before same-target rechecks.
• Interpretation speed: added inline state definitions and stronger visual emphasis so triage intent is clearer at a glance.
• Data continuity: backend diff payload format remains stable while UI clarity was improved on top of it.
• Product scope: GitHub issue handoff controls were intentionally removed to keep remediation workflow focused inside Diverg Console.
• Closeout: a full internal before/after wrap-up was published to consolidate the complete two-week improvement cycle.

Documentation site launch

• Published complete docs structure: Getting Started, Core Concepts, Features, and Reference.
• Added whitepaper, API reference, integrations pages, and initial changelog page.
• Shipped responsive docs layout and dark/light theme support.