feat(examples): add validated example catalog - #251
Merged
Merged
Conversation
mattsse
force-pushed
the
mattsse/examples-rpc-configuration
branch
from
July 16, 2026 14:35
706ead8 to
2e018c2
Compare
mattsse
force-pushed
the
mattsse/examples-catalog
branch
from
July 16, 2026 14:39
29fc63c to
c1651fc
Compare
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
Why
Cargo metadata exposed a helper module as a runnable example, while the human README omitted a real receipt-decoding target. Agents and users also had no structured way to distinguish offline examples from examples requiring networks, processes, credentials, or hardware.
Impact
Every real example now has a stable discovery record and a CI-enforced README entry. Consumers can select compatible examples without trial-and-error, and shared helpers no longer pollute the executable target list.
This PR is stacked on #250 so cataloged runtime requirements match the explicit endpoint configuration introduced there.