Beava v0.0.6

chore(release): bump version to 0.0.6 (#154)

Cuts 0.0.6: the Phase 27.1 snapshot fork-COW + WAL hardening (SEV-1
incident fix) and docs alignment, both already merged to main via #152.

• Bump Cargo.toml (workspace) + python/pyproject.toml to 0.0.6
• Refresh Cargo.lock
• CHANGELOG [0.0.6] entry

Tag v0.0.6 will be pushed after merge to fire the release workflows
(GitHub Release, wheels, Docker, Homebrew).

---

Co-authored-by: Hoang Phan hoang@beava.dev
Co-authored-by: dosubot[bot] <131922026+dosubot[bot]@users.noreply.github.com>

Beava v0.0.5

chore: bump version to 0.0.5

Beava v0.0.4

feat(home): green Decision column for passive (no-action) reflexes (#114)

Summary

The Live Product Reflexes feed on the home page renders every
decision in accent orange today, which makes a non-firing row
(`continue monitoring`, `keep default ranking`, `allow`, `keep
value picks`) visually indistinguishable from a firing one (`require
approval`, `boost trending item`, `launch setup rescue`, …).

This PR colours passive decisions in `var(--beava-success)` so the
reader can tell at a glance which rows fired and which didn't. Active
decisions keep the existing accent orange. One regex covers the four
passive strings the synthetic feed can emit:

```js
/^(continue monitoring|allow|no action|keep .+)$/i
```

The static PipelineShowcase rows lower on the page are all action-firing
examples by construction (the threshold-above scenario), so they stay
orange.

Test plan

• Render `/` — confirm passive rows (`continue monitoring`,
  `keep default ranking`, etc.) are green; active rows (`require
  approval`, `boost trending item`) stay orange.
• Both the `→` arrow and decision text take the new colour
  together.
• PipelineShowcase rows (`session_44.risky_tools_10m = 2 → require
  approval`, etc.) remain orange.

---

Co-authored-by: Hoang Phan hoang.phan@viggle.ai

Beava v0.0.3

fix(release): sync workspace Cargo version 0.0.0 → 0.0.3 (#77)

Bumps the workspace Cargo.toml version that was left lagging behind
python/pyproject.toml since launch. After this lands, retag v0.0.3 —
beava --version will then match pip show beava.

Co-authored-by: Hoang Phan hoang.phan@viggle.ai

Beava v0.0.2

chore(release): bump 0.0.1 → 0.0.2 (#74)

Bumps pyproject + cargo crate version (so beava --version matches pip show beava). Tag triggers the homebrew workflow with tarball assets in
place per #73.

Co-authored-by: Hoang Phan hoang.phan@viggle.ai

Beava v0.0.1

chore(release): bump 0.0.0 → 0.0.1 for first PyPI publish (#72)

Bumps python/pyproject.toml version to 0.0.1 + adds a CHANGELOG entry.
The v0.0.0 tag was pushed pre-PyPI gate; rather than force-pushing the
tag, this advances to v0.0.1 as the inaugural PyPI release.
Source-identical to v0.0.0.

Co-authored-by: Hoang Phan hoang.phan@viggle.ai