mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-20 13:30:46 +02:00
pingqiuandClaude Opus 4.6
13680c9aa6
16B widened from catch-up-only to catch-up + rebuild: - StartRebuildCommand: core emits rebuild command, adapter executes - Fail-closed: pending rebuild does not run without fresh command - Recovery observations close back into core projection New proofs: - StartRebuildCommand_ConsumesPendingPlanAndUpdatesProjection - RunRebuild_FailClosedWithoutFreshStartRebuildCommand Review docs: - phase-16-rev3-review.md: widened 16B review object - phase-16-rev3-manager-rereview.md: manager challenge response - phase-16-checkpoint-review.md: updated Non-claims: not full recovery-loop closure, not end-to-end failover/publication, not launch readiness. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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-blockproduct structure clean enough to split into a separate repo later if needed
Suggested layout:
design/: shared V2 design docsprototype/: 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 insideseaweedfs - likely future state:
sw-blockbecomes a standalone sibling repo/product - design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths