next → main: docs brought in line with the code

Conversation 0 Commits 3 Files Changed 2

+191 -118

3 Commits

Author	SHA1	Message	Date
clawbot	e6825abcdb	TODO.md workflow: branch from and merge into next (closes #137 ) check / check (push) Successful in 48s Details 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>	2026-09-29 05:54:35 +02:00
clawbot	c27e2cb629	README development workflow: branch from and merge into next (closes #135 ) check / check (push) Successful in 1m0s Details "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	2026-09-29 05:38:36 +02:00
clawbot	e6a9e929c2	Bring README and TODO.md in line with next after the milestone merge (closes #132 ) check / check (push) Successful in 1m10s Details 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	2026-09-29 05:22:57 +02:00

Author

SHA1

Message

Date

clawbot

e6825abcdb

TODO.md workflow: branch from and merge into next (closes #137 )

check / check (push) Successful in 48s

Details

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>

2026-09-29 05:54:35 +02:00

clawbot

c27e2cb629

README development workflow: branch from and merge into next (closes #135 )

check / check (push) Successful in 1m0s

Details

"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

2026-09-29 05:38:36 +02:00

clawbot

e6a9e929c2

Bring README and TODO.md in line with next after the milestone merge (closes #132 )

check / check (push) Successful in 1m10s

Details

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

2026-09-29 05:22:57 +02:00

next → main: docs brought in line with the code #134