fix(linkedin-studio): S22 harden outreach — add missing Bash grant, drop orphan WebFetch+Write, re-source fabricated pod/DM stats to SSOT

Outreach is the first command in the hardening queue that both delegates to an
agent (network-builder) and mutates real state (recordOutreachContact), so the
weight fell on axis-d. Five fixes across two files (operator-approved scope
extension to the SSOT-diverging guide source):

- allowed-tools: ADD Bash (Step 8c runs `node state-updater.mjs --record-outreach`
  and needs it — firsthour precedent grants Bash for the same pattern; the command
  promised a mutation it couldn't execute), DROP orphan WebFetch + Write grants
  (zero body use; :410/:1040 "Write a post" is prose). Now
  Read·Glob·WebSearch·AskUserQuestion·Task·Bash.
- Step 7 pod-warning (axis-b'): replaced fabricated magnitudes ("30-55% reach
  reduction", "shadow suppression", "credibility score", "penalizes",
  "Post-March 2025", "low dwell") with the SSOT statement
  (algorithm-signals-reference.md:98 — demote out of "Most Relevant" / scope to
  own network / restrict repeat offenders) + cite.
- :652 DM-amplification "2-3x first-hour" (axis-b'): re-attributed 2-3x to collab
  reach (where SSOT places it), kept the first-hour effect qualitative.
- collaborations-guide.md:349-370 (axis-b', scope extension): same SSOT rewrite of
  the "March 2025 Crackdown" section so the Step 7 fix can't be re-rendered from a
  stale reference (dropped "shadow banning ALL future content / 90+ days / 6+
  months / permanent penalty" + speculative detection methods).

Verify: re-grep both files clean (orphans/fabricated stats NONE, Bash :21, SSOT
text in place); recordOutreachContact throwaway-fixture 10/10 PASS (additive,
$-safe, newest-first, untouched undeclared fields); test-runner 81/0/0 exit 0;
counts 29/19 unchanged (.md-only).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016qgzo6rxthw7KuxHjn5vyE

commands/outreach.md

@@ -16,10 +16,9 @@ allowed-tools:
   - Read
   - Glob
   - WebSearch
-  - WebFetch
   - AskUserQuestion
-  - Write
   - Task
+  - Bash
 ---
 
 # LinkedIn Outreach Orchestrator (Collaborations + Speaking)
@@ -649,7 +648,8 @@ DM Amplification Protocol:
    Both partners share/comment on each other's version.
    Creates compound visibility effect.
 
-Impact: DM amplification can boost first-hour engagement 2-3x.
+Impact: this feeds the first-hour engagement that carries collaborative
+content to its 2-3x reach (ref: collaborations-guide.md).
 ```
 
 ### Step 5b: Speaking — Outreach by Channel
@@ -918,24 +918,22 @@ LinkedIn: [profile URL]
 
 ## Step 7: Engagement-Pod Warning (Both Tracks)
 
-**Post-March 2025 LinkedIn Algorithm Update:**
+LinkedIn runs an active engagement-pod crackdown (see
+`references/algorithm-signals-reference.md`):
 
 ```
 ⚠️ ENGAGEMENT PODS: DO NOT USE
 
-LinkedIn now actively detects and penalizes engagement pods:
+What LinkedIn does to pods (its stated crackdown):
+- Pod-style auto-comments are demoted out of "Most Relevant"
+- Their reach is scoped to your own network — it stops spreading beyond it
+- Repeat offenders get restricted
 
-Detection methods:
+How pods get detected:
 - Consistent same-person engagement patterns
 - Engagement timing clusters (everyone engages within minutes)
-- Low dwell time on engaged posts (engage without reading)
 - Reciprocal engagement loops (A→B→A→B pattern)
 
-Penalties:
-- 30-55% reach reduction on detected posts
-- Shadow suppression of pod participants
-- Account credibility score reduction
-
 INSTEAD, build genuine engagement through:
 - CEA method comments (Compliment, Expand, Ask)
 - 5x5x5 daily routine (organic engagement)