@jaguilar87/gaia 5.0.2 → 5.0.5

package/tools/scan/ui.py

@@ -16,6 +16,22 @@ import sys
 from typing import Any, Dict, List, Optional
 
 
+# ---------------------------------------------------------------------------
+# Glyphs
+#
+# Hoisted to module-level constants so they are never written as escape
+# sequences *inside* an f-string replacement field. A backslash within an
+# f-string expression (e.g. f"{self._green('◇')}") is a SyntaxError on
+# Python 3.11 (our declared minimum); it is only permitted on 3.12+ via PEP
+# 701. Referencing a bare name inside the braces keeps the same rendered
+# output while staying 3.11-compatible.
+# ---------------------------------------------------------------------------
+
+_GLYPH_DIAMOND_OUTLINE = "◇"  # ◇
+_GLYPH_WARNING = "⚠"          # ⚠
+_GLYPH_CORNER_BL = "└"        # └
+
+
 # ---------------------------------------------------------------------------
 # ANSI color helpers
 # ---------------------------------------------------------------------------
@@ -119,7 +135,7 @@ class RailUI:
             name: Section title (e.g. "Stack", "Infrastructure").
             lines: Detail lines to display under the section.
         """
-        self._write(f"{self._green('\u25c7')}  {self._cyan(name)}")
+        self._write(f"{self._green(_GLYPH_DIAMOND_OUTLINE)}  {self._cyan(name)}")
         for line in lines:
             self._write(f"{self._rail()}  {line}")
         self._write(self._rail())
@@ -131,7 +147,7 @@ class RailUI:
             names: List of section names to join with middle-dot.
         """
         joined = self._cyan(" \u00b7 ".join(names))
-        self._write(f"{self._green('\u25c7')}  {joined}")
+        self._write(f"{self._green(_GLYPH_DIAMOND_OUTLINE)}  {joined}")
         self._write(self._rail())
 
     def warning(self, count: int, messages: List[str]) -> None:
@@ -141,7 +157,7 @@ class RailUI:
             count: Total number of warnings.
             messages: Warning messages to display.
         """
-        self._write(f"{self._yellow('\u26a0')}  {self._yellow(f'Warnings ({count})')}")
+        self._write(f"{self._yellow(_GLYPH_WARNING)}  {self._yellow(f'Warnings ({count})')}")
         for msg in messages:
             self._write(f"{self._rail()}  {msg}")
         self._write(self._rail())
@@ -193,7 +209,7 @@ class RailUI:
         Args:
             message: Footer message text.
         """
-        self._write(f"{self._dim('\u2514')}  {message}")
+        self._write(f"{self._dim(_GLYPH_CORNER_BL)}  {message}")
 
 
 # ---------------------------------------------------------------------------

package/tools/scan/verify.py

@@ -45,8 +45,8 @@ class CheckResult:
 def check_symlinks(project_root: Path) -> CheckResult:
     """Verify that all expected symlinks exist in .claude/.
 
-    Checks for: agents, tools, hooks, commands, templates, config,
-    skills, CHANGELOG.md (8 total).
+    Checks for: agents, tools, hooks, commands, config,
+    skills, CHANGELOG.md (7 total).
 
     Args:
         project_root: Project root directory.
@@ -56,7 +56,7 @@ def check_symlinks(project_root: Path) -> CheckResult:
     """
     names = [
         "agents", "tools", "hooks", "commands",
-        "templates", "config", "skills",
+        "config", "skills",
         "CHANGELOG.md",
     ]
     valid = 0

package/tools/validation/README.md

@@ -25,7 +25,7 @@ without requiring explicit imports in agent code.
 - ✅ Subject line rules (max 72 chars, no period at end)
 - ✅ Forbidden footers (no "Generated with" footers)
 
-**Configuration:** `.claude/config/git_standards.json` (SSOT)
+**Configuration:** Standards are inlined as module-level constants in `hooks/modules/validation/commit_validator.py` (`TYPE_ALLOWED`, `SUBJECT_MAX_LENGTH`, `SUBJECT_RULES`, `BODY_MAX_LINE_LENGTH`, `ENFORCEMENT`). Forbidden-footer detection lives in `bash_validator`.
 **Logs:** `.claude/logs/commit-violations.jsonl`
 
 ---
