feat(projections): add provider-neutral agent adapters - #45
Merged
Conversation
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
aether.projection-interface/v1with a versioned provider registry and JSON Schema.github/agentsoutput rather than duplicating filesArchitecture
Provider formats remain generated adapters. Aether source is canonical; Empathy owns downstream integration profiles and Holon may materialize pinned Aether releases.
Authority and safety
manual-importuntil a repository-native custom-agent format is verifiedCompatibility
The existing entrypoint remains valid:
python3 library/organization/agents/build-projections.py \ --output-directory "dist"It delegates to the provider-neutral implementation while preserving the legacy
AGENTS_DIRoverride used by existing release tests. Existing./aether distribution buildand release validation therefore exercise every projection adapter without changing their command surface.Baseline repairs uncovered by CI
Aether's default branch was already failing PR validation before this work. Advancing #39 through the complete pipeline exposed two inherited defects that are repaired here rather than bypassed:
architecture/document.spec.mdhad a stale digest and the newarchitecture/set.spec.mdwas missing fromcatalog.v1.json. The catalog is regenerated from Aether's canonical generator.$id, causing its local fragment references to resolve as an invalid remote URL. The schema now uses Aether's absolutehttps://egohygiene.io/schemas/...namespace with a regression test.These are baseline synchronization/validation repairs; they do not broaden the provider-projection architecture.
Validation
Added focused tests for:
The complete Aether PR workflow is green:
gh skill publish "dist" --dry-runCloses #39