TODO.md Next Step is stale: the STRTA conversion it names already landed #27

New Issue

clawbot · 2026-08-09T03:59:43+02:00

clawbot commented

2026-08-09 03:59:43 +02:00

TODO.md:15-18 still reads:

# Next Step

- convert Makefile targets to scripts-to-rule-them-all `script/`
  entrypoints like the other managed repos

That work landed in 3abeacf on 2026-07-26 and closed #1. All 12 script/ entrypoints exist and every Makefile target is already a thin shim.

The root cause is a missed step in the repo's own documented workflow. TODO.md:3-9 says to move Next Step into Completed Steps as part of the same commit as the work, and 3abeacf did not do that — there is no Completed Steps entry for the scaffold at all, so the conversion is simultaneously done, unrecorded, and still listed as the next thing to do. PR #2 then added its own Completed Steps entry on top without noticing the stale Next Step beneath it.

The practical harm: TODO.md is what a fresh agent reads first to decide what to work on, so it currently points the next contributor at work that is already finished.

Separately, the backlog is no longer file-shaped. The Gitea tracker is now authoritative, with 20 issues under the 1.0.0 milestone, so Next Step should name the tracker rather than duplicate a single item that will immediately drift.

Definition of done

The scripts-to-rule-them-all conversion moves from Next Step into Completed Steps, dated 2026-07-26, naming commit 3abeacf and #1, in the same style as the surrounding entries.
# Next Step points at the 1.0.0 milestone on the tracker as the source of truth, rather than restating one issue.
# Status notes that the tracker is authoritative for the pre-1.0 backlog.
The # Workflow section is reconciled with how work actually happens now — issue first, branch, review, merge — so it stops describing a file-driven process the repo no longer follows.
The golangci entry records the actual merge (38a01bd, 2026-08-09, closes #3), not just the branch date.
Docs-only: TODO.md is the only file touched. No code, config, scripts, CI or build files.
make check green.

`TODO.md:15-18` still reads: # Next Step - convert Makefile targets to scripts-to-rule-them-all `script/` entrypoints like the other managed repos That work landed in `3abeacf` on 2026-07-26 and closed #1. All 12 `script/` entrypoints exist and every Makefile target is already a thin shim. The root cause is a missed step in the repo's own documented workflow. `TODO.md:3-9` says to move Next Step into Completed Steps as part of the same commit as the work, and `3abeacf` did not do that — there is no Completed Steps entry for the scaffold at all, so the conversion is simultaneously done, unrecorded, and still listed as the next thing to do. PR #2 then added its own Completed Steps entry on top without noticing the stale Next Step beneath it. The practical harm: `TODO.md` is what a fresh agent reads first to decide what to work on, so it currently points the next contributor at work that is already finished. Separately, the backlog is no longer file-shaped. The Gitea tracker is now authoritative, with 20 issues under the `1.0.0` milestone, so Next Step should name the tracker rather than duplicate a single item that will immediately drift. ## Definition of done 1. The scripts-to-rule-them-all conversion moves from Next Step into Completed Steps, dated 2026-07-26, naming commit `3abeacf` and #1, in the same style as the surrounding entries. 2. `# Next Step` points at the `1.0.0` milestone on the tracker as the source of truth, rather than restating one issue. 3. `# Status` notes that the tracker is authoritative for the pre-1.0 backlog. 4. The `# Workflow` section is reconciled with how work actually happens now — issue first, branch, review, merge — so it stops describing a file-driven process the repo no longer follows. 5. The golangci entry records the actual merge (`38a01bd`, 2026-08-09, closes #3), not just the branch date. 6. Docs-only: `TODO.md` is the only file touched. No code, config, scripts, CI or build files. 7. `make check` green.

clawbot added this to the 1.0.0 milestone 2026-08-09 03:59:43 +02:00

clawbot commented

2026-08-09 04:01:03 +02:00

Implementation plan

Docs-only change on branch todo-next-step-stale, branched from main at 38a01bd. TODO.md is the only file touched; no code, config, script/, CI or build files.

Concretely, in TODO.md:

# Workflow — rewrite the six file-driven bullets to describe the process actually in use: pick an issue from the 1.0.0 milestone, branch from main, implement with tests in small commits, record the result in Completed Steps in the same commit as the work, push and open a PR titled ... (closes #N), independent review, then merge. Drops the "move the top item of Future Steps into Next Step" step, which no longer describes anything real now that the tracker holds the queue.
# Status — keep pre-1.0 and add a bullet stating that the Gitea tracker is authoritative for the pre-1.0 backlog and that this file records history and process rather than the queue.
# Next Step — replace the stale STRTA bullet with a pointer to the 1.0.0 milestone (https://git.eeqj.de/sneak/sfdupes/milestone/17) as the source of truth, explicitly noting that individual issues are deliberately not restated here so they cannot drift.
# Completed Steps — insert a new entry for the scripts-to-rule-them-all conversion, dated 2026-07-26, naming commit 3abeacf and #1, in the existing - item (DATE, ...): description shape. It sorts below the golangci entry (newest first).
golangci entry — restate its date as the merge date 2026-08-09 and name merge commit 38a01bd and #3, alongside the existing branch name. The historical v2.12.1 -> v2.12.2 text stays as-is; it is an accurate record of what changed.

Left alone: # Future Steps, and the entire # Repo Policy Compliance section.

Wrapping is hand-done at the file's existing ~70 columns; make fmt in this repo is Go-only and does not touch Markdown (#19), and adding Markdown formatting tooling is out of scope here.

Verification: make check must be green, and git diff --stat main..HEAD must show TODO.md as the only changed file.

## Implementation plan Docs-only change on branch `todo-next-step-stale`, branched from `main` at `38a01bd`. `TODO.md` is the only file touched; no code, config, `script/`, CI or build files. Concretely, in `TODO.md`: 1. **`# Workflow`** — rewrite the six file-driven bullets to describe the process actually in use: pick an issue from the `1.0.0` milestone, branch from `main`, implement with tests in small commits, record the result in Completed Steps in the same commit as the work, push and open a PR titled `... (closes #N)`, independent review, then merge. Drops the "move the top item of Future Steps into Next Step" step, which no longer describes anything real now that the tracker holds the queue. 2. **`# Status`** — keep `pre-1.0` and add a bullet stating that the Gitea tracker is authoritative for the pre-1.0 backlog and that this file records history and process rather than the queue. 3. **`# Next Step`** — replace the stale STRTA bullet with a pointer to the `1.0.0` milestone (`https://git.eeqj.de/sneak/sfdupes/milestone/17`) as the source of truth, explicitly noting that individual issues are deliberately not restated here so they cannot drift. 4. **`# Completed Steps`** — insert a new entry for the scripts-to-rule-them-all conversion, dated 2026-07-26, naming commit `3abeacf` and #1, in the existing `- item (DATE, ...): description` shape. It sorts below the golangci entry (newest first). 5. **golangci entry** — restate its date as the merge date 2026-08-09 and name merge commit `38a01bd` and #3, alongside the existing branch name. The historical `v2.12.1` -> `v2.12.2` text stays as-is; it is an accurate record of what changed. Left alone: `# Future Steps`, and the entire `# Repo Policy Compliance` section. Wrapping is hand-done at the file's existing ~70 columns; `make fmt` in this repo is Go-only and does not touch Markdown (#19), and adding Markdown formatting tooling is out of scope here. Verification: `make check` must be green, and `git diff --stat main..HEAD` must show `TODO.md` as the only changed file.

clawbot referenced this issue from a commit

2026-08-09 04:03:28 +02:00

Point TODO.md at the tracker and record landed work (closes #27)

clawbot referenced a pull request that will close this issue

2026-08-09 04:03:45 +02:00

Point TODO.md at the tracker and record landed work (closes #27) #28

clawbot closed this issue

2026-08-09 04:05:04 +02:00

clawbot referenced this issue from a commit

2026-08-09 04:05:06 +02:00

Merge branch 'todo-next-step-stale': point TODO.md at the tracker (closes #27)

clawbot referenced this issue