3 Commits

Include renames

Author	SHA1	Message	Date
samiandClaude Opus 5	facd851824	docs: define the cross-platform porting strategy (ADR 0020, macOS first) ... The tree is Ubuntu-first, but the Linux-specific surface is about ten files and already sits at the bottom of the I/O and RPC stacks. Rather than fork the repo or scatter ifdefs, platform differences go behind narrow seams with one backend directory per OS, selected centrally in cmake/platform.cmake. Linux stays the reference implementation and its behaviour does not change: the owning lanes (CORE, DAEMON) move today's Linux code behind the seams on Ubuntu first, with the suite still green, before any macOS code exists. A new PORT lane owns only the per-OS backends, so macOS work never writes shared logic and CLAUDE.md's lane rule stays intact. Adds ADR 0020 (the decision and phases), docs/08-porting.md (seam list, API mapping for macOS and Windows, dependency table, verification gates) and docs/agents/AGENT-PORT.md (the lane brief), plus the PORT row in the ownership table. Co-Authored-By: Claude Opus 5 <[email protected]>	2026-09-15 17:36:27 +04:00
samiandClaude Sonnet 5	1aed222ae2	docs: ADR-number convention in CLAUDE.md §7 — second merger renumbers ... Six lanes pick ADR numbers with no allocator. This lane dodged one collision by taking 0012 while DAEMON drafted 0011, and just hit a real one — two 0014s in the same integration round. Codify what already happened in practice: take the next free number in main's docs/adr/, and on collision whoever merges second renumbers and fixes cross-refs rather than round-tripping. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_012fgjnqFCS5h5L7gZTZo3rV	2026-09-10 15:31:01 +04:00
samiandClaude Opus 5	8bb683b09d	scaffold: project structure, wire contract, roadmap and agent briefs ... Lays out Velox Download Manager (IDM-class download manager for Ubuntu 26.04) as a monorepo ready for parallel lane development. No implementation code by design. - docs/: architecture, roadmap M0-M7, IDM-parity GUI spec, engine design, Firefox extension spec, risks/spikes, packaging - contracts/: wire-contract skeleton (JSON Schema + fixture templates) — the single synchronization point between lanes - docs/agents/: one brief per lane (PROTO, CORE, DAEMON, GUI, EXT, PKG/QA) with owned directories, build order and definition of done - CLAUDE.md: rules of engagement — lane ownership, layering, non-negotiables - CMake scaffolding with dev/tsan/release/ci presets Two environment findings shape the design: Firefox here is the Mozilla snap (native-messaging risk, so the extension carries a loopback-WebSocket fallback), and Wayland forbids passive clipboard monitoring (so clipboard capture is explicit-action-first). Co-Authored-By: Claude Opus 5 <[email protected]>	2026-09-09 18:21:11 +04:00