Release archive
3.2.44

ASSISTANT-SECURITY-READINESS (Paid MVP Workflow Entry) & SECURITY-READINESS-WORKFLOW (Structured Handoffs)

Release v3.2.44 focuses on ASSISTANT-SECURITY-READINESS (Paid MVP Workflow Entry), SECURITY-READINESS-WORKFLOW (Structured Handoffs), and SECURITY-READINESS-BRIEF (Evidence-Bound Output).

AddedFixedInternal
ASSISTANT-SECURITY-READINESS (Paid MVP Workflow Entry) & SECURITY-READINESS-WORKFLOW (Structured Handoffs)

Release digest

Added

  • ASSISTANT-SECURITY-READINESS (Paid MVP Workflow Entry) — Added a guided Security readiness brief starter to /app/assistant so Web3 projects can enter a pre-audit trust and security review workflow from the assistant workspace.
  • SECURITY-READINESS-WORKFLOW (Structured Handoffs) — Crypto security readiness prompts now produce a distinct security_readiness_brief workflow with project profile and watchlist handoff targets.
  • SECURITY-READINESS-BRIEF (Evidence-Bound Output) — The assistant now renders a deterministic readiness brief from existing crypto trust signals, evidence gaps, recommended next actions, and an explicit non-audit disclaimer.
  • SECURITY-READINESS-CTA (Paid Review Handoff) — Security readiness workflows now promote the crypto evidence profile as the primary assistant rail action while preserving the full route trace for review.
  • REPORT-WORKFLOW-METADATA (Assistant Report State) — Company analysis workflows now expose additive report_workflow metadata with AI Report state, freshness, score context, and the report workspace target.
  • REPORT-WORKFLOW-BLOCKED-STATES (Actionable Report Readiness) — Assistant report metadata now distinguishes insufficient_data and analysis_in_progress blocked states from report-ready company briefs.
  • REPORT-WORKFLOW-HANDOFF-CONTEXT (State-Aware Report Route) — Assistant report handoffs now open /app/report with company, report state, blocker, and workflow-version query context for easier review.
  • TRUST-GRAPH-READ-MODEL (Crypto Project Context) — Crypto project payloads now expose an additive trust_graph.v1 read model with related entities, source-family coverage, holder-preview availability, and explicit low-coverage states.
  • TRUST-GRAPH-SURFACE (Visible Related-Entity Card)/app/crypto/:slug now renders a Trust Graph card that explains graph state, related entities, holder-preview readiness, and missing-edge states without adding a graph database dependency.

Fixed

  • SECURITY-READINESS-ROUTE (Crypto-Safe Handoff) — Web3 readiness workflows now avoid the corporate-only /app/report route and send the primary CTA to the crypto evidence profile instead.
  • ASSISTANT-SUMMARY-LAYOUT (Bottom Summary Rail) — Moved the latest-brief workflow summary below the assistant workspace so the main analysis canvas is no longer compressed by a persistent right rail.
  • ASSISTANT-FOLLOWUP-WORKFLOW (Sticky Workflow Context) — Follow-up answers now keep the latest routed workflow summary visible instead of resetting the assistant rail to an empty state when the follow-up execution has no new workflow payload.
  • ASSISTANT-REPORT-WORKFLOW-RAIL (Visible Report State) — The assistant summary rail now renders the current AI Report workflow state and freshness when a company brief resolves.
  • ASSISTANT-REPORT-BLOCKED-COPY (Readable Blockers) — The assistant summary rail now renders user-readable report blocker messages when the AI Report workflow is not ready.

Internal

  • Added regression coverage for the assistant starter contract and backend security_readiness_brief workflow metadata.
  • Added regression coverage for the crypto trust_graph read-model contract, router payload exposure, and dashboard rendering source contract.
  • Verified the assistant workspace with local source-contract tests, dashboard lint, dashboard production build, changelog build, and a Playwright smoke render of /app/assistant.
  • Polished the assistant first fold so guided starter cards keep stable action buttons, avoid narrow four-column compression, and keep the workflow summary rail focused on outcome and next-step evidence.
  • Verified the readiness CTA handoff with a local browser smoke that runs the starter, checks the workflow metadata, and follows the report route.
  • Preserved the Web3 AI security-module research as an internal strategic input and linked it from the Q3 roadmap, product roadmap, and Security Readiness strategy.
  • Kept the broader AI security platform capabilities in future strategic scope; only the assistant readiness brief workflow is represented as a shipped slice.

Technical notes