chore: update database configuration to use PostgreSQL

Author: tae2089

.ccg.yaml

@@ -1,6 +1,7 @@
 db:
-  driver: sqlite # sqlite | postgres
-  dsn: ccg.db
+  # driver: sqlite # sqlite | postgres/
+  driver: postgres
+  dsn: "host=localhost user=postgres password=postgres dbname=ccg_test sslmode=disable"
 
 namespace: default
 

AGENTS.md

@@ -27,13 +27,13 @@ Graceful shutdown: SIGINT/SIGTERM propagates context cancellation to in-progress
 
 ## Agent Skills (5)
 
-| Skill            | Description                                                                                 |
-| ---------------- | ------------------------------------------------------------------------------------------- |
-| `/ccg`           | Core build and search: parsing, graph build, query, search                                   |
-| `/ccg-analyze`   | Code analysis: impact radius, flow tracing, dead code, architecture                          |
-| `/ccg-annotate`  | Annotation system: AI annotation workflow and tag reference                                  |
-| `/ccg-docs`      | Documentation: doc generation, RAG indexing, lint                                            |
-| `/ccg-namespace` | Namespace file management: upload, list, delete                                              |
+| Skill            | Description                                                         |
+| ---------------- | ------------------------------------------------------------------- |
+| `/ccg`           | Core build and search: parsing, graph build, query, search          |
+| `/ccg-analyze`   | Code analysis: impact radius, flow tracing, dead code, architecture |
+| `/ccg-annotate`  | Annotation system: AI annotation workflow and tag reference         |
+| `/ccg-docs`      | Documentation: doc generation, RAG indexing, lint                   |
+| `/ccg-namespace` | Namespace file management: upload, list, delete                     |
 
 Skill files are located under `skills/` and are written so coding agents such as Codex and Claude Code
 can use them as slash-command style workflows.
@@ -120,3 +120,24 @@ CGO_ENABLED=1 go test -tags "fts5" ./... -count=1
 
 For documentation-only changes, prioritize regenerating docs with `ccg docs` and running `ccg lint`.
 Code tests may be skipped depending on the change scope.
+
+## Skill Routing
+
+- When writing, modifying, or reviewing code, apply `coding-quality-guardrails` as the quality gate.
+- When debugging bugs, regressions, flaky behavior, or failing tests, use `diagnosing-bugs` before changing behavior.
+- Before implementing new logic with branching, side effects, resource lifecycles, or ordering constraints, use `flow-design` and keep the design note in the task workspace.
+- When designing module boundaries, refactoring, or shaping interfaces, use `codebase-design`.
+- When aligning terminology or modeling the domain, use `domain-modeling`.
+- When a plan is fuzzy, high-impact, or lacks testable acceptance criteria, use `planning-grill` to sharpen scope, acceptance, and failure modes before decomposing it.
+- For multi-step or multi-agent work, use `decompose-and-dispatch` to split the work into bounded units. Use `execute-dispatch-unit` only for a clearly assigned unit with scope, dependencies, and verification.
+- When preparing context for human or AI code review, use `ready-code-review`; do not use it to perform the review itself.
+- To record a session, distill completed work into a replayable recipe, or replay a `recipe.yaml`, use `session-recipe`.
+
+## agent-team Routing
+
+agent-team bundles its own skills; restrict them as follows so methodology stays single-sourced:
+
+- Use only agent-team's CLI operation skills (the `agent-team-*` prefix: run/task/message/inbox/sync/event commands), and load `agent-team-shared` before any command-specific one — it defines the state directory, global flags, and error handling they all assume. Never use its `recipe-*` and `persona-*` skills — the skills routed above own all methodology, even where an excluded skill looks like a closer match (worker checkpoints → `execute-dispatch-unit`'s Ledger Checkpoints; plan sharpening / `recipe-agent-team-planning-grill` → `planning-grill`; decomposition → `decompose-and-dispatch`; architecture → `codebase-design`; terminology → `domain-modeling`).
+- When executing an assigned unit, follow `execute-dispatch-unit` for scope, verification, and reporting; its Ledger Checkpoints section defines which `agent-team-*` calls to make.
+- When planning, `decompose-and-dispatch` owns decomposition and executor mapping, and its Durable Ledger section defines the run/task registration calls.
+- Do not route by the word "recipe": here it means a replayable session recipe (`session-recipe`, `recipe.yaml`); agent-team's `recipe-*` skills are excluded above.