Repository navigation
Correct capability documentation and exclude compiler caches from releases - #11
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
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.
The learning guide presents repeat suppression as active even though its rules are not connected to the repair loop. The search guide says individual invocation receipts and external MCP connections are absent, although the broker and reviewed GitHub adapter provide them. Correct those capability descriptions, include native knowledge lookup in the broker summary, and use lowercase forge in ordinary prose while preserving legal attribution.
Exclude generated TypeScript compiler caches from source archives and reject them in both release archive types. A native source build previously included ignored caches; the corrected build excludes them and its wheel retains all 185 runtime bytes, including Studio.
Validation: six boundary RED cases then eight passing archive/checksum cases; native source-to-wheel reconstruction; strict docs, 55 discovery pages/cards, 56 HTML pages and 5,980 local links; focused documentation browser cases and static checks. Root repeated the combined archive tests, strict/link/discovery gates and Ruff. Runtime, APIs, versions, existing URLs, diagrams and screenshots are unchanged. Published v0.2.3 assets remain immutable. General OAuth work is separate.
The documentation browser helper previously accepted SVG insertion before its layout was measurable. A native zero-geometry regression fails before the fix; readiness now requires the same successful snapshot to have a painted graph. All original geometry, raw-source and label checks remain. Validation: 11 focused Mermaid cases and 42 full documentation browser cases, then 11 focused cases on formatted source with an identical executable AST; configured lint and formatting passed. No product runtime changes.