chore(capy): Add repository setup files

.capy/BUILD.md

@@ -0,0 +1,6 @@
+- Treat GARZA OS as a monorepo: `mcp-servers/` for MCP implementations, `services/` for app services, `workers/` for Cloudflare Workers, `infra/` for state and manifests, `operations/` for runbooks/templates, `docs/` and `prompts/` for operating guidance.
+- Before adding code, check adjacent services plus `templates/` and `docs/stack-first.md`; reuse existing patterns and extend current services before creating a new implementation.
+- Keep decisions stack-first: prefer Fly.io, Cloudflare Workers, n8n Cloud, Supabase, and GitHub Actions over new VPSes, ad hoc schedulers, extra databases, or one-off infrastructure.
+- Reach for the repo's documented verification entrypoints first: `./scripts/test.sh` for tests, `garza health` for service health, and `garza status` for deployment/status checks.
+- Never hardcode secrets or credentials. Follow the repo's existing secret-management paths and deployment conventions.
+- When touching infra state, deployment manifests, or automation config, keep related `infra/` state files, lock conventions, and service manifests coherent with the code change.

.capy/CAPTAIN.md

@@ -0,0 +1,6 @@
+- GARZA OS is a monorepo for Jaden Garza's personal AI operating system: a unified intelligence layer spanning services, automations, and operational context.
+- Major planning areas are `mcp-servers/`, `services/`, `workers/`, `infra/`, `operations/`, plus supporting `docs/`, `prompts/`, `templates/`, and workflow/config directories.
+- Craft is the conceptual source of truth for system knowledge; repo docs and prompts provide the operational context agents should follow when planning implementation work.
+- Prefer extending an existing service, worker, template, or workflow before proposing a new component.
+- New work should generally target Fly.io, Cloudflare Workers, n8n, Supabase, or GitHub Actions. Treat DigitalOcean as legacy/phasing out.
+- For infra or operations changes, account for `infra/` state-management conventions, lock files, deployment manifests, and existing runbooks/docs before planning mutations.

.capy/REVIEW.md

@@ -0,0 +1,6 @@
+- Prioritize stack-first violations: flag changes that introduce new infrastructure or bypass Fly.io, Workers, n8n, Supabase, or GitHub Actions without strong justification.
+- Check for secret leakage, hardcoded credentials, unsafe `.env` usage, or docs/code that expose operational access details.
+- Verify service contracts across routers, MCP tools, workers, dashboards, and infra manifests so interfaces stay aligned.
+- When changes affect deployment, operations, or infra, confirm repo docs/state manifests remain consistent with the implementation and audit trail expectations in `infra/`.
+- Flag unnecessary churn across unrelated monorepo areas; prefer tightly scoped edits.
+- Ignore style-only nits unless they affect clarity, maintainability, or correctness.

.capy/settings.json

@@ -0,0 +1,21 @@
+{
+  "$schema": "https://capy.ai/settings.schema.json",
+  "hooks": {
+    "setup": [
+      "./scripts/setup.sh",
+      "cd services/garza-dashboard && npm install"
+    ],
+    "terminals": [
+      {
+        "name": "garza-dashboard",
+        "command": "cd services/garza-dashboard && npm start"
+      }
+    ],
+    "previews": [
+      {
+        "name": "garza-dashboard",
+        "port": 8080
+      }
+    ]
+  }
+}