Review toward 1.0: identify and file all next steps #119
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sneak/vaultik#119
Reference in New Issue
Block a user
Owner directive (sneak, 2026-09-21, chat, verbatim): "please instruct each individual repo manager to review mfer, vaultik, autistmask, webhooker, pixa, dnswatcher, sfdupes, imaptagger, and keyfunc to identify any next steps toward a 1.0 and make sure issues are filed for them, surface any questions or design review for me, and make sure implementors are working in the direction of making them all usable and ready."
Definition of done, for this repo:
model: claude-fable-5
Review toward 1.0
State:
mainat696ed9a,nextone commit ahead (d257f8f, lint in a container, issue #113). The milestone PR pull request #114 isneeds-reworkafter its second review: the gate holds, the guard test's shell scanner does not. Release mechanism (script/release, goreleaser, tag workflow) exists and was exercised;TODO.mdnames the scope decision as the only remaining release step. No tag exists yet.What the product does well: the backup, restore, verify, prune and list paths are covered by real integration tests; stdout/stderr and
--jsoncontracts are now clean; the gate cannot report an unearned green.Blockers found in this review that had no issue, now filed:
snapshot createshells out to asqlite3binary to VACUUM the metadata database, after every blob has been uploaded. Ago installuser without that CLI cannot complete a backup. CI is green only becausescript/bootstrapinstalls the binary; on a host without it,make checkonnextfails two tests withexec: "sqlite3": executable file not found. Highest priority.parseDurationimplementations with different grammars, and the README's--older-than 6mexample means six minutes, not six months, on a command that deletes snapshots.main; nothing runs onnextor on the unit PRs that target it.Already tracked in the
1.0.0milestone and still valid: issue #66, issue #67, issue #68, issue #70, issue #72, issue #73, issue #74, issue #75, issue #87, issue #96, issue #105, issue #112. Each has a definition of done I checked against the tree today; none is stale.For the owner: issue #125 (release scope and the post-tag index-disposability question), issue #94 (daemon mode, recommendation: after 1.0), issue #76 (package names, recommendation: keep), issue #90 and issue #101 (org-wide config and policy, not vaultik work). Decisions the record already settles I am taking myself, on issue #112 and issue #105.
Roadmap items in the README that are not 1.0 work and get no issue: parallel restore downloads,
--bwlimit, restore resume, man pages,snapshot diff, the--cronnotification hook.Dispatch order: #120, #121, #122 and the small units (#87, #96, #70, #67, #66, #75) first; then #68, #74, #123, #112, #105, #124, #72; #73 as an audit on the strongest model.
Model: fable-5-1
Manager instruction (top-level sdlc manager, owner directive 2026-09-21): register a recurring session cron now (off-minute, roughly every 15-20 minutes) that wakes you to re-check open issues and PRs, check your spawned workers and reviewers, replace anything wedged, merge passed reviews, and dispatch the next unit; session crons expire after 7 days, re-register before then. Branch workflow addition: if
nextmust ever be frozen, keep spawning workers whose PRs targetnext2branched offnext;next2becomes the newnextwhennextmerges tomain. Both rules are now in the repo-manager agent definition.model: claude-fable-5