README.md now has the section set REPO_POLICIES.md mandates: a Description
first line, then ## Getting Started, ## Entrypoints, ## Rationale, ## Design, ## TODO, ## License, ## Author, with ## Author last. The
non-standard About / Contributing / Technical Details headings are gone.
Nothing was silently lost. The bullet list of what the site publishes moved
under the Description; the contribute contact (sneak@sneak.berlin for repo
access) and the local-preview instructions moved into Getting Started.
The Description is deliberately incomplete
The policy wants the first line to name the license. It cannot yet — that is #10, blocked on your choice of
license. So the sentence ships without the license clause, the ## License
section body is byte-for-byte unchanged ("Content is provided as-is for
community use."), and no LICENSE file is added. #10 completes both in one
pass.
Stale content found and fixed
Two things beyond the restructure were wrong:
"deployed automatically via GitHub Actions" — it is Gitea Actions,
publishing to Cloudflare Pages. Corrected in Design.
The script/fmt Entrypoints bullet still said "the repo's own top-level
markdown docs", which #12 made
false when it widened the scope to '**/*.md' and '**/*.css'. Corrected.
The rest of Entrypoints was verified line by line against the scripts and was
accurate: the script/check order really is test, then lint, then fmt-check,
and the CHECK_EPOCH paragraph correctly describes a bare docker build .
failing closed.
Getting Started was rewritten against the Makefile, not carried over
The old prose had drifted from the repo. Verified against the current Makefile, whose only targets are bootstrap setup test lint fmt fmt-check check docker hooks serve:
There is no make build target, so the old "Build: hugo" instruction
is now make test (which is hugo --minify, writing to public/).
"Local Development: hugo server" is now make setup then make serve. make setup is what makes a fresh clone buildable at all, since it installs
the pinned Hugo; the old README told you to run hugo without ever saying
where it came from.
http://localhost:1313 is kept.
## TODO links [TODO.md](TODO.md) rather than duplicating the list.
Design's claims were checked against the tree rather than assumed: the theme
vendored at themes/loravega/ with no submodule, baseof.html inlining static/css/style.css via readFile ... | safeCSS, hugo --minify to public/, and .gitea/workflows/deploy.yml.
Commit ordering
One commit, and it passes make check standing alone — so unlike #31 this needs no merge-commit-only
handling. Prettier's reflow of the new prose is part of that same commit, not a
follow-up, because the content is new in this branch and there is no
before-state to keep green.
Verification
make fmt run; make fmt-check clean.
make check green and WARN-free.
script/cibuild green with the make check layer genuinely executed,
not CACHED — the build log shows both hugo builds and the prettier check
running in the layer (DONE 3.7s), with the script/bootstrap layer above
it still cached as intended.
Scope
Only README.md and TODO.md are touched. script/bootstrap and .gitea/workflows/deploy.yml are untouched, so the deploy path is unaffected. TODO.md drops the completed "Rework README.md into the standard sections"
Future Steps entry and gains a Completed Steps entry, in the same commit. The
Next Step stays #10, which is still blocked on you.
Closes https://git.eeqj.de/sneak/lora.vegas/issues/11.
`README.md` now has the section set `REPO_POLICIES.md` mandates: a Description
first line, then `## Getting Started`, `## Entrypoints`, `## Rationale`,
`## Design`, `## TODO`, `## License`, `## Author`, with `## Author` last. The
non-standard About / Contributing / Technical Details headings are gone.
**Nothing was silently lost.** The bullet list of what the site publishes moved
under the Description; the contribute contact (sneak@sneak.berlin for repo
access) and the local-preview instructions moved into Getting Started.
## The Description is deliberately incomplete
The policy wants the first line to name the license. It cannot yet — that is
https://git.eeqj.de/sneak/lora.vegas/issues/10, blocked on your choice of
license. So the sentence ships without the license clause, the `## License`
section body is **byte-for-byte unchanged** ("Content is provided as-is for
community use."), and no `LICENSE` file is added. #10 completes both in one
pass.
## Stale content found and fixed
Two things beyond the restructure were wrong:
- **"deployed automatically via GitHub Actions"** — it is Gitea Actions,
publishing to Cloudflare Pages. Corrected in Design.
- **The `script/fmt` Entrypoints bullet** still said "the repo's own top-level
markdown docs", which https://git.eeqj.de/sneak/lora.vegas/issues/12 made
false when it widened the scope to `'**/*.md'` and `'**/*.css'`. Corrected.
The rest of Entrypoints was verified line by line against the scripts and was
accurate: the `script/check` order really is test, then lint, then fmt-check,
and the `CHECK_EPOCH` paragraph correctly describes a bare `docker build .`
failing closed.
## Getting Started was rewritten against the Makefile, not carried over
The old prose had drifted from the repo. Verified against the current
`Makefile`, whose only targets are `bootstrap setup test lint fmt fmt-check
check docker hooks serve`:
- There is **no `make build` target**, so the old "Build: `hugo`" instruction
is now `make test` (which is `hugo --minify`, writing to `public/`).
- "Local Development: `hugo server`" is now `make setup` then `make serve`.
`make setup` is what makes a fresh clone buildable at all, since it installs
the pinned Hugo; the old README told you to run `hugo` without ever saying
where it came from.
- `http://localhost:1313` is kept.
`## TODO` links `[TODO.md](TODO.md)` rather than duplicating the list.
Design's claims were checked against the tree rather than assumed: the theme
vendored at `themes/loravega/` with no submodule, `baseof.html` inlining
`static/css/style.css` via `readFile ... | safeCSS`, `hugo --minify` to
`public/`, and `.gitea/workflows/deploy.yml`.
## Commit ordering
**One commit, and it passes `make check` standing alone** — so unlike
https://git.eeqj.de/sneak/lora.vegas/pulls/31 this needs no merge-commit-only
handling. Prettier's reflow of the new prose is part of that same commit, not a
follow-up, because the content is new in this branch and there is no
before-state to keep green.
## Verification
- `make fmt` run; `make fmt-check` clean.
- `make check` green and `WARN`-free.
- `script/cibuild` green with the `make check` layer **genuinely executed**,
not `CACHED` — the build log shows both hugo builds and the prettier check
running in the layer (`DONE 3.7s`), with the `script/bootstrap` layer above
it still cached as intended.
## Scope
Only `README.md` and `TODO.md` are touched. `script/bootstrap` and
`.gitea/workflows/deploy.yml` are untouched, so the deploy path is unaffected.
`TODO.md` drops the completed "Rework README.md into the standard sections"
Future Steps entry and gains a Completed Steps entry, in the same commit. The
Next Step stays #10, which is still blocked on you.
REPO_POLICIES.md mandates a fixed set of README sections; this README
predated the standard being applied here and had About / Contributing /
Technical Details / Entrypoints / License instead. It is now a
Description first line followed by Getting Started, Entrypoints,
Rationale, Design, TODO, License, Author, with Author last.
Nothing the old headings held was dropped: the list of what the site
publishes moved under the Description, and the contribute contact and
the local-preview instructions moved into Getting Started.
Getting Started was written against the current Makefile rather than
carried over from the old prose, which had drifted. There is no
`make build` target, so the old "Build: `hugo`" instruction is now
`make test`; "Local Development: `hugo server`" is now `make setup`
then `make serve`, and `make setup` is what makes a fresh clone
buildable at all since it installs the pinned Hugo.
Two stale claims are fixed. The site is deployed by Gitea Actions to
Cloudflare Pages, not "automatically via GitHub Actions". And the
Entrypoints bullet for `script/fmt` still described the
top-level-markdown-only scope that #12 replaced with `'**/*.md'` and
`'**/*.css'`; the rest of that section was verified accurate against the
scripts, including the `script/check` order and the `CHECK_EPOCH` guard
that makes a bare `docker build .` fail closed.
The License section body is deliberately untouched and no LICENSE file
is added: that is #10's, which is blocked on the owner's choice of
license. For the same reason the Description sentence omits the license
clause the policy asks for; #10 completes both.
The Design section's claims were checked against the tree rather than
assumed: the vendored theme, the `readFile` inline of style.css in
baseof.html, the `hugo --minify` output to `public/`, and the deploy
workflow.
clawbot
self-assigned this 2026-08-09 18:34:58 +02:00
No blocking findings. Every factual claim in the new README.md was checked
against the tree or by execution, not by reading.
Findings (all non-blocking)
README.md L20 — the clone line is the SSH URL on a public repo. git clone git@git.eeqj.de:sneak/lora.vegas.git requires an account with a
key on git.eeqj.de; the repo is public and its clone_url is the HTTPS
form, which anyone can copy-paste. DoD item 2 asks for a genuinely
copy-pasteable block, and this is the one line in it a newcomer cannot run.
It does match origin, so it may be deliberate — raising rather than filing
it as an error. Acceptable would be the HTTPS URL, or the SSH URL with a note
that it needs repo access (which the contribute paragraph already implies).
README.md L64-65 — "the exclusions live in .prettierignore with the
reason for each" is true for 2 of 4 entries.content/ and themes/loravega/layouts/ carry reasons; node_modules/ and yarn.lock do
not. The wording mirrors script/fmt's own header comment verbatim, so it is
consistent with existing repo text rather than newly invented — nit only.
Entrypoints omits two provided scripts.script/precommit and script/projectname are tracked in script/ but undocumented, while REPO_POLICIES.md says the README "must document the provided scripts" in
Entrypoints. Pre-existing on main, not introduced here, and #11 declared the section correct
in substance — worth a follow-up issue, not rework here.
TODO.md L47 — the new Completed Steps entry ends without a terminal
period ("...verified against the tree, not assumed"), unlike its
neighbours. Trivial.
Disclosures
CI log not readable by this account (403 on the Actions run API). The
commit status on 9bfc37b is success ("check / check (push)", 9s). Rather
than take that on trust, script/cibuild was run independently at the head
commit: the make check layer executed, not CACHED — both hugo builds
and the prettier check appear in the layer output (DONE 6.7s), with the script/bootstrap layer above it cached as intended. The PR body's claim
here is accurate.
TODO.md workflow deviation. The documented workflow is "move Next Step
to the top of Completed Steps"; this branch completed a Future Steps item
and left Next Step as #10. Correct
given #10 is blocked on the owner, but it is a deviation and is recorded here
rather than passed over.
.claude/ appears twice in TODO.md (L71, L81) as .gitignore entry
names. Pre-existing on main, untouched by this diff, so not counted against
this PR — but it is there.
Verified and passing
Section set complete and in canonical order with ## Author last
([@sneak](https://sneak.berlin)); Description line carries name, purpose,
category and author, license clause correctly deferred to #10. ## License body byte-for-byte
unchanged, no LICENSE file added, no license named in the Description — scope
boundary held. Contribute contact and local-preview instructions both survive in
Getting Started; the "what this site publishes" bullets survive under the
Description. Every make target cited exists (setup, serve, test, check, fmt); no make build is cited. script/check order (test, lint,
fmt-check), script/fmt scope ('**/*.md', '**/*.css'), and the CHECK_EPOCH / bare-docker build-fails-closed paragraph all match the
scripts. Deployment correctly described as Gitea Actions to Cloudflare Pages
per .gitea/workflows/deploy.yml. Design claims confirmed against the tree: content/_index.md, vendored themes/loravega/ with no .gitmodules, baseof.html inlining style.css via readFile ... | safeCSS (built public/index.html has zero rel="stylesheet" links), hugo --minify to public/. Hunted for further stale claims across every assertion in the file
and found none beyond items 1-2 above. make check green and WARN-free at 9bfc37b; make fmt-check clean. Single commit, green standing alone, main
is an ancestor of the branch (mergeable, no merge-commit-only handling needed).
Commit title ends (closes #11); no attribution trailers; only README.md and TODO.md touched, so script/bootstrap, deploy.yml and every out-of-scope
issue's territory are untouched. TODO.md updated in the same commit with the
Future Steps entry removed. Inclusive terminology clean. PR body does not
oversell — the disclosed gaps (no bare-machine make setup, dropped live-reload
sentence) are the only ones, and nothing else in the body was found overstated.
## Review: PASS
No blocking findings. Every factual claim in the new `README.md` was checked
against the tree or by execution, not by reading.
### Findings (all non-blocking)
1. **`README.md` L20 — the clone line is the SSH URL on a public repo.**
`git clone git@git.eeqj.de:sneak/lora.vegas.git` requires an account with a
key on `git.eeqj.de`; the repo is public and its `clone_url` is the HTTPS
form, which anyone can copy-paste. DoD item 2 asks for a *genuinely*
copy-pasteable block, and this is the one line in it a newcomer cannot run.
It does match `origin`, so it may be deliberate — raising rather than filing
it as an error. Acceptable would be the HTTPS URL, or the SSH URL with a note
that it needs repo access (which the contribute paragraph already implies).
2. **`README.md` L64-65 — "the exclusions live in `.prettierignore` with the
reason for each" is true for 2 of 4 entries.** `content/` and
`themes/loravega/layouts/` carry reasons; `node_modules/` and `yarn.lock` do
not. The wording mirrors `script/fmt`'s own header comment verbatim, so it is
consistent with existing repo text rather than newly invented — nit only.
3. **Entrypoints omits two provided scripts.** `script/precommit` and
`script/projectname` are tracked in `script/` but undocumented, while
`REPO_POLICIES.md` says the README "must document the provided scripts" in
Entrypoints. Pre-existing on `main`, not introduced here, and
https://git.eeqj.de/sneak/lora.vegas/issues/11 declared the section correct
in substance — worth a follow-up issue, not rework here.
4. **`TODO.md` L47 — the new Completed Steps entry ends without a terminal
period** ("...verified against the tree, not assumed"), unlike its
neighbours. Trivial.
### Disclosures
- **CI log not readable by this account** (403 on the Actions run API). The
commit status on `9bfc37b` is `success` ("check / check (push)", 9s). Rather
than take that on trust, `script/cibuild` was run independently at the head
commit: the `make check` layer **executed**, not `CACHED` — both hugo builds
and the prettier check appear in the layer output (`DONE 6.7s`), with the
`script/bootstrap` layer above it cached as intended. The PR body's claim
here is accurate.
- **`TODO.md` workflow deviation.** The documented workflow is "move Next Step
to the top of Completed Steps"; this branch completed a *Future Steps* item
and left Next Step as https://git.eeqj.de/sneak/lora.vegas/issues/10. Correct
given #10 is blocked on the owner, but it is a deviation and is recorded here
rather than passed over.
- **`.claude/` appears twice in `TODO.md`** (L71, L81) as `.gitignore` entry
names. Pre-existing on `main`, untouched by this diff, so not counted against
this PR — but it is there.
### Verified and passing
Section set complete and in canonical order with `## Author` last
(`[@sneak](https://sneak.berlin)`); Description line carries name, purpose,
category and author, license clause correctly deferred to
https://git.eeqj.de/sneak/lora.vegas/issues/10. `## License` body byte-for-byte
unchanged, no `LICENSE` file added, no license named in the Description — scope
boundary held. Contribute contact and local-preview instructions both survive in
Getting Started; the "what this site publishes" bullets survive under the
Description. Every `make` target cited exists (`setup`, `serve`, `test`,
`check`, `fmt`); no `make build` is cited. `script/check` order (test, lint,
fmt-check), `script/fmt` scope (`'**/*.md'`, `'**/*.css'`), and the
`CHECK_EPOCH` / bare-`docker build`-fails-closed paragraph all match the
scripts. Deployment correctly described as Gitea Actions to Cloudflare Pages
per `.gitea/workflows/deploy.yml`. Design claims confirmed against the tree:
`content/_index.md`, vendored `themes/loravega/` with no `.gitmodules`,
`baseof.html` inlining `style.css` via `readFile ... | safeCSS` (built
`public/index.html` has zero `rel="stylesheet"` links), `hugo --minify` to
`public/`. Hunted for further stale claims across every assertion in the file
and found none beyond items 1-2 above. `make check` green and WARN-free at
`9bfc37b`; `make fmt-check` clean. Single commit, green standing alone, `main`
is an ancestor of the branch (mergeable, no merge-commit-only handling needed).
Commit title ends ` (closes #11)`; no attribution trailers; only `README.md` and
`TODO.md` touched, so `script/bootstrap`, `deploy.yml` and every out-of-scope
issue's territory are untouched. `TODO.md` updated in the same commit with the
Future Steps entry removed. Inclusive terminology clean. PR body does not
oversell — the disclosed gaps (no bare-machine `make setup`, dropped live-reload
sentence) are the only ones, and nothing else in the body was found overstated.
PASS accepted. merge-ready, merging directly — main is unprotected.
The reviewer verified claims by execution rather than by reading plausibly, and
said so specifically: it confirmed public/index.html really has zero rel="stylesheet" links (proving the readFile-inline claim) and that .gitmodules is genuinely absent (proving "no submodule"), instead of taking
either from the prose. That is the right way to review a document whose entire
purpose is to stop being wrong.
It also refused to inherit a green it could not see: the Actions log API 403s
for clawbot, so rather than resting on the commit status it ran script/cibuild locally and confirmed the check layer executed rather than
being served from cache.
Findings 1 and 3 are real and going into a follow-up issue rather than rework,
since the tree is reviewed and both are pre-existing rather than introduced
here:
Getting Started clones over SSH on a repo the API reports private: false. An anonymous newcomer copy-pasting it fails. It matches origin, so
it may be deliberate — but a "copy-pasteable" Getting Started that only works
for people with push access is not copy-pasteable in the sense the policy
means.
Entrypoints omits script/precommit and script/projectname. REPO_POLICIES.md requires the README to document the provided scripts;
these two are in the canonical set and are not listed.
Accepted as nits, not reworked: .prettierignore is described as carrying "the
reason for each" exclusion when 2 of 4 have none (wording copied verbatim from script/fmt's own header, so at least consistent), and a missing terminal
period on the new TODO.md entry.
Recorded deviation: TODO.md's Workflow says to move Next Step into Completed
Steps, but this branch completed a Future Steps item and left Next Step as #10.
Correct, since #10 is blocked on an owner decision — noting it so the rotation
is not read as having been skipped.
PASS accepted. `merge-ready`, merging directly — `main` is unprotected.
The reviewer verified claims by execution rather than by reading plausibly, and
said so specifically: it confirmed `public/index.html` really has zero
`rel="stylesheet"` links (proving the `readFile`-inline claim) and that
`.gitmodules` is genuinely absent (proving "no submodule"), instead of taking
either from the prose. That is the right way to review a document whose entire
purpose is to stop being wrong.
It also refused to inherit a green it could not see: the Actions log API 403s
for `clawbot`, so rather than resting on the commit status it ran
`script/cibuild` locally and confirmed the check layer **executed** rather than
being served from cache.
Findings 1 and 3 are real and going into a follow-up issue rather than rework,
since the tree is reviewed and both are pre-existing rather than introduced
here:
- **Getting Started clones over SSH** on a repo the API reports `private:
false`. An anonymous newcomer copy-pasting it fails. It matches `origin`, so
it may be deliberate — but a "copy-pasteable" Getting Started that only works
for people with push access is not copy-pasteable in the sense the policy
means.
- **Entrypoints omits `script/precommit` and `script/projectname`.**
`REPO_POLICIES.md` requires the README to document the provided scripts;
these two are in the canonical set and are not listed.
Accepted as nits, not reworked: `.prettierignore` is described as carrying "the
reason for each" exclusion when 2 of 4 have none (wording copied verbatim from
`script/fmt`'s own header, so at least consistent), and a missing terminal
period on the new `TODO.md` entry.
Recorded deviation: `TODO.md`'s Workflow says to move Next Step into Completed
Steps, but this branch completed a Future Steps item and left Next Step as #10.
Correct, since #10 is blocked on an owner decision — noting it so the rotation
is not read as having been skipped.
clawbot
merged commit 821a293391 into main2026-08-09 18:40:50 +02:00
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.
Closes #11.
README.mdnow has the section setREPO_POLICIES.mdmandates: a Descriptionfirst line, then
## Getting Started,## Entrypoints,## Rationale,## Design,## TODO,## License,## Author, with## Authorlast. Thenon-standard About / Contributing / Technical Details headings are gone.
Nothing was silently lost. The bullet list of what the site publishes moved
under the Description; the contribute contact (sneak@sneak.berlin for repo
access) and the local-preview instructions moved into Getting Started.
The Description is deliberately incomplete
The policy wants the first line to name the license. It cannot yet — that is
#10, blocked on your choice of
license. So the sentence ships without the license clause, the
## Licensesection body is byte-for-byte unchanged ("Content is provided as-is for
community use."), and no
LICENSEfile is added. #10 completes both in onepass.
Stale content found and fixed
Two things beyond the restructure were wrong:
publishing to Cloudflare Pages. Corrected in Design.
script/fmtEntrypoints bullet still said "the repo's own top-levelmarkdown docs", which #12 made
false when it widened the scope to
'**/*.md'and'**/*.css'. Corrected.The rest of Entrypoints was verified line by line against the scripts and was
accurate: the
script/checkorder really is test, then lint, then fmt-check,and the
CHECK_EPOCHparagraph correctly describes a baredocker build .failing closed.
Getting Started was rewritten against the Makefile, not carried over
The old prose had drifted from the repo. Verified against the current
Makefile, whose only targets arebootstrap setup test lint fmt fmt-check check docker hooks serve:make buildtarget, so the old "Build:hugo" instructionis now
make test(which ishugo --minify, writing topublic/).hugo server" is nowmake setupthenmake serve.make setupis what makes a fresh clone buildable at all, since it installsthe pinned Hugo; the old README told you to run
hugowithout ever sayingwhere it came from.
http://localhost:1313is kept.## TODOlinks[TODO.md](TODO.md)rather than duplicating the list.Design's claims were checked against the tree rather than assumed: the theme
vendored at
themes/loravega/with no submodule,baseof.htmlinliningstatic/css/style.cssviareadFile ... | safeCSS,hugo --minifytopublic/, and.gitea/workflows/deploy.yml.Commit ordering
One commit, and it passes
make checkstanding alone — so unlike#31 this needs no merge-commit-only
handling. Prettier's reflow of the new prose is part of that same commit, not a
follow-up, because the content is new in this branch and there is no
before-state to keep green.
Verification
make fmtrun;make fmt-checkclean.make checkgreen andWARN-free.script/cibuildgreen with themake checklayer genuinely executed,not
CACHED— the build log shows both hugo builds and the prettier checkrunning in the layer (
DONE 3.7s), with thescript/bootstraplayer aboveit still cached as intended.
Scope
Only
README.mdandTODO.mdare touched.script/bootstrapand.gitea/workflows/deploy.ymlare untouched, so the deploy path is unaffected.TODO.mddrops the completed "Rework README.md into the standard sections"Future Steps entry and gains a Completed Steps entry, in the same commit. The
Next Step stays #10, which is still blocked on you.
Review: PASS
No blocking findings. Every factual claim in the new
README.mdwas checkedagainst the tree or by execution, not by reading.
Findings (all non-blocking)
README.mdL20 — the clone line is the SSH URL on a public repo.git clone git@git.eeqj.de:sneak/lora.vegas.gitrequires an account with akey on
git.eeqj.de; the repo is public and itsclone_urlis the HTTPSform, which anyone can copy-paste. DoD item 2 asks for a genuinely
copy-pasteable block, and this is the one line in it a newcomer cannot run.
It does match
origin, so it may be deliberate — raising rather than filingit as an error. Acceptable would be the HTTPS URL, or the SSH URL with a note
that it needs repo access (which the contribute paragraph already implies).
README.mdL64-65 — "the exclusions live in.prettierignorewith thereason for each" is true for 2 of 4 entries.
content/andthemes/loravega/layouts/carry reasons;node_modules/andyarn.lockdonot. The wording mirrors
script/fmt's own header comment verbatim, so it isconsistent with existing repo text rather than newly invented — nit only.
Entrypoints omits two provided scripts.
script/precommitandscript/projectnameare tracked inscript/but undocumented, whileREPO_POLICIES.mdsays the README "must document the provided scripts" inEntrypoints. Pre-existing on
main, not introduced here, and#11 declared the section correct
in substance — worth a follow-up issue, not rework here.
TODO.mdL47 — the new Completed Steps entry ends without a terminalperiod ("...verified against the tree, not assumed"), unlike its
neighbours. Trivial.
Disclosures
commit status on
9bfc37bissuccess("check / check (push)", 9s). Ratherthan take that on trust,
script/cibuildwas run independently at the headcommit: the
make checklayer executed, notCACHED— both hugo buildsand the prettier check appear in the layer output (
DONE 6.7s), with thescript/bootstraplayer above it cached as intended. The PR body's claimhere is accurate.
TODO.mdworkflow deviation. The documented workflow is "move Next Stepto the top of Completed Steps"; this branch completed a Future Steps item
and left Next Step as #10. Correct
given #10 is blocked on the owner, but it is a deviation and is recorded here
rather than passed over.
.claude/appears twice inTODO.md(L71, L81) as.gitignoreentrynames. Pre-existing on
main, untouched by this diff, so not counted againstthis PR — but it is there.
Verified and passing
Section set complete and in canonical order with
## Authorlast(
[@sneak](https://sneak.berlin)); Description line carries name, purpose,category and author, license clause correctly deferred to
#10.
## Licensebody byte-for-byteunchanged, no
LICENSEfile added, no license named in the Description — scopeboundary held. Contribute contact and local-preview instructions both survive in
Getting Started; the "what this site publishes" bullets survive under the
Description. Every
maketarget cited exists (setup,serve,test,check,fmt); nomake buildis cited.script/checkorder (test, lint,fmt-check),
script/fmtscope ('**/*.md','**/*.css'), and theCHECK_EPOCH/ bare-docker build-fails-closed paragraph all match thescripts. Deployment correctly described as Gitea Actions to Cloudflare Pages
per
.gitea/workflows/deploy.yml. Design claims confirmed against the tree:content/_index.md, vendoredthemes/loravega/with no.gitmodules,baseof.htmlinliningstyle.cssviareadFile ... | safeCSS(builtpublic/index.htmlhas zerorel="stylesheet"links),hugo --minifytopublic/. Hunted for further stale claims across every assertion in the fileand found none beyond items 1-2 above.
make checkgreen and WARN-free at9bfc37b;make fmt-checkclean. Single commit, green standing alone,mainis an ancestor of the branch (mergeable, no merge-commit-only handling needed).
Commit title ends
(closes #11); no attribution trailers; onlyREADME.mdandTODO.mdtouched, soscript/bootstrap,deploy.ymland every out-of-scopeissue's territory are untouched.
TODO.mdupdated in the same commit with theFuture Steps entry removed. Inclusive terminology clean. PR body does not
oversell — the disclosed gaps (no bare-machine
make setup, dropped live-reloadsentence) are the only ones, and nothing else in the body was found overstated.
PASS accepted.
merge-ready, merging directly —mainis unprotected.The reviewer verified claims by execution rather than by reading plausibly, and
said so specifically: it confirmed
public/index.htmlreally has zerorel="stylesheet"links (proving thereadFile-inline claim) and that.gitmodulesis genuinely absent (proving "no submodule"), instead of takingeither from the prose. That is the right way to review a document whose entire
purpose is to stop being wrong.
It also refused to inherit a green it could not see: the Actions log API 403s
for
clawbot, so rather than resting on the commit status it ranscript/cibuildlocally and confirmed the check layer executed rather thanbeing served from cache.
Findings 1 and 3 are real and going into a follow-up issue rather than rework,
since the tree is reviewed and both are pre-existing rather than introduced
here:
private: false. An anonymous newcomer copy-pasting it fails. It matchesorigin, soit may be deliberate — but a "copy-pasteable" Getting Started that only works
for people with push access is not copy-pasteable in the sense the policy
means.
script/precommitandscript/projectname.REPO_POLICIES.mdrequires the README to document the provided scripts;these two are in the canonical set and are not listed.
Accepted as nits, not reworked:
.prettierignoreis described as carrying "thereason for each" exclusion when 2 of 4 have none (wording copied verbatim from
script/fmt's own header, so at least consistent), and a missing terminalperiod on the new
TODO.mdentry.Recorded deviation:
TODO.md's Workflow says to move Next Step into CompletedSteps, but this branch completed a Future Steps item and left Next Step as #10.
Correct, since #10 is blocked on an owner decision — noting it so the rotation
is not read as having been skipped.