docs: back-fill §14 entries for #53/#57/#65/#59; add PR-body footer-strip rule - #76
Merged
Merged
Conversation
…r-strip rule Back-fill four docs/ARCHIVE.md §14 entries for merged fixes that landed without a dated entry, using docs/reviews/STATUS.md § "ARCHIVE.md §14 gaps" and the actual PR history as the source of truth: - #53 — H1/SEC-1: repository scan targets must be remote clone URLs (local-path arbitrary-read closed). Notes explicitly that this SEC-1 is distinct from the older webhook-URL "SEC-1" already in §14. - #57 — H9/SC-2 + H10/SC-3: SHA-pin all Actions, expand Dependabot to pip/npm/docker/docker-compose + composite-action dir, harden publish checkouts, converge D3/SC-10/L25 version skew. - #65 — D1/D2/R1–R6 compliance-drift closure pointing at already-logged deviations. - #59 — backend dev-dependency bumps (pytest, pytest-asyncio, black; ruff held at 0.8.6). Each entry is dated to its merge date (2026-07-13) and marked as a back-fill written 2026-07-20. Also add a CLAUDE.md § Git & PR conventions rule: after opening any PR, re-check the live PR body and strip any auto-appended attribution footer, so PR bodies carry no Claude/Anthropic identity — with a matching dated §14 entry (2026-07-20) recording the addition. Docs only.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Docs-only. Closes the
docs/ARCHIVE.md§14 record gaps identified indocs/reviews/STATUS.md§ "ARCHIVE.md §14 gaps": four merged fixes landed without a dated §14 entry. Back-fills all four using STATUS.md's findings and the actual PR history (#53/#57/#59/#65, all merged 2026-07-13 intodev) as the source of truth. Also codifies a recurring PR-body hygiene rule in CLAUDE.md.What changed
docs/ARCHIVE.md§14 — four back-fill entries (each dated to its merge date, 2026-07-13, and marked as a back-fill written 2026-07-20):repowalking the container filesystem, bypassingSCRYE_FILESYSTEM_SCAN_ROOTS) is closed. The entry explicitly notes this SEC-1 is distinct from the older, unrelated webhook-URL "SEC-1" already in §14 (2026-07-05 P0 entry) to prevent future confusion.ci.ymlhalf of L24/SC-11 was logged separately in the fix: hop scanner JSON parse/normalize off the event loop (CON-4/H5) #67 CON-4 entry.CLAUDE.md§ Git & PR conventions — new rule (with a matching 2026-07-20 §14 entry): after opening/editing any PR, re-fetch the live PR body and strip any auto-appended attribution footer ("Generated by Claude Code", a "🤖 Generated with…" line, a session/claude.ailink, a co-author trailer), so PR bodies carry no Claude/Anthropic identity — matching the existing commit-authorship rule. This footer has recurred on essentially every PR in this effort; codifying it gives a future session the rule to follow even if it doesn't catch the append.Notes
devwhen ready.