feat(codegen): pluggable embedding system with --auto-embed flag [CI]

[pyramation]

Summary

Adds a pluggable text-to-vector embedding system for generated CLI commands. When a table has pgvector embedding fields (Vector or [Float] gqlType), the codegen now:

1. Generates an embedder.ts runtime module using @agentic-kit/ollama — provides resolveEmbedder() (env vars → appstash config → null) and autoEmbedWhere() to convert text values in vector where-clause fields to real embedding vectors.

2. Injects --auto-embed flag into list and search handlers via a new buildAutoEmbedBlock() AST builder. When passed, the CLI resolves an embedder and converts text queries to vectors before sending to the GraphQL server.

3. Extends --auto-embed to create and update mutations via autoEmbedInput() and buildAutoEmbedInputBlock(). When --auto-embed is passed on a create/update command, text strings in vector fields are converted to embeddings before the ORM call. This is a CLI-only convenience until server-side triggers/job queues handle it.

4. Generates field-specific search examples in docs (README, skills) showing --auto-embed usage for vector fields (read and write paths), replacing the previous generic search examples.

5. Adds CLI e2e tests — verifies error without EMBEDDER_PROVIDER, plus conditional real Ollama/nomic-embed-text integration tests.

6. Renames --fields to --select across all CLI codegen, templates, docs, and e2e tests for consistency with the TS SDK's select parameter naming.

Embedding is opt-in via --auto-embed — no implicit behavior or field name clobbering. Configuration via EMBEDDER_PROVIDER, EMBEDDER_MODEL, EMBEDDER_BASE_URL env vars (or appstash config equivalents).

Updates since last revision

• --fields → --select rename: All CLI usage text, doc examples, runtime parseSelectFlag() (now reads argv.select), generated snapshots, and e2e tests updated for TS SDK consistency. The internal variable names (select, parseSelectFlag) were already correct — only the user-facing flag name changed.

Review & Testing Checklist for Human

• Verify @agentic-kit/ollama API: embedder.ts imports OllamaClient as default export and calls client.generateEmbedding(text, model). If this doesn't match the actual @agentic-kit/ollama@1.0.3 API, every generated CLI embedder will break at runtime. This is the highest-risk item since it was written without runtime verification.
• Validate { vector: query } key for embedding fields: buildSearchHandler changed the where-clause key from value to vector for embedding category fields (~line 693 of table-command-generator.ts). Confirm the graphile pgvector plugin expects vector not value as the input key for similarity search.
• Verify autoEmbedInput mutation integration: The auto-embed block is injected into the mutation handler's tryBody after cleanedData is created but before the ORM call. autoEmbedInput mutates data in-place (converts string values in vector fields to embedding arrays). Confirm the generated code positions the block correctly and that mutating cleanedData before passing it to the ORM is safe with the TypeScript type assertions (as CreateXxxInput[...] / as XxxPatch).
• Run codegen on a table with vector fields and inspect output: Verify the generated if (argv['auto-embed']) { ... } block appears in handleList, handleSearch, handleCreate, and handleUpdate — and that handleDelete does not include it.
• Spot-check --select rename: Verify that --select id,name works in a generated CLI command (replaces the old --fields flag). The runtime reads argv.select now — confirm minimist parses --select foo into { select: 'foo' } without conflicts.

Notes

• The Ollama e2e tests skip gracefully when Ollama isn't running — only the "no provider" error test runs unconditionally.
• The lockfile diff is large due to @agentic-kit/ollama resolution cascading through pnpm deduplication — not a code concern but worth a glance.
• autoEmbedInput is intentionally a temporary CLI-only convenience. The long-term plan is server-side triggers/job queues for embedding generation.
• buildSearchExamples / buildSearchExamplesMarkdown in docs-utils.ts now include create/update examples alongside the existing search examples.
• The --fields → --select rename was done for consistency with the TS SDK's select parameter. All 7 affected snapshots were regenerated and pass.

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

[devin-ai-integration]

🤖 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