4dpocket 0.1.3__tar.gz

4dpocket-0.1.3/.claude/AGENTS.md

@@ -0,0 +1 @@
+../AGENTS.md

4dpocket-0.1.3/.claude/CLAUDE.md

@@ -0,0 +1,65 @@
+<!-- OMC:START -->
+<!-- OMC:VERSION:4.9.3 -->
+
+# oh-my-claudecode - Intelligent Multi-Agent Orchestration
+
+You are running with oh-my-claudecode (OMC), a multi-agent orchestration layer for Claude Code.
+Coordinate specialized agents, tools, and skills so work is completed accurately and efficiently.
+
+<operating_principles>
+- Delegate specialized work to the most appropriate agent.
+- Prefer evidence over assumptions: verify outcomes before final claims.
+- Choose the lightest-weight path that preserves quality.
+- Consult official docs before implementing with SDKs/frameworks/APIs.
+</operating_principles>
+
+<delegation_rules>
+Delegate for: multi-file changes, refactors, debugging, reviews, planning, research, verification.
+Work directly for: trivial ops, small clarifications, single commands.
+Route code to `executor` (use `model=opus` for complex work). Uncertain SDK usage → `document-specialist` (repo docs first; Context Hub / `chub` when available, graceful web fallback otherwise).
+</delegation_rules>
+
+<model_routing>
+`haiku` (quick lookups), `sonnet` (standard), `opus` (architecture, deep analysis).
+Direct writes OK for: `~/.claude/**`, `.omc/**`, `.claude/**`, `CLAUDE.md`, `AGENTS.md`.
+</model_routing>
+
+<skills>
+Invoke via `/oh-my-claudecode:<name>`. Trigger patterns auto-detect keywords.
+Tier-0 workflows include `autopilot`, `ultrawork`, `ralph`, `team`, and `ralplan`.
+Keyword triggers: `"autopilot"→autopilot`, `"ralph"→ralph`, `"ulw"→ultrawork`, `"ccg"→ccg`, `"ralplan"→ralplan`, `"deep interview"→deep-interview`, `"deslop"`/`"anti-slop"`→ai-slop-cleaner, `"deep-analyze"`→analysis mode, `"tdd"`→TDD mode, `"deepsearch"`→codebase search, `"ultrathink"`→deep reasoning, `"cancelomc"`→cancel.
+Team orchestration is explicit via `/team`.
+Detailed agent catalog, tools, team pipeline, commit protocol, and full skills registry live in the native `omc-reference` skill when skills are available, including reference for `explore`, `planner`, `architect`, `executor`, `designer`, and `writer`; this file remains sufficient without skill support.
+</skills>
+
+<verification>
+Verify before claiming completion. Size appropriately: small→haiku, standard→sonnet, large/security→opus.
+If verification fails, keep iterating.
+</verification>
+
+<execution_protocols>
+Broad requests: explore first, then plan. 2+ independent tasks in parallel. `run_in_background` for builds/tests.
+Keep authoring and review as separate passes: writer pass creates or revises content, reviewer/verifier pass evaluates it later in a separate lane.
+Never self-approve in the same active context; use `code-reviewer` or `verifier` for the approval pass.
+Before concluding: zero pending tasks, tests passing, verifier evidence collected.
+</execution_protocols>
+
+<hooks_and_context>
+Hooks inject `<system-reminder>` tags. Key patterns: `hook success: Success` (proceed), `[MAGIC KEYWORD: ...]` (invoke skill), `The boulder never stops` (ralph/ultrawork active).
+Persistence: `<remember>` (7 days), `<remember priority>` (permanent).
+Kill switches: `DISABLE_OMC`, `OMC_SKIP_HOOKS` (comma-separated).
+</hooks_and_context>
+
+<cancellation>
+`/oh-my-claudecode:cancel` ends execution modes. Cancel when done+verified or blocked. Don't cancel if work incomplete.
+</cancellation>
+
+<worktree_paths>
+State: `.omc/state/`, `.omc/state/sessions/{sessionId}/`, `.omc/notepad.md`, `.omc/project-memory.json`, `.omc/plans/`, `.omc/research/`, `.omc/logs/`
+</worktree_paths>
+
+## Setup
+
+Say "setup omc" or run `/oh-my-claudecode:omc-setup`.
+
+<!-- OMC:END -->

