oh-my-customcode 0.51.0 → 0.51.2

package/README.md

@@ -228,7 +228,7 @@ Key rules: R010 (orchestrator never writes files), R009 (parallel execution mand
 
 ---
 
-### Guides (29)
+### Guides (30)
 
 Reference documentation covering best practices, architecture decisions, and integration patterns. Located in `guides/` at project root, covering topics from agent design to CI/CD to observability.
 
@@ -281,7 +281,7 @@ your-project/
 │   ├── specs/                  # Extracted canonical specs
 │   ├── contexts/               # 4 shared context files
 │   └── ontology/               # Knowledge graph for RAG
-└── guides/                     # 29 reference documents
+└── guides/                     # 30 reference documents
 ```
 
 ---

package/dist/cli/index.js

@@ -9323,7 +9323,7 @@ var init_package = __esm(() => {
   package_default = {
     name: "oh-my-customcode",
     workspaces: ["packages/*"],
-    version: "0.51.0",
+    version: "0.51.2",
     description: "Batteries-included agent harness for Claude Code",
     type: "module",
     bin: {

package/dist/index.js

@@ -1668,7 +1668,7 @@ import { join as join6 } from "node:path";
 var package_default = {
   name: "oh-my-customcode",
   workspaces: ["packages/*"],
-  version: "0.51.0",
+  version: "0.51.2",
   description: "Batteries-included agent harness for Claude Code",
   type: "module",
   bin: {

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "oh-my-customcode",
   "workspaces": ["packages/*"],
-  "version": "0.51.0",
+  "version": "0.51.2",
   "description": "Batteries-included agent harness for Claude Code",
   "type": "module",
   "bin": {

package/templates/.claude/hooks/scripts/agent-teams-advisor.sh

@@ -21,6 +21,22 @@ if [ -f "$ENV_STATUS" ]; then
   fi
 fi
 
+# Batch context detection: check for workflow or release-plan state
+BATCH_ISSUES=0
+# Use wildcard to match any workflow name: /tmp/.claude-workflow-*-${PPID}.json
+WORKFLOW_FILE=$(ls /tmp/.claude-workflow-*-"${PPID}".json 2>/dev/null | head -1 || true)
+if [ -n "$WORKFLOW_FILE" ] && [ -f "$WORKFLOW_FILE" ]; then
+  BATCH_ISSUES=$(jq -r '.issue_count // 0' "$WORKFLOW_FILE" 2>/dev/null || echo 0)
+fi
+
+# Also check release-plan context (existence only — if file exists, treat as batch)
+RELEASE_PLAN="/tmp/.claude-release-plan-${PPID}"
+if [ -f "$RELEASE_PLAN" ]; then
+  if [ "$BATCH_ISSUES" -lt 3 ]; then
+    BATCH_ISSUES=3
+  fi
+fi
+
 # Extract task info from input
 agent_type=$(echo "$input" | jq -r '.tool_input.subagent_type // "unknown"')
 prompt_preview=$(echo "$input" | jq -r '.tool_input.description // ""' | head -c 60)
@@ -37,8 +53,14 @@ else
 fi
 echo "$COUNT" > "$COUNTER_FILE"
 
-# Warn from 2nd Task call onward -- Agent Teams may be more appropriate
-if [ "$COUNT" -ge 2 ]; then
+# Warn when batch context detected (even on first call) or from 2nd call onward
+if [ "$BATCH_ISSUES" -ge 3 ] && [ "$COUNT" -eq 1 ]; then
+  echo "" >&2
+  echo "--- [R018 Advisor] Batch context detected (${BATCH_ISSUES} issues) ---" >&2
+  echo "  RECOMMENDATION: Use Agent Teams (TeamCreate) for this batch." >&2
+  echo "  Current: Agent(${agent_type}) -- ${prompt_preview}" >&2
+  echo "-----------------------------------------------------------" >&2
+elif [ "$COUNT" -ge 2 ]; then
   echo "" >&2
   echo "--- [R018 Advisor] Agent/Task tool call #${COUNT} in this session ---" >&2
   echo "  WARNING: Multiple Task calls detected. Consider Agent Teams if:" >&2

package/templates/CLAUDE.md

@@ -140,7 +140,7 @@ project/
 |   +-- rules/                   # 전역 규칙 (R000-R021)
 |   +-- hooks/                   # 훅 스크립트 (보안, 검증, HUD)
 |   +-- contexts/                # 컨텍스트 파일 (ecomode)
-+-- guides/                      # 레퍼런스 문서 (29 토픽)
++-- guides/                      # 레퍼런스 문서 (30 토픽)
 ```
 
 ## 오케스트레이션

package/templates/guides/drizzle-orm/README.md

@@ -0,0 +1,69 @@
+# Drizzle ORM: sql Template Literal Pitfalls
+
+## The Bug: Column References in Subqueries
+
+When using Drizzle ORM's `sql` template literals, `${table.column}` generates a **bare column name without the table qualifier**. This causes silent semantic errors inside aliased subqueries.
+
+### Symptom
+
+```typescript
+// Code
+sql`SELECT ${agentInvocations.errorSummary} as sub_es
+    FROM ${agentInvocations} AS ai2
+    WHERE ai2.agent_type = ${agentInvocations.agentType}`
+
+// Generated SQL (WRONG)
+SELECT "error_summary" as sub_es
+FROM "agent_invocations" AS ai2
+WHERE ai2.agent_type = "agent_type"  -- "agent_type" becomes a literal string, always true!
+```
+
+`${agentInvocations.agentType}` expands to the **quoted column name** `"agent_type"` — not the value of the column. The `WHERE` clause compares `ai2.agent_type = "agent_type"`, which SQLite treats as a string literal match — always true for rows where `agent_type` equals the string `"agent_type"`.
+
+### Why Reviewers Miss It
+
+- The code *looks* correct — you see `agentInvocations.agentType` and assume it's a column reference.
+- Drizzle's `${table.column}` syntax works fine in top-level queries where table context is unambiguous.
+- The bug only manifests inside subqueries with table aliases (`AS ai2`) — normal queries pass.
+- No compile-time error; the SQL executes but returns wrong results.
+
+## The Fix: Raw SQL for Subquery Internal References
+
+Use raw SQL strings for column references *inside* aliased subqueries. Reserve `${table.column}` only for Drizzle's top-level query builder where it resolves correctly.
+
+```typescript
+// CORRECT: raw SQL column references inside aliased subquery
+sql`SELECT ai2.error_summary as sub_es
+    FROM ${agentInvocations} AS ai2
+    WHERE ai2.agent_type = ${agentInvocations}.agent_type`
+```
+
+Note: `${agentInvocations}` (the table object itself) still correctly expands to the table name and is safe to use for the `FROM` clause. Only *column* references inside subqueries must be written as raw SQL.
+
+## Decision Table
+
+| Context | Pattern | Safe? |
+|---------|---------|-------|
+| Top-level `FROM` clause | `${table}` | ✅ Yes |
+| Top-level `WHERE` with parameterized value | `${value}` | ✅ Yes (auto-parameterized) |
+| Top-level `SELECT` column | `${table.column}` | ✅ Yes |
+| Inside aliased subquery `SELECT` | `${table.column}` | ❌ No — bare column name |
+| Inside aliased subquery `WHERE` comparison | `${table.column}` | ❌ No — string literal, not column ref |
+| Inside aliased subquery (fixed) | `alias.column_name` | ✅ Yes |
+
+## Verification
+
+Use `.toSQL()` to inspect generated SQL before running:
+
+```typescript
+const query = sql`SELECT ${agentInvocations.errorSummary} as sub_es
+    FROM ${agentInvocations} AS ai2
+    WHERE ai2.agent_type = ${agentInvocations.agentType}`
+
+console.log(query.toSQL())
+// Reveals the bare column names — catches the bug before runtime
+```
+
+## Key Takeaway
+
+> **`${table.column}` in Drizzle's `sql` template generates a bare column identifier, not a qualified reference.** Inside aliased subqueries, this breaks table-qualified comparisons. Always use raw `alias.column_name` strings inside subquery bodies.

package/templates/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.51.0",
+  "version": "0.51.2",
   "lastUpdated": "2026-03-16T00:00:00.000Z",
   "components": [
     {
@@ -24,7 +24,7 @@
       "name": "guides",
       "path": "guides",
       "description": "Reference documentation",
-      "files": 29
+      "files": 30
     },
     {
       "name": "hooks",