samiandClaude Sonnet 5 55f0c6099d daemon: D4b — download.pause/resume/start/cancel and queue.start/stop drive the scheduler
download.pause/resume/start/cancel and queue.start/stop were stubs; now they call into
the scheduler and take effect immediately, not on the next 1s tick — pausing, resuming
or cancelling a live transfer can't wait, and per ADR 0013 §3 the governor never
touches a user-owned pause on its own.

New rpc::TaskActionPort interface (owned by rpc/, implemented by sched::Scheduler) is
what dispatcher.hpp depends on instead of sched/scheduler.hpp directly. Needed because
veloxd_sched already links veloxd_rpc (for EventHub); dispatcher.hpp pulling in
sched/scheduler.hpp directly would make it a real circular library dependency, breaking
anything that links veloxd_rpc alone (cli's tests, as it turned out — hit and fixed
during this change).

Scheduler::user_pause/user_resume/user_start/user_cancel + pause_queue follow tick()'s
existing to_pause pattern: call the engine (async, no synchronous effect) and transition
the store eagerly so download.get/list are correct the instant the RPC call returns.

Fixed a real bug surfaced while building this: transition() always overwrote
pause_reason to NULL when the engine's own delayed pause-ack callback (on_state to
paused, no error) arrived after whoever actually initiated the pause had already
written the real reason — now it preserves the stored reason when the callback supplies
none, instead of clobbering it. Covered by a regression check in sched_scheduler_test.

store/queues gets get() and set_state() (was list()-only) for queue.start/stop.

Verified against real veloxd + tools/testserver, not just unit tests: pausing a live
single-segment throttled transfer freezes downloadedBytes, resume continues it from
that point, cancel stops it; a bad taskId comes back in BulkTaskResult.failed with
-32010, not a crash; queue.stop(pauseRunning:true) pauses the queue's running task
immediately and queue.start resumes admission.

Known gap: download.start's contract "a task in 'queued' jumps its queue" (priority
bump) is not implemented — admission is still plain FIFO by created_at. Noted in
deferrals.md.

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01GRDjHGgpYmMoPE2UFbe7pP
2026-09-11 17:20:58 +04:00
2026-09-10 18:55:19 +04:00
2026-09-10 15:18:43 +04:00

Velox Download Manager (VDM)

An IDM-class download manager for Ubuntu 26.04 LTS: multi-segment accelerated HTTP(S) downloading, resume, categories and automatic file distribution, queues and scheduler, speed limiter, a Firefox extension that captures downloads automatically, and clipboard link capture.

Name is a placeholder. Binaries are veloxd, velox-gui, velox, velox-nmhost. Rename before first release if you want something else — do it in M0, never later.


Status

Phase M0 — scaffolding. No implementation code exists yet. This repository currently contains the architecture, the wire contract, the roadmap, and one brief per build lane so that several agents can work in parallel without colliding.

Start here:

Document What it answers
docs/01-architecture.md Process model, why four binaries, framework choices and why
docs/02-roadmap.md Milestones M0M7, what runs in parallel, exit gates
docs/03-gui-spec.md IDM-parity UI: every window, dialog, column, menu
docs/04-engine-design.md Segmentation, resume, buffers, rate limiting, disk I/O
docs/05-extension-spec.md Firefox capture, transports, pairing, media grabber
docs/06-risks-and-spikes.md Snap Firefox, Wayland clipboard, and the other landmines
docs/07-packaging.md .deb/PPA, Flatpak, AMO signing, install layout
contracts/README.md The interface. Both sides build against this
CLAUDE.md Rules of engagement for agents working in this repo

Per-lane briefs live in docs/agents/ — one per agent, each with an owned directory list, a definition of done, and the files it must never touch. To dispatch the agents, use docs/agents/PROMPTS.md — six copy-paste prompts plus the worktree commands and the wave order.


