1 Commits
Author SHA1 Message Date
clawbot 62719f4bd1 Bind the local index only after a backup writes the marker (closes #420)
check / check (push) Successful in 9m27s
A first backup that failed before writing anything (a mistyped bucket,
a refused credential) bound the local index to that destination, and
the corrected config was then refused.

A backup now checks for a different binding first, writes the
destination marker, and only then records the configured destination.
Purge, prune, snapshot remove and remote nuke still refuse a different
binding but no longer record one: only a backup puts data in the local
index, so an unbound local index holds nothing from any destination.

Model: opus-5-5
2026-11-11 01:30:14 +00:00
+1205 -3
View File
File diff suppressed because it is too large. Load diff