funifier-mcp 0.3.16 → 0.3.18

package/skills/funifier/references/audit-permissions.md

@@ -0,0 +1,89 @@
+# funifier-audit-permissions
+
+Cross-check a project's Funifier API calls against the live security document — scan code for usage, build an evidence-backed manifest, run the deterministic audit engine, and report missing scopes, excess tokens, and static danger findings; use when debugging 401s, auditing minimum privilege, or verifying permissions before deploying; audit is read-only and never changes any configuration
+
+---
+
+## Before starting — find relevant docs
+
+Use the `funifier_search_docs` MCP tool to load only what you need:
+
+```
+funifier_search_docs "audit permissions security scope 401 missing-scope excess-token danger manifest bearer basic app-secret role least-privilege"
+```
+
+Then read the most relevant results with `funifier_read_doc path=<path>`.
+
+## Primary docs for this skill
+
+If search returns insufficient results, read these directly:
+
+- `funifier_read_doc path=guides/permission-audit`
+- `funifier_read_doc path=modules/security`
+
+## Steps
+
+## Regras críticas
+
+- **O audit é read-only.** Nenhuma configuração é alterada. O MCP apenas lê o documento de segurança e avalia o manifest.
+- **Bearer tokens embtem o scope no login.** Corrigir o role não invalida tokens existentes — o jogador precisa fazer login novamente.
+- **Excess findings podem ser necessários** a consumidores fora deste manifest. Verifique antes de remover qualquer token.
+- **Low-confidence entries** (URLs dinâmicas ou wrappers): use `"confidence": "low"` e um path com o prefixo mais específico possível. Nunca omita chamadas suspeitas.
+
+---
+
+## Steps
+
+### 1. Descobrir chamadas Funifier no projeto
+
+Procure no código todas as chamadas à API Funifier (endpoints, métodos HTTP e mecanismo de auth):
+
+- **Com GitNexus indexado:** `gitnexus_query("funifier API calls")` para localizar call sites
+- **Fallback (busca em código):** grep por `/v3/`, `funifier`, `apiKey`, `app_secret`, `Authorization`
+- Para cada chamada, registre: `method`, `path`, `auth context` (ver tabela em `guides/permission-audit.md` §2), e `file:line` como `evidence`
+- Classifique o auth:
+  - Sem secret / token público → `"public"`
+  - Player Bearer → `"player"`
+  - App secret em config/env → `"app:<name>"` (use o `name` da entrada em `apps[]`)
+
+### 2. Montar o manifest
+
+Construa o JSON seguindo o schema de `guides/permission-audit.md` §3. Exemplo mínimo:
+
+```json
+{
+  "version": 1,
+  "entries": [
+    { "method": "GET",  "path": "/v3/player/me",    "auth": "player",      "evidence": "src/api.ts:12" },
+    { "method": "POST", "path": "/v3/action/log",   "auth": "player",      "evidence": "src/events.ts:58" },
+    { "method": "POST", "path": "/v3/player",        "auth": "app:backend", "evidence": "workers/sync.ts:34" },
+    { "method": "GET",  "path": "/v3/database/orders", "auth": "app:backend", "evidence": "workers/sync.ts:80" }
+  ]
+}
+```
+
+Para chamadas com URL dinâmica: use o prefixo mais específico e defina `"confidence": "low"`.
+
+### 3. Executar o audit
+
+```
+funifier_permissions action=audit data=<manifest JSON>
+```
+
+O resultado inclui:
+- `missing`: chamadas que seriam negadas — 401 em produção. Campo `requiredTokens` indica o token mínimo.
+- `excess`: tokens concedidos que nenhuma entrada requer. Campo `narrowingSuggestion` para broad tokens.
+- `danger`: riscos estáticos no documento de segurança (independentes do manifest).
+- `manual-review`: tokens não verificáveis por análise de paths (`cross_domain`, `write_upload`, etc.).
+- `missing-principal`: auth context referenciado no manifest não existe no documento de segurança.
+
+### 4. Apresentar o relatório e encaminhar remediação
+
+Apresente os findings agrupados por severidade (`missing` primeiro). Para cada `missing`:
+- Indique o token exato necessário (`requiredTokens`), a chamada e a evidência.
+- **Não aplique a correção automaticamente.** Apresente a ação sugerida ao utilizador e aguarde aprovação.
+- Quando aprovado: `funifier_permissions action=save_security_role` ou `save_api_app` (cada mutação cria backup automático).
+
+Para `excess`: adverta que o token pode ser necessário a consumidores fora deste manifest antes de sugerir remoção.
+
+Para `danger`: explique o risco e sugira remoção ou restrição do scope afetado como ação separada.

