Repository navigation
Update the product overview and Koinon migration status - #85
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.
The README still presented the retained knowledge stack as the product direction and mixed setup with detailed recovery internals. Reorganize it around product journeys, natural source-control interaction, implementation, QA and operation. Link Koinon as the selected unified knowledge platform and state clearly that its composed installer is still in development; the current Compose compatibility contract and retained data remain explicit.
Keep pyfly and larafly links, configurable providers, tool prerequisites, runner restrictions, framework refresh, learning and the API/SDK/MCP entry points. Remove stale version-specific recovery details from the landing page and link their maintained guides instead. Whole-product end-to-end acceptance remains explicitly pending.
Validation: all 37 local Markdown targets resolve; strict MkDocs passes and generates 72 checked social cards. Independent factual and Humanizer copy review found no blocker. README-only change; no application, dependency, UI or execution-policy source changes.