@@ -108,16 +108,11 @@ This validation module works with skills in a **hybrid model**:
 
 ```
 ┌──────────────────────────────────────────────────────────┐
-│  config/git_standards.json (SSOT)                         │
-│  - Conventional commit types                              │
-│  - Forbidden footers                                      │
-│  - Max lengths                                            │
-└──────────────────────────────────────────────────────────┘
-                        │
-                        ▼
-┌──────────────────────────────────────────────────────────┐
 │  hooks/modules/validation/ (Commit Validation)            │
 │  └─ commit_validator.py                                   │
+│     ├─ Standards inlined as module-level constants        │
+│     │   (types, subject/body max lengths, rules)          │
+│     ├─ Forbidden footers handled by bash_validator        │
 │     └─ Used by bash_validator.py only                     │
 └──────────────────────────────────────────────────────────┘
                         │
@@ -178,24 +173,20 @@ Note: commit_validator.py moved to hooks/modules/validation/
 
 ## Configuration
 
-**Git Standards:** `.claude/config/git_standards.json`
+**Git Standards:** Inlined as module-level constants in `hooks/modules/validation/commit_validator.py`.
 
 Example:
-```json
-{
-  "commit_message": {
-    "type_allowed": ["feat", "fix", "refactor", "docs", "test", "chore"],
-    "subject_max_length": 72,
-    "footer_forbidden": ["Generated with Claude Code"]
-  },
-  "enforcement": {
-    "enabled": true,
-    "block_on_failure": true,
-    "log_violations": true
-  }
-}
+```python
+TYPE_ALLOWED = ("feat", "fix", "refactor", "docs", "test", "chore",
+                "ci", "perf", "style", "build")
+SUBJECT_MAX_LENGTH = 72
+SUBJECT_RULES = {"no_period_at_end": True, "no_emoji": True,
+                 "imperative_mood": True, "capitalize_first_letter": False}
+ENFORCEMENT = {"enabled": True, "block_on_failure": True, "log_violations": True}
 ```
 
+Forbidden-footer detection lives, hardcoded, in `bash_validator`.
+
 ---
 
 ## Logs
@@ -232,7 +223,7 @@ Example entry:
 
 ## See Also
 
-- `.claude/config/git_standards.json` - Git standards configuration
+- `hooks/modules/validation/commit_validator.py` - Git standards (inlined constants)
 - `.claude/skills/subagent-request-approval/SKILL.md` - Approval-request workflow patterns
 - `.claude/skills/execution/SKILL.md` - Execution workflow patterns
 - `CLAUDE.md` - Orchestrator protocol with T3 workflow

package/commands/README.md

