Adotar o log de auditoria do Bridger na Luma
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript, node.js
Research direction
Read the linked Bridger issues #224 and #223 first; this work is explicitly blocked until they ship in an @usebridger/* release. Then inspect the Luma plugin actions in the table and the dashboard documentation at apps/lumabot/docs/dashboard.md. Done means adopting ctx.audit for the listed administrative actions, adding a test for each action with @usebridger/testing, configuring retention, and documenting the workflow in apps/lumabot/docs/.
Written by the indexing model from the issue text.
Description
Contexto
O kernel vai ganhar ctx.audit (murillous/usebridger#224) e usuários individuais no dashboard (murillous/usebridger#223). A Luma deve adotar os dois assim que saírem numa versão do @usebridger/*, para responder "quem mudou o quê" no bot em produção.
Bloqueada por murillous/usebridger#224 e murillous/usebridger#223. Não contornar aqui: lacuna é do Bridger.
O que auditar na Luma
O kernel e o dashboard já auditam plugin enable/disable/reload, config, segredos e login. Fica com a Luma o que só ela faz:
| Plugin | Ação | action |
Observação |
|---|---|---|---|
luma |
troca de persona do chat, criação/remoção de persona custom | luma.persona.set / .create / .delete |
target: chat; sem o texto da persona em details |
luma |
!luma limpar (esquecer histórico) |
luma.history.clear |
ator = contato (titular) |
ai |
troca de provider/modelo pela config ou comando de owner | ai.model.change |
sem chave de API |
reminders |
lembrete criado/cancelado por terceiro (owner apagando de outro) | reminders.delete |
só quando o ator ≠ dono do lembrete |
rank |
reset de ranking | rank.reset |
|
comandos role: 'owner' |
qualquer execução | command.owner |
registro único no middleware, não comando a comando |
pairing |
novo pareamento / sessão do WhatsApp perdida | transport.pairing |
Volume: não auditar mensagem comum nem resposta da IA. Auditoria registra o ato administrativo, não a conversa.
Tarefas
- Subir as versões do
@usebridger/*comctx.audite usuários no dashboard - Migrar o token do dashboard (
data/dashboard-token) para o bootstrap do primeiro owner; atualizarapps/lumabot/docs/dashboard.md - Middleware que audita comandos
owner -
ctx.audit.recordnas ações da tabela, com teste por ação no@usebridger/testing - Retenção da auditoria na config da Luma (proposta: 1 ano; não é contrato público)
- Docs do COMO em
apps/lumabot/docs/
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 6
- Avg merge
- 45m
- Merged PRs (30d)
- 142
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from murillous/LumaBot
-
feat(lumabot): tools só de leitura restantes devem declarar sideEffects: falsePossibly taken A pull request linked to this issue is open or already merged. Openarea:plugin good first issue type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area:plugin type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:plugin good first issue type:bug
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area:plugin type:feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
area:plugin good first issue type:debt
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in murillous/LumaBot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
oskarrough/dodgethis#115 ·
Maintainers usually reply within 1 day
-
[Bug]: REST API URL starting with "http" but no scheme (e.g. httpbin.org/get) is not given an http:// prefixPossibly taken @ItsDeadlyProgrammer claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
appsmithorg/appsmith#42471 · 1 comment ·
Maintainers usually reply within 2 days
-
external-plugin requires-submitter-fixes
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/awesome-copilot#5396 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
chenasraf/nextcloud-forum#348 ·
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melodic-software/claude-code-plugins#9619 ·
Maintainers usually reply within 1 day