sneak/sfdupes
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Vendored REPO_POLICIES.md is stale (368 lines vs the canonical 408) #20

New Issue
Closed
opened 2026-08-09 03:46:53 +02:00 by clawbot · 1 comment
clawbot commented 2026-08-09 03:46:53 +02:00
Collaborator
Copy Link

REPO_POLICIES.md in this repo is a vendored copy of the org policy document, and it has drifted. It is 368 lines against the canonical 408 at ~/dev/prompts/prompts/REPO_POLICIES.md, while still declaring last_modified: 2026-07-06 — so nothing about the file signals that it is out of date.

Missing sections, all of which this repo is actually governed by:

  • The entire scripts-to-rule-them-all section, including the required list of 12 script/ entrypoints.
  • The bootstrap, setup and hooks Makefile targets in the required-target list.
  • The paragraph on script/precommit and how the pre-commit hook is wired.
  • The README Entrypoints section requirement (tracked separately as #21).

This matters beyond tidiness: agents working in this repo read the vendored copy, so a stale copy means work gets done against superseded rules. That is very likely how #19 (Markdown formatting dropped from script/fmt) and the missing Entrypoints section happened in the first place.

Definition of done

  1. REPO_POLICIES.md is replaced with a byte-identical copy of the canonical file. Verify with diff and record the sha256 in the PR description.
  2. No hand-editing, no partial merge, no local additions — it is a vendored copy.
  3. Docs-only change.
  4. make check green.
`REPO_POLICIES.md` in this repo is a vendored copy of the org policy document, and it has drifted. It is 368 lines against the canonical 408 at `~/dev/prompts/prompts/REPO_POLICIES.md`, while still declaring `last_modified: 2026-07-06` — so nothing about the file signals that it is out of date. Missing sections, all of which this repo is actually governed by: - The entire scripts-to-rule-them-all section, including the required list of 12 `script/` entrypoints. - The `bootstrap`, `setup` and `hooks` Makefile targets in the required-target list. - The paragraph on `script/precommit` and how the pre-commit hook is wired. - The README **Entrypoints** section requirement (tracked separately as #21). This matters beyond tidiness: agents working in this repo read the vendored copy, so a stale copy means work gets done against superseded rules. That is very likely how #19 (Markdown formatting dropped from `script/fmt`) and the missing Entrypoints section happened in the first place. ## Definition of done 1. `REPO_POLICIES.md` is replaced with a byte-identical copy of the canonical file. Verify with `diff` and record the sha256 in the PR description. 2. No hand-editing, no partial merge, no local additions — it is a vendored copy. 3. Docs-only change. 4. `make check` green.
clawbot added this to the 1.0.0 milestone 2026-08-09 03:46:53 +02:00
clawbot commented 2026-08-09 11:56:14 +02:00
Author
Collaborator
Copy Link

Implementation plan

Mechanical re-vendor, single file, no hand-editing.

  1. Branch refresh-repo-policies from current main (a5fa600), in a throwaway worktree.
  2. Record before-state: vendored REPO_POLICIES.md is 368 lines, sha256 b632c46d4ccd7fe4bd11f714fec2d3b2098d8f697d9d2022795a15a97749831a. Canonical ~/dev/prompts/prompts/REPO_POLICIES.md is confirmed still 408 lines, sha256 117dde7f148ed3cd693b333312f6345a0a0ee84fadbbe5cca559ca6fed4a1775.
  3. cp the canonical file over the vendored one wholesale. No merge, no local adaptation, no reformatting — including leaving the policy document's own prose untouched.
  4. Verify: diff between the two files is empty, the new sha256 equals the canonical one, and git status shows REPO_POLICIES.md as the only changed path.
  5. make check green (make/script/ entrypoints only). Deliberately skipping make fmt rewriting this file: it is a vendored copy and must match upstream byte-for-byte, so if the repo formatter disagrees with upstream that is an upstream matter, not a local edit. Will confirm make check does not itself demand a change to it.
  6. Single commit titled with (closes #20), push, open PR against main, label needs-review, assign clawbot.

Scope notes:

  • No TODO.md update in this commit. The repo convention is to update it alongside the work, but this issue's definition of done explicitly restricts the change to REPO_POLICIES.md alone; the departure will be called out in the PR body.
  • Requirements newly visible in the restored text that this repo does not yet meet are out of scope here and will be reported for separate filing, not fixed drive-by.
## Implementation plan Mechanical re-vendor, single file, no hand-editing. 1. Branch `refresh-repo-policies` from current `main` (`a5fa600`), in a throwaway worktree. 2. Record before-state: vendored `REPO_POLICIES.md` is 368 lines, sha256 `b632c46d4ccd7fe4bd11f714fec2d3b2098d8f697d9d2022795a15a97749831a`. Canonical `~/dev/prompts/prompts/REPO_POLICIES.md` is confirmed still 408 lines, sha256 `117dde7f148ed3cd693b333312f6345a0a0ee84fadbbe5cca559ca6fed4a1775`. 3. `cp` the canonical file over the vendored one wholesale. No merge, no local adaptation, no reformatting — including leaving the policy document's own prose untouched. 4. Verify: `diff` between the two files is empty, the new sha256 equals the canonical one, and `git status` shows `REPO_POLICIES.md` as the only changed path. 5. `make check` green (`make`/`script/` entrypoints only). Deliberately skipping `make fmt` rewriting this file: it is a vendored copy and must match upstream byte-for-byte, so if the repo formatter disagrees with upstream that is an upstream matter, not a local edit. Will confirm `make check` does not itself demand a change to it. 6. Single commit titled with ` (closes #20)`, push, open PR against `main`, label `needs-review`, assign `clawbot`. Scope notes: - No `TODO.md` update in this commit. The repo convention is to update it alongside the work, but this issue's definition of done explicitly restricts the change to `REPO_POLICIES.md` alone; the departure will be called out in the PR body. - Requirements newly visible in the restored text that this repo does not yet meet are out of scope here and will be reported for separate filing, not fixed drive-by.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
merge-ready
Review passed; ready to merge
 needs-checks
CI checks failing or not yet green
 needs-rebase
Branch conflicts with main; rebase required
 needs-review
PR awaiting independent adversarial review
 needs-rework
Review found blocking problems; author must rework
No Label
Milestone
No items
No Milestone 1.0.0
Projects
Clear projects
No project
Assignees
Clear assignees
clawbot sneak
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/sfdupes#20
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?