4dpocket-0.1.3/.claude/rules/README.md

@@ -0,0 +1,41 @@
+# Rules Templates
+
+This directory contains rule templates that you can copy to your project's `.claude/rules/` directory.
+
+## How to Use
+
+1. Create a `.claude/rules/` directory in your project root
+2. Copy the templates you want to use
+3. Customize them for your project
+4. Rules in `.claude/rules/*.md` will be auto-discovered and injected into context
+
+## Available Templates
+
+| Template | Purpose |
+|----------|---------|
+| `coding-style.md` | Code style and formatting guidelines |
+| `testing.md` | Testing requirements and coverage targets |
+| `security.md` | Security checklist and best practices |
+| `performance.md` | Performance guidelines and model selection |
+| `git-workflow.md` | Git commit and PR workflow |
+| `karpathy-guidelines.md` | Coding discipline — think before coding, simplicity, surgical changes |
+
+## Auto-Discovery
+
+When you place rules in `.claude/rules/`, they are automatically discovered by oh-my-claudecode and injected into the context for all agents working in your project.
+
+## Example
+
+```bash
+# Copy templates to your project
+mkdir -p .claude/rules
+cp templates/rules/security.md .claude/rules/
+cp templates/rules/testing.md .claude/rules/
+
+# Customize for your project
+# Edit .claude/rules/security.md to add project-specific checks
+```
+
+## Customization
+
+Each template has `[CUSTOMIZE]` markers where you should add project-specific guidelines.

4dpocket-0.1.3/.claude/rules/coding-style.md

@@ -0,0 +1,74 @@
+# Coding Style Rules
+
+## Immutability (CRITICAL)
+
+ALWAYS create new objects, NEVER mutate:
+
+```javascript
+// WRONG: Mutation
+function updateUser(user, name) {
+  user.name = name  // MUTATION!
+  return user
+}
+
+// CORRECT: Immutability
+function updateUser(user, name) {
+  return { ...user, name }
+}
+```
+
+## File Organization
+
+MANY SMALL FILES > FEW LARGE FILES:
+- High cohesion, low coupling
+- 200-400 lines typical, 800 max
+- Extract utilities from large components
+- Organize by feature/domain, not by type
+
+## Error Handling
+
+ALWAYS handle errors comprehensively:
+
+```typescript
+try {
+  const result = await riskyOperation()
+  return result
+} catch (error) {
+  console.error('Operation failed:', error)
+  throw new Error('User-friendly error message')
+}
+```
+
+## Input Validation
+
+ALWAYS validate user input:
+
+```typescript
+import { z } from 'zod'
+
+const schema = z.object({
+  email: z.string().email(),
+  age: z.number().int().min(0).max(150)
+})
+
+const validated = schema.parse(input)
+```
+
+## Code Quality Checklist
+
+Before marking work complete:
+- [ ] Code is readable and well-named
+- [ ] Functions are small (<50 lines)
+- [ ] Files are focused (<800 lines)
+- [ ] No deep nesting (>4 levels)
+- [ ] Proper error handling
+- [ ] No console.log statements
+- [ ] No hardcoded values
+- [ ] Immutable patterns used
+
+## [CUSTOMIZE] Project-Specific Style
+
+Add your project-specific coding style rules here:
+- Naming conventions
+- File structure requirements
+- Framework-specific patterns

4dpocket-0.1.3/.claude/rules/git-workflow.md

@@ -0,0 +1,41 @@
+# Git Workflow Rules
+
+## Commit Message Format
+
+```
+<type>: <description>
+
+<optional body>
+```
+
+Types: feat, fix, refactor, docs, test, chore, perf, ci
+
+## Pull Request Workflow
+
+When creating PRs:
+1. Analyze full commit history (not just latest commit)
+2. Use `git diff [base-branch]...HEAD` to see all changes
+3. Draft comprehensive PR summary
+4. Include test plan with TODOs
+5. Push with `-u` flag if new branch
+
+## Feature Implementation Workflow
+
+1. **Plan First** - Use `planner` agent
+2. **TDD Approach** - Use `tdd-guide` agent
+3. **Code Review** - Use `code-reviewer` agent after writing code
+4. **Commit** - Follow conventional commits format
+
+## Branch Naming
+
+- `feature/` - New features
+- `fix/` - Bug fixes
+- `refactor/` - Code refactoring
+- `docs/` - Documentation changes
+
+## [CUSTOMIZE] Project-Specific Git Rules
+
+Add your project-specific git workflow here:
+- Branch protection rules
+- Required reviewers
+- CI/CD requirements