@@ -1,64 +0,0 @@
-# Commands
-
-Slash commands are direct shortcuts into Gaia's orchestration layer. When you type `/gaia` or `/scan-project`, Claude Code detects the slash prefix, finds the matching `.md` file in this directory, and injects its contents as instructions to the currently active orchestrator. There is no subagent spawn — the orchestrator reads the command file and executes inline.
-
-This makes slash commands different from agent dispatch. An agent dispatch creates a new Claude Code subprocess with its own identity, skills, and tool set. A slash command is a context injection into the orchestrator's current session. Think of it as a macro: the `.md` file says "when the user invokes this command, do the following." The orchestrator follows those instructions directly.
-
-The practical implication is that slash commands are best suited for tasks that the orchestrator can complete by delegating to existing agents — not tasks that require a new agent identity. They are entry points, not agents.
-
-## Cuándo se activa
-
-```
-User types /command-name [args]
-        |
-Claude Code detects / prefix
-        |
-Looks up commands/<command-name>.md
-        |
-Injects the file's contents into the orchestrator's active context
-        |
-Orchestrator reads the command instructions and executes them
-  (may dispatch agents, call tools, or respond directly)
-        |
-Result returned to user in the current session
-```
-
-No subagent is spawned. No new identity is loaded. The orchestrator handles execution within its current session using its existing tool set and the instructions from the command file.
-
-## Qué hay aquí
-
-```
-commands/
-├── gaia.md           # /gaia — invoke the Gaia meta-agent (gaia-system) for system work
-└── scan-project.md   # /scan-project — scan codebase, detect stack, update ~/.gaia/gaia.db
-```
-
-Note: a `/gaia-plan` command is referenced in some older documentation but the file does not exist here. Planning is handled conversationally through the orchestrator and the `gaia-planner` agent — not via a slash command.
-
-## Convenciones
-
-**File format:**
-
-```markdown
----
-name: command-name
-description: One-line description shown in Claude Code autocomplete
----
-
-# Command Name
-
-[Instructions the orchestrator follows when this command is invoked]
-```
-
-**Registration:** Each command file must also be listed in `build/gaia-ops.manifest.json` under the `commands` array. A file that exists here but is not in the manifest will not appear in Claude Code's slash command list.
-
-**Scope:** Commands inject instructions into the orchestrator. If the task requires domain work (Terraform, code changes, cloud ops), the command's instructions should dispatch the appropriate agent — the command itself should not attempt domain execution.
-
-**Arguments:** Slash commands can receive arguments after the command name (e.g., `/gaia-plan Add OAuth2 support`). The command's `.md` file can reference these as context, and the orchestrator receives them as part of the injected content.
-
-## Ver también
-
-- [`build/gaia-ops.manifest.json`](../build/gaia-ops.manifest.json) — command registration
-- [`agents/gaia-system.md`](../agents/gaia-system.md) — the Gaia meta-agent invoked by `/gaia`
-- [`agents/gaia-orchestrator.md`](../agents/gaia-orchestrator.md) — orchestrator that executes command instructions
-- [`skills/gaia-planner/SKILL.md`](../skills/gaia-planner/SKILL.md) — planning workflow (used by gaia-planner agent, not a slash command)

package/commands/gaia.md

@@ -1,37 +0,0 @@
----
-name: gaia
-description: Invoke the Gaia meta-agent for system architecture analysis, agent design, skill creation, and orchestration debugging
-allowed-tools:
-  - Bash(*)
-  - Read
-  - Edit
-  - Write
-  - Glob
-  - Grep
-  - WebSearch
-  - WebFetch
-  - Task
-  - Agent
-  - Skill
----
-
-Invoke the Gaia meta-agent (`gaia-system`) to work on the gaia-ops orchestration
-system itself. This is the entry point for tasks that modify or analyze agents,
-skills, hooks, or system architecture.
-
-## When to use
-
-- Analyze or improve the gaia-ops architecture
-- Create or update agent definitions (`.md` files)
-- Create or update skills (`SKILL.md` files)
-- Write or debug Python hooks and tools
-- Update `CLAUDE.md` or system configuration
-- Research best practices for agent orchestration
-
-## How it works
-
-This command delegates to the `gaia-system` agent, which is the meta-agent
-specialized in the orchestration system. It follows the standard agent protocol
-and returns a `agent_contract_handoff` block with findings and status.
-
-$ARGUMENTS

package/commands/scan-project.md