package/skills/funifier/references/configure-security.md

@@ -112,9 +112,3 @@ funifier_permissions action=restore_backup backup_path=<path retornado por list_
 O restore valida que o `serverUrl` do snapshot coincide com a conexão atual — não aplique backup de outro tenant. O próprio restore também gera um snapshot prévio, permitindo desfazer o rollback.
 
 Variáveis opcionais: `FUNIFIER_PROJECT_ROOT` (diretório do projeto; definida nos configs gerados pelo `init`) e `FUNIFIER_BACKUP_ROOT` (substitui `.funifier/backups/` por outro diretório). Snapshots não expiram automaticamente — remova arquivos antigos manualmente quando necessário.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-

package/skills/funifier/references/create-action.md

@@ -91,10 +91,3 @@ funifier_list type=action search=<_id>
 ```
 
 Do NOT use `funifier_logs` — that is only for triggers and schedulers.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| ActionLog is the entity class recording each player action event with fields actionId, userId, attributes, time, and id | ✓ verified | Class:src/main/java/com/funifier/engine/action/ActionLog.java:ActionLog |
-| ActionManager handles action registration and dispatching in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/action/ActionManager.java:ActionManager |

package/skills/funifier/references/create-aggregate.md

@@ -131,12 +131,14 @@ POST /v3/database/achievement/aggregate
 
 ### 4. Registrar como Prepared Aggregate
 
+**Formatação obrigatória:** o campo `aggregate` é o pipeline serializado como **string identada**, com `\n` ao fim de cada linha (equivalente a `JSON.stringify(pipeline, null, 4)`) — **nunca** minificado em uma linha única. O `script` Groovy também preserva indentação e `\n`. Os escapes (`\"`, `\\`) seguem a seção "Formato do payload" acima.
+
 ```json
 {
   "_id": "top_players_month",
   "title": "Top Players Month",
   "collection": "achievement",
-  "aggregate": "[{\"\$match\":{\"type\":0,\"item\":\"xp\"}},{\"\$group\":{\"_id\":\"\$player\",\"total\":{\"\$sum\":\"\$total\"}}},{\"\$sort\":{\"total\":-1}},{\"\$limit\":10}]",
+  "aggregate": "[\n    {\n        \"$match\": {\n            \"type\": 0,\n            \"item\": \"xp\"\n        }\n    },\n    {\n        \"$group\": {\n            \"_id\": \"$player\",\n            \"total\": {\n                \"$sum\": \"$total\"\n            }\n        }\n    },\n    {\n        \"$sort\": {\n            \"total\": -1\n        }\n    },\n    {\n        \"$limit\": 10\n    }\n]",
   "script": ""
 }
 ```
@@ -176,9 +178,3 @@ api.post('/v3/find/<id>', { player: 'abc' })
 | Script vazio | Se o pipeline só usa `"$param:nome"`, o `script` pode ser `""` — não precisa de `prepare()` |
 
 Se o resultado vier vazio ou inesperado: `GET /v3/find/<id>/params` lista os params que o pipeline espera, e `POST /v3/prepared/aggregate/<id>/analyze` (mesmo corpo da execução) retorna outputs/exceções do script e o resultado de cada etapa do pipeline (`aggregate_step_N`) — veja `references/debug.md`.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| DatabaseManager provides MongoDB connection and collection access for aggregate queries in Groovy scripts | ✓ verified | Class:src/main/java/com/funifier/engine/database/DatabaseManager.java:DatabaseManager |

package/skills/funifier/references/create-audit.md

