Add cross-language readiness checks and offline fixture probes - #1
Open
haddanki-personal wants to merge 1 commit into
Open
haddanki-personal wants to merge 1 commit into
haddanki-personal wants to merge 1 commit into
Conversation
Add doctor, revision-specific analysis preflight, strict compatibility checks, offline production-instrumentation probes, and toolchain-aware baseline cache identities. Preserve readiness diagnostics through MCP and CI and package deterministic fixtures. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4d14fc06-a348-44f0-a68c-55174c5cad3c
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.
Summary
Adds a shared readiness stage before expensive instrumentation and analysis, covering .NET, Java, Node/TypeScript, Go, Rust, and Python.
realdiff doctor <repo> [--json] [--out <file>] [--probe]through the native and managed entry points.--readiness-probefor analysis and warm.readiness.jsonthrough CLI failures, MCP, and CI/action integrations.Intentional behavior changes and limits
Validation
Local execution was on Windows using SDK 10.0.401 because the repository-pinned SDK 8.0.424 was not installed. Windows/Linux CI coverage is configured; Linux was not executed locally. The existing native
detectGradle-marker gap remains outside this change; managed detection and doctor routing are separate from that limitation.