Repository navigation
Align reporting diagnostics and signed runtime guidance with MCP operations - #75
Merged
Merged
Conversation
…boundary-2026-10-09
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 public MCP descriptor now advertises named workflow operations, so the reporting diagnostic must recognize that catalog without treating it as this peer's authenticated runtime inventory. Keep the signed
commanderruntime contract, fix the recommendation narrative path, and remove invented deviation-tool and blind write-retry guidance.Direct chronicle and callable commander recommendation reporting both read
chronicle.reportingNarrative.briefMarkdown, matching the canonical MCP producer. Client attribution is supplied only where declared, and a public descriptor is not treated as authenticated runtime discovery.Native Codex listing metadata now follows the current public submission limits: a 25-character subtitle, the required HTTPS support URL, and guarded listing lengths and all four HTTPS URLs without credentials. The default briefing prompt uses the actual nested narrative path within its 128-character limit. Native root
interface, MCP configuration, signed commander policy and lifecycle hooks remain coherent. This runtime package is distributed manually or through the local Codex marketplace: official public submissions exclude lifecycle hooks; the separate ChatGPT candidate is hook-free.Validation:
npm run check;npm test(218 passed, 2 existing Wizard integration skips), repeated after adversarial review. Focused negative cases reject overlong metadata, missing support URL, non-HTTPS/credential-bearing URLs and overlong URLs.npm pack --dry-runconfirms the imported validator is packed alongside the native manifest and hooks. Verified published PR diff against the clean local commit and distinct commander runtime profile. Merged current main, including security release changes. Default operation discovery and Gateway terminal outbox remain distinct from the peer's signed runtime policy.