Skip to content

chore: regenerate SDK/CLI/schemas end-to-end with spatial-relations blueprint#27

Merged
pyramation merged 1 commit intomainfrom
devin/1776495606-regen-sdk-cli
Apr 18, 2026
Merged

chore: regenerate SDK/CLI/schemas end-to-end with spatial-relations blueprint#27
pyramation merged 1 commit intomainfrom
devin/1776495606-regen-sdk-cli

Conversation

@pyramation
Copy link
Copy Markdown
Contributor

Summary

Full regeneration of sdk/schemas, sdk/sdk, sdk/cli, packages/agentic-db, packages/agentic-db-services, and .agents/skills/cli-default/references after provisioning a fresh agentic-db that includes the five RelationSpatial entries (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:

  • CLI field rename — fullTextSearchunifiedSearch: 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.
  • ORM signature change — condition argument dropped: FindManyArgs<TSelect, TWhere, TCondition, TOrderBy>FindManyArgs<TSelect, TWhere, TOrderBy> in sdk/sdk/src/generated/orm/select-types.ts, with matching removals in query-builder.ts's buildFindManyDocument / buildFindFirstDocument and in every generated models/*.ts. The underlying GraphQL connection fields apparently no longer surface a condition: arg, so the ORM regen drops it. Any downstream code calling .findMany({ condition: { ... } }) will break at compile time.
  • Regenerated .graphql SDL now includes spatial-relation filter fields on the 6 geo-bearing tables (memories/trips/places/contacts/events/venues) via the @spatialRelationRelationSpatial path.

Companion PRs (independent, both already sent for review):

  • constructive-db#863 — relaxes validate_blueprint_definition to allow metadata-only blueprints (empty tables[] + relations[]). Required for this regen to provision at all.
  • constructive-db#865 — fixes ast_helpers.smart_comments to emit real \n instead of literal \\n between smart tags. Required because this regen produces columns with three @spatialRelation tags each.

The regen was produced locally after applying both fixes via CREATE OR REPLACE and manually seeding services_public.apis + domains entries for the user DB (local-dev only; production platform wires these automatically).

Review & Testing Checklist for Human

  • API break — condition removal in FindManyArgs / FindFirstArgs. Grep any consumer of @agentic-db/sdk for .findMany({ or .findFirst({ using a condition: key. This was present in the previous generated output and is gone now. Confirm no live code paths break.
  • CLI field rename — fullTextSearchunifiedSearch. Verify any scripts, docs, shell aliases, or agents that still reference --where.fullTextSearch on an agentic-db CLI command. Those commands will now reject the field name.
  • Merge order with upstream PRs: this PR's regen presumes constructive-db#863 and #865 are live. If this lands before the companion PRs are merged and a constructive-db release ships, CI here may still pass (it doesn't re-provision from scratch), but a future pnpm provision && pnpm export:all won't reproduce this output without those fixes. Safest is to land after both companion PRs are merged.
  • Spot-check a handful of regenerated files — suggest sdk/schemas/agentic-db.graphql (search spatialRelation), sdk/sdk/src/generated/orm/models/memory.ts, and one of the renamed alteration files under packages/agentic-db/verify/schemas/... to confirm only ordering/numbering changed.
  • Full reproduction:
    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

  • RAG / embedding-pipeline tests failed locally (18 failed) — every failure is 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.
  • This is purely codegen output — no hand-edited source files in this diff. If anything looks non-mechanical, that's worth flagging, but I didn't find any such edits in the sampling I did.

Link to Devin session: https://app.devin.ai/sessions/c5eeee65a3c546c4ac6753bb05fa03e0
Requested by: @pyramation

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-integration
Copy link
Copy Markdown

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@pyramation pyramation merged commit ba7e9ef into main Apr 18, 2026
8 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