chore: release packages - #74
Merged
Merged
Conversation
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@tenphi/akno@0.13.1
Patch Changes
20cb951,745a8c4,558954d,60db7e3]:@tenphi/akno-client@0.13.1
Patch Changes
@tenphi/akno-core@0.13.1
Patch Changes
#73
20cb951Thanks @tenphi! - Recognize bounded English and Russian queries about relayed reports, assistant speculation, unrealized benefits, fictional examples and competing hypotheses. Preserve clause boundaries so unrelated narrative words do not change factual queries into discourse inspection.#73
745a8c4Thanks @tenphi! - Preserve ordinary Markdown qualification under indented and closed ATX headings, and correctly end scopeat empty sibling headings. Reindexing upgrades existing derived classifications without editing source files.
Use consistent evidence-view precedence for mixed English/Russian queries, so a planning topic cannot hide
an explicit report, question, discussion, or history request in the other language. Explicit view and answer
language settings remain authoritative. These deterministic corrections do not establish live-model quality
or resolve the remaining language and discourse reliability limitations.
#73
558954dThanks @tenphi! - Keep indented headings inside their Markdown list item, preserving enclosing qualifications and rebuilding stale projections. Narrow multilingual routing so device error messages, incidental assistant speculation, conditional rejection and document titles do not hide the requested evidence.#73
60db7e3Thanks @tenphi! - Route bounded Russian requests about rejected proposals, plans and options to history, excluding negated and conditional rejection while preserving clause boundaries and higher-priority report or discussion views.Updated dependencies []:
@tenphi/akno-protocol@0.13.1