History

pingqiu 1578adfba5 fix: wire real v2bridge I/O into engine executors (Phase 08 P2 closure) Engine executors now have IO interfaces for real bridge I/O: - CatchUpExecutor.IO (CatchUpIO): StreamWALEntries - RebuildExecutor.IO (RebuildIO): TransferFullBase, TransferSnapshot, StreamWALEntries (for tail replay) When IO is set, executor calls real bridge I/O during execution. When IO is nil, executor uses caller-supplied progress (test mode). RecoveryPlan.CatchUpStartLSN: bound at plan time for IO bridge. v2bridge.Executor now implements both interfaces: - StreamWALEntries: real ScanFrom - TransferFullBase: validates extent accessible - TransferSnapshot: validates checkpoint accessible Chain tests wire IO: - CatchUpClosure: exec.IO = executor → real WAL scan through engine - RebuildClosure: exec.IO = executor → real transfer through engine This closes the engine → executor → v2bridge → blockvol chain. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2 days ago
..
.gocache_v2	feat: add V2 protocol simulator and enginev2 sender/session prototype	5 days ago
.private	fix: stable ServerID in assignments, fail-closed on missing identity, wire into ProcessAssignments	2 days ago
bridge/blockvol	fix: update contract.go field source docs to match P1 implementation	3 days ago
design	fix: stable ServerID in assignments, fail-closed on missing identity, wire into ProcessAssignments	2 days ago
engine/replication	fix: wire real v2bridge I/O into engine executors (Phase 08 P2 closure)	2 days ago
private	feat: add V2 protocol simulator and enginev2 sender/session prototype	5 days ago
prototype	fix: stable ServerID in assignments, fail-closed on missing identity, wire into ProcessAssignments	2 days ago
test	feat: add V2 protocol simulator and enginev2 sender/session prototype	5 days ago
README.md	feat: add V2 protocol simulator and enginev2 sender/session prototype	5 days ago

README.md

sw-block

Private WAL V2 and standalone block-service workspace.

Purpose:

keep WAL V2 design/prototype work isolated from WAL V1 production code in weed/storage/blockvol
allow private design notes and experiments to evolve without polluting V1 delivery paths
keep the future standalone sw-block product structure clean enough to split into a separate repo later if needed

Suggested layout:

design/: shared V2 design docs
prototype/: code prototypes and experiments
.private/: private notes, phase development, roadmap, and non-public working material

Repository direction:

current state: sw-block/ is an isolated workspace inside seaweedfs
likely future state: sw-block becomes a standalone sibling repo/product
design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths