chore: regenerate SDK/CLI/schemas end-to-end with spatial-relations blueprint#27
Merged
pyramation merged 1 commit intomainfrom Apr 18, 2026
Merged
Conversation
Regenerates: - sdk/schemas/agentic-db.graphql — GraphQL SDL via introspection of the provisioned agentic-db with 5 RelationSpatial entries (nearbyContacts, nearbyMemories, nearbyPlaces on memories/contacts/places, plus trips.location_geo -> venues.location_geo, contacts.location_geo -> places.location_geo). - sdk/sdk/src/generated — ORM client with spatial-relation where-filters exposed on the generated models. - sdk/cli/generated — CLI commands mirroring the regen. - packages/agentic-db, packages/agentic-db-services — pgpm export output. - .agents/skills/cli-default/references — regenerated CLI reference docs. Unblocks three upstream fixes: - constructive-db#844 (RelationSpatial blueprint node) now exercised end-to-end. - constructive-db#863 (empty-tables[] metadata-only blueprints). - constructive-db#865 (smart_comments real-newline separator — required for multi-tag columns like the three @spatialRelation tags per geo field). ORM integration tests pass against the regenerated client; RAG/embedding tests fail on Ollama unavailability (unrelated, pre-existing env dependency).
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
4 tasks
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
Full regeneration of
sdk/schemas,sdk/sdk,sdk/cli,packages/agentic-db,packages/agentic-db-services, and.agents/skills/cli-default/referencesafter provisioning a fresh agentic-db that includes the fiveRelationSpatialentries (nearbyContacts,nearbyMemories,nearbyPlaces,trips.location_geo → venues.location_geo,contacts.location_geo → places.location_geo) shipped earlier in this chain.~5,500 files touched; almost all is pure codegen (alteration renumbering, mirrored model files, regenerated CLI reference docs). The changes that are not structurally trivial:
fullTextSearch→unifiedSearch: reflected everywhere in.agents/skills/cli-default/references/*.md. This tracks an upstream rename in the public GraphQL API; the regenerated CLI now expects the new field name.conditionargument dropped:FindManyArgs<TSelect, TWhere, TCondition, TOrderBy>→FindManyArgs<TSelect, TWhere, TOrderBy>insdk/sdk/src/generated/orm/select-types.ts, with matching removals inquery-builder.ts'sbuildFindManyDocument/buildFindFirstDocumentand in every generatedmodels/*.ts. The underlying GraphQL connection fields apparently no longer surface acondition:arg, so the ORM regen drops it. Any downstream code calling.findMany({ condition: { ... } })will break at compile time..graphqlSDL now includes spatial-relation filter fields on the 6 geo-bearing tables (memories/trips/places/contacts/events/venues) via the@spatialRelation→RelationSpatialpath.Companion PRs (independent, both already sent for review):
validate_blueprint_definitionto allow metadata-only blueprints (emptytables[]+relations[]). Required for this regen to provision at all.ast_helpers.smart_commentsto emit real\ninstead of literal\\nbetween smart tags. Required because this regen produces columns with three@spatialRelationtags each.The regen was produced locally after applying both fixes via
CREATE OR REPLACEand manually seedingservices_public.apis+domainsentries for the user DB (local-dev only; production platform wires these automatically).Review & Testing Checklist for Human
conditionremoval inFindManyArgs/FindFirstArgs. Grep any consumer of@agentic-db/sdkfor.findMany({or.findFirst({using acondition:key. This was present in the previous generated output and is gone now. Confirm no live code paths break.fullTextSearch→unifiedSearch. Verify any scripts, docs, shell aliases, or agents that still reference--where.fullTextSearchon anagentic-dbCLI command. Those commands will now reject the field name.pnpm provision && pnpm export:allwon't reproduce this output without those fixes. Safest is to land after both companion PRs are merged.sdk/schemas/agentic-db.graphql(searchspatialRelation),sdk/sdk/src/generated/orm/models/memory.ts, and one of the renamed alteration files underpackages/agentic-db/verify/schemas/...to confirm only ordering/numbering changed.pnpm install && pnpm --filter @agentic-db/integration-tests test— ORM tests should all pass. RAG/embedding tests will fail without a local Ollama at:11434(pre-existing env dependency, unrelated to this regen).Notes
FetchError: request to http://localhost:11434/api/embeddings failed. CI should either skip them or have Ollama; either way, those failures are unrelated to this PR.Link to Devin session: https://app.devin.ai/sessions/c5eeee65a3c546c4ac6753bb05fa03e0
Requested by: @pyramation