Architecture in one picture

  ┌────────────────────┐   native messaging (stdio JSON)   ┌──────────────┐
  │  Firefox extension │◄─────────────  or  ──────────────►│ velox-nmhost │
  │       (MV3, TS)    │   loopback WS 127.0.0.1 + token   └──────┬───────┘
  └────────────────────┘                                          │
                                                                  │
  ┌────────────────────┐                                          ▼
  │  velox-gui (Qt 6)  │◄──── JSON-RPC 2.0 over Unix socket ──► ┌─────────────┐
  └────────────────────┘      $XDG_RUNTIME_DIR/velox/velox.sock │   veloxd    │
                                                                │  (daemon)   │
  ┌────────────────────┐                                        │             │
  │   velox (CLI)      │◄───────────────────────────────────────┤ libveloxcore│
  └────────────────────┘                                        └──────┬──────┘
                                                                       │
                                                              SQLite + sparse files

The daemon owns all state and all sockets. The GUI is a view — closing it does not stop a download. The extension never touches the disk; it hands URL + headers + cookies to the daemon and gets a task id back.


Repository layout

vdm/
├── contracts/          ⭐ Wire contract: JSON Schema, fixtures, codegen. Frozen per version.
├── core/               C++23  libveloxcore — engine. No UI, no RPC, no SQL.
├── daemon/             C++23  veloxd — RPC server, scheduler, queues, SQLite store.
├── gui/                C++23  velox-gui — Qt 6 Widgets, IDM-parity UI.
├── cli/                C++23  velox — scriptable client.
├── nmhost/             C++23  velox-nmhost — Firefox native-messaging bridge (thin pipe).
├── extension/          TS     Firefox MV3 WebExtension.
├── tools/
│   ├── mockd/          TS mock daemon — lets GUI + extension work before veloxd exists.
│   ├── testserver/     Deliberately hostile HTTP server (no Range, flaky, redirects, auth).
│   ├── bench/          Throughput and CPU benchmarks.
│   └── fuzz/           libFuzzer targets for parsers.
├── tests/
│   ├── conformance/    Protocol suite. Every lane must pass it. Gate for merging.
│   ├── integration/    veloxd + testserver.
│   └── e2e/            Playwright: real Firefox + real daemon + real file on disk.
├── packaging/          debian/, flatpak/, appimage/, native-host manifests.
└── docs/               Everything above, plus adr/ and agents/.

Toolchain bootstrap

Surveyed on this machine 2026-09-09 — most of it is already installed:

Present Version
git · cmake · ninja · g++ · gdb 2.53.0 · 4.2.3 · — · 15.2.0 (C++23 ready)
qt6-base-dev · qt6-tools-dev · qt6-tools-dev-tools
libcurl4-openssl-dev · libsqlite3-dev · nlohmann-json3-dev · libssl-dev
libavformat-dev · libavcodec-dev · ffmpeg
clang-format · clang-tidy · python3 · pkg-config
python3-jsonschema · python3-referencing (conformance static runner)

Only these four are missing:

sudo apt update && sudo apt install -y \
  qt6-svg-dev \       # GUI: SVG icon rendering
  libsecret-1-dev \   # DAEMON: Secret Service for site logins
  nodejs npm \        # EXT + PROTO: extension build, mockd, conformance runner
  clang               # optional: libFuzzer targets in M7

Node in the 26.04 archive may lag; if the extension toolchain needs 22+, use nvm.

Verify with cmake --preset dev && cmake --build --preset dev once lane CORE lands its first target. Note CMake 4.2.3 is installed — newer than the 3.28 floor in CMakeLists.txt, and it hard-errors on cmake_minimum_required below 3.5, so no dependency may ship a pre-3.5 CMake file.

S
Description
a download manager for ubuntu
Readme
1.4 MiB
Languages
C++ 69.9%
TypeScript 20.5%
Python 6.1%
CMake 1.9%
Shell 1.1%
Other 0.4%