From d8ac3e8a846de68e0ebd5b10802d2d03f5773156 Mon Sep 17 00:00:00 2001
From: Conal <33135619+Conalh@users.noreply.github.com>
Date: Thu, 21 May 2026 19:18:41 -0700
Subject: [PATCH 1/2] Tone down team-validation framing in README

The paid-layer / hosted-SaaS framing read as commercial intent on the
front page. The TEAM_PILOT and team-validation feedback paths still
exist as the same docs and issue templates; just describing them as
team feedback for multi-repo trials rather than paid-tier validation.
---
 README.md | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index f93bd5f..f465780 100644
--- a/README.md
+++ b/README.md
@@ -159,12 +159,11 @@ PolicyMesh is intentionally small right now. If a warning is noisy, open a
 [false-positive report](https://github.com/Conalh/PolicyMesh/issues/new?template=false-positive.yml).
 If your team uses another agent config surface, open a
 [missing-surface request](https://github.com/Conalh/PolicyMesh/issues/new?template=missing-surface.yml).
-If your team is testing PolicyMesh across multiple repositories, needs org-level
-policy review, shared baselines, exception ownership, or cross-repo reports, open a
-[team validation signal](https://github.com/Conalh/PolicyMesh/issues/new?template=team-validation.yml).
-For a concrete multi-repo trial path, use the [team pilot guide](docs/TEAM_PILOT.md).
-The paid-layer validation tracker is
-[issue #5](https://github.com/Conalh/PolicyMesh/issues/5); hosted SaaS work should wait for repeated team signals there.
+If you're trying PolicyMesh across multiple repositories or want shared baselines,
+exception ownership, or cross-repo reports, the [team pilot guide](docs/TEAM_PILOT.md)
+walks through a concrete multi-repo trial path and the
+[team feedback form](https://github.com/Conalh/PolicyMesh/issues/new?template=team-validation.yml)
+collects results.
 
 ## Development
 

From 79248099f335e311ea896602519b56d7cb4cf6a5 Mon Sep 17 00:00:00 2001
From: Conal <33135619+Conalh@users.noreply.github.com>
Date: Fri, 22 May 2026 08:51:04 -0700
Subject: [PATCH 2/2] Update README assertions to match scrubbed framing
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

PR #42 dropped the 'paid-tier validation tracker' and 'team validation
signal' framing from the README. The corresponding test assertions
pinned the old strings — updating them to match the new neutralized
phrasing ('team feedback form', and dropping the issues/5 link check
since #5 is no longer referenced as a paid-layer tracker).
---
 test/workflow.test.mjs | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/test/workflow.test.mjs b/test/workflow.test.mjs
index 6c6fc86..76ca6fc 100644
--- a/test/workflow.test.mjs
+++ b/test/workflow.test.mjs
@@ -118,7 +118,6 @@ test('issue templates collect detector and team validation feedback', async () =
   assert.match(teamPilot, /team-validation\.yml/);
   assert.match(readme, /TEAM_PILOT\.md/);
   assert.match(readme, /team-validation\.yml/);
-  assert.match(readme, /issues\/5/);
 });
 
 test('README documents Action credibility and robustness signals', async () => {
@@ -137,7 +136,7 @@ test('README documents Action credibility and robustness signals', async () => {
   assert.match(readme, /Codex network access enabled alongside other configured or unreadable agent surfaces/);
   assert.match(readme, /Claude MCP grants for servers missing from MCP configs/);
   assert.match(readme, /Malformed JSON and Codex TOML agent config files/);
-  assert.match(readme, /team validation signal/);
+  assert.match(readme, /team feedback form/);
 });
 
 test('README separates original demo PR proof from richer fixture proof', async () => {