From 262157ed62ff9ec1032e98691f3c4abfb21c1bc3 Mon Sep 17 00:00:00 2001
From: ProfessorPolymorphic
 <116023536+ProfessorPolymorphic@users.noreply.github.com>
Date: Wed, 20 May 2026 15:52:15 -0700
Subject: [PATCH] Fix leading-digit searchphrase breaking award-compliance
 Vandalizer import

The uniform_guidance_applicability searchphrase began with "2 CFR 200".
Vandalizer derives extraction field names by slugifying the searchphrase
and prepends an underscore to digit-leading names, which its own
field-name validator then rejects on import. Reworded to "Uniform
Guidance (2 CFR 200) applicability details." and bumped the workflow to
v0.1.1; the extraction contract is unchanged. Regenerated the Vandalizer
export and component catalog from the authored manifest.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---
 component_catalog.json                                      | 2 +-
 workflows/award-compliance-extraction/CHANGELOG.md          | 4 ++++
 .../award-compliance-extraction.vandalizer.json             | 6 +++---
 workflows/award-compliance-extraction/manifest.yaml         | 6 +++---
 4 files changed, 11 insertions(+), 7 deletions(-)

diff --git a/component_catalog.json b/component_catalog.json
index 52ec06e..c121029 100644
--- a/component_catalog.json
+++ b/component_catalog.json
@@ -1905,7 +1905,7 @@
       "slug": "award-compliance-extraction",
       "name": "Award Compliance & Financial Overview Extraction",
       "description": "Uploads a federal award notice or agreement and returns a single structured JSON object covering both the compliance framework (Uniform Guidance applicability, RTC, financial reporting, progress reporting, prior approvals, budget modification rules, property, deliverables, high-risk conditions, compliance calendar) and the financial management structure (total award amount, budget periods, cost share, F&A rate and base, performance period, budget categories, FFR, audit, record retention). Output conforms to the award-compliance-extraction-udm component schema. The runtime mirrors the ui-insight/ProcessMapping award-compliance-extraction workflow (two parallel Extraction tasks plus a Consolidation Prompt).",
-      "workflow_version": "0.1.0",
+      "workflow_version": "0.1.1",
       "status": "experimental",
       "vandalizer_schema_version": 2,
       "paths": {
diff --git a/workflows/award-compliance-extraction/CHANGELOG.md b/workflows/award-compliance-extraction/CHANGELOG.md
index 0bf372f..ad6e886 100644
--- a/workflows/award-compliance-extraction/CHANGELOG.md
+++ b/workflows/award-compliance-extraction/CHANGELOG.md
@@ -2,6 +2,10 @@
 
 All notable changes to this workflow. Versions follow semver.
 
+## [0.1.1] — 2026-05-20
+
+- Reworded the `uniform_guidance_applicability` searchphrase from "2 CFR 200 Uniform Guidance applicability details." to "Uniform Guidance (2 CFR 200) applicability details." so it no longer begins with a digit. Vandalizer derives each extraction field name by slugifying the searchphrase; a leading digit made Vandalizer prepend an underscore, which its own field-name validator then rejected on import. The extraction contract is unchanged.
+
 ## [0.1.0] — 2026-04-30
 
 - Initial experimental release.
diff --git a/workflows/award-compliance-extraction/award-compliance-extraction.vandalizer.json b/workflows/award-compliance-extraction/award-compliance-extraction.vandalizer.json
index ceaeb69..eb56bbd 100644
--- a/workflows/award-compliance-extraction/award-compliance-extraction.vandalizer.json
+++ b/workflows/award-compliance-extraction/award-compliance-extraction.vandalizer.json
@@ -2,7 +2,7 @@
   "vandalizer_export": true,
   "schema_version": 2,
   "export_type": "workflow",
-  "exported_at": "2026-04-30T00:00:00+00:00",
+  "exported_at": "2026-05-20T00:00:00+00:00",
   "exported_by": "ui-insight",
   "items": [
     {
@@ -27,7 +27,7 @@
                   "cross_field_rules": [],
                   "items": [
                     {
-                      "searchphrase": "2 CFR 200 Uniform Guidance applicability details.",
+                      "searchphrase": "Uniform Guidance (2 CFR 200) applicability details.",
                       "searchtype": "extraction",
                       "title": "uniform_guidance_applicability",
                       "is_optional": true,
@@ -255,7 +255,7 @@
       "validation_inputs": [],
       "x_ai4ra": {
         "workflow_source": "workflows/award-compliance-extraction/manifest.yaml",
-        "workflow_version": "0.1.0",
+        "workflow_version": "0.1.1",
         "status": "experimental",
         "components": [
           {
diff --git a/workflows/award-compliance-extraction/manifest.yaml b/workflows/award-compliance-extraction/manifest.yaml
index 3365f80..ca083cf 100644
--- a/workflows/award-compliance-extraction/manifest.yaml
+++ b/workflows/award-compliance-extraction/manifest.yaml
@@ -27,12 +27,12 @@ description: >
   award-compliance-extraction workflow (two parallel Extraction tasks plus
   a Consolidation Prompt).
 
-workflow_version: 0.1.0
+workflow_version: 0.1.1
 vandalizer_schema_version: 2
 status: experimental
 owner: ui-insight
 created: 2026-04-30
-updated: 2026-04-30
+updated: 2026-05-20
 
 components:
   - slug: award-compliance-extraction-udm
@@ -97,7 +97,7 @@ steps:
           domain: research-administration
           items:
             - title: uniform_guidance_applicability
-              searchphrase: 2 CFR 200 Uniform Guidance applicability details.
+              searchphrase: Uniform Guidance (2 CFR 200) applicability details.
               is_optional: true
             - title: rtc_applicability
               searchphrase: Research Terms and Conditions applicability.