Files
projax/CLAUDE.md
mAi 1d5db0fe7b feat(phase 3j pwa): manifest + service worker + icons → installable PWA
- web/static/manifest.webmanifest: name/short_name/start_url=/dashboard/
  display=standalone/theme_color/background_color + three icons (192, 512,
  512-maskable with ~12% safe-zone padding)
- web/static/sw.js: minimal SW — install caches /static/* shell assets,
  fetch is network-first with cache fallback on GETs only, skips /mcp/
  and non-GETs entirely. CACHE_NAME versioned for clean activate-time
  prune.
- cmd/icongen: stdlib-only generator that produces the three PNG icons
  from a stylised "p" monogram. Run once at brand-change, commit output.
- web.init() registers .webmanifest → application/manifest+json with
  mime.AddExtensionType so Chrome accepts the manifest at all
- layout.tmpl + login.tmpl: manifest link, apple-touch-icon, theme-color,
  apple-mobile-web-app-* metas, inline SW-register on load (silent on
  failure — older browsers still work)
- design.md gets §"PWA install (Phase 3j)"; CLAUDE.md "Out of scope"
  drops the Phase-3j line and adds push/background-sync as the
  remaining Otto-PWA territory
- 4 new tests cover manifest MIME, sw.js delivery, all 3 icons, layout
  meta tags
2026-05-15 19:32:48 +02:00

66 lines
3.2 KiB
Markdown

# projax — Project Instructions
## Purpose
Data backbone for m's complete self-management — projects (digital + physical + strategic + life themes), tasks, lifecycle, milestones. Multiple interfaces consume it. No interface is canonical; each is a view.
**Memory group_id:** `projax`
**Live spec:** `docs/design.md` (PRD, schema, migration plan, deferred phases)
## Architecture principles
1. **Model first, interfaces second.** The data model is the asset; UIs are replaceable.
2. **First-class non-code projects.** Greenhouse construction, household chores, career positioning, sport goals — same model as code projects.
3. **No CLI required.** m has explicitly opted out of CLI-first. Interfaces are visual / API / Otto-mediated.
4. **Subsumes existing scattered state.** mai.projects (adapter view today), Gitea issues, CalDAV tasks, mBrian topics. Migration not greenfield isolation.
5. **Otto is a consumer, not an owner.** Otto-PWA renders projax data; otto coordinates work *based on* projax; otto does not *define* projax.
## Tech stack (Phase 1)
- **Backend**: Go single binary. `pgx` for Postgres. `html/template` + HTMX (CDN), no JS build step. Static assets and migrations bundled with `embed`.
- **Database**: msupabase, schema `projax` (new). View `projax.items_unified` reads across `projax.*` + `mai.projects`. RLS off for v1 (single-user, Tailscale-only).
- **Hosting**: Dokploy on mlake, domain `projax.msbls.de`, Tailscale-only.
- **Tests**: `go test ./...` against `SUPABASE_DATABASE_URL` (skips when unset).
## Layout
```
cmd/projax/ main entrypoint (pool, migrate, serve)
db/ migrations (embedded) + runner + integration tests
store/ pgx-backed data access
web/ handlers, templates, static
deploy/dokploy.yaml reference manifest for projax.msbls.de
docs/design.md PRD — the source of truth for behaviour
```
## Branch strategy
- `main` = production-deployable
- `feat/*` / `fix/*` — short-lived
- No `dev` branch initially (small project)
- `--no-ff` merges to main
## Status
- **PRD landed** (`docs/design.md`, 2026-05-15) — schema, lifecycle, interface contracts settled.
- **Phase 1 underway**: schema + path trigger + adapter view + Go server + tree/detail/new/classify pages + Docker/Dokploy + README all on a feature branch.
- **Phase 2** (CalDAV + Gitea ingest) and **Phase 3** (Excalidraw / MCP / Otto-PWA) are scoped in `docs/design.md` but not started.
When a phase-1 follow-up surfaces (auth, hiding mai.projects test rows, mBrian topic-hub auto-link, …), file it against `docs/design.md` §8 first, then split into commits.
## Out of scope (still)
- Multi-user
- Push notifications + background sync (Otto-PWA's domain)
- Public exposure
- Generic SaaS-product instincts
- CLI surface (m has explicitly opted out)
## Refs
- `docs/design.md` — live spec (this is the source of truth)
- `mai.projects` schema (msupabase) — primary current state (read-only adapted via `projax.items_unified`)
- mBrian conventions (topic-hub pattern) — relevant for non-code project tracking, deferred to Phase 3
- otto session 2026-05-15 — inventory of where project data lives today, justifying this project's existence
- `~/.claude/CLAUDE.md` § Git Strategy, Channel Routing, Memory Protocol