Skip to content

feat: add content type intake policy support#1654

Open
ebarroca wants to merge 9 commits into
mainfrom
feat-ai-intake
Open

feat: add content type intake policy support#1654
ebarroca wants to merge 9 commits into
mainfrom
feat-ai-intake

Conversation

@ebarroca

@ebarroca ebarroca commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add shared content type intake policy fields and JSON schema for type-driven text conversion, extraction, rendering, and embedding behavior.
  • Update workflow activities to use explicit text, vision, mixed, and auto extraction sources with fallback type assignment behavior.
  • Add schema-backed intake policy editor UI exports for content type configuration.
  • Fix the template smoke Verdaccio config so public scoped transitive packages proxy to npm while Vertesia/Llumiverse scopes stay local.

Test Plan

  • ../../node_modules/.bin/tsc -p tsconfig.json --noEmit (packages/common)
  • ../../node_modules/.bin/tsc -p tsconfig.json --noEmit (packages/ui)
  • ../../node_modules/.bin/tsc -p tsconfig.json --noEmit (packages/client)
  • ../../node_modules/.bin/tsc -p tsconfig.test.json --noEmit (packages/workflow)
  • ./node_modules/.bin/vitest run src/activities/generateDocumentProperties.test.ts src/activities/generateOrAssignContentType.test.ts (packages/workflow)
  • ./.github/bin/test-template-integration.sh --release-type snapshot --template "Vertesia Plugin"
  • CI for a72a862: Check codebase, Unit tests, Template smoke test (Plugin), CodeQL, and zizmor passed.

@ebarroca
ebarroca requested a review from a team as a code owner July 3, 2026 17:28
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