Repository navigation
A folder marked as published data can no longer hide source code or agent files from /ship's review (GST-3158) - #4516
Merged
Conversation
…gent files from /ship's review (GST-3158) Source code in any language, agent instruction files, config and data named by kept code stay in review inside review_content_patterns folders, in the binary branch too. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
|
😎 This pull request was merged. |
Merged
4 tasks done
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
A CMakeLists.txt or .mdx file in a declared folder now stays in review as code, and a data file named by an unchanged declared executable on the base is tested both ways. Review-Finding: p1/red-team#1 reader=red-team Review-Finding: p1/specialist-batched#1 reader=specialist-batched Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
…what it names in review Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
Merged
capy-ai Bot
added a commit
that referenced
this pull request
Nov 19, 2026
- `gstack-artifact validate` no longer passes a run.json that gstack-autoplan never wrote. (#4494) - /ship's changed-number check no longer stops on tests that only share a word with the change (#4478). (#4496) - On Capy, /ship no longer edits or comments on pull requests as you. (#4518) - The destructive-command check stops asking about scratch deletes and catches the real damage it used to miss. (#4513) - The destructive-command check reads commands more carefully, closing gaps found after the last release. (#4525) - The Codex readiness check and the second-model review now pick the same model for a custom Codex provider (GST-3089). (#4491) - gstack's Codex hooks work when your Codex folder's path has a `(`, `&` or other shell character in it. (#4528) - Uninstalling gstack keeps your own Codex hooks trusted. (#4528) - Codex hook setup matches Codex more closely. (#4528) - On Windows, setup copies the Claude Code hook code that gstack's Codex hooks import (#4528) - /review's checklist on Codex reads shell commands more carefully. (#4528) - On Codex, gstack now suggests the right skill for a prompt and stops destructive commands before they run. (#4512) - On Codex, /review is now held once when it tries to finish without its adversarial pass or its report, as it already is on Claude Code. (#4522) - On Codex, gstack's skill suggestion now names the skill the way Codex lists it. (#4523) - On Codex, gstack's suggested prompts and docs now name skills the way Codex lists them. (#4524) - /review on Codex with gpt-6.1-sol is no longer held back for a second-model pass it already ran. (#4526) - On Codex, office-hours, plan-design-review and gstack-upgrade work again when you name them. (#4510) - gstack knows when Codex is running unattended. (#4510) - Codex reviewers start with a clean context. (#4510) - Docs no longer say Codex has no hook support. (#4510) - A command whose output was cut off no longer counts as a finished read. (#4492) - A folder marked as published data can no longer hide source code or agent files from /ship's review. (#4516) - Correction to the on-by-default helper hooks entry: the hook still routes only to /review, /qa and /verify, so skills you've installed yourself aren't suggested yet. With gstack's skills it routes 14 of 60 real bug reports (was 17), and long prompts are no longer skipped. (#4505) - /sync-gbrain's read check now works when the first page in your code source is over 64 KB. (#4497) - Free-suite CI no longer fails before any test runs when Ubuntu's package mirror is slow. (#4530) - Syncing a second repo no longer makes the first one ask for /sync-gbrain again. (#4532) - gstack's helper hooks are now on by default in Claude Code, OpenClaw and Hermes, and the prompt-routing hook fires on real bug reports. (#4503) - `gstack-pregate clear --receipt` accepts a remote gate run from before a merged release when the release only regenerated a declared release output. (#4483) - The second-model review now keeps the reviewer's own result, and reports a used-up budget as a budget stop. (#4515) - When the reviewer wrote its review to the result file it was asked for, Codex then replaced that file with its short closing message ("Done, I wrote the review"), so the review was thrown away and reported as missing its markers. (#4515) - When the provider refuses the call with HTTP 402 Payment Required (usually a metering proxy that hit its allowance, or an account out of credits or quota), gstack used to record only "exit 1". (#4515) - The pre-commit /verify check now fails a check that times out, and its checks share one time budget (GST-3201). (#4527) - /ship's review collector no longer reads a reviewer's own scope list or list of passed checks as findings (GST-3201). (#4527) - Merge-queue stack tests fail when git cannot list a PR's added test files (GST-3201). (#4527) - /ship can now review results PRs that publish raw session data. (#4511) - /ship's review pass works when the checkout you ship isn't the project's default checkout. (#4507) - A second review round no longer reports done when nothing was reviewed. (#4520) - The prompt-routing hook now suggests skills you install yourself, and no longer sends ordinary bug reports to /qa (GST-3123). (#4506) - gstack's script runner and merge-queue checks now also refuse cut-off output. (#4502) - A failed second-model review reports the cause that actually stopped it, and the runner never deletes its own prompt. (#4519) - `gstack-ship-queue ready` now fills in the trial merges and the second-model trail read instead of printing lines to fill. (#4529) - Five small ship-tool fixes. (#4529) - A ruling the owner gives while a `/ship` run is open can be relayed. (#4529) - /ship no longer kills a working test run as stalled when the test command starts its workers in their own session. (#4533) - /ship no longer stops a review because the state-machine reader started its reply the way its instructions say. (#4504) - When Claude Code runs /verify right before a commit, it now gets a quick check instead of the full fix loop (GST-3150). (#4508) Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
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.
In a folder a repo marks as published data (
review_content_patterns), source code in any language, agent instruction files, config and data that kept code names by full path now stay in /ship's review.Why: #4511 let a
.javafile, a binaryAGENTS.mdor a file named by a kept script leave review there, and reviewers must see every line of code a PR changes.Nothing to do: no base policy sets the key yet.
What changed
A repo that marks a folder as published data could still have code in that folder skipped by review. That included a
.javaor.ps1file, anAGENTS.mdwith a NUL byte, aCMakeLists.txtor.mdxpage, or a data file that a kept script reads by full path. Now one rule inlib/review-exclude.tsdecides when a declared file is data. Source by name (a broad, case-insensitive list of program extensions and build file names), agent prose, config, gate paths and.gstack/or.github/files stay code, in the text and binary branches alike, and a docs-looking name that is really source (CMakeLists.txt,.mdx) is no longer excluded as docs. A declared file that stays in review (kept in the range, or an executable or link in the tree) counts as code when the scan looks for files that name excluded data, so the data it reads stays in review too.Blast radius
Only repos whose base policy sets
review_content_patternsorreview_exclude_pathssee a difference, and every difference keeps more files in review, never fewer (file:line read atlib/review-exclude.tscontentKind and declaredData; 12 fixture cases intest/review-content-patterns.test.tsrun the real plan command).Test Coverage
Coverage: 5 of 9 new code paths have a test (56%), audit only, no tests generated. Gaps proposed as tests: a config file in a declared folder, a
.github/or gate path in a declared folder, a declared symlink as a reader of data, and a declared.javafile naming a data file.Tests ran: free 1704 (files)
Pre-Landing Review
Two full review passes. The first found two informational items, both fixed:
CMakeLists.txtand.mdxwere listed as source but still excluded as docs, and no test covered an unchanged declared executable on the base reading a data file. The second pass and the second-model review found nothing blocking.Review notes
Below the blocking floor; recorded here and not fixed in this PR.
lib/review-exclude.ts:270: the build-file names in SOURCE match any suffix, sodocs/BUILD.md,guides/workspace.mdand every.mdxpage under an excluded docs folder stay in review as code. That is the safe direction, but a large docs PR could hitREVIEW_EXCLUDE_KEEP_TOO_LARGE; untested.lib/review-exclude.ts:277:requirements.txt,constraints.txtand other dependency.txtfiles still count as docs, so a broad base exclude pattern can drop an unnamed root-level dependency file from review. Unchanged from main; a policy call.results/BUILD.jsonorresults/BUILD.logthat both keys match still leaves review as data or log, even though the build-name rule matches it. Those lines are unchanged from main; the maintainer ruled this an open note.results/config/runtime.db, still leaves review through the binary rule.TODOS
No TODO items completed in this PR.
Documentation
Status: updated. Two factual edits in docs/ship-policy.md; no blockers.
Scope: base f13dbb0 to head 50be17f (3 commits): changelog.d/declared-content-folders-keep-code.md, docs/ship-policy.md, lib/review-exclude.ts, test/review-content-patterns.test.ts. No staged, unstaged or new files. Cross-checked docs/troubleshooting.md and the earlier review_content_patterns changelog fragment.
Documentation health:
review_content_patternsnow says source code and the other keep rules still apply, and thenamed-by-codekeep-reason row now counts declared files that stay in review as references that keep data.Coverage debt: the declared-content keep rules have reference docs only (no how-to or explanation). Files with a source extension under a docs root are no longer excluded as docs, and no doc states this yet. No architecture diagrams are affected.
Tests
bun test test/review-content-patterns.test.ts test/review-exclude.test.ts test/review-exclude-secret-value.test.ts: green locallybun run typecheck: cleanAgent notes
Plan: exempt: bug fix (requested by the coordinator, GEVA-2)
Follow-up to #4511, split by the coordinator after the second-family trail read (reports/GSTA-636-decisions.tsv rows 21-26). The BUILD.json/BUILD.log note is GStack Minder's ruling A1.
REVIEW_LOOP: passes=2 blocking_found=0 deferred=0 noted=3 fixed=2 scope=frozen dispatches=6
Gate edits: none detected (2 listed, 0 read; patterns: RH-1,RH-3,RH-4,RH-12,RH-13,RH-14,RH-15,RH-16; unlisted idioms: none)
Approvals
No approvals recorded for branch declared-content-folders-keep-code.