fiddlerwoaroof/improvise
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc-site: name context/code/pr-review.md as an omission

Browse Source 
The `build` job fails on main and on every branch merged from it:

  doc-site: context/code/pr-review.md is neither published nor a named omission

NOT a merge loss -- scripts/build-doc-site.mjs in this branch is
byte-identical to main's, and neither lists the file. PR #96 added
context/code/pr-review.md without a manifest line, which is exactly the
gate improvise-res9 added: a doc added without a line publishes nothing
and says nothing, so the generator refuses.

Omitted rather than published, and the line is cloud-agents.md's rather
than tooling.md's. tooling.md explains checkers a reader of the code will
meet; pr-review.md is about THIS REPOSITORY'S PROCESS -- where a Codex
review appears, how to tell it from our own agents' comments, why absence
is not approval. Nobody visiting a website is about to read a PR thread.

Both homes updated, because an omission is restated beside the manifest
AND in doc-site.md section 2, and the prose there counted them ("Neither
is referenced...") so it went stale at three.

This strays into scripts/, which is Wave N's ground. Flagged in the
hand-back; it is a one-line data entry either way if the orchestrator
would rather publish it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FC2jVn8Au7E9JPkw6bwXXH
This commit is contained in:
Edward Langley
2026-09-21 11:12:00 -07:00
parent 3d0850c132
commit 787e354b9b
29 changed files with 5617 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
context/code/doc-site.md
+7 -1
View File
@@ -35,8 +35,14 @@ Not published:
cloud session — tracker hydration, `bd` pitfalls, what the sandbox blocks.
It is true and it is useful and it is addressed to nobody who visits a
website.
- **`context/code/pr-review.md`** is how an agent reads a PR's reviews — where
a ChatGPT Codex review appears, how to tell it from this repo's own agents'
comments, and why absence is not approval. It is about *this repository's
process*, not about the program, which is the `cloud-agents.md` line and not
the `tooling.md` one: `tooling.md` explains checkers a reader of the code
will meet, and nobody visiting a website is about to read a PR thread.
Neither is referenced by any published document except as a row in
None of the three is referenced by any published document except as a row in
`repo-map.md`'s file inventory, which is inside a code fence, so leaving them
out creates no dangling link. That was checked rather than assumed.