feat(toolchain): add runtime capability registry - #371
Merged
Conversation
Introduce the canonical provider/tool registry, structured availability diagnostics, provider-aware planning, selected-tool fingerprints, CLI/SDK inspection surfaces, and generated registry documentation. Use the bounded process service for version probes, preserve provider identity through the transform graph, and make graph cache compatibility depend on the relevant selected toolchain rather than arbitrary host state. Closes #359
Pull Request Summary by devActivityMetricsAchievements
|
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
Introduces the runtime tool/provider capability registry and reproducible selected-toolchain fingerprint required by #359.
This makes external tool availability, compatibility, provider identity, and capabilities first-class planner inputs instead of scattered executable assumptions.
Architecture
crates/renderflow-core/data/tool-registry.yaml.ToolRegistryruntime model for built-in and runtime/plugin-provided tool capabilities.doctorand adds structuredtools list,tools inspect, and capability surfaces backed by the same machine-readable registry model.Built-in capability model
Registry descriptors capture stable tool/provider IDs, executable/version probes, supported platforms/architectures, capability IDs, media constraints, determinism, local/network behavior, fidelity/loss characteristics, required environment/configuration, validation notes, licensing/distribution notes, and fallback/substitution relationships.
Compatibility and boundaries
Tests
Coverage includes canonical registry parsing/validation, fake probe results, availability-state classification, version compatibility, stable tool/capability IDs, selected-toolchain fingerprint stability/change detection, provider-aware graph planning, runtime provider registration, registry-driven Tectonic availability checks, and the existing CLI/library/plugin example suite.
Final validation
Final review commit:
5f9e7a9865d321cc9fae869d5ff5b4afb64a0941(single Conventional Commit).All PR-triggered workflows passed on that exact SHA:
33442142287— successrenderflow --versionsmoke test, and artifact upload33442142327— success33442142130— successCloses #359