Files
Veskslop-t/CURRENT.md
T

59 lines
2.5 KiB
Markdown

# CURRENT.md — session state
Last updated: 2026-09-11
This file tracks the work state. Read it first. Update it before you stop.
## Current focus (broad)
Rework the Vesktop integration into a validated capability layer ("core bridge"). Move all logic
into the external daemon. Keep upstream divergence small.
## In progress
- None. The rework milestone is complete and verified live.
## Done
- Audit of the earlier Vesktop patches. `src/` was reverted to upstream.
- Action protocol and validated renderer actions: `src/shared/puppetProtocol.ts`,
`src/renderer/puppet/actions.ts`.
- Core bridge wired: events, renderer init, main bridge, and the upstream hooks.
- Auth persistence re-added: pinned `DATA_DIR`, token file, preload seeding, `VESKSLOP_HEADLESS`.
- Daemon moved to the core-bridge transport. CDP stays as a development fallback.
- Mock core and trigger test added. The daemon runs without Electron.
- Live verification (2026-09-11): `get_state` returned the real account and 7 guilds, `send_dm`
reached zzib, and a synthetic owner message flowed through the real event path into the daemon
log with the command parsed.
- Module docs in `docs/` and the agent entry point in `AGENTS.md`.
## Next (in order)
1. Keep `CURRENT.md`, `AGENTS.md`, and `docs/` in sync with each change.
2. Voice join and leave actions. Validated actions, then a trigger command.
3. Audio in and out with PipeWire.
4. Video streaming.
5. Fetch-based message read. The current read is cache-only.
6. Client lightening and the web debug UI.
7. Remote client authentication over LAN or Tailscale.
## Blocked / needs input
- The original repo `zib/Veskslop` has a broken server-side git setup. Fetches and clones fail with
`bad pack header` because a script (`/home/git/.sys_health_s3`) runs on the Veskslop read path.
Gitea's branch metadata is stale, so the web UI does not show `headless` or `headless-rework`.
The admin must fix that hook and re-enable or repair push processing.
- Workaround: use `zib/Veskslop-t` (remote `veskslop-t`). All branches and tags are pushed there,
and its read path works.
- `main` on the original server is `68fc8bb` (zib, "Upload files to docs/images"). It diverged from
the local `main` (`24447f5`). Reconcile after the server is fixed.
- The hero image was copied from the original `main` into `docs/images/veskslop-hero.png`.
## Where to look
- Design documents: `docs/INDEX.md`
- Agent rules: `AGENTS.md`
- Daemon code: `poc/src/`
- Core bridge code: `src/shared/puppetProtocol.ts`, `src/renderer/puppet/`,
`src/main/puppetBridge.ts`