4dpocket-0.1.3/.claude/rules/karpathy-guidelines.md

@@ -0,0 +1,59 @@
+# Karpathy Coding Guidelines
+
+Behavioral guidelines to reduce common LLM coding mistakes, derived from Andrej Karpathy's observations on LLM coding pitfalls. These principles bias toward caution over speed — for trivial tasks, use judgment.
+
+## 1. Think Before Coding
+
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
+
+Before implementing:
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them — don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it — don't delete it.
+
+When your changes create orphans:
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+
+The test: Every changed line should trace directly to the user's request.
+
+## 4. Goal-Driven Execution
+
+**Define success criteria. Loop until verified.**
+
+Transform tasks into verifiable goals:
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+```
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+```
+
+Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

4dpocket-0.1.3/.claude/rules/performance.md

@@ -0,0 +1,40 @@
+# Performance Rules
+
+## Model Selection Strategy
+
+**Haiku** (90% of Sonnet capability, 3x cost savings):
+- Lightweight agents with frequent invocation
+- Code generation and exploration
+- Worker agents in multi-agent systems
+
+**Sonnet** (Best coding model):
+- Main development work
+- Orchestrating multi-agent workflows
+- Complex coding tasks
+
+**Opus** (Deepest reasoning):
+- Complex architectural decisions
+- Maximum reasoning requirements
+- Research and analysis tasks
+
+## Context Window Management
+
+Avoid last 20% of context window for:
+- Large-scale refactoring
+- Feature implementation spanning multiple files
+- Debugging complex interactions
+
+## Algorithm Efficiency
+
+Before implementing:
+- [ ] Consider time complexity
+- [ ] Avoid O(n^2) when O(n log n) possible
+- [ ] Use appropriate data structures
+- [ ] Cache expensive computations
+
+## [CUSTOMIZE] Project-Specific Performance
+
+Add your project-specific performance requirements here:
+- Response time targets
+- Bundle size limits
+- Database query limits

4dpocket-0.1.3/.claude/rules/security.md

@@ -0,0 +1,41 @@
+# Security Rules
+
+## Mandatory Security Checks
+
+Before ANY commit:
+- [ ] No hardcoded secrets (API keys, passwords, tokens)
+- [ ] All user inputs validated
+- [ ] SQL injection prevention (parameterized queries)
+- [ ] XSS prevention (sanitized HTML)
+- [ ] CSRF protection enabled
+- [ ] Authentication/authorization verified
+- [ ] Rate limiting on all endpoints
+- [ ] Error messages don't leak sensitive data
+
+## Secret Management
+
+```typescript
+// NEVER: Hardcoded secrets
+const apiKey = "sk-proj-xxxxx"
+
+// ALWAYS: Environment variables
+const apiKey = process.env.API_KEY
+if (!apiKey) throw new Error('API_KEY not configured')
+```
+
+## Security Response Protocol
+
+If security issue found:
+1. STOP immediately
+2. Use `security-reviewer` agent
+3. Fix CRITICAL issues before continuing
+4. Rotate any exposed secrets
+5. Review entire codebase for similar issues
+
+## [CUSTOMIZE] Project-Specific Security
+
+Add your project-specific security requirements here:
+- Authentication method
+- Authorization rules
+- Data encryption requirements
+- Compliance requirements (GDPR, HIPAA, etc.)

4dpocket-0.1.3/.claude/rules/testing.md

