Repository navigation
Proposal/itf target composition with backwards compatibility for supported targets - #155
Draft
ihebs3ideni wants to merge 2 commits into
Draft
ihebs3ideni wants to merge 2 commits into
ihebs3ideni wants to merge 2 commits into
Conversation
ihebs3ideni
force-pushed
the
proposal/itf-target-composition-compatible
branch
7 times, most recently
from
November 12, 2026 12:21
28f0266 to
7bddb3f
Compare
ihebs3ideni
force-pushed
the
proposal/itf-target-composition-compatible
branch
from
November 12, 2026 12:39
7bddb3f to
bdcde52
Compare
Author
This branch has not been deployed
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
Propose composing ITF targets from self-describing capabilities and actions while preserving the original test API through the compatibility layer.
Proposed Model
Scope
This proposal PR adds only
docs/proposals/rfc.md. It contains no RST navigation or runtime implementation changes.The RFC links a reference implementation for evaluation and suggests possible review groupings without prescribing individual PRs, commit boundaries or landing order. Maintainers choose the integration strategy. Validation boundaries and remaining runtime limitations are recorded explicitly.
Review Requested
Feedback is requested on policy ownership, contract and version semantics, migration compatibility, and an integration strategy suitable for the project. Compatibility-layer support duration and eventual removal remain open decisions.