663bc77afe
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
51 lines
1.3 KiB
Markdown
51 lines
1.3 KiB
Markdown
---
|
||
kind: epic
|
||
slug: markdown-backlog
|
||
title: Markdown backlog structure and templates
|
||
plan_slug: multitenant-cursor-sync
|
||
status: in_progress
|
||
priority: P0
|
||
tenant_id: global
|
||
cursor_epic_id: null
|
||
updated_at: "2026-04-26"
|
||
---
|
||
|
||
# Epic objective
|
||
|
||
Establish a **consistent, tool-friendly** filesystem layout and templates so plans, epics, and tasks can be generated by humans, agents, and future import/export jobs without ambiguity.
|
||
|
||
## In scope / out of scope
|
||
|
||
**In scope**
|
||
|
||
- `plans/` hierarchy and `plans/README.md`
|
||
- `docs/templates/` for plan, epic, task
|
||
- `docs/Glossary.md` conventions
|
||
|
||
**Out of scope**
|
||
|
||
- Database schema migrations for backlog entities (see multitenant epic)
|
||
|
||
## Related tasks
|
||
|
||
| Task | Link |
|
||
|------|------|
|
||
| Folder layout and templates | `./Task-folder-layout-and-templates.md` |
|
||
| Parser requirements note | `./Task-parser-requirements.md` |
|
||
|
||
## Dependencies
|
||
|
||
- Depends on: none (foundational)
|
||
- Blocks: Cursor sync layer (needs stable paths and frontmatter)
|
||
|
||
## Acceptance criteria
|
||
|
||
- [ ] Any contributor can copy templates and create a valid tree under `plans/Plan-<slug>/`.
|
||
- [ ] Glossary defines status, priority, and tenancy terms used in frontmatter.
|
||
|
||
## Proposed timeline
|
||
|
||
| Phase | Window | Notes |
|
||
|-------|--------|-------|
|
||
| Scaffolding | Week 1 | Done in repo |
|
||
| Parser | Week 2–3 | Implement in app |
|