Skip to content

release: v0.16.1#131

Closed
Fail-Safe wants to merge 4 commits into
mainfrom
next
Closed

release: v0.16.1#131
Fail-Safe wants to merge 4 commits into
mainfrom
next

Conversation

@Fail-Safe

@Fail-Safe Fail-Safe commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Summary

Patch release for the federation and consolidation fixes currently on next.

  • Normalize live vector clocks so legacy display-name buckets are pruned from current federation state, event emission, merge, and conflict comparison paths.
  • Tighten short-to-mid consolidation scoring so one-source provenance traces do not promote from passive search hits alone.
  • Add regression coverage for legacy vector-clock cleanup and one-source promotion scoring.

Validation

  • go build ./...
  • go test ./...
  • go vet ./...
  • go test -race ./...
  • Hermes MCP smoke test: list, create, recall, and search all passed in a test cortex.

Fail-Safe and others added 4 commits June 11, 2026 00:00
keygen is a top-level command but was only mentioned in the federation
event-signing prose; add it to the command table next to the federation
block so it's discoverable when scanning the command list.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Fail-Safe

Copy link
Copy Markdown
Owner Author

Closing this release PR because next carries pre-squash history against main. I will open a clean v0.16.1 patch PR from a branch based on main with only the fix cherry-picked.

@Fail-Safe Fail-Safe closed this Jun 17, 2026
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