Fixes two false doc comments from #403. Comments only.
ExportSnapshotMetadata in internal/snapshot/snapshot.go described an SQL dump uploaded under snapshots/. It now lists the steps the function performs and the two keys it writes: metadata/<remote-key>/db.zst.age and metadata/<remote-key>/manifest.json.zst. Its first line says "backup destination store" instead of "S3".
EnsureStorageBinding in internal/vaultik/storage_bind.go now names vaultik database delete.
Left alone, outside the issue: the package comment at the top of internal/snapshot/snapshot.go still says "Upload to S3 as: metadata/{snapshot-id}/db.zst.age", and the key is the remote key, not the snapshot ID.
TODO.md is unchanged: this work is not its Next Step.
Model: opus-5-5
Fixes two false doc comments from https://git.eeqj.de/sneak/vaultik/issues/403. Comments only.
- `ExportSnapshotMetadata` in `internal/snapshot/snapshot.go` described an SQL dump uploaded under `snapshots/`. It now lists the steps the function performs and the two keys it writes: `metadata/<remote-key>/db.zst.age` and `metadata/<remote-key>/manifest.json.zst`. Its first line says "backup destination store" instead of "S3".
- `EnsureStorageBinding` in `internal/vaultik/storage_bind.go` now names `vaultik database delete`.
Left alone, outside the issue: the package comment at the top of `internal/snapshot/snapshot.go` still says "Upload to S3 as: metadata/{snapshot-id}/db.zst.age", and the key is the remote key, not the snapshot ID.
`TODO.md` is unchanged: this work is not its Next Step.
Model: opus-5-5
clawbot
self-assigned this 2026-11-09 07:19:05 +01:00
ExportSnapshotMetadata now lists the steps it performs and the metadata/ keys it writes. EnsureStorageBinding names `vaultik database delete`.
Comments only.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes two false doc comments from #403. Comments only.
ExportSnapshotMetadataininternal/snapshot/snapshot.godescribed an SQL dump uploaded undersnapshots/. It now lists the steps the function performs and the two keys it writes:metadata/<remote-key>/db.zst.ageandmetadata/<remote-key>/manifest.json.zst. Its first line says "backup destination store" instead of "S3".EnsureStorageBindingininternal/vaultik/storage_bind.gonow namesvaultik database delete.Left alone, outside the issue: the package comment at the top of
internal/snapshot/snapshot.gostill says "Upload to S3 as: metadata/{snapshot-id}/db.zst.age", and the key is the remote key, not the snapshot ID.TODO.mdis unchanged: this work is not its Next Step.Model: opus-5-5
PASS: both doc comments now state what the code on
nextdoes, and the change touches only comments.Model: opus-5-5