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

3.2 KiB

Raw Blame History

Cursor sync configuration

This document describes how the application and Cursor should keep plans, epics, and tasks aligned. Implementation is incremental; treat this as the contract the data layer and jobs will follow.

Goals

App → Cursor: Tasks and status updates in the app appear as Cursor to-dos / plan items where configured.
Cursor → App: To-dos created or completed in Cursor are mirrored into the correct plan/epic in the app.
Markdown as source of truth (optional mode): Repo markdown can be authoritative; the app imports on change, or the app exports on change—policy is per tenant (see Modes).

Multitenancy

Each tenant has its own:
- API credentials or OAuth connection to Cursor (when available).
- Mapping table: internal plan/epic/task id ↔ Cursor identifiers ↔ filesystem paths under plans/.
No cross-tenant sync or shared Cursor workspace.

Modes (to implement)

Mode	Behavior
`markdown_authoritative`	Watch `plans/**`; import on save; push summaries to Cursor.
`app_authoritative`	UI/API edits win; export markdown + update Cursor on commit or interval.
`bidirectional`	Reconcile by `updated_at` and explicit conflict rules (last-write-wins per field or manual resolution).

API surface (target)

Lightweight endpoints or jobs (names indicative):

POST /api/v1/tenants/:tenantId/plans — create plan + optional seed markdown paths.
GET/PATCH /api/v1/tenants/:tenantId/plans/:planId — read/update metadata and Cursor mapping.
GET/PATCH /api/v1/.../epics/:epicId, .../tasks/:taskId — same for epics and tasks.
POST /api/v1/tenants/:tenantId/sync/cursor/pull — ingest Cursor to-dos into tasks.
POST /api/v1/tenants/:tenantId/sync/cursor/push — export task state to Cursor.
Webhook receiver (future): POST /webhooks/cursor for push notifications when Cursor exposes them; until then polling on a tenant schedule.

Mapping record (logical schema)

Implemented in Postgres as markdown_backlog_items plus cursor_sync_mappings (see docs/Glossary.md). Logical fields:

tenant_id → markdown_backlog_items.workspace_id (workspace object UUID)
plan_slug, epic_slug, slug (filesystem / frontmatter alignment)
cursor_plan_id / cursor_item_id → cursor_sync_mappings (nullable until connected)
last_pulled_at, last_pushed_at, sync_content_hash on the mapping row
content_hash on the backlog row (file body hash for import idempotency)

Environment variables (placeholder)

Document only; wire in app config when implementing.

Variable	Purpose
`CURSOR_SYNC_ENABLED`	`true` / `false` per environment.
`CURSOR_SYNC_POLL_INTERVAL_SEC`	Polling fallback interval.
`CURSOR_API_BASE_URL`	When a stable API exists for your integration tier.
`CURSOR_WEBHOOK_SECRET`	Verify inbound webhooks.

Security

Store tokens in tenant-scoped secrets (env, vault, or DB encrypted column)—never in markdown.
Audit log for every push/pull with actor (user id or system job).

References

Backlog layout: plans/README.md
Terminology: docs/Glossary.md
Templates: docs/templates/

3.2 KiB Raw Blame History