Skip to content

v0.7.0 — Governed recall and feedback-driven setup

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Sep 19:12
Immutable release. Only release title and notes can be modified.
v0.7.0
10f689f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

FAVA Trails 0.7.0 brings the feedback-driven changes since 0.6.0 into one release. It supersedes the unpublished 0.6.1 candidate.

What changed

  • Drafts stay out of default recall. Governed reads expose current approved records; authoring and historical access use explicit process identity and operator boundaries. PR #93
  • JJ installation uses current stable when needed, preserves compatible installed versions, and verifies published download hashes. The supported minimum and current-version CI coverage are separate from installation selection. #98
  • MCP registration and version reporting are corrected, with tested MCP SDK 2 support, installed wheel/sdist checks, and an upgrade test from 0.6.0. #83, #99
  • Trust Gate data egress is disclosed, and a bounded secret preflight rejects supported credential shapes before normal persistence or review. The rubric is not independent fact verification, and secret preflight is not complete DLP. #101, #102
  • Setup respects application configuration. Scope setup avoids application .env files by default; native MCP registration can be generated and verified explicitly. #103
  • Compact MCP descriptions are optional, and context measurement distinguishes schema size from observed client behavior. #104
  • Local-only repositories work explicitly. Sync distinguishes no remote from a configured but broken remote. #105
  • Rich Views adds scope dashboards, thought details, lineage and typed relationship navigation, with a managed local serving path. The owner waived the five-session acceptance wait; no measured adoption improvement is claimed. #51
  • Recall documentation now describes the actual lexical matcher. It is not semantic similarity search. #100

Upgrade

pip install --upgrade 'fava-trails==0.7.0'
fava-trails version

Restart the MCP connection after upgrading. A wrapper or source-runtime selector may still choose an older checkout even after a package upgrade. Configure FAVA_TRAILS_AGENT_ID for each ordinary authoring server; enable operator access only on a separate operator-controlled endpoint. Review governed recall before relying on historical-data visibility or identity behavior. Shared filesystem access is not a separate identity boundary.

The package includes reviewed migration/recovery tooling; installing it does not authorize or execute a migration of your trails data.

Verification and provenance

Publication uses the existing gated Release workflow: it tests the exact wheel and sdist, verifies native MCP registration and upgrade from 0.6.0, and compares the published PyPI artifact SHA-256 values before making the GitHub Release public. The attached candidate-SHA256SUMS binds artifacts to the tagged commit.

Assets 6
Loading