chore: auto-commit (129 archivos)

- .claude/agents/fn-analizador/SKILL.md
- .claude/agents/fn-constructor/SKILL.md
- .claude/agents/fn-executor/SKILL.md
- .claude/agents/fn-mejorador/SKILL.md
- .claude/agents/fn-orquestador/SKILL.md
- .claude/agents/fn-recopilador/SKILL.md
- .claude/commands/app.md
- .claude/commands/compile.md
- .claude/commands/cpp-app.md
- .claude/commands/create_functions.md
- ...

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

dev/proposals_e2e_checks_0121/registry_dashboard.yaml

@@ -44,7 +44,7 @@
 #      (antes del primer "##" de prosa).
 #   2. El check 'build' asume que el directorio cpp/build/linux existe y cmake
 #      fue configurado previamente. Si no: anteponer
-#      "cmake -B /home/lucas/fn_registry/cpp/build/linux -S /home/lucas/fn_registry/cpp &&"
+#      "cmake -B $HOME/fn_registry/cpp/build/linux -S $HOME/fn_registry/cpp &&"
 #      al cmd o usar el check 'build_configure' (opcional, ver abajo).
 #   3. El check 'integration_sqlite_direct' requiere que registry.db exista en
 #      la raiz del repo. En CI, puede copiarse de un fixture o generarse con
@@ -62,7 +62,7 @@ e2e_checks:
   # CGO no aplica (es C++, no Go). FTS5 se compila via SQLITE_ENABLE_FTS5
   # en la amalgamation vendoreada (CMakeLists.txt lo setea).
   - id: build
-    cmd: "cmake --build /home/lucas/fn_registry/cpp/build/linux --target registry_dashboard -j$(nproc)"
+    cmd: "cmake --build $HOME/fn_registry/cpp/build/linux --target registry_dashboard -j$(nproc)"
     timeout_s: 300
     severity: critical
     # por que: la app enlaza ~20 funciones del registry C++ + sqlite + ws_client.
@@ -74,7 +74,7 @@ e2e_checks:
   # Confirma que el binario existe y es ejecutable tras el build.
   # Tambien verifica la version de symbols minimos esperados (sin linkage roto).
   - id: verify_binary
-    cmd: "test -x /home/lucas/fn_registry/cpp/build/linux/apps/registry_dashboard && /home/lucas/fn_registry/cpp/build/linux/apps/registry_dashboard --help 2>&1 || true"
+    cmd: "test -x $HOME/fn_registry/cpp/build/linux/apps/registry_dashboard && $HOME/fn_registry/cpp/build/linux/apps/registry_dashboard --help 2>&1 || true"
     expect_exit: 0
     timeout_s: 5
     severity: critical
@@ -93,8 +93,8 @@ e2e_checks:
   - id: integration_sqlite_direct
     cmd: >
       DISPLAY="" timeout 3
-      /home/lucas/fn_registry/cpp/build/linux/apps/registry_dashboard
-      /home/lucas/fn_registry/registry.db
+      $HOME/fn_registry/cpp/build/linux/apps/registry_dashboard
+      $HOME/fn_registry/registry.db
       2>&1 | head -5
     expect_exit: 1
     timeout_s: 10
@@ -116,7 +116,7 @@ e2e_checks:
   # Actua como pre-condicion para integration_sqlite_direct.
   - id: data_schema_check
     cmd: >
-      sqlite3 /home/lucas/fn_registry/registry.db
+      sqlite3 $HOME/fn_registry/registry.db
       "SELECT COUNT(*) FROM sqlite_master WHERE type='table'
        AND name IN ('functions','types','apps','analysis','proposals','unit_tests');"
     expect_stdout_contains: "6"
@@ -133,7 +133,7 @@ e2e_checks:
   # via HTTP, pero aqui queremos detectar schema drift independientemente.
   - id: call_monitor_schema_check
     cmd: >
-      sqlite3 /home/lucas/fn_registry/projects/fn_monitoring/apps/call_monitor/operations.db
+      sqlite3 $HOME/fn_registry/projects/fn_monitoring/apps/call_monitor/operations.db
       "SELECT COUNT(*) FROM sqlite_master WHERE type='table'
        AND name IN ('calls','violations','sessions');"
     expect_stdout_contains: "3"
@@ -151,7 +151,7 @@ e2e_checks:
   # WsClient sin actualizar todos los call sites.
   - id: ws_client_compile_check
     cmd: >
-      cmake --build /home/lucas/fn_registry/cpp/build/linux
+      cmake --build $HOME/fn_registry/cpp/build/linux
       --target registry_dashboard -j$(nproc) -- --warn-undefined-functions
       2>&1 | grep -i "ws_client" | grep -i "error" || true
     expect_stdout_contains: ""