docs: root README + Architecture accuracy pass (ai-autopilot framework + connectors family)#132
Merged
Merged
Conversation
… (README, Architecture, package guide)
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.
Two accuracy gaps in the root docs, same "make the README/Architecture match what shipped" goal.
1. ai-autopilot was described as just its Supervisor seed.
ai-autopilotrow expanded to the full AI-building framework (personas/presets, runner, surfaces, decisions ledger, the loop + prompt library, bootstrap, scale mode); examples line now lists all three quickstarts.ai-autopilotsection said "parked as a design sketch / records direction, not a committed API", contradicting the doc's own header and ship-order table. Rewritten to "shipped", keeping the design rule and enumerating what got built.2. The connectors family was missing entirely.
@gemstack/connectors+connector-github+connector-google-driveexist and are documented (docs/packages/connectors*.md) but were never added to the README table or the layering diagram.mcpaxis, notai-*), and added a short "Connectors" subsection explaining thedefineConnector/mountConnectorscontract and the extensibleconnector-*pattern.@gemstack/mcp)" section on the server-framework axis.Note: the connectors packages are built but not yet published (v0.0.0) — their npm badges resolve once the open release PR #92 merges.
Docs only, no changeset. The VitePress site rebuilds from
docs/in CI.