Skip to content

feat(spec): remove extends support - #36

Merged
rohangpta merged 2 commits into
masterfrom
codex/remove-spec-extends
Sep 1, 2026
Merged

feat(spec): remove extends support#36
rohangpta merged 2 commits into
masterfrom
codex/remove-spec-extends

Conversation

@rohangpta

Copy link
Copy Markdown
Contributor

Summary

  • removes SPEC inheritance from the compiler and compiled IR
  • removes extends-only local workspace artifact and session-manifest machinery
  • stops registry skill discovery from traversing parent specs
  • removes the unused Harbor adapter option
  • rejects an extends field explicitly instead of silently ignoring it

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

  • go vet ./...
  • go test ./...
  • go test -race ./...
  • python3 -m unittest integrations.harbor.telos_agent_test
  • ruff check integrations/harbor/telos_agent.py integrations/harbor/telos_agent_test.py
  • ruff format --check integrations/harbor/telos_agent.py
  • git diff --check

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.
@rohangpta
rohangpta merged commit 55197c1 into master Sep 1, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant