connector-core Package Skill

Package: @epicdm/connector-core Repository: epic-flowstate-community Path: packages/connector-core Version: 0.2.6

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

Connector Core Git Kernel

Use this skill for the provider-agnostic Git connector kernel in packages/connector-core/src/git.

Source Map

• src/git/index.ts: public Git kernel export surface.
• src/git/types.ts: adapter, connection, entity, stream, sync, webhook, and policy contracts.
• src/git/GitConnectionService.ts: connection row lifecycle and in-memory store.
• src/git/FieldPolicy.ts: field ownership/conflict policy registry.
• src/git/RateLimitBudget.ts and src/git/RedisRateLimitBudget.ts: rate-limit accounting.
• src/git/EntityStreamRunner.ts: backfill/incremental stream execution.
• src/git/InstallationTokenCache.ts: installation token cache contract and memory implementation.
• src/git/WebhookRouter.ts: webhook routing and event persistence.
• src/git/conflictResolver.ts: field-level conflict behavior.

Mental Model

The Git kernel is provider-neutral. Provider adapters supply API-specific behavior, while the kernel owns durable connection rows, stream execution, field policy, rate-limit budget, token cache abstractions, and webhook event routing.

Implementation Flow

1. Start with types.ts and confirm whether the change belongs in the provider-neutral kernel or a provider adapter.
2. For connection lifecycle changes, update GitConnectionService and its store interface together.
3. For sync execution changes, follow EntityStreamRunner from stream request to batch handling and summary output.
4. For ownership/conflict behavior, update FieldPolicy and conflict resolver logic as a pair.
5. For production rate limiting, prefer RedisRateLimitBudget; use memory implementations only for tests or local-only hosts.
6. For webhook behavior, preserve idempotent event storage and route result status semantics.

Guardrails

• Do not import provider-specific code into the Git kernel.
• Keep tenancy checks explicit on connection rows and webhook routing.
• Treat installation tokens as short-lived secrets; do not persist them in logs or skill examples.
• Keep in-memory stores available for tests, but do not let them become the only production path.
• Update src/git/index.ts when adding a public kernel contract.

Verification

yarn workspace @epicdm/connector-core test -- Git
yarn workspace @epicdm/connector-core typecheck

If public Git kernel exports change, also build connector-core and typecheck downstream connector consumers.

Package Skill Inventory

Skill Inventory: @epicdm/connector-core

Package path: packages/connector-core.

Skillset

Composition Notes

• Use connector-core-integration-lifecycle before host UI or backend connector-service work.
• Use connector-core-manifest-connectors for YAML-driven API connectors and connector-core-provider-development for code-backed providers.
• Use connector-core-git-kernel before editing GitHub/Forgejo/GitLab-style adapters.
• Use connector-core-react-host-ui only in UI hosts; keep React imports out of service-side code.

Publication Readiness

Status: drafted, pending verification.

Before Dojo publication, rebuild package Dojo artifacts from this reviewed skillset and verify downstream consumers that rely on connector-core contracts.

Review Gate

Package Skill Review: @epicdm/connector-core

Package path: packages/connector-core.

Review Result

Status: drafted, source-backed, verified with one package-script lint blocker, pending publication.

The skillset is workflow-shaped around connector lifecycle, declarative manifests, provider development, Git kernel infrastructure, and React host UI.

Checks

• Source review: completed from package exports, core/react barrels, integration service, sync config service, provider registry, base provider, manifest runtime/schema, Git kernel, React hooks/components, and generated artifact drift.
• Skill inventory: completed.
• Skill files: completed.
• Verification: completed.
• Generated Dojo replacement: pending.
• Cloud Dojo publication: pending.

Verification Commands

Commands run:

yarn workspace @epicdm/connector-core test
yarn workspace @epicdm/connector-core typecheck
yarn workspace @epicdm/connector-core build
yarn workspace @epicdm/connector-core lint
yarn nx build @epicdm/connector-core
yarn workspace @epicdm/flowstate-connector typecheck

Results:

• Skill file ASCII scan passed.
• Tests passed: 69 suites, 1055 tests passed, 7 skipped.
• Typecheck passed.
• Package build passed with existing esbuild direct-eval warnings from src/manifest/load.ts.
• Nx build passed; dependent flowstate-crypto and flowstate-collections builds came from cache; Nx Cloud reported the existing unconnected-workspace 401.
• Downstream @epicdm/flowstate-connector typecheck passed.
• Lint did not run because the package script resolved eslint as missing: command not found: eslint.

Optional contract drift checks:

rg -n "@epicdm/connector-core|connector-core" packages docs docker
rg -n "connector-core.d.ts|registerBuiltInProviders|getBuiltInProviderIds" packages/flowstate-connector packages/connector-core

Publication Gate

Do not publish existing .flowstate/dojo artifacts until they are rebuilt from reviewed package skills.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/connector-core/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.