@@ -0,0 +1,42 @@
+# Testing Rules
+
+## Minimum Test Coverage: 80%
+
+Test Types (ALL required):
+1. **Unit Tests** - Individual functions, utilities, components
+2. **Integration Tests** - API endpoints, database operations
+3. **E2E Tests** - Critical user flows
+
+## Test-Driven Development
+
+MANDATORY workflow:
+1. Write test first (RED)
+2. Run test - it should FAIL
+3. Write minimal implementation (GREEN)
+4. Run test - it should PASS
+5. Refactor (IMPROVE)
+6. Verify coverage (80%+)
+
+## Edge Cases to Test
+
+Every function must be tested with:
+- [ ] Null/undefined inputs
+- [ ] Empty arrays/strings
+- [ ] Invalid types
+- [ ] Boundary values (min/max)
+- [ ] Error conditions
+
+## Test Quality Checklist
+
+- [ ] Tests are independent (no shared state)
+- [ ] Test names describe behavior
+- [ ] Mocks used for external dependencies
+- [ ] Both happy path and error paths tested
+- [ ] No flaky tests
+
+## [CUSTOMIZE] Project-Specific Testing
+
+Add your project-specific testing requirements here:
+- Test framework configuration
+- Mock setup patterns
+- E2E test scenarios

4dpocket-0.1.3/.claude/skills/omc-reference/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: omc-reference
+description: OMC agent catalog, available tools, team pipeline routing, commit protocol, and skills registry. Auto-loads when delegating to agents, using OMC tools, orchestrating teams, making commits, or invoking skills.
+user-invocable: false
+---
+
+# OMC Reference
+
+Use this built-in reference when you need detailed OMC catalog information that does not need to live in every `CLAUDE.md` session.
+
+## Agent Catalog
+
+Prefix: `oh-my-claudecode:`. See `agents/*.md` for full prompts.
+
+- `explore` (haiku) — fast codebase search and mapping
+- `analyst` (opus) — requirements clarity and hidden constraints
+- `planner` (opus) — sequencing and execution plans
+- `architect` (opus) — system design, boundaries, and long-horizon tradeoffs
+- `debugger` (sonnet) — root-cause analysis and failure diagnosis
+- `executor` (sonnet) — implementation and refactoring
+- `verifier` (sonnet) — completion evidence and validation
+- `tracer` (sonnet) — trace gathering and evidence capture
+- `security-reviewer` (sonnet) — trust boundaries and vulnerabilities
+- `code-reviewer` (opus) — comprehensive code review
+- `test-engineer` (sonnet) — testing strategy and regression coverage
+- `designer` (sonnet) — UX and interaction design
+- `writer` (haiku) — documentation and concise content work
+- `qa-tester` (sonnet) — runtime/manual validation
+- `scientist` (sonnet) — data analysis and statistical reasoning
+- `document-specialist` (sonnet) — SDK/API/framework documentation lookup
+- `git-master` (sonnet) — commit strategy and history hygiene
+- `code-simplifier` (opus) — behavior-preserving simplification
+- `critic` (opus) — plan/design challenge and review
+
+## Model Routing
+
+- `haiku` — quick lookups, lightweight inspection, narrow docs work
+- `sonnet` — standard implementation, debugging, and review
+- `opus` — architecture, deep analysis, consensus planning, and high-risk review
+
+## Tools Reference
+
+### External AI / orchestration
+- `/team N:executor "task"`
+- `omc team N:codex|gemini "..."`
+- `omc ask <claude|codex|gemini>`
+- `/ccg`
+
+### OMC state
+- `state_read`, `state_write`, `state_clear`, `state_list_active`, `state_get_status`
+
+### Team runtime
+- `TeamCreate`, `TeamDelete`, `SendMessage`, `TaskCreate`, `TaskList`, `TaskGet`, `TaskUpdate`
+
+### Notepad
+- `notepad_read`, `notepad_write_priority`, `notepad_write_working`, `notepad_write_manual`
+
+### Project memory
+- `project_memory_read`, `project_memory_write`, `project_memory_add_note`, `project_memory_add_directive`
+
+### Code intelligence
+- LSP: `lsp_hover`, `lsp_goto_definition`, `lsp_find_references`, `lsp_diagnostics`, and related helpers
+- AST: `ast_grep_search`, `ast_grep_replace`
+- Utility: `python_repl`
+
+## Skills Registry
+
+Invoke built-in workflows via `/oh-my-claudecode:<name>`.
+
+### Workflow skills
+- `autopilot` — full autonomous execution from idea to working code
+- `ralph` — persistence loop until completion with verification
+- `ultrawork` — high-throughput parallel execution
+- `visual-verdict` — structured visual QA verdicts
+- `team` — coordinated team orchestration
+- `ccg` — Codex + Gemini + Claude synthesis lane
+- `ultraqa` — QA cycle: test, verify, fix, repeat
+- `omc-plan` — planning workflow and `/plan`-safe alias
+- `ralplan` — consensus planning workflow
+- `sciomc` — science/research workflow
+- `external-context` — external docs/research workflow
+- `deepinit` — hierarchical AGENTS.md generation
+- `deep-interview` — Socratic ambiguity-gated requirements workflow
+- `ai-slop-cleaner` — regression-safe cleanup workflow
+
+### Utility skills
+- `ask`, `cancel`, `note`, `learner`, `omc-setup`, `mcp-setup`, `hud`, `omc-doctor`, `trace`, `release`, `project-session-manager`, `skill`, `writer-memory`, `configure-notifications`
+
+### Keyword triggers kept compact in CLAUDE.md
+- `"autopilot"→autopilot`
+- `"ralph"→ralph`
+- `"ulw"→ultrawork`
+- `"ccg"→ccg`
+- `"ralplan"→ralplan`
+- `"deep interview"→deep-interview`
+- `"deslop" / "anti-slop"→ai-slop-cleaner`
+- `"deep-analyze"→analysis mode`
+- `"tdd"→TDD mode`
+- `"deepsearch"→codebase search`
+- `"ultrathink"→deep reasoning`
+- `"cancelomc"→cancel`
+- Team orchestration is explicit via `/team`.
+
+## Team Pipeline
+
+Stages: `team-plan` → `team-prd` → `team-exec` → `team-verify` → `team-fix` (loop).
+
+- Use `team-fix` for bounded remediation loops.
+- `team ralph` links the team pipeline with Ralph-style sequential verification.
+- Prefer team mode when independent parallel lanes justify the coordination overhead.
+
+## Commit Protocol
+
+Use git trailers to preserve decision context in every commit message.
+
+### Format
+- Intent line first: why the change was made
+- Optional body with context and rationale
+- Structured trailers when applicable
+
+### Common trailers
+- `Constraint:` active constraint shaping the decision
+- `Rejected:` alternative considered | reason for rejection
+- `Directive:` forward-looking warning or instruction
+- `Confidence:` `high` | `medium` | `low`
+- `Scope-risk:` `narrow` | `moderate` | `broad`
+- `Not-tested:` known verification gap
+
+### Example
+```text
+feat(docs): reduce always-loaded OMC instruction footprint
+
+Move reference-only orchestration content into a native Claude skill so
+session-start guidance stays small while detailed OMC reference remains available.
+
+Constraint: Preserve CLAUDE.md marker-based installation flow
+Rejected: Sync all built-in skills in legacy install | broader behavior change than issue requires
+Confidence: high
+Scope-risk: narrow
+Not-tested: End-to-end plugin marketplace install in a fresh Claude profile
+```