@@ -113,11 +113,3 @@ Filtros combináveis em `$match`: `user`/`login` (ator), `type` (`studio`/`playe
 ### 6. Exclusão (cuidado)
 
 `funifier_delete type=audit id=<id>` remove a config **e todos os seus logs em cascata**. Confirme com o usuário antes.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Audit config fields are _id, title, active, entity, event, clean, type with event constants create/update/delete and type constants studio/player/all | ✓ verified | Class:src/main/java/com/funifier/engine/audit/Audit.java:Audit |
-| AuditManager.log only writes an AuditLog when an active Audit matches entity+event and the config type matches the operation origin | ✓ verified | Class:src/main/java/com/funifier/engine/audit/AuditManager.java:AuditManager |
-| clearExpiredLogs purges audit_log entries older than each config's clean retention and is invoked from AsyncProcessor | ✓ verified | Method:src/main/java/com/funifier/engine/audit/AuditManager.java:AuditManager.clearExpiredLogs#0 |

package/skills/funifier/references/create-challenge.md

@@ -114,10 +114,3 @@ funifier_get type=challenge id=<_id>
 ```
 
 Não use `funifier_logs` — isso é só para triggers e schedulers.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Challenge is the core entity class storing action rules and reward configuration in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/challenge/Challenge.java:Challenge |
-| ChallengeManager manages challenge lifecycle including progress checking and achievement dispatch | ✓ verified | Class:src/main/java/com/funifier/engine/challenge/ChallengeManager.java:ChallengeManager |

package/skills/funifier/references/create-competition.md

@@ -96,10 +96,3 @@ POST /v3/competition/join   { "competition": "<_id>", "player": "<player_id>" }
 POST /v3/competition/leader/aggregate?id=<_id>
 GET /v3/competition/<_id>/execute   (manual execution only)
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Competition is the entity class for timed ranking contests with enrollment and position-based rewards in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/competition/Competition.java:Competition |
-| CompetitionManager manages competition execution, ranking computation, and reward distribution in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/competition/CompetitionManager.java:CompetitionManager |

package/skills/funifier/references/create-crossword.md

@@ -572,9 +572,3 @@ funifier_list type=crossword search=<titulo>
 ```
 
 Teste o jogo no Studio e verifique que as dicas e palavras estão corretas.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Crossword is the entity class for word puzzle games with title, words, and clue positions in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/crossword/Crossword.java:Crossword |

package/skills/funifier/references/create-custom-object.md

@@ -89,9 +89,3 @@ DELETE /v3/database/car__c?q=_id:'car001'
 ### 7. Usar em triggers
 
 Para executar trigger em eventos da coleção, use `entity: "car__c"` no payload do trigger.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| DatabaseManager provides MongoDB connection for custom __c collection CRUD operations in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/database/DatabaseManager.java:DatabaseManager |

package/skills/funifier/references/create-custom-page.md

@@ -133,9 +133,3 @@ PUT /v3/database/studio_page   { "_id": "...", "display": true, "title": "...",
 
 Acesse `/studio/custom/<slug>` no browser para testar.
 Para CRUD completo: crie página de lista (`display: true`) + formulário (`display: false`, slug com `/:id`).
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| DatabaseManager provides MongoDB connection access for aggregate-backed Studio custom pages | ✓ verified | Class:src/main/java/com/funifier/engine/database/DatabaseManager.java:DatabaseManager |

package/skills/funifier/references/create-folder.md

@@ -102,10 +102,3 @@ funifier_save type=folder-log payload=<json>
 funifier_folder operation=progress   { "folder": "<root_id>", "player": "player123" }
 funifier_folder operation=inside     { "folder": "<root_id>" }
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Folder is the entity class for learning trail nodes with unlock_policy, parent, and position fields in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/folder/Folder.java:Folder |
-| FolderManager handles folder tree traversal, progress computation, and cascade deletion in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/folder/FolderManager.java:FolderManager |

package/skills/funifier/references/create-lastmile.md

@@ -641,9 +641,3 @@ funifier_list type=lastmile
 ```
 
 Simule progresso do jogador até 80% do desafio e verifique se a mensagem é disparada.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| LastMile is the entity class for threshold-triggered motivational messages linked to challenge progress in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/lastmile/LastMile.java:LastMile |

package/skills/funifier/references/create-leaderboard.md

@@ -124,9 +124,3 @@ funifier_list type=leaderboard search=<title>
 ```
 
 If scores look wrong, reset cache: `GET /v3/leaderboard/reset`
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| LeaderBoardManager manages leaderboard ranking computation and cache reset in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/leader/LeaderBoardManager.java:LeaderBoardManager |

package/skills/funifier/references/create-level.md

@@ -92,10 +92,3 @@ funifier_list type=level
 ```
 
 Confirme que os níveis estão em ordem crescente de `minPoints`.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Level is the entity class defining level thresholds and point item reference in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/level/Level.java:Level |
-| LevelManager tracks player level progression and threshold evaluation | ✓ verified | Class:src/main/java/com/funifier/engine/level/LevelManager.java:LevelManager |

package/skills/funifier/references/create-lottery.md

@@ -911,10 +911,3 @@ GET /v3/lottery/participants?lottery=<_id>
 ```
 
 To undo: `DELETE /v3/lottery/:id/execute`
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Lottery is the entity class for ticket-based prize draws with drawDate, choiceMethod, and maxWinners in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/lottery/Lottery.java:Lottery |
-| LotteryManager handles ticket generation, draw execution, and winner selection in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/lottery/LotteryManager.java:LotteryManager |

package/skills/funifier/references/create-mystery.md

@@ -767,9 +767,3 @@ funifier_save type=mystery payload=<json>
 GET /v3/mystery/evaluate/<_id>?player=<player_id>
 GET /v3/mystery/execute/<_id>?player=<player_id>
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| MysteryBox is the entity class for probability-based instant games with options, win_chart, and requirements in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/mystery/MysteryBox.java:MysteryBox |

package/skills/funifier/references/create-notification.md

@@ -73,9 +73,3 @@ funifier_list type=notification
 ```
 
 Dispare o evento correspondente e verifique se a notificação é entregue.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Notification is the entity class for automated player feedback messages with event, scope, and content fields in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/notify/Notification.java:Notification |

package/skills/funifier/references/create-point.md

@@ -93,10 +93,3 @@ funifier_list type=point search=<_id>
 ```
 
 Do NOT use `funifier_logs` — that is only for triggers and schedulers.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| PointCategory is the entity class with category, shortName, and techniques fields for defining point types | ✓ verified | Class:src/main/java/com/funifier/engine/point/PointCategory.java:PointCategory |
-| PointManager manages point accumulation and balance queries in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/point/PointManager.java:PointManager |

package/skills/funifier/references/create-quiz.md

@@ -96,10 +96,3 @@ POST /v3/quiz/start   { "quiz": "<id>", "player": "<player_id>" }
 POST /v3/question/log/bulk   [{ "quiz": "<id>", "quiz_log": "<log_id>", "question": "<q_id>", "answer": ["1"], "player": "<player_id>" }]
 POST /v3/quiz/finish  { "quiz_log": "<log_id>" }
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Quiz is the entity class storing questions and answer configuration in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/quiz/Quiz.java:Quiz |
-| QuizManager handles quiz scoring, lifecycle, and player response processing | ✓ verified | Class:src/main/java/com/funifier/engine/quiz/QuizManager.java:QuizManager |

package/skills/funifier/references/create-scheduler.md

@@ -139,9 +139,3 @@ funifier_logs type=scheduler id=<_id>
 ```
 
 Confirme que não há erros de compilação ou execução no stack trace.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| SchedulerManager is the class that manages cron-based script execution in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/integration/scheduler/SchedulerManager.java:SchedulerManager |

package/skills/funifier/references/create-story.md

@@ -634,9 +634,3 @@ GET /v3/story/<_id>
 ```
 
 Teste a navegação entre cenas no Studio antes de publicar.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-

package/skills/funifier/references/create-swap.md

@@ -93,9 +93,3 @@ POST /v3/swap/receive   { "swap": "<swap_id>" }
 POST /v3/swap/counter/offer   { "swap": "<swap_id>", "buyer": "jerry", "offer": [{ "total": 1, "type": 0, "item": "coin" }] }
 POST /v3/swap/counter/offer/accept   { "offer": "<offer_id>" }
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Swap is the entity class for player-to-player trade offers with seller, rewards, and requires fields in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/swap/Swap.java:Swap |

package/skills/funifier/references/create-trigger.md

@@ -183,11 +183,3 @@ funifier_logs type=trigger id=<_id>
 ```
 
 Confirme que não há erros de compilação ou execução. Se houver, leia o stack trace e corrija o script.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Achievement constants TYPE_POINT=0, TYPE_CHALLENGE=1, TYPE_VIRTUAL_GOOD=2, TYPE_LEVEL=3 are defined in the Achievement class | ✓ verified | Class:src/main/java/com/funifier/engine/achievement/Achievement.java:Achievement |
-| ActionLog is the entity class for action triggers with fields actionId, userId, attributes (Map), time, and id | ✓ verified | Class:src/main/java/com/funifier/engine/action/ActionLog.java:ActionLog |
-| TriggerManager is the class that manages trigger script execution and lifecycle in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/integration/trigger/TriggerManager.java:TriggerManager |

package/skills/funifier/references/create-virtual-good.md

@@ -94,9 +94,3 @@ Para testar uma compra:
 ```
 POST /v3/virtualgoods/purchase   { "player": "<id>", "item": "<item_id>", "total": 1 }
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| CatalogManager is the class managing virtual goods catalog items, pricing, and purchase lifecycle in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/catalog/CatalogManager.java:CatalogManager |

package/skills/funifier/references/create-webhook.md

@@ -70,9 +70,3 @@ funifier_list type=webhook
 ### 5. Testar
 
 Dispare um evento (ex: log uma ação que gera conquista) e verifique se o endpoint externo recebeu o payload.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Webhook is the entity class for outbound event notifications to external HTTP endpoints in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/webhook/Webhook.java:Webhook |

package/skills/funifier/references/create-websocket.md

@@ -69,9 +69,3 @@ funifier_list type=websocket
 ```
 
 Conecte um cliente WebSocket e dispare um evento para confirmar que as mensagens chegam em tempo real.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| WebSocket is the entity class for real-time bidirectional communication configuration in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/websocket/WebSocket.java:WebSocket |

package/skills/funifier/references/create-widget.md

@@ -74,9 +74,3 @@ Cole o código de embed na página destino (intranet, LMS, etc.) e verifique que
 funifier_list type=widget
 GET /v3/widget/<_id>
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Widget is the entity class for embeddable visual gamification components with type, configuration, and display settings in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/widget/Widget.java:Widget |

package/skills/funifier/references/date-handling.md

@@ -170,9 +170,3 @@ Não coloque o parâmetro convertido para `Date` dentro de `{ "$date": "$param:s
 - [ ] Em prepared aggregate, usar `"$param:nome"` exatamente como string.
 - [ ] Para data absoluta em prepared aggregate, converter no `script` com `DateUtil.parse`, validar `null`, e substituir o `Date` diretamente em `$gte`/`$lte`.
 - [ ] Testar aggregate direto antes de salvar como prepared aggregate.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-

package/skills/funifier/references/debug.md

@@ -90,9 +90,3 @@ Leia o arquivo de doc específico para o módulo com problema:
 - Scheduler → `funifier_read_doc path=modules/scheduler`
 - Aggregate → `funifier_read_doc path=guides/aggregates`
 - Security/Auth → `funifier_read_doc path=modules/security`
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| TriggerManager is the entry point for trigger script execution and error capture in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/integration/trigger/TriggerManager.java:TriggerManager |

package/skills/funifier/references/help.md

@@ -79,9 +79,3 @@ Baseado na tabela acima, instrua o usuário a usar a skill específica.
 ### 4. Se não encontrar skill específica
 
 Consulte `funifier_read_doc path=index` e leia o módulo relevante diretamente.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Achievement is the core entity class representing all gamification rewards in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/achievement/Achievement.java:Achievement |

package/skills/funifier/references/implement-frontend.md

@@ -122,10 +122,3 @@ await fetch('/v3/database/cycle__c?strict=true', {
 ### 5. Hospedar no Funifier (opcional)
 
 Para arquivos estáticos, leia `funifier_read_doc path=modules/static-repo`.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| PlayerManager handles player authentication and session management in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/player/PlayerManager.java:PlayerManager |
-| ActionManager processes action event registration from frontend clients | ✓ verified | Class:src/main/java/com/funifier/engine/action/ActionManager.java:ActionManager |

package/skills/funifier/references/import-csv.md

@@ -73,9 +73,3 @@ Após import, verifique se os registros foram criados:
 ```
 funifier_list type=player search=<nome_importado>
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-

package/skills/funifier/references/manage-indexes.md

@@ -83,9 +83,3 @@ Get the index name from `action=list`. The `_id_` index cannot be dropped.
 | Unique email | `{"email": 1}` (uniqueness enforced by MongoDB, not this API) |
 
 For a composite (e.g. `{player: 1, time: -1}` to back filter+sort in one plan), use the Groovy/trigger path shown in the Limitation section — not this tool.
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-

package/skills/funifier/references/manage-player.md

@@ -80,10 +80,3 @@ GET /v3/player/<_id>/status
 ```
 GET /v3/team/<team_id>/member/add/<player_id>
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Player is the entity class with _id, name, email, teams, extra fields in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/player/Player.java:Player |
-| PlayerManager handles player CRUD, authentication, and status queries in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/player/PlayerManager.java:PlayerManager |

package/skills/funifier/references/manage-team.md

@@ -74,9 +74,3 @@ GET /v3/team/sales/status
 ```
 GET /v3/team/sales/member/remove/tom
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-| Team is the entity class for player groups with _id, name, members, owner fields in funifier-service | ✓ verified | Class:src/main/java/com/funifier/engine/team/Team.java:Team |

package/skills/funifier/references/upload-file.md

@@ -89,9 +89,3 @@ funifier_save type=player payload=<json>
 ```
 DELETE /v3/upload/<upload_id>
 ```
-
-## Verified References
-
-| Claim | Status | Evidence |
-|-------|--------|----------|
-