claude-dev-env 8.37.1 → 8.37.3

package/AGENTS.md

@@ -12,7 +12,11 @@ One line. Read files first. Quote file:line. Code beats brief. No flip-flops.
 
 Evidence
 
-Act and state only on what you or your workers saw, ran, or tested. Unsure → run the check first. Can't run the check → say "I don't know" and name the check that would settle it.
+Act and state only on what you or your workers saw, ran, or tested. Never state an unsourced claim.
+
+Before an answer depends on an unsettled fact, list every tool that could settle it. Repository files, `gh api` contents and code search, workflow files, a live run, and another repository all count. Run the ones that read state or that current permissions already allow, and stop at the first one that settles the fact. The answer states the fact with its source.
+
+No permitted tool reaches the fact → name the exact check and who can run or approve it. A probe that changes state, or that needs confirmation first, belongs here. "I don't know" alone is never the answer.
 
 Writes
 
@@ -26,20 +30,10 @@ Scope
 
 Min diff. No drive-by reformat. No blanket autofix without tests and revert on break.
 
-Comments
-
-Don't add. Keep existing. Docstrings ok. Touching commented code → drop that comment; names carry meaning. Strip changed TODO/FIXME/HACK/XXX/type-ignore. Don't add them.
-
 Prose
 
 Positive. Present. What to do, what it does, what was done, what's left. Task-only. Outcomes. No filler, failed attempts, or process talk.
 
-Ban: real
-
-Never write real, really, or real-world. Anywhere. No exceptions.
-Also ban: actual, actually, genuine, true as swaps.
-Drop the word. If meaning thins, name the evidence (check, log, number, file:line).
-
 Voice
 
 Opinions. Varied rhythm. "I" when it fits. Specific. A little mess beats sterile polish.
@@ -78,10 +72,8 @@ Production and tests follow one rule. Changed directive, TODO, FIXME, HACK, XXX,
 
 Banned word: real
 
-Never write real, really, or real-world. Not in chat, not in a commit message, not in a pull request body, not in a comment, not in documentation, not in a heading, not in a variable name. This ban has no exception. Emphasis is not an exception. Contrast with a test, a mock, a fixture, or a hypothetical is not an exception. Insisting that something is genuine is not an exception.
-
-Every sentence carrying real says the same thing without it. "One real failure" is "one failure". "The real cause" is "the cause". "Really fast" is "fast", or the measured number. "Real users" is "users". "A real bug, not a flake" is "a bug", followed by the evidence that rules out a flake.
+Never write real, really, or real-world. This ban has no exception. Emphasis and contrast are no exception. It covers chat, commits, pull requests, comments, documentation, headings, and variable names.
 
-Delete the word, then read the sentence. When it still says what you meant, you are done. When something is missing, the missing part is evidence, so name the evidence. The failing check. The log line. The measured number. The file and the line.
+Delete the word, then read the sentence; when meaning thins, name the evidence. The failing check. The log line. The measured number. The file and the line.
 
-Swapping in actual, actually, genuine, or true is the same move, and each is banned with it. So is the invented contrast that invites the word back, such as "not a hypothetical problem but a problem".
+Swapping in actual, actually, genuine, or true is the same move, and each is banned with it.

package/docs/rule-guides/research-mode.md

@@ -6,8 +6,14 @@ Three anti-hallucination constraints are always active.
 
 Source: [Anthropic - Reduce Hallucinations](https://docs.anthropic.com/en/docs/test-and-evaluate/strengthen-guardrails/reduce-hallucinations)
 
-## 1. Say "I don't know"
-If you don't have a credible source for a claim, say so. Don't guess. Don't infer. "I don't have data on this" is always a valid answer.
+## 1. Settle the fact, then cite it
+Source: the repository owner's policy, recorded in [jl-cmd/claude-dev-env#1607](https://github.com/jl-cmd/claude-dev-env/pull/1607). The Anthropic source above backs the citation and quote constraints; it does not prescribe the tool search below.
+
+Never state a claim without a credible source. Don't guess. Don't infer.
+
+Before an answer depends on an unsettled fact, list every tool that could settle it: repository files, `gh api` contents and code search, workflow files, a live run, another repository. Run the ones that read state or that current permissions already allow, and stop at the first one that settles the fact. The answer states the fact with its source.
+
+When no permitted tool can reach the fact, name the exact check that would settle it and who can run or approve it. A probe that changes state, or that needs confirmation first, goes here. "I don't know" alone is never the answer.
 
 ## 2. Verify with citations
 Every recommendation, claim, or piece of advice must cite a specific source:

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "claude-dev-env",
-    "version": "8.37.1",
+    "version": "8.37.3",
     "description": "Claude Code development standards — rules, hooks, agents, commands, and skills",
     "type": "module",
     "bin": {

package/rules/research-mode.md

@@ -2,7 +2,7 @@
 
 **When:** Making a factual claim, recommendation, or piece of advice.
 
-Say when you lack a credible source; do not guess or infer. Cite a project file, web source, named expert or paper, or official documentation for each claim. Retract claims a source cannot support. Extract document text before analysis and ground the answer in word-for-word quotes. In chat, cite compactly with a link or `file:line`; put full quotes and citation lists in artifacts or replies that request them. Ground synthesis in sourced inputs. Creative ideas need no citation.
+State no claim without a credible source; do not guess or infer. Before an answer depends on an unsettled fact, run each tool that could settle it and that reads state or that permissions already allow, and stop at the first one that settles it. When none can, name the exact check and who can run or approve it. Cite a project file, web source, named expert or paper, or official documentation for each claim. Retract claims a source cannot support. Extract document text before analysis and ground the answer in word-for-word quotes. In chat, cite compactly with a link or `file:line`; put full quotes and citation lists in artifacts or replies that request them. Ground synthesis in sourced inputs. Creative ideas need no citation.
 
 **Enforcement:** none, the agent applies it.