Repository navigation
docs: synchronize current usage and engineering records - #13
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.
Description
Gateway authentication guidance appeared after the license and the local example still installed an old source pin. Both READMEs now place connection guidance with usage, and the example installs public server 0.3.1a5. The engineering index states the HTTP-only/source-delivery scope and reconciles accepted notes.
Requested by the maintainer: synchronize recent changes into each repository's current documentation and
.agents/records. This is routine documentation maintenance; no new bug Issue or package publication is needed.Type of Change
Changes
Testing
Locked npm installation, typecheck, all 24 tests, actual public-a5 local runtime loop, package dry-run, 33 changed-document relative links and diff checks passed. The initial missing-runtime failure is preserved in the new evidence, followed by the fresh-environment passing rerun.
No runtime code changed. No new cloud experiment was run: the maintainer requested documentation synchronization, and prior real-component records remain referenced with their exact original versions/scope. Full latest-head remote CI remains a merge gate.
Checklist
.agents/evidence/verify/2026-10-24-current-docs-and-records.mdDefinition of Done
Documentation, links and owner record checks passed locally. Runtime tests/E2E were not newly required by this documentation-only scope; existing repository CI runs unchanged. Independent review and exact-head CI must pass before merging. No new release is included.