Two documents on next still describe finished 1.0 work as remaining.
The README ## roadmap section is headed "Items still to do before / shortly after 1.0". Under "correctness and operability" it calls a security audit of the encryption implementation a "Pre-1.0 blocker" and says fault-injection ("error-condition") tests are needed. Both were done for 1.0: the encryption and blob-generation code was reviewed and every finding fixed (#73), and fault-injection tests cover the listed failure cases (#72; the disk-full case is being switched on by #207).
TODO.md says the next step is to define the remaining 1.0 scope, "which is the owner's", and that no future steps are queued because "the release-scoping item is now the Next Step". The scope was settled on #125 as the work already planned for 1.0, and that work is done. What is left is merging next to main and tagging, both the owner's.
Definition of done
The README roadmap lists only work planned after 1.0, and its heading says so.
The security item says plainly what was done (a review of the encryption code before 1.0, every finding fixed) and that no outside audit has been done. An outside audit stays on the roadmap as after-1.0 work, not as a blocker.
The error-condition item drops every failure case that has a test in the tree; a listed case with no test stays, stated plainly.
Every other roadmap item is checked against the tree and left as it is if still true.
TODO.md Next Step says the 1.0 work is complete on next and that merging to main and tagging are the owner's; the paragraph about three conflicting version answers goes. Future Steps points to the README roadmap. Status stays pre-1.0.
No other file changes, and no new version number appears anywhere.
Markdown formatted with make fmt; make check passes.
Model: opus-5-5
Two documents on `next` still describe finished 1.0 work as remaining.
- The README `## roadmap` section is headed "Items still to do before / shortly after 1.0". Under "correctness and operability" it calls a security audit of the encryption implementation a "Pre-1.0 blocker" and says fault-injection ("error-condition") tests are needed. Both were done for 1.0: the encryption and blob-generation code was reviewed and every finding fixed (https://git.eeqj.de/sneak/vaultik/issues/73), and fault-injection tests cover the listed failure cases (https://git.eeqj.de/sneak/vaultik/issues/72; the disk-full case is being switched on by https://git.eeqj.de/sneak/vaultik/issues/207).
- `TODO.md` says the next step is to define the remaining 1.0 scope, "which is the owner's", and that no future steps are queued because "the release-scoping item is now the Next Step". The scope was settled on https://git.eeqj.de/sneak/vaultik/issues/125 as the work already planned for 1.0, and that work is done. What is left is merging `next` to `main` and tagging, both the owner's.
## Definition of done
1. The README roadmap lists only work planned after 1.0, and its heading says so.
2. The security item says plainly what was done (a review of the encryption code before 1.0, every finding fixed) and that no outside audit has been done. An outside audit stays on the roadmap as after-1.0 work, not as a blocker.
3. The error-condition item drops every failure case that has a test in the tree; a listed case with no test stays, stated plainly.
4. Every other roadmap item is checked against the tree and left as it is if still true.
5. `TODO.md` Next Step says the 1.0 work is complete on `next` and that merging to `main` and tagging are the owner's; the paragraph about three conflicting version answers goes. Future Steps points to the README roadmap. Status stays `pre-1.0`.
6. No other file changes, and no new version number appears anywhere.
7. Markdown formatted with `make fmt`; `make check` passes.
Model: opus-5-5
clawbot
added this to the 1.0.0 milestone 2026-10-01 19:54:31 +02:00
clawbot
self-assigned this 2026-10-01 19:54:31 +02:00
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.
Two documents on
nextstill describe finished 1.0 work as remaining.## roadmapsection is headed "Items still to do before / shortly after 1.0". Under "correctness and operability" it calls a security audit of the encryption implementation a "Pre-1.0 blocker" and says fault-injection ("error-condition") tests are needed. Both were done for 1.0: the encryption and blob-generation code was reviewed and every finding fixed (#73), and fault-injection tests cover the listed failure cases (#72; the disk-full case is being switched on by #207).TODO.mdsays the next step is to define the remaining 1.0 scope, "which is the owner's", and that no future steps are queued because "the release-scoping item is now the Next Step". The scope was settled on #125 as the work already planned for 1.0, and that work is done. What is left is mergingnexttomainand tagging, both the owner's.Definition of done
TODO.mdNext Step says the 1.0 work is complete onnextand that merging tomainand tagging are the owner's; the paragraph about three conflicting version answers goes. Future Steps points to the README roadmap. Status stayspre-1.0.make fmt;make checkpasses.Model: opus-5-5