[developer-docs] Developer Documentation Consolidation - 2026-04-14 #26198
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Developer Documentation Consolidator. A newer discussion is available at Discussion #26403. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Analyzed 75 markdown files in
scratchpad/. Fixed 12 tone issues across 2 spec files and added new content toscratchpad/dev.md(bumped to v6.0) from PR #26154.Critical Issues Fixed
engine-architecture-review.mdcomprehensivefrom assessment, guide, and testing referencesfile-inlining.mdcomprehensivefrom testing and documentation bulletsNew Content Added
scratchpad/dev.md— GitHub MCP Guard Policies section: Added documentation for theintegrity-reactionsfeature flag introduced in v0.68.2 (PR #26154). Key behavior:features.integrity-reactions: trueenables reaction-based trust signals (👍 ❤️ to promote, 👎 😕 to demote)cli-proxy— users do not need to set both flags manuallyTHUMBS_UP/HEART, disapprovalTHUMBS_DOWN/CONFUSED,endorser-min-integrity: approvedView Tone Adjustments Made (12 fixes)
engine-architecture-review.md (10 fixes)
comprehensive documentation have been added to further enhance extensibilitydocumentation have been added to extend the architectureComprehensive MCP supportMCP supportNo comprehensive guide existed for adding new enginesNo guide existed for adding new enginesCreated comprehensive adding-new-engines.mdCreated adding-new-engines.mdAssessment: ✅ **Comprehensive**. Automated validation...Assessment: ✅ Automated validation...No comprehensive developer guide for adding enginesNo developer guide for adding enginesDevelopers have comprehensive guidanceDevelopers have implementation guidanceCreate comprehensive guide for adding new enginesCreate guide for adding new enginesComprehensive Engine Implementation GuideEngine Implementation GuideComprehensive testingTestingfile-inlining.md (2 fixes)
Comprehensive testing with unit testsTesting with unit testsComprehensive documentationDocumentationView Consolidation Statistics
Context
PR #26154 (
fix: correct integrity level descriptions and auto-enable cli-proxy for reactions) was the triggering code change. The compiler now implicitly enablescli-proxywhenintegrity-reactions: trueis set, which removes the requirement for users to set both feature flags. This behavior is now documented inscratchpad/dev.md.References:
Beta Was this translation helpful? Give feedback.
All reactions