@@ -1,74 +0,0 @@
----
-name: scan-project
-description: Scan the current project to detect stack, infrastructure, tools, and update the project context in ~/.gaia/gaia.db
-allowed-tools:
-  - Bash(*)
-  - Read
----
-
-Run the gaia modular project scanner to detect the project stack, infrastructure,
-git setup, CLI tools, orchestration, and runtime environment. The scanner writes
-structured, machine-readable context to `~/.gaia/gaia.db` that agents consume.
-
-No `project-context.json` file is generated. The DB is the canonical source of
-truth. Use `gaia context show` to inspect the stored context.
-
-## What this does
-
-The scanner runs 6 independent modules in parallel:
-- **stack** -- languages, frameworks, package managers
-- **git** -- platform, remotes, branching strategy, monorepo detection
-- **infrastructure** -- cloud providers, IaC, CI/CD, containers
-- **orchestration** -- Kubernetes, GitOps (Flux/Argo), Helm charts
-- **tools** -- installed CLI tools (kubectl, terraform, gcloud, etc.)
-- **environment** -- OS info, language runtimes, .env file patterns
-
-It preserves agent-enriched sections (data added by agents via update_contracts)
-and merges new scan data with existing context using section-ownership rules.
-Projects that temporarily disappear are soft-deleted (`status='missing'`) and
-reactivated when they reappear -- data is never purged.
-
-## How to run
-
-```bash
-gaia scan
-```
-
-Optional flags:
-- `--verbose` -- show scanner-by-scanner progress
-- `--scanners stack,git` -- run only specific scanners
-- `--check-staleness` -- skip scan if context is already fresh (<24h old)
-
-$ARGUMENTS
-
-## Expected output
-
-The CLI prints a JSON summary to stdout:
-
-```
-{
-  "status": "success",
-  "scanner_version": "0.1.0",
-  "sections_updated": ["project_identity", "stack", "git", ...],
-  "scanners_run": 6,
-  "warnings_count": 0,
-  "duration_ms": 2500.0
-}
-```
-
-A human-readable summary is also printed to stderr showing scanner count,
-section count, warnings, and elapsed time.
-
-## After scanning
-
-Inspect the stored context:
-
-```bash
-gaia context show
-```
-
-Or query a specific section:
-
-```bash
-gaia context get stack
-```

package/config/crons-schema.md

@@ -1,81 +0,0 @@
-# Crons Persistence Schema
-
-**Version:** 1  
-**File location:** `.claude/crons.json`  
-**Owner:** Gaia cron persistence system
-
----
-
-## Schema
-
-```json
-{
-  "crons": [
-    {
-      "name": "check-email",
-      "interval_minutes": 180,
-      "prompt": "Revisa el correo y haz triage según gmail-triage skill",
-      "enabled": true,
-      "created": "2026-04-13T20:00:00Z",
-      "last_run": "2026-04-13T23:00:00Z"
-    }
-  ],
-  "version": 1
-}
-```
-
-## Field Definitions
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `name` | string | yes | Unique identifier for the cron. Used as the dedup key during restore. Must be URL-safe (alphanumeric, hyphens). |
-| `interval_minutes` | integer | yes | How often the cron fires, in minutes. Mirrors CronCreate interval. |
-| `prompt` | string | yes | The exact prompt sent to the orchestrator on each tick. |
-| `enabled` | boolean | yes | If false, the cron is skipped during restore. Allows pausing without deletion. |
-| `created` | string (ISO 8601 UTC) | yes | Timestamp when the cron was first created. Set once, never updated. |
-| `last_run` | string (ISO 8601 UTC) or null | yes | Timestamp of the most recent execution. Null if the cron has never run. |
-
-## Top-level Fields
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `crons` | array | The list of persisted cron entries. May be empty. |
-| `version` | integer | Schema version. Currently 1. Increment when field semantics change. |
-
-## Constraints
-
-- `name` must be unique within the `crons` array. Duplicate names are invalid.
-- `interval_minutes` must be a positive integer greater than 0.
-- `last_run` is `null` when the cron has been created but has not yet fired.
-
-## Example: Multiple Crons
-
-```json
-{
-  "crons": [
-    {
-      "name": "check-email",
-      "interval_minutes": 180,
-      "prompt": "Revisa el correo y haz triage según gmail-triage skill",
-      "enabled": true,
-      "created": "2026-04-13T20:00:00Z",
-      "last_run": "2026-04-13T23:00:00Z"
-    },
-    {
-      "name": "drift-monitor",
-      "interval_minutes": 60,
-      "prompt": "Check for infrastructure drift in the current project",
-      "enabled": false,
-      "created": "2026-04-10T10:00:00Z",
-      "last_run": null
-    }
-  ],
-  "version": 1
-}
-```
-
-## File Location
-
-The file lives at `.claude/crons.json`, resolved relative to the active project root (same directory where `.claude/` is found). The path module `find_claude_dir()` from `hooks/modules/core/paths.py` provides the canonical `.claude/` path.
-
-For projects that use `CLAUDE_PLUGIN_DATA`, the file lives under that data directory instead, consistent with how other persisted data (logs, sessions, grants) is stored.

