feat(spec): remove extends support - #36
Merged
Merged
Conversation
SPEC inheritance was never part of the intended product surface, but the parser, compiler, local workspace runtime, registry prefetch, session manifest, and Harbor adapter still carried it. Remove that path end to end and reject extends explicitly so old specs fail clearly instead of being silently reinterpreted.
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
This belongs in the telos repository: Cloud has no independent extends implementation and consumes the Telos runtime contract.
Compatibility
Existing session JSON remains readable because retired fields are ignored during decoding. New plans, applies, and runs containing extends fail with a direct unsupported-field error.
Merge after #35 so the public telos-cli documentation lands before the implementation is retired.
Validation