4dpocket-0.1.3/.dockerignore

@@ -0,0 +1,51 @@
+# Git
+.git
+.gitignore
+
+# Python
+__pycache__
+*.pyc
+*.pyo
+.mypy_cache
+.pytest_cache
+.ruff_cache
+*.egg-info
+dist/
+build/
+
+# Frontend (built in Docker)
+frontend/node_modules
+frontend/dist
+frontend/.omc
+
+# Dev/IDE
+.venv
+.env
+.env.local
+*.swp
+*.swo
+.vscode
+.idea
+.DS_Store
+
+# OMC / Claude
+.omc
+.claude
+.playwright-mcp
+missions
+
+# Data
+data/
+*.db
+*.db-wal
+*.db-shm
+
+# Tests
+tests/
+htmlcov/
+.coverage
+
+# Docs
+*.md
+!pyproject.toml
+LICENSE

4dpocket-0.1.3/.env.example

@@ -0,0 +1,77 @@
+# 4DPocket Configuration
+# Copy this to .env and fill in your values
+# WARNING: Never commit .env to git - it contains secrets
+
+# ─── Database ────────────────────────────────────────────────────
+# SQLite (default, zero-config)
+FDP_DATABASE__URL=sqlite:///./data/4dpocket.db
+# PostgreSQL (production/Docker)
+# FDP_DATABASE__URL=postgresql://4dp:4dp@localhost:5432/4dpocket
+
+# ─── Authentication ──────────────────────────────────────────────
+FDP_AUTH__MODE=single  # "single" (no login) or "multi" (JWT auth)
+# FDP_AUTH__SECRET_KEY=  # auto-generated and persisted if not set
+# FDP_AUTH__TOKEN_EXPIRE_MINUTES=10080  # 7 days
+
+# ─── Search ──────────────────────────────────────────────────────
+FDP_SEARCH__BACKEND=sqlite  # "sqlite" (FTS5) or "meilisearch"
+# FDP_SEARCH__MEILI_URL=http://localhost:7700
+# FDP_SEARCH__MEILI_MASTER_KEY=masterkey123
+
+# ─── AI Chat Provider ───────────────────────────────────────────
+# Supported: "ollama" (local), "groq" (cloud), "nvidia" (cloud), "custom" (any OpenAI-compatible)
+FDP_AI__CHAT_PROVIDER=ollama
+
+# Ollama (default - local, free)
+FDP_AI__OLLAMA_URL=http://localhost:11434
+FDP_AI__OLLAMA_MODEL=llama3.2
+
+# Groq (fast cloud inference)
+# FDP_AI__CHAT_PROVIDER=groq
+# FDP_AI__GROQ_API_KEY=gsk_...
+
+# NVIDIA (powerful cloud models)
+# FDP_AI__CHAT_PROVIDER=nvidia
+# FDP_AI__NVIDIA_API_KEY=nvapi-...
+
+# Custom (any OpenAI-compatible or Anthropic-compatible endpoint)
+# FDP_AI__CHAT_PROVIDER=custom
+# FDP_AI__CUSTOM_BASE_URL=https://api.minimax.io/anthropic/v1
+# FDP_AI__CUSTOM_API_KEY=sk-...
+# FDP_AI__CUSTOM_MODEL=MiniMax-M2.7
+# FDP_AI__CUSTOM_API_TYPE=anthropic  # "openai" (default) or "anthropic"
+#
+# More examples:
+# Together AI:
+#   FDP_AI__CUSTOM_BASE_URL=https://api.together.xyz/v1
+#   FDP_AI__CUSTOM_MODEL=meta-llama/Llama-3.3-70B-Instruct-Turbo
+# Fireworks:
+#   FDP_AI__CUSTOM_BASE_URL=https://api.fireworks.ai/inference/v1
+#   FDP_AI__CUSTOM_MODEL=accounts/fireworks/models/llama-v3p3-70b-instruct
+# OpenRouter:
+#   FDP_AI__CUSTOM_BASE_URL=https://openrouter.ai/api/v1
+#   FDP_AI__CUSTOM_MODEL=meta-llama/llama-3.3-70b-instruct
+
+# ─── Embedding Provider ─────────────────────────────────────────
+FDP_AI__EMBEDDING_PROVIDER=local  # "local" (sentence-transformers) or "nvidia"
+FDP_AI__EMBEDDING_MODEL=all-MiniLM-L6-v2
+
+# ─── AI Features ─────────────────────────────────────────────────
+FDP_AI__AUTO_TAG=true
+FDP_AI__AUTO_SUMMARIZE=true
+FDP_AI__TAG_CONFIDENCE_THRESHOLD=0.7
+FDP_AI__TAG_SUGGESTION_THRESHOLD=0.4
+FDP_AI__SYNC_ENRICHMENT=true  # Run AI enrichment inline if Huey worker is not running
+
+# ─── Storage ─────────────────────────────────────────────────────
+FDP_STORAGE__BASE_PATH=./data
+FDP_STORAGE__MAX_ARCHIVE_SIZE_MB=50
+
+# ─── Server ──────────────────────────────────────────────────────
+FDP_SERVER__HOST=0.0.0.0
+FDP_SERVER__PORT=4040
+FDP_SERVER__CORS_ORIGINS=["http://localhost:5173","http://localhost:4040"]
+FDP_SERVER__SECURE_COOKIES=false  # Set true behind HTTPS in production
+
+# ─── Docker Compose ──────────────────────────────────────────────
+MEILI_MASTER_KEY=masterkey123