Skip to content

CAP-001 Phase 2D provider hardening - #137

Draft
csailer wants to merge 5 commits into
developmentfrom
feature/cap-001-provider-hardening
Draft

CAP-001 Phase 2D provider hardening#137
csailer wants to merge 5 commits into
developmentfrom
feature/cap-001-provider-hardening

Conversation

@csailer

@csailer csailer commented May 27, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Completes CAP-001 Phase 2D provider hardening and compatibility closure.
  • Adds regression coverage for existing DB reuse, repeated export/verify reads, malformed data behavior, legacy DB upgrade, and deterministic rehydration.
  • Hardens internal SQLite provider health for connectivity, migration/schema readiness, writable state, and closed provider lifecycle.
  • Finalizes CAP-001 storage abstraction documentation and phase completion assessment.

Validation

  • go test ./...
  • go vet ./...
  • go build -o bin/yanzi ./cmd/yanzi
  • make docs-build
  • Fresh DB representative CLI workflow: project create/list/use/current, capture, list, show, checkpoint create/list, rehydrate, verify, chain, export markdown/json/html
  • Repeated CLI workflow: verify, rehydrate, export json
  • Upgraded DB compatibility: legacy SQLite upgrade and rehydration regression coverage

Notes

  • SQLite remains the only provider.
  • No provider config switching, runtime, REST, federation, MCP, schema redesign, or user-visible behavior changes are introduced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant