Skip to content

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

Open
JimCollinson wants to merge 2 commits into
mainfrom
claude/update-autonomy-docs-RNl36
Open

Tighten prose-PR envelope + add sweep_report*.json to .gitignore#42
JimCollinson wants to merge 2 commits into
mainfrom
claude/update-autonomy-docs-RNl36

Conversation

@JimCollinson
Copy link
Copy Markdown
Collaborator

Summary

Two small follow-ups to PR #41's prose-guard failure:

  1. Tighten the routine prompt so prose PRs stay strictly within the prose envelope. The routine has now twice (PR docs: antd v0.6.1 — health fields, upload visibility, MCP port discovery #37, PR prose: update CLI and Rust library reference for ant-client timeout split — 2026-05-13 #41) done legitimate infrastructure tidying during the audit and silently bundled it into the prose PR, where prose-guard correctly rejects it. The new bullet in step 5.2 names the specific categories the routine has slipped on (.gitignore, scripts/, .github/, repo-registry.yml, component-registry.yml) and tells the routine to surface infrastructure cleanups in a "Suggested follow-ups" section of the PR body instead. Humans can then open separate PRs.

  2. Add sweep_report*.json to .gitignore. The routine writes sweep_report.json on every run, and local invocations of scripts/sweep_poll.py do the same. Never part of the docs assembly. This addition was first attempted inside PR prose: update CLI and Rust library reference for ant-client timeout split — 2026-05-13 #41 (commit 73114b6) and correctly rejected — landing it as the kind of standalone change the new prompt bullet is designed to encourage.

Test plan

  • Markdown / config-only change; nothing to compile.
  • Grep confirms the new bullet at step 5.2 names every guard-forbidden path category.
  • Local git status shows sweep_report.json is now ignored after the routine writes one.
  • Required checks pass on this PR.
  • After merge: future prose PRs should stop bundling root-level housekeeping. If a prose PR continues to do so, the prompt needs further work.

https://claude.ai/code/session_019cz1M7pXuXFQykMZxfdXHm


Generated by Claude Code

claude added 2 commits May 13, 2026 10:04
PR #41 hit prose-guard because the routine bundled a useful .gitignore
addition (ignore transient sweep_report*.json files) into a prose PR.
PR #37 hit the same shape of issue with a misnamed sweep summary file.
Both cases were the routine doing legitimate infrastructure tidying
during the audit and silently bundling it into the prose envelope,
where prose-guard correctly rejects it.

Add an explicit "stay strictly within the prose envelope" bullet to
step 5.2's Prose PR section that names the categories of root-level
housekeeping the routine has slipped on (.gitignore, scripts/,
.github/, repo-registry.yml, component-registry.yml) and points to
"Suggested follow-ups" in the PR body as the place to surface
infrastructure cleanups the audit noticed. A human can then open a
separate PR for those.

No rule duplication; this just makes the existing prose-guard envelope
explicit at the moment the routine is assembling the PR.

https://claude.ai/code/session_019cz1M7pXuXFQykMZxfdXHm
scripts/sweep_poll.py writes sweep_report.json on every routine run
and on local validation invocations. The file is never part of the
docs assembly, and committing it would just create noise in PR diffs.

This addition was first attempted as part of prose PR #41 (commit
73114b6), which the prose-guard correctly rejected because the prose
envelope does not cover root-level housekeeping. Landing it as a
standalone change here.

https://claude.ai/code/session_019cz1M7pXuXFQykMZxfdXHm
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants