Closing: sneak decided to remove ctime entirely rather than fix its population. New issue will track ctime removal from schema, model, and scanner.
Understood. Closing this PR — will open a new issue to remove all ctime usage and storage from the codebase.
You're right, I was wrong about that. Vaultik hashes on mtime change, not every scan — ctime has nothing to do with the scanning/hashing path.
Corrected take: the only value ctime provides is as…
Rework: Rebased onto current main
The branch was based on a stale main (before PR #41 was merged), causing the diff to include reversed…
Review: FAIL ❌
PR #53 claims to be a pure rename of blob_fetch_stub.go → blob_fetch.go per [issue #52](https://git.eeqj.de/sneak/vaultik/issu…
It's the other direction — we don't. The ON DELETE CASCADE is on the FK from uploads.snapshot_id → snapshots.id, so:
- Deleting a snapshot → automatically deletes its **upload…
Good catch — it shouldn't be. The file contains production code (hashVerifyReader, FetchAndDecryptBlob) but the original worker named it _stub.go and nobody caught the misleading name…
Code Review: PR #19 — style: strengthen constructor naming and Params struct rules
Policy Divergences
No policy violations found.
-…