ubiquitous-invention/plans/Plan-multitenant-cursor-sync/Epic-cursor-sync-layer/Epic-cursor-sync-layer.md
Randall Stillwell 663bc77afe feat: ECHODO app shell, Coolify deploy, Authentik + Umami
Bundles in-flight ECHODO work with the Coolify deployment configuration:

App
- New routes: ai, forms, planner, settings (templates/types), teams,
  doc detail, whiteboard detail
- New components: app shell rework (icon-rail, top-header), forms
  builder/renderer/responses, types manager, objects creation dialog,
  card primitive, form + overview views
- New tRPC routers: favorites, forms, types, workspaces; updates to
  health and objects routers
- Markdown backlog sync (packages/database) + cursor-sync schema/migrations
- Schema additions: forms, types, favorites, markdown_backlog, cursor_sync
- Initial Drizzle migrations checked in

Deployment
- docker/docker-compose.coolify.yml: drops bundled Postgres/Redis
  (uses CT 102 shared services), removes host port mappings, adds
  Coolify SERVICE_FQDN_* magic vars for web + collab
- .env.example rewritten as the full ECHODO/Coolify variable manifest
- NextAuth gains an Authentik OIDC provider (gated on env presence)
- Root layout injects Umami tracking script when configured;
  metadata title flipped to ECHODO

Security
- .gitignore expanded to exclude AGENT-DEPLOY.md, .env.*, secrets/,
  credentials.*, *.key, *.crt, *.pem, ssh keys

Made-with: Cursor
2026-04-26 14:34:34 -05:00

1.4 KiB
Raw Blame History

kind slug title plan_slug status priority tenant_id cursor_epic_id updated_at
epic cursor-sync-layer Cursor integration and bidirectional to-do sync multitenant-cursor-sync ready P0 global null 2026-04-26

Epic objective

Implement the data integration layer that maps internal plans/epics/tasks to Cursor artifacts and runs push, pull, and optional reconciliation per tenant.

In scope / out of scope

In scope

  • Mapping schema (see config/CursorSync.md)
  • API stubs or routers for sync triggers
  • Polling job skeleton; webhook handler behind feature flag

Out of scope

  • Cursor product features not exposed by API (document as risk; use export fallback)
Task Link
Mapping model and migration ./Task-mapping-model-and-migration.md
Push/pull job interface ./Task-push-pull-job-interface.md

Dependencies

  • Depends on: Markdown backlog epic (stable paths + frontmatter)
  • Blocks: None for MVP if file export is enough for v0

Acceptance criteria

  • Tenant can store cursor_plan_id / cursor_todo_id on entities (DB or sidecar table).
  • One documented manual flow: export task list to Cursor via copy or file.

Proposed timeline

Phase Window Notes
Spec Week 1 config/CursorSync.md
MVP Week 24 Mapping + manual id