zib/Veskslop-t
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add tiers, continuation, fetch cooldown, persistent action log, voice read, batch MCP

Browse Source
This commit is contained in:
Fisto
2026-09-11 15:53:06 +02:00
parent 82f78bb2b4
commit 8e8c15e8bc
17 changed files with 669 additions and 139 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CURRENT.md
+18 -16
View File
@@ -6,36 +6,38 @@ This file tracks the work state. Read it first. Update it before you stop.
## Current focus (broad)
Build the text-based communication layer: trusted-only triggers, conversation context, response
routing, and MCP tools. Voice, audio, and video stay deferred.
Build the text-based communication layer: trusted tiers, context, response routing, MCP tools, and
persistent logging. Voice, audio, and video stay deferred.
## In progress
- None. The text milestone is complete and verified with the mock core.
- None. The latest text milestone is complete and verified with the mock core.
## Done
- Validated core bridge: protocol, actions, validation, structured errors, hard outbound rate limit.
- Core bridge wired: renderer events, main bridge, and the upstream hooks.
- Auth persistence: pinned `DATA_DIR`, token file, preload seeding, `VESKSLOP_HEADLESS`.
- Daemon moved to the core-bridge transport. CDP stays as a development fallback.
- Trusted-only triggers: direct messages and direct mentions.
- Context: 15 messages or 4000 characters, file names only, incremental fetch, tmp cache with a
size limit.
- Daemon on the core-bridge transport. CDP stays as a development fallback.
- Trusted-only triggers: DMs and direct mentions. Trust tiers: user, trusted, admin.
- Context: 15 messages or 4000 characters, time stamps, file names only, incremental fetch, tmp
cache with a size limit, fetch cooldown.
- Continuation window: a rushed follow-up joins the request context.
- Response policy: origin channel or DM. Sensitive commands default to DM.
- MCP tools: context and config tools beside the earlier state and log tools.
- Unit tests for the pure logic and the cache. Mock end-to-end tests passed.
- Persistent action log: triggers, commands, replies, errors, rotation, and secret redaction.
- MCP tools: context, config, voice state, action log, and a read-only batch tool.
- Event processing is serialized. Replayed events are dropped.
- Unit tests for the pure logic and the cache. Mock end-to-end tests pass.
- Live verification: state, DM send, and a synthetic trigger through the real event path.
## Next (in order)
1. Notification parsing: edits, deletes, reactions, replies, and message references.
2. Persistent trigger log with rotation.
1. Notification parsing: edits, deletes, reactions, and message references.
2. Reply-to-puppet counts as a trigger.
3. Per-user rate limit and command cooldowns.
4. More commands: `ask`, `summarize`, `context`, and `config`.
5. MCP event delivery for agents. Push or a stateful stream.
6. Multi-identity: a read-only collector account beside the puppet.
7. Later: voice, audio, video, client lightening, web debug UI, remote authentication.
4. Setup command with reaction-based multiple choice.
5. MCP event delivery decision: poll, stateful session, or a local event stream.
6. Collector account: read-only modules for voice membership fallback.
7. Later: voice actions, audio, video, client lightening, web debug UI, remote authentication.
## Blocked / needs input