package/config/git_standards.json

@@ -1,72 +0,0 @@
-{
-  "commit_message": {
-    "format": "conventional_commits",
-    "description": "Commit messages must follow Conventional Commits specification",
-
-    "type_allowed": [
-      "feat",
-      "fix",
-      "refactor",
-      "docs",
-      "test",
-      "chore",
-      "ci",
-      "perf",
-      "style",
-      "build"
-    ],
-
-    "scope_required": false,
-    "scope_examples": ["helmrelease", "terraform", "pg-non-prod", "infrastructure"],
-
-    "subject_max_length": 72,
-    "subject_rules": {
-      "capitalize_first_letter": false,
-      "no_period_at_end": true,
-      "imperative_mood": true,
-      "no_emoji": true
-    },
-
-    "body_max_line_length": 72,
-    "body_required": false,
-
-    "footer_forbidden": [
-      "Generated with Claude Code",
-      "Co-Authored-By: Claude",
-      "🤖 Generated with"
-    ],
-
-    "footer_allowed": [
-      "BREAKING CHANGE:",
-      "Refs:",
-      "Closes:",
-      "Fixes:",
-      "Implements:",
-      "See:"
-    ],
-
-    "examples_valid": [
-      "feat(helmrelease): add Phase 3.3 services",
-      "fix(pg-non-prod): correct API key environment variable mappings",
-      "refactor: simplify context provider logic",
-      "docs: update README with new workflow",
-      "chore(deps): update terraform to v1.6.0"
-    ],
-
-    "examples_invalid": [
-      "Added new feature",
-      "Fixed bugs",
-      "Updates",
-      "feat: add feature\n\n🤖 Generated with Claude Code",
-      "feat: add new feature 🚀",
-      "fix: 🐛 correct bug"
-    ]
-  },
-
-  "enforcement": {
-    "enabled": true,
-    "block_on_failure": true,
-    "log_violations": true,
-    "log_path": ".claude/logs/commit-violations.jsonl"
-  }
-}

package/dist/gaia-ops/commands/gaia.md

@@ -1,37 +0,0 @@
----
-name: gaia
-description: Invoke the Gaia meta-agent for system architecture analysis, agent design, skill creation, and orchestration debugging
-allowed-tools:
-  - Bash(*)
-  - Read
-  - Edit
-  - Write
-  - Glob
-  - Grep
-  - WebSearch
-  - WebFetch
-  - Task
-  - Agent
-  - Skill
----
-
-Invoke the Gaia meta-agent (`gaia-system`) to work on the gaia-ops orchestration
-system itself. This is the entry point for tasks that modify or analyze agents,
-skills, hooks, or system architecture.
-
-## When to use
-
-- Analyze or improve the gaia-ops architecture
-- Create or update agent definitions (`.md` files)
-- Create or update skills (`SKILL.md` files)
-- Write or debug Python hooks and tools
-- Update `CLAUDE.md` or system configuration
-- Research best practices for agent orchestration
-
-## How it works
-
-This command delegates to the `gaia-system` agent, which is the meta-agent
-specialized in the orchestration system. It follows the standard agent protocol
-and returns a `agent_contract_handoff` block with findings and status.
-
-$ARGUMENTS

package/dist/gaia-ops/config/crons-schema.md

