chore(agents): sync portable agent core vfbbb8f0b

.claude/rules/agent-core.md

@@ -4,7 +4,7 @@
 > portable core reaches Claude -- locally, in subagents, and in GitHub-hosted runs.
 > Generated from ~/.claude/portable/AGENT_CORE.md. Edit there, not here.
 
-<!-- BEGIN AGENT CORE vc06c74a9 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
+<!-- BEGIN AGENT CORE vfbbb8f0b (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
 # Agent Core (portable operating rules)
 
 Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
@@ -22,6 +22,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
 - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks.
 - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence.
 - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims.
+- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body.
 - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it.
 
 ## 2. Concurrency: you are never the only writer

.cursor/rules/agent-core.mdc

@@ -3,7 +3,7 @@ description: Portable agent operating rules
 alwaysApply: true
 ---
 
-<!-- BEGIN AGENT CORE vc06c74a9 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
+<!-- BEGIN AGENT CORE vfbbb8f0b (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
 # Agent Core (portable operating rules)
 
 Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
@@ -21,6 +21,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
 - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks.
 - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence.
 - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims.
+- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body.
 - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it.
 
 ## 2. Concurrency: you are never the only writer

.gemini/styleguide.md

@@ -3,7 +3,7 @@
 > Read by the Gemini Code Assist GitHub app when it reviews pull requests.
 > Generated mirror of the portable agent core. See AGENTS.md.
 
-<!-- BEGIN AGENT CORE vc06c74a9 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
+<!-- BEGIN AGENT CORE vfbbb8f0b (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
 # Agent Core (portable operating rules)
 
 Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
@@ -21,6 +21,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
 - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks.
 - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence.
 - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims.
+- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body.
 - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it.
 
 ## 2. Concurrency: you are never the only writer

.github/copilot-instructions.md

@@ -2,7 +2,7 @@
 
 > Generated mirror of the portable agent core. See AGENTS.md.
 
-<!-- BEGIN AGENT CORE vc06c74a9 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
+<!-- BEGIN AGENT CORE vfbbb8f0b (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
 # Agent Core (portable operating rules)
 
 Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
@@ -20,6 +20,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
 - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks.
 - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence.
 - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims.
+- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body.
 - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it.
 
 ## 2. Concurrency: you are never the only writer

AGENTS.md

@@ -3,7 +3,7 @@
 > Cross-tool agent contract for this repo. Spec: <https://agents.md/>
 > Project-specific rules go ABOVE the managed block and override it.
 
-<!-- BEGIN AGENT CORE vc06c74a9 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
+<!-- BEGIN AGENT CORE vfbbb8f0b (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
 # Agent Core (portable operating rules)
 
 Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
@@ -21,6 +21,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
 - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks.
 - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence.
 - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims.
+- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body.
 - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it.
 
 ## 2. Concurrency: you are never the only writer

GEMINI.md

@@ -2,7 +2,7 @@
 
 > Generated mirror of the portable agent core. See AGENTS.md.
 
-<!-- BEGIN AGENT CORE vc06c74a9 (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
+<!-- BEGIN AGENT CORE vfbbb8f0b (generated by ~/.claude/scripts/sync_agent_context.py -- edit ~/.claude/portable/AGENT_CORE.md, do not edit here) -->
 # Agent Core (portable operating rules)
 
 Tool-agnostic rules for any coding agent working in this user's repositories: Claude Code,
@@ -20,6 +20,7 @@ that file, then re-run `python ~/.claude/scripts/sync_agent_context.py --all`.
 - ASCII-only in program output on Windows consoles (cp1252): use `+/-/->`, never box-drawing or check marks.
 - **No em dashes, anywhere**: replies, code, comments, commit messages, docs, generated text. Restructure with a comma, a semicolon, parentheses, or a second sentence.
 - **Nothing you write may read as machine-written.** No stock openers or closers ("I hope this finds you well", "excited to leverage", "delve", "it's not just X, it's Y"), no three perfectly parallel bullets, no restating the question before answering it. Vary sentence length; one concrete specific beats three generic claims.
+- **Never set a heading in an email in all caps.** No `MONEY FOR SPENDING YOU HAVE ALREADY DONE`, no `NEXT STEPS`, no shouted label of any kind. All caps is how a generated document signals its structure and no person writing to another person does it. A long email gets sentence-case headings on their own line, or numbered sections, or nothing at all and a lead sentence per paragraph doing the work. The same goes for a plain-text attachment or anything pasted into a message body.
 - In anything a person receives (email, DM, chat message, letter), the colon and the dash used as punctuation are out as well ("Hi Derek -", "Quick background:"); hyphens inside compound words and product names are fine. A project may exempt an artifact that is machine-read before a human sees it.
 
 ## 2. Concurrency: you are never the only writer