Skip to content

Tighten prose-PR envelope + add sweep_report*.json to .gitignore #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JimCollinson wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Tighten prose-PR envelope + add sweep_report*.json to .gitignore #42

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
05dca5e
Tighten prose-PR envelope to forbid root-level housekeeping changes
claude May 13, 2026
997a3ca
Ignore transient sweep_report*.json scanner output
claude May 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,3 +3,8 @@
# docs assembly.
__pycache__/
*.pyc

# Transient sweep scanner output. Written by the daily routine and by
# local invocations of scripts/sweep_poll.py; never part of the docs
# assembly.
sweep_report*.json
1 change: 1 addition & 0 deletions planning/routines/upstream-sweep-prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,6 +243,7 @@ Do **not** include a PR backlink in any issue body at this stage — the PR URL
- For case 5, every deferred record's `<!-- verification: ... -->` block is byte-identical to base (deferred-record self-check from step 4.9).
- If the audit found skill impact, include the `SKILL.md` body edit and the linked patch release set per step 4.8.
- The two PRs never touch the same page.
- **Stay strictly within the prose envelope**: no `.gitignore`, no `scripts/`, no `.github/`, no `repo-registry.yml`, no `component-registry.yml`, no other root-level housekeeping files. If the audit observes a useful infrastructure cleanup (a missing gitignore entry, a stale workflow, a registry tidy-up), do **not** include it in the prose PR. Mention it in a "Suggested follow-ups" section of the PR body so a human can open a separate PR for it. `prose-guard` rejects any change outside the envelope.
- PR body: see `## PR body format` below; include a "Why prose changed" section, and (for case 5) a "Deferred ambiguous records" section with the issue numbers captured in 5.1.

**5.3 Post backlinks last**. For each manual-review issue captured in 5.1 (newly-created **and** reused), comment with the matching prose-PR URL:
Expand Down