Repository navigation
docs(msdmd): align public contract with native readers - #114
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5de6068b58
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3ea19c02c1
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Summary
skills.json,msdmd/SKILL.md, or merged fix(msdmd): integrate native standards readers and fail-closed coverage #111Scope
This is a documentation/public-contract repair. It does not add reader behavior. The implemented reader surface remains exactly the existing schema-2 supported subset in
msdmd/collect.py/msdmd/readers.py, plus the separate Python module projection runner.Verification
GitHub checks are required for terminal verification. I could not run the repository's local stdlib suite from this connector-only path.
hmmm
Downstream propagation into Stack and other consumers remains a separate exact-source-pinned refresh after this PR merges.