docs: refresh documentation for 0.16.0 — fusion default, updated benchmarks, bundled skill bump - #1157
Closed
ajianaz wants to merge 1 commit into
Closed
docs: refresh documentation for 0.16.0 — fusion default, updated benchmarks, bundled skill bump#1157ajianaz wants to merge 1 commit into
ajianaz wants to merge 1 commit into
Conversation
…hmarks, bundled skill bump (#1156) * docs: refresh README (EN+ID) for 0.16.0 — fusion default, 500Q benchmarks, new features * docs: align strategy/version references with 0.16.0 defaults (fusion, install pins) * docs(roadmap): record v0.15.0 and v0.16.0 as released * docs: correct 500Q results-availability claim (aggregates in repo, raw on volume) * chore(skill): bump bundled uteke-memory-skill to 0.16.0 (fusion default, lifecycle, onboard) --------- Co-authored-by: ajianaz <ajianaz@users.noreply.github.com>
🔍 Cora AI Code Review✅ No issues found. Code looks good! Review powered by cora-code · BYOK · MIT |
Collaborator
Author
|
Superseded: branch-name policy requires chore/release-* for PRs into main (per Source Branch check). Reopened as PR from chore/release-docs-016-refresh. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Carry of #1156 (merged to develop) to
main— same presedent as #1042: content commits go to develop first, then are carried to main outside release cycles so main does not advance to unreleased develop content.Post-release documentation refresh for v0.16.0 (released 2026-08-29 from main). Docs were still describing the 0.14.3 era:
docs/BENCHMARKS.mdlinkinclude_str!): 0.10.0 → 0.16.0, strategy enum includesfusiondefault,lifecycle/onboardrows addedbenchmarks/longmemeval/RESULTS.md, raw results stay on the Modal benchmark volume. No numbers changed.Why
v0.16.0 made
fusionthe default recall strategy, but the public front page, the bundled skill asset, install pins, and several doc pages still described pre-0.15 behavior. Users installing v0.16.0 read instructions for v0.14.3.Testing
include_str!asset, no test asserts its literal content