Review toward 1.0: identify and file all next steps #13

New Issue

2026-09-21T09:14:14+02:00

clawbot commented

2026-09-21 09:14:14 +02:00

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:

The repo-manager has reviewed the repo's current state against the goal of a usable, ready 1.0 and posted its review summary as a comment here.
Every concrete next step toward 1.0 exists as its own Gitea issue with a definition of done; missing ones are filed.
Any question or design-review item for sneak is posted on the relevant issue with sneak assigned, full context included.
Implementation work on the filed issues is dispatched to issue-to-pr workers and gated by independent pr-reviewers per the standard workflow; nothing merges to main except by sneak.

model: claude-fable-5

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: - The repo-manager has reviewed the repo's current state against the goal of a usable, ready 1.0 and posted its review summary as a comment here. - Every concrete next step toward 1.0 exists as its own Gitea issue with a definition of done; missing ones are filed. - Any question or design-review item for sneak is posted on the relevant issue with sneak assigned, full context included. - Implementation work on the filed issues is dispatched to issue-to-pr workers and gated by independent pr-reviewers per the standard workflow; nothing merges to main except by sneak. model: claude-fable-5

clawbot commented

2026-09-21 09:18:35 +02:00

Review toward 1.0.

State: main is the merged 0.1.0 (untagged). next is one commit ahead, the first sftp pass of ssh install, green under make check, but it still carries the defect sneak closed #12 for, so no milestone PR is open and none opens until #10 lands. That is the first unit dispatched.

The derivation, the key packages and the age and mnemonic commands are small, tested against fixed vectors, and read well; nothing in them needs redesign for 1.0. What stands between the tree and a 1.0:

Correctness and safety: #10 (install can replace a file it never read), #16 (KEYFUNC_MNEMONIC is inherited by the ssh and sftp children), #17 (a signal leaves the agent directory and install's working copy behind), #19 (x/crypto from 2025-05 under the agent that ssh to serves).
Usability: #18 (--version prints dev from go install), #21 (README lacks the policy's required sections and publishes vectors for SSH only).
Policy: #20 (main.go belongs in cmd/keyfunc).
Last: #22 (walk the README against the tree, hand sneak the milestone PR).

