Skip to content

v0.4.0-beta.1 - Internal Beta

Choose a tag to compare

View all tags
@rafal-k rafal-k released this 22 Mar 01:10
· 55 commits to main since this release
v0.4.0-beta.1
6dac92b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.4.0-beta.1 - Internal Beta

This release adds post-run reliability analysis as a first-class workflow in both UI and MCP/CLI.

Highlights

  • Added After-Action Reports (AAR) for task runs:
    • backend endpoint: GET /api/task-runs/:id/after-action-report
    • deterministic report sections: what happened, variance vs expected, risks, remediation
    • explicit insufficient_evidence state when canonical outcome is missing
    • markdown export payload for sharing
  • Added Task Run AAR UI:
    • generate report on demand
    • copy markdown directly from Task Run detail view
    • report state resets after outcome changes to prevent stale summaries
  • Expanded MCP reliability coverage with new tools:
    • suboculo_get_reliability_kpis
    • suboculo_get_reliability_trends
    • suboculo_get_failure_mode_trends
    • suboculo_get_task_run_after_action_report
    • suboculo_record_task_run_outcome
  • Completed CLI workflow docs for reliability operations:
    • added prompt examples for Claude Code and OpenCode usage
    • added repeatable MCP Reliability Workflows (triage, comparison, postmortem)

Why this matters

Suboculo now supports a full loop:

  1. derive task runs,
  2. label outcomes,
  3. track KPI/trend signals,
  4. generate actionable after-action reports,
  5. run the same analysis from CLI via MCP.

Validation

  • node --check backend/server.js
  • node --check backend/mcp-analytics-server.mjs
  • npm --prefix backend run smoke
  • npm --prefix svelte-app run build

All checks pass for this release scope.

Assets 2
Loading