docs: make the library loop discoverable from the served skill - #117
Merged
Conversation
The library is the bridge between analysis runs and synthesis - publish a finished reimplementation-spec, and later runs consume it - yet no served text mentioned it: no guide topic, no overview sentence, and the four library tools appeared nowhere outside server registration. Both full field-test runs finished specs that were never published (issue #113). New references/library.md guide topic covers the anatomy (marker, entries, generated index), all four tools with their contracts (content-hash idempotent publish, provenance fields, namespaces, reindex-after-merge), the publish moment at pipeline completion, and the distinction from the carrying-results-forward product-repo snapshot flow. SKILL.md links the topic and states the flow where rewrites are discussed; the guide test pins the topic's presence. Closes #113.
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.
Third 0.15.0 field-test finding: the analysis → publish → synthesis loop was unreachable by discovery.
codecarto_publish,codecarto_library_init,codecarto_library_list, andcodecarto_library_reindexappeared in zero files outside server registration; the guide had no library topic; the served overview never said the words. Both full field-test runs produced specs that were never published.Change
references/library.md: what a library is (marker, entries/, generatedindex.yaml/INDEX.md), the four tools with their real contracts (content-hash idempotent publish, requiredsource_repo/headline/spec, namespace rules, provenance fields, reindex-for-merge-conflicts), when to publish (the moment the spec validates, withcwdso provenance rides along),publish_confirm, and how it differs fromcarrying-results-forward.md's product-repo snapshot.library.Terminal
next_actionsrouting to publish lands separately in #114's PR.Suite green (the topic list is derived from the references directory, so the new file is served with no server change).
Closes #113.
🤖 Generated with Claude Code