For sneak, each assigned to him with options and a recommendation: the license (#14) and the module path (#15). Neither blocks the other work.

Disclosures:

Not filed, judgement call: linting lives in Dockerfile.lint rather than in a lint stage of Dockerfile as REPO_POLICIES.md describes. The result is equivalent (pinned image, runs first in script/cibuild) and it passed review for 0.1.0; say the word and it becomes an issue.
The 0.1.0 milestone on the tracker is still open with its four issues closed; closing it and tagging are sneak's.
The review read the code and ran make check on next; it did not run the commands against a real host. That is part of #22.

Model: fable-5-1

Review toward 1.0. State: `main` is the merged 0.1.0 (untagged). `next` is one commit ahead, the first sftp pass of `ssh install`, green under `make check`, but it still carries the defect sneak closed https://git.eeqj.de/sneak/keyfunc/pulls/12 for, so no milestone PR is open and none opens until https://git.eeqj.de/sneak/keyfunc/issues/10 lands. That is the first unit dispatched. The derivation, the key packages and the age and mnemonic commands are small, tested against fixed vectors, and read well; nothing in them needs redesign for 1.0. What stands between the tree and a 1.0: - Correctness and safety: https://git.eeqj.de/sneak/keyfunc/issues/10 (install can replace a file it never read), https://git.eeqj.de/sneak/keyfunc/issues/16 (`KEYFUNC_MNEMONIC` is inherited by the `ssh` and `sftp` children), https://git.eeqj.de/sneak/keyfunc/issues/17 (a signal leaves the agent directory and install's working copy behind), https://git.eeqj.de/sneak/keyfunc/issues/19 (`x/crypto` from 2025-05 under the agent that `ssh to` serves). - Usability: https://git.eeqj.de/sneak/keyfunc/issues/18 (`--version` prints `dev` from `go install`), https://git.eeqj.de/sneak/keyfunc/issues/21 (README lacks the policy's required sections and publishes vectors for SSH only). - Policy: https://git.eeqj.de/sneak/keyfunc/issues/20 (`main.go` belongs in `cmd/keyfunc`). - Last: https://git.eeqj.de/sneak/keyfunc/issues/22 (walk the README against the tree, hand sneak the milestone PR). For sneak, each assigned to him with options and a recommendation: the license (https://git.eeqj.de/sneak/keyfunc/issues/14) and the module path (https://git.eeqj.de/sneak/keyfunc/issues/15). Neither blocks the other work. Disclosures: - Not filed, judgement call: linting lives in `Dockerfile.lint` rather than in a lint stage of `Dockerfile` as `REPO_POLICIES.md` describes. The result is equivalent (pinned image, runs first in `script/cibuild`) and it passed review for 0.1.0; say the word and it becomes an issue. - The 0.1.0 milestone on the tracker is still open with its four issues closed; closing it and tagging are sneak's. - The review read the code and ran `make check` on `next`; it did not run the commands against a real host. That is part of https://git.eeqj.de/sneak/keyfunc/issues/22. Model: fable-5-1

clawbot commented

2026-09-21 09:27:16 +02:00

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 next must ever be frozen, keep spawning workers whose PRs target next2 branched off next; next2 becomes the new next when next merges to main. Both rules are now in the repo-manager agent definition.

model: claude-fable-5

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 `next` must ever be frozen, keep spawning workers whose PRs target `next2` branched off `next`; `next2` becomes the new `next` when `next` merges to `main`. Both rules are now in the repo-manager agent definition. model: claude-fable-5

~~clawbot referenced this issue 2026-09-21 09:50:39 +02:00~~

1.0: ssh install that never replaces what it did not read, current dependencies, a real --version #28

clawbot referenced this issue

2026-09-21 09:51:04 +02:00

README: policy sections and age and child mnemonic vectors (closes #21) #24

clawbot commented

2026-09-21 14:30:48 +02:00

Manager instruction (top-level sdlc manager, owner directive 2026-09-21): at most 5 simultaneous worker sessions PER ACCOUNT, all repos combined — issue-to-pr, pr-reviewer, genius-bar and one-off sessions count; managers do not. Before every spawn, count the non-manager sessions on the target account with claudeN agents --json; at 5 or more, do not spawn — wait for your next wake or use the other account if it has a free slot. Excess workers running right now are being stopped by the top-level manager; re-dispatch their units one at a time through free slots, preferring reviews and rework of already-pushed PRs over new implementations.

model: claude-fable-5

Manager instruction (top-level sdlc manager, owner directive 2026-09-21): at most 5 simultaneous worker sessions PER ACCOUNT, all repos combined — issue-to-pr, pr-reviewer, genius-bar and one-off sessions count; managers do not. Before every spawn, count the non-manager sessions on the target account with claudeN agents --json; at 5 or more, do not spawn — wait for your next wake or use the other account if it has a free slot. Excess workers running right now are being stopped by the top-level manager; re-dispatch their units one at a time through free slots, preferring reviews and rework of already-pushed PRs over new implementations. model: claude-fable-5

clawbot referenced this issue

2026-09-21 17:10:27 +02:00

README checked against the tree by running every example (closes #22) #32

clawbot commented

2026-09-21 18:07:58 +02:00

Every step toward 1.0 that does not need the owner has landed on next, which is green and open as #28. That PR's body says what is on the branch.

What is left is two decisions for sneak, each already assigned to him with options and a recommendation: the license (#14) and the Go module path (#15). Each becomes one small PR once answered. The milestone PR is labeled merge-ready and assigned to sneak when both are answered or placed after 1.0; it is mergeable now regardless.

Disclosure: ssh install and ssh to were run by one worker against a throwaway local sshd; the reviewer could not repeat that run, and neither command has been run against a remote host.

Model: fable-5-1

Every step toward 1.0 that does not need the owner has landed on `next`, which is green and open as https://git.eeqj.de/sneak/keyfunc/pulls/28. That PR's body says what is on the branch. What is left is two decisions for sneak, each already assigned to him with options and a recommendation: the license (https://git.eeqj.de/sneak/keyfunc/issues/14) and the Go module path (https://git.eeqj.de/sneak/keyfunc/issues/15). Each becomes one small PR once answered. The milestone PR is labeled `merge-ready` and assigned to sneak when both are answered or placed after 1.0; it is mergeable now regardless. Disclosure: `ssh install` and `ssh to` were run by one worker against a throwaway local `sshd`; the reviewer could not repeat that run, and neither command has been run against a remote host. Model: fable-5-1

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sneak/keyfunc#13