Tags: smaramwbc/statewave

chore: bump version to 1.5.0 (and propagate mirrors)

Server 1.5.0: timeline and resolutions pagination with newest_first windows
and has-more flags; numpy/httpx declared as runtime dependencies. Truth
(pyproject) and the README status lines move together per the release
checklist; issue-template version examples updated from the stale 1.0.0.

chore: bump version to v1.4.0

- pyproject.toml: 1.3.0 → 1.4.0
- README.md status blurb + active-development line to v1.4.0

Companion statewave-docs updates (banners → 1.4.x, overview.md v1.4
history entry, test-counts label → v1.4.0, product.md status line →
1.4.0) are landed via smaramwbc/statewave-docs#78 and #79. Release
workflow's verify-workspace-versions gate is green against 1.4.0 as
truth.

v1.3.0 — hybrid retrieval + compile pipeline

Hybrid retrieval (semantic + BM25) and compile-pipeline improvements. Search
defaults to hybrid. Non-breaking — existing deployments are unaffected.

chore: bump version to 1.2.0

v1.1.0 — compile-budget, NUL strip, idempotent ingest (migration 0025)

v1.0.0 — first stable public developer release

v0.9.2 — version-consistency & SDK-readiness stabilization patch

Stabilization patch on top of the canonical v0.9 governance release
(v0.9.1). No new backend features, no API changes, no schema
migrations.

Server changes
--------------
* pyproject.toml bumped from 0.9.0 to 0.9.2 so 'pip show statewave'
  reports a version matching the GitHub release. The v0.9.0 (stub,
  superseded) and v0.9.1 (canonical) tags both reported '0.9.0'
  from pip metadata; v0.9.2 closes that drift.

No code, behaviour, or API changes vs. v0.9.1. Operators upgrading
from v0.9.1 → v0.9.2 should expect zero functional difference;
only 'pip show statewave' now reports the right version.

Companion PRs landing in the same stabilization patch
-----------------------------------------------------
* statewave-py v0.10.1 — receipt verify/replay convenience methods
* statewave-ts v0.10.1 — verifyReceipt/replayReceipt + Receipt
  type completion
* statewave-examples — install-command fix
* statewave-web — stale v0.9 string sweep

v0.9.1 — v0.9 governance release correction

The v0.9.0 tag was cut too early (at e51a553) and does not contain
the v0.9 governance stack. v0.9.1 is the canonical v0.9 governance
release, including:

* Scheduled retention-purge worker (#162, closes #156)
* HMAC-signed receipts with tenant-scoped key ids (#163, closes #157)
* Heuristic auto-labeling pipeline (#164, closes #158)
* Receipt replay with embedded policy snapshot (#165, closes #159)
* Admin promote endpoint + admin-replay shim (#166, part of #160)
* Admin app: review queue, promote UI, receipt-detail replay button
  (statewave-admin#89, completes #160)
* Per-tenant residency with hard application-layer enforcement
  (#167, closes #161)
* Handoff receipts replay symmetry (#168)
* Release-hardening docs sweep across server, statewave-docs, and
  statewave-admin (#168 + statewave-docs#45 + statewave-admin#90)

No breaking API changes beyond the already-documented v0.9 surfaces.
v0.9.0 is superseded by this tag.

docs: align v0.8 shipped state

Surface the v0.8 Adoption shipments in this repo's user-facing docs.

What was stale or missing
- docs/capabilities.md did not list Memory templates (statewave#152
  feature in main); the full capability inventory was missing the
  feature.
- README.md "Use cases" tail listed "Plus four more" examples and did
  not acknowledge the three framework-integration quickstarts
  (LangChain, CrewAI, AutoGen) that shipped in statewave-examples#12.

What was updated
- docs/capabilities.md: one new bullet for Memory templates under
  "Core runtime" (the right category — templates are an ingestion
  pattern, not a governance feature), linking to docs/memory-templates.md.
- README.md: replaced the "Plus four more" tail with one that
  acknowledges the framework integrations, linking each.

What was intentionally left unchanged
- README.md Capabilities section — kept the curated 8-bullet list as-is;
  memory templates land in the fuller docs/capabilities.md inventory
  the README links to.
- README.md webhook event-filter mention — STATEWAVE_WEBHOOK_EVENTS is
  already documented in the configuration-reference table.

Validation
  git diff --stat
  → README.md (+1 -1), docs/capabilities.md (+1)

  grep -rni "planned\|coming soon\|memory template" README.md docs/capabilities.md
  (no stale matches)

v0.8.0 — State-assembly receipts + sensitivity-label policy

Two governance pillars land in this release:

- State-assembly receipts (#49): immutable, ULID-addressable audit
  artifact for every retrieval, with SHA-256 content-hash integrity,
  per-entry supersession status, caller identity, and policy decisions.
- Sensitivity labels and policy bundles (#50): per-memory TEXT[] labels
  + declarative YAML policy bundles with first-match-wins evaluation,
  log_only -> enforce rollout, and per-tenant configuration via
  optimistic-concurrency PATCH.

See CHANGELOG.md and docs/receipts.md + docs/sensitivity-labels.md.