feat(readiness): Add shared AWS program library + Kevin's updated program catalog

aws-managed-definitions/README.md

@@ -16,8 +16,8 @@ Out-of-box transformation definitions provided by AWS for common migration and u
 | General | [Codebase Analysis](comprehensive-codebase-analysis/codebase-analysis.md) | Static analysis and documentation for migration planning |
 | Readiness | [Modernization Readiness Analysis](readiness-analysis/modernization-readiness-analysis.md) | Scans portfolios for cloud-native maturity gaps and maps findings to AWS modernization pathways |
 | Readiness | [Agentic Readiness Analysis](readiness-analysis/agentic-readiness-analysis.md) | Evaluates whether systems are ready to be safely called by AI agents — covering APIs, identity, state management, human-in-the-loop, and observability |
-| Readiness | [Portfolio Modernization Readiness](readiness-analysis/portfolio-modernization-readiness.md) | Aggregates per-repo MOD reports into portfolio-level roadmap and cross-cutting analysis |
-| Readiness | [Portfolio Agentic Readiness](readiness-analysis/portfolio-agentic-readiness.md) | Aggregates per-repo ARA reports into portfolio-level cross-cutting analysis |
+| Readiness | [Portfolio Modernization Readiness](readiness-analysis/portfolio-modernization-readiness-analysis.md) | Aggregates per-repo MOD reports into portfolio-level roadmap and cross-cutting analysis |
+| Readiness | [Portfolio Agentic Readiness](readiness-analysis/portfolio-agentic-readiness-analysis.md) | Aggregates per-repo ARA reports into portfolio-level cross-cutting analysis |
 
 ## Directory Structure
 
@@ -44,6 +44,8 @@ aws-managed-definitions/
 └── readiness-analysis/
     ├── modernization-readiness-analysis.md
     ├── agentic-readiness-analysis.md
-    ├── portfolio-modernization-readiness.md
-    └── portfolio-agentic-readiness.md
+    ├── portfolio-modernization-readiness-analysis.md
+    ├── portfolio-agentic-readiness-analysis.md
+    └── references/
+        └── program-library.md   # AWS Program & GTM catalog; loaded by the two portfolio TDs
 ```

aws-managed-definitions/readiness-analysis/agentic-readiness-analysis.md

@@ -1889,6 +1889,15 @@ The complete report structure, for reference:
 ```
 
 
+### Next Steps — Engagement Programs (Portfolio-Level)
+
+This per-repo report intentionally does NOT recommend AWS engagement programs (MAP, EBA, AppMod, AI Assessment, SHIP, ACP, etc.). Program eligibility depends on cross-repo scope, customer segment, ARR, and partner context that a single-repo analysis does not have.
+
+Engagement-level program recommendations are produced by the **Portfolio Agentic Readiness Analysis**, which aggregates all per-repo ARA reports and evaluates them against the shared AWS Program & GTM Library. Run the portfolio TD after all per-repo reports are generated.
+
+Code-level remediation for this repo is captured in the BLOCKERs, RISKs, and INFO sections above.
+
+
 ## Constraints and Guardrails
 
 Strictly follow these rules at all times:
@@ -2200,8 +2209,8 @@ Ordered by severity (High → Medium → Low) then by section order (AUTH → AP
 Source: `remediation_roadmap.items[]`
 
 **Recommended Actions:**
-- Custom Transformation row (always present)
-- AWS Programs subsection: EBA, MAP
+- AWS Transform Custom row (always present) — expand analysis to additional repositories
+- Engagement-program recommendations (MAP, EBA, AppMod, etc.) are NOT produced per-repo; they come from the Portfolio Agentic Readiness Analysis. If no portfolio analysis is available, this subsection shows only the AWS Transform Custom row plus a pointer to run the portfolio TD.
 
 **Agent Deployment Recommendation** (footer block):
 

aws-managed-definitions/readiness-analysis/modernization-readiness-analysis.md

@@ -1719,6 +1719,14 @@ The evidence index compiles all file references cited across the detailed findin
 
 Include every file path that appears in any finding's evidence field. Group by directory for readability if the list exceeds 20 entries.
 
+### Next Steps — Engagement Programs (Portfolio-Level)
+
+This per-repo report intentionally does NOT recommend AWS engagement programs (MAP, OLA, AppMod, EBA, VMCCO, etc.). Program eligibility depends on cross-repo scope, customer segment, ARR, on-prem/migration context, and partner relationships that a single-repo analysis does not have.
+
+Engagement-level program recommendations are produced by the **Portfolio Modernization Readiness Analysis**, which aggregates all per-repo MOD reports and evaluates them against the shared AWS Program & GTM Library. Run the portfolio TD after all per-repo reports are generated.
+
+Modernization guidance for this repo is captured in the pathway detail subsections, top gaps, and detailed findings above.
+
 
 ## Constraints and Guardrails
 
@@ -2184,6 +2192,8 @@ The full visual contract is defined inline below — do NOT reference external f
 - Modernization Recommendation footer block (emoji-headlined with top-3 High-severity recommendations).
 - Footer line (`Generated by AWS Transform · Modernization Readiness Analysis Report`).
 
+> **Note on the "programs" tab / Recommended Actions:** In the per-repo MOD report these render modernization pathways (Move to X) and pathway-mapped learning materials only — NOT AWS engagement programs (MAP, OLA, AppMod, etc.). Engagement-program recommendations are produced exclusively by the Portfolio Modernization Readiness Analysis from the shared AWS Program & GTM Library. The per-repo `recommended_actions` content is limited to AWS Transform Custom (expand-analysis) plus a pointer to run the portfolio TD.
+
 **HTML-escaping discipline.** Every data value rendered in HTML originates from the JSON artifact (MD prose is NOT part of the HTML round-trip contract). All attacker-controlled strings MUST be HTML-escaped before embedding: repo names, evidence file paths, finding titles, finding descriptions, recommendation text, pathway names, and any other string that originates from repository content or from free-text fields in `additionalPlanContext`. Escape `<`, `>`, `&`, `"`, `'` at render time. This is the same escaping discipline applied to the ARA HTML artifact.
 
 #### Slug Derivation