Skip to content

v2.4.2 — RFC-010 hotfix + RFC-009 Phase 0.5

Choose a tag to compare

View all tags
@rolandpg rolandpg released this 24 Apr 22:35
v2.4.2
b576007
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Patch release bundling the RFC-010 enrichment-pipeline hotfix with the RFC-009 Phase 0.5 latency-attribution instrumentation and preliminary attribution artifact. Full response to the 2026-04-24 Vigil telemetry audit.

Highlights

  • fix(enrichment): RFC-010 — OllamaProvider timeout plumbing + consolidation shutdown race guard (#88)
  • feat(telemetry): RFC-009 Phase 0.5 — per-phase timers in remember() via phase_timings_ms (#90)
  • docs: Phase 0.5 preliminary attribution — 98.4% of remember() wall-clock is LanceDB notes_cti writes; 7,356 uncompacted fragments identified (#91)

Honest scope note

This release does NOT yet address:

  • The ~2,329 daily enrichment-job drops — those are driven by HTTP 200 + empty Ollama responses, not by hangs. Fix ships in RFC-009 Phases 1–3 (v2.5.0: durable outbox + circuit breaker).
  • LanceDB fragment accumulation — identified here but not fixed here. RFC-009 is being revised to add periodic compaction to Phase 1 scope.

Upgrade action (Vigil)

Bump Vigil's ZettelForge pin to 2.4.2, restart, run ~1h of representative CTI traffic. The new phase_timings_ms will be emitted inside ocsf_api_activity events in zettelforge.log — this refines or falsifies the preliminary Phase 0.5 attribution in docs/superpowers/research/2026-04-24-phase-0.5-attribution-prelim.md.

See CHANGELOG.md for the full set of changes.

Assets 2
Loading