@@ -1,81 +0,0 @@
-# Crons Persistence Schema
-
-**Version:** 1  
-**File location:** `.claude/crons.json`  
-**Owner:** Gaia cron persistence system
-
----
-
-## Schema
-
-```json
-{
-  "crons": [
-    {
-      "name": "check-email",
-      "interval_minutes": 180,
-      "prompt": "Revisa el correo y haz triage según gmail-triage skill",
-      "enabled": true,
-      "created": "2026-04-13T20:00:00Z",
-      "last_run": "2026-04-13T23:00:00Z"
-    }
-  ],
-  "version": 1
-}
-```
-
-## Field Definitions
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `name` | string | yes | Unique identifier for the cron. Used as the dedup key during restore. Must be URL-safe (alphanumeric, hyphens). |
-| `interval_minutes` | integer | yes | How often the cron fires, in minutes. Mirrors CronCreate interval. |
-| `prompt` | string | yes | The exact prompt sent to the orchestrator on each tick. |
-| `enabled` | boolean | yes | If false, the cron is skipped during restore. Allows pausing without deletion. |
-| `created` | string (ISO 8601 UTC) | yes | Timestamp when the cron was first created. Set once, never updated. |
-| `last_run` | string (ISO 8601 UTC) or null | yes | Timestamp of the most recent execution. Null if the cron has never run. |
-
-## Top-level Fields
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `crons` | array | The list of persisted cron entries. May be empty. |
-| `version` | integer | Schema version. Currently 1. Increment when field semantics change. |
-
-## Constraints
-
-- `name` must be unique within the `crons` array. Duplicate names are invalid.
-- `interval_minutes` must be a positive integer greater than 0.
-- `last_run` is `null` when the cron has been created but has not yet fired.
-
-## Example: Multiple Crons
-
-```json
-{
-  "crons": [
-    {
-      "name": "check-email",
-      "interval_minutes": 180,
-      "prompt": "Revisa el correo y haz triage según gmail-triage skill",
-      "enabled": true,
-      "created": "2026-04-13T20:00:00Z",
-      "last_run": "2026-04-13T23:00:00Z"
-    },
-    {
-      "name": "drift-monitor",
-      "interval_minutes": 60,
-      "prompt": "Check for infrastructure drift in the current project",
-      "enabled": false,
-      "created": "2026-04-10T10:00:00Z",
-      "last_run": null
-    }
-  ],
-  "version": 1
-}
-```
-
-## File Location
-
-The file lives at `.claude/crons.json`, resolved relative to the active project root (same directory where `.claude/` is found). The path module `find_claude_dir()` from `hooks/modules/core/paths.py` provides the canonical `.claude/` path.
-
-For projects that use `CLAUDE_PLUGIN_DATA`, the file lives under that data directory instead, consistent with how other persisted data (logs, sessions, grants) is stored.

package/dist/gaia-ops/config/git_standards.json

@@ -1,72 +0,0 @@
-{
-  "commit_message": {
-    "format": "conventional_commits",
-    "description": "Commit messages must follow Conventional Commits specification",
-
-    "type_allowed": [
-      "feat",
-      "fix",
-      "refactor",
-      "docs",
-      "test",
-      "chore",
-      "ci",
-      "perf",
-      "style",
-      "build"
-    ],
-
-    "scope_required": false,
-    "scope_examples": ["helmrelease", "terraform", "pg-non-prod", "infrastructure"],
-
-    "subject_max_length": 72,
-    "subject_rules": {
-      "capitalize_first_letter": false,
-      "no_period_at_end": true,
-      "imperative_mood": true,
-      "no_emoji": true
-    },
-
-    "body_max_line_length": 72,
-    "body_required": false,
-
-    "footer_forbidden": [
-      "Generated with Claude Code",
-      "Co-Authored-By: Claude",
-      "🤖 Generated with"
-    ],
-
-    "footer_allowed": [
-      "BREAKING CHANGE:",
-      "Refs:",
-      "Closes:",
-      "Fixes:",
-      "Implements:",
-      "See:"
-    ],
-
-    "examples_valid": [
-      "feat(helmrelease): add Phase 3.3 services",
-      "fix(pg-non-prod): correct API key environment variable mappings",
-      "refactor: simplify context provider logic",
-      "docs: update README with new workflow",
-      "chore(deps): update terraform to v1.6.0"
-    ],
-
-    "examples_invalid": [
-      "Added new feature",
-      "Fixed bugs",
-      "Updates",
-      "feat: add feature\n\n🤖 Generated with Claude Code",
-      "feat: add new feature 🚀",
-      "fix: 🐛 correct bug"
-    ]
-  },
-
-  "enforcement": {
-    "enabled": true,
-    "block_on_failure": true,
-    "log_violations": true,
-    "log_path": ".claude/logs/commit-violations.jsonl"
-  }
-}