maaz519
5abee1b5b7
Versioned, per-topic project memory (index + entries): IIOS overview, the generic-safety rule, run/test + the replay.spec flake workaround, recent features (Supabase auth, reactions/pins/saves, mentions, media, notifications), the chat-web consumer, and workflow conventions. CLAUDE.md points to it as the accumulating-notes companion to the canonical rules. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.2 KiB
1.2 KiB
name, description, metadata
| name | description | metadata | ||
|---|---|---|---|---|
| feedback_workflow | Working conventions — commits, prod flags, TDD, rebuild-before-restart |
|
- Commits: conventional (
feat:/fix:/docs:/chore:), git emailmaaz@insigniaconsultancy.com, co-author every commit with Claude. The user commits directly tomainin this project (fine); branch only if asked. - ⚠
IIOS_DEV_TOKENSMUST be0/unset in production — it exposes/v1/dev/*(unauth token minting, chaos, retention sweep). The single most important prod-hardening flag. - TDD — write the failing spec first; verify it fails; implement; verify it passes.
- Rebuild before restart — after backend changes,
nest buildthen restart fromdist;lsof -ti :3200 | xargs kill -9first or the old build keeps serving (stale-dist bites). - New kernel capability = a generic primitive only — add domain meaning in OPA policy + the app, never the kernel. See feedback_generic_safety.
- The user prefers direct, fast iteration (implement → verify end-to-end → commit), not heavyweight multi-agent/spec ceremony. Include "how to test" in summaries; report failures honestly.