Standing next → main pull request, opened after #31 was merged.
What is on next beyond main
Documentation only:
README.md and TODO.md were read end to end against the code, and every sentence the code contradicted was corrected (#133). TODO.md's next step now says no implementation work is open.
The README's development workflow and the "Workflow" list in TODO.md now say work branches from next, every pull request targets next, reviewed units are squash-merged into next, and only you merge next into main (#136, #138).
What changes runtime behavior
Nothing. No code, test, script or build file changed.
Merging updates main only. It creates no tag and no release.
Model: opus-5-5
Standing `next` → `main` pull request, opened after https://git.eeqj.de/sneak/quak/pulls/31 was merged.
## What is on `next` beyond `main`
Documentation only:
- `README.md` and `TODO.md` were read end to end against the code, and every sentence the code contradicted was corrected (https://git.eeqj.de/sneak/quak/pulls/133). `TODO.md`'s next step now says no implementation work is open.
- The README's development workflow and the "Workflow" list in `TODO.md` now say work branches from `next`, every pull request targets `next`, reviewed units are squash-merged into `next`, and only you merge `next` into `main` (https://git.eeqj.de/sneak/quak/pulls/136, https://git.eeqj.de/sneak/quak/pulls/138).
## What changes runtime behavior
Nothing. No code, test, script or build file changed.
## What waits on you
- The cache design review, https://git.eeqj.de/sneak/quak/issues/36.
## Merging
Merging updates `main` only. It creates no tag and no release.
Model: opus-5-5
README.md and TODO.md were read end to end against the code after the milestone merge, and every sentence the code contradicted was corrected. The corrections cover the login and key-derivation steps (the TOTP step, email OTP, the SRP library), retries and download staging, which CLI commands take which options, which of each file's metadata the backup keeps, how default and fresh reads behave, the cache options, and what the tests cover. TODO.md's next step now says no implementation work is open and the cache design waits on sneak.
Docs only.
Left as written: the development workflow's `main` base, a process question.
Merged under the docs-only rule after four reviews; the fix for the fourth review's one finding was not re-reviewed.
Model: opus-5-5
"Development workflow" and "For LLMs" said work branches off main and merges into main. They now say work branches from next, every pull request targets next, the repository manager squash-merges reviewed pull requests into next once make check is green, and only sneak merges next into main. The rest of both sections is unchanged.
Docs only; merged under the docs-only rule without an adversarial review.
Model: opus-5-5
The "Workflow" list said to branch from main and to merge to main or open a pull request. It now says to branch from next, open a pull request that targets next, that the repository manager squash-merges a reviewed pull request into next, and that only sneak merges next into main, as the README does. The other items are unchanged. No other text in the repo contradicted the policy.
Docs only; merged under the docs-only rule without an adversarial review.
Model: opus-5-5
Co-authored-by: clawbot <sneak+clawbot@sneak.cloud>
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.
Standing
next→mainpull request, opened after #31 was merged.What is on
nextbeyondmainDocumentation only:
README.mdandTODO.mdwere read end to end against the code, and every sentence the code contradicted was corrected (#133).TODO.md's next step now says no implementation work is open.TODO.mdnow say work branches fromnext, every pull request targetsnext, reviewed units are squash-merged intonext, and only you mergenextintomain(#136, #138).What changes runtime behavior
Nothing. No code, test, script or build file changed.
What waits on you
Merging
Merging updates
mainonly. It creates no tag and no release.Model: opus-5-5
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.