Repository navigation
feat(release): ship Jev-governed memory in v0.8.0 - #138
Conversation
|
Claude review findings were written locally at Failed to authenticate: OAuth session expired and could not be refreshed |
yia-mw-agent
left a comment
There was a problem hiding this comment.
Native Codex fallback review of exact head 3ebd0cc: no blocking findings in this documentation and metadata release change. Package/module/lockfile version values agree at 0.8.0; the calibration claims match the published 53-case aggregate report and disclose reference labels, threshold selection, and seven missed approval labels. Upgrade guidance preserves explicit policy selection and process-scoped identities; hosted review egress is disclosed. Announcement drafts contain no unsupported first/accuracy/latency claims. Existing implementation behavior is unchanged. Version policy, Ruff, and diff checks pass. Merge remains subject to the exact-head test checks and candidate verification. The one Claude review attempt failed due to expired OAuth; no successful external Claude review is claimed.
FAVA Trails has shipped the Jev Decisions integration on main, but the latest public package is still 0.7.0. This release change synchronizes package/module/lockfile versions at 0.8.0 and gives the release a clear Jev story: a typed review decision, an explicit threshold, and durable promotion provenance.
Adds release notes, a long-form announcement, and owner-published LinkedIn/X/Hacker News drafts. The copy distinguishes the 53-case calibration replay from an independent benchmark, records the seven missed approval labels, explains hosted review egress and per-process identities, and preserves existing-install policy selection. The incomplete formal positioning workshop is left pending.
Validation: 1,119 tests passed, with the exact 0.8.0 wheel and sdist bound through
FAVA_CANDIDATE_WHEEL/FAVA_CANDIDATE_SDIST. Both artifact hashes remained unchanged. Version-policy check, Ruff, and diff checks pass. The native Codex fallback review found no blockers and is recorded at this exact head; the one Claude attempt failed because its OAuth session expired. GitHub release/PyPI publication will use the existing owner-gated workflow after protected merge. No runtime installation or social posting is included.