feat(knowledge): generate versioned library introductions - #603
Closed
LikiosSedo wants to merge 1 commit into
Closed
LikiosSedo wants to merge 1 commit into
LikiosSedo wants to merge 1 commit into
Conversation
Collaborator
Author
|
Superseded. Siclaw delivery has moved off this public repository; this change is continuing on the internal Siclaw repo. Closing the public PR. |
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.
Summary
A library name and short domain sentence do not explain the Wiki's topic relationships, applicability or reading order. Extend compilation to generate a complete
.library-introduction.jsonbeside the Wiki pages, using the same summary as the existing domain subtitle. Full and incremental compilation and the full-catalog refresh flow review the whole finished Wiki before reporting the introduction.Validate required sections, size and existing confined reading paths. Agent catalogs expose every library's summary, bounded overview preview, sample questions and full-introduction entry. Complete prose remains in the versioned artifact; previews are explicitly samples and do not exclude libraries from search. Introduction metadata does not become answer-page evidence.
The artifact travels through the existing snapshot/package path without a new production dependency. Legacy packages remain usable. The schema and publishing/consumption contract are documented in
docs/design/library-introduction.md.Validation
Normal-agent routing and answer-quality measurements on representative real libraries remain a separate acceptance step. No deployment is included.