A repo can now list published-data folders under a new `review_content_patterns` ship-policy key, so /ship leaves `.patch` diffs, `MANIFEST.sha256` and extension-less licences out of review, while source files there stay reviewed. Why: gstack-evals #352 is 13.8 MB, 13.6 MB of it published session data, and could never pass /ship's 2 MB review limit. Nothing to do until a repo adds the key to its base-branch policy; a pattern that keeps too many files now stops with `REVIEW_EXCLUDE_KEEP_TOO_LARGE` instead of being dropped. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> Review-Finding: p1/red-team#2 reader=red-team Review-Finding: p2full/red-team#1 reader=red-team
CHANGELOG fragments
A PR adds its CHANGELOG entry here as changelog.d/<branch-slug>.md: the entry text only, with no ## [x] heading, and bump: minor or bump: major front matter only when the change warrants more than a patch, and important: security|regression|data-loss|blocker only when it must reach stable within about a day (docs/releases.md#the-daily-check). It never edits VERSION, package.json's version or a released CHANGELOG section. The merge step (gstack-ship-queue land, or train land in a stamped train) assigns the version (under merge: direct, the release PR from gstack-release-stamp open does), folds every fragment into one CHANGELOG section and deletes the files. The entry's first sentence (or bold lead) becomes its line in the GitHub release notes, so write it for someone using gstack: docs/releases.md#release-notes. This README is skipped. See docs/ship-policy.md#changelog-fragments.