euparliamentmonitor 0.8.41 → 0.8.42

package/README.md

@@ -131,11 +131,11 @@ import {
 
 **MCP Server Integration**: The project uses the
 [European-Parliament-MCP-Server](https://github.com/Hack23/European-Parliament-MCP-Server)
-v1.2.11 for accessing real EU Parliament data via the Model Context Protocol.
+v1.2.13 for accessing real EU Parliament data via the Model Context Protocol.
 
 - **MCP Server Status**: ✅ Fully operational — 60+ EP data tools available
   (feeds, direct lookups, analytical tools, intelligence correlation)
-- **Agentic Workflows**: 10 gh-aw markdown workflows (compiled with
+- **Agentic Workflows**: 18 gh-aw markdown workflows — 8 split-pair article types (`news-<type>-analysis.md` + `news-<type>-article.md`) + `news-article-generator.md` + `news-translate.md` (compiled with
   `gh-aw v0.69.3`) for automated news generation with AI-driven political
   intelligence analysis. See [`.github/workflows/README.md`](.github/workflows/README.md).
 - **Analysis Chain**: 5-stage pipeline (Data → Analysis → Completeness Gate →
@@ -479,7 +479,9 @@ npm run generate-news -- --types=week-ahead --languages=all
 # Generate language-specific index pages
 npm run generate-news-indexes
 
-# Generate sitemap.xml
+# Generate sitemap.xml, sitemap_<lang>.html, and political-intelligence_<lang>.html
+# (14 language-specific sitemap pages + 14 language-specific Political Intelligence
+#  pages that index every methodology, template, and daily analysis run)
 npm run generate-sitemap
 ```
 
@@ -523,7 +525,11 @@ euparliamentmonitor/
 ├── index-{lang}.html                # Language-specific index pages
 ├── typedoc.json                     # TypeDoc configuration
 ├── tsconfig.json                    # TypeScript configuration
-├── sitemap.xml                      # SEO sitemap
+├── sitemap.xml                      # SEO sitemap with hreflang alternates
+├── sitemap.html                     # Human-readable sitemap (English)
+├── sitemap_{lang}.html              # Per-language human-readable sitemaps
+├── political-intelligence.html      # Index of every methodology + template + daily analysis run
+├── political-intelligence_{lang}.html # Localized political-intelligence pages
 └── package.json                     # Project dependencies
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "euparliamentmonitor",
-  "version": "0.8.41",
+  "version": "0.8.42",
   "type": "module",
   "description": "European Parliament Intelligence Platform - Monitor political activity with systematic transparency",
   "main": "scripts/index.js",
@@ -172,7 +172,7 @@
     "node": ">=25"
   },
   "dependencies": {
-    "european-parliament-mcp-server": "1.2.11"
+    "european-parliament-mcp-server": "1.2.13"
   },
   "optionalDependencies": {
     "worldbank-mcp": "1.0.1"

package/scripts/constants/language-ui.d.ts

@@ -191,4 +191,6 @@ export declare const FOOTER_DISCLAIMER_LABELS: LanguageMap;
 export declare const FOOTER_REPORT_ISSUES_LABELS: LanguageMap;
 /** Localized "{count} articles available" stats text used in footer About section */
 export declare const FOOTER_ARTICLES_AVAILABLE_LABELS: LanguageMap;
+/** Localized "Political Intelligence" link label used in footer Quick Links section */
+export declare const FOOTER_POLITICAL_INTELLIGENCE_LABELS: LanguageMap;
 //# sourceMappingURL=language-ui.d.ts.map

package/scripts/constants/language-ui.js

@@ -1849,4 +1849,21 @@ export const FOOTER_ARTICLES_AVAILABLE_LABELS = {
     ko: '{count}개 기사 이용 가능',
     zh: '{count}篇文章可用',
 };
+/** Localized "Political Intelligence" link label used in footer Quick Links section */
+export const FOOTER_POLITICAL_INTELLIGENCE_LABELS = {
+    en: 'Political Intelligence',
+    sv: 'Politisk underrättelse',
+    da: 'Politisk efterretning',
+    no: 'Politisk etterretning',
+    fi: 'Poliittinen tiedustelu',
+    de: 'Politische Aufklärung',
+    fr: 'Intelligence politique',
+    es: 'Inteligencia política',
+    nl: 'Politieke intelligentie',
+    ar: 'الاستخبارات السياسية',
+    he: 'מודיעין פוליטי',
+    ja: '政治インテリジェンス',
+    ko: '정치 정보',
+    zh: '政治情报',
+};
 //# sourceMappingURL=language-ui.js.map

package/scripts/constants/languages.d.ts

@@ -8,7 +8,7 @@
  * - **language-articles** — Article-type title generators and body-text strings
  */
 export { ALL_LANGUAGES, LANGUAGE_PRESETS, LANGUAGE_FLAGS, LANGUAGE_NAMES, getLocalizedString, isSupportedLanguage, getTextDirection, } from './language-core.js';
-export { PAGE_TITLES, PAGE_DESCRIPTIONS, SECTION_HEADINGS, NO_ARTICLES_MESSAGES, SKIP_LINK_TEXTS, ARTICLE_TYPE_LABELS, READ_TIME_LABELS, BACK_TO_NEWS_LABELS, ARTICLE_NAV_LABELS, RELATED_ARTICLES_NAV_LABELS, BREADCRUMB_HOME_LABELS, BREADCRUMB_NEWS_LABELS, TIMELINE_HEADINGS, COMPARISON_BEFORE_LABELS, COMPARISON_AFTER_LABELS, KEY_FIGURES_HEADINGS, AI_SECTION_CONTENT, FILTER_LABELS, SOURCES_HEADING_LABELS, HEADER_SUBTITLE_LABELS, THEME_TOGGLE_LABELS, FOOTER_ABOUT_HEADING_LABELS, FOOTER_ABOUT_TEXT_LABELS, FOOTER_QUICK_LINKS_LABELS, FOOTER_BUILT_BY_LABELS, FOOTER_LANGUAGES_LABELS, FOOTER_HOME_LABELS, FOOTER_SITEMAP_LABELS, FOOTER_RSS_LABELS, FOOTER_GITHUB_REPO_LABELS, FOOTER_LICENSE_LABELS, FOOTER_EUROPARL_LABELS, FOOTER_LINKEDIN_LABELS, FOOTER_SECURITY_POLICY_LABELS, FOOTER_CONTACT_LABELS, FOOTER_DISCLAIMER_LABELS, FOOTER_REPORT_ISSUES_LABELS, FOOTER_ARTICLES_AVAILABLE_LABELS, TOC_ARIA_LABELS, RELATED_ANALYSIS_LABELS, ANALYSIS_TRANSPARENCY_LABELS, ANALYSIS_SUMMARY_LABELS, METHODOLOGY_LABELS, TRANSPARENCY_DISCLOSURE_LABELS, CLASSIFICATION_ANALYSIS_LABELS, THREAT_ASSESSMENT_LABELS, RISK_SCORING_LABELS, DEEP_ANALYSIS_LABELS, VIEW_SOURCE_LABELS, OPEN_SOURCE_NOTE_LABELS, AI_ANALYSIS_GUIDE_LABELS, SWOT_FRAMEWORK_LABELS, RISK_METHODOLOGY_LABELS, THREAT_FRAMEWORK_LABELS, CLASSIFICATION_GUIDE_LABELS, STYLE_GUIDE_LABELS, SIGNIFICANCE_CLASSIFICATION_LABELS, ACTOR_MAPPING_LABELS, FORCES_ANALYSIS_LABELS, IMPACT_MATRIX_LABELS, POLITICAL_THREAT_LANDSCAPE_LABELS, ACTOR_THREAT_PROFILING_LABELS, CONSEQUENCE_TREES_LABELS, LEGISLATIVE_DISRUPTION_LABELS, RISK_MATRIX_LABELS, QUANTITATIVE_SWOT_LABELS, POLITICAL_CAPITAL_RISK_LABELS, LEGISLATIVE_VELOCITY_RISK_LABELS, AGENT_RISK_WORKFLOW_LABELS, STAKEHOLDER_IMPACT_LABELS, COALITION_DYNAMICS_LABELS, VOTING_PATTERNS_LABELS, CROSS_SESSION_INTELLIGENCE_LABELS, SYNTHESIS_SUMMARY_LABELS, DOCUMENT_ANALYSIS_LABELS, SIGNIFICANCE_SCORING_LABELS, } from './language-ui.js';
+export { PAGE_TITLES, PAGE_DESCRIPTIONS, SECTION_HEADINGS, NO_ARTICLES_MESSAGES, SKIP_LINK_TEXTS, ARTICLE_TYPE_LABELS, READ_TIME_LABELS, BACK_TO_NEWS_LABELS, ARTICLE_NAV_LABELS, RELATED_ARTICLES_NAV_LABELS, BREADCRUMB_HOME_LABELS, BREADCRUMB_NEWS_LABELS, TIMELINE_HEADINGS, COMPARISON_BEFORE_LABELS, COMPARISON_AFTER_LABELS, KEY_FIGURES_HEADINGS, AI_SECTION_CONTENT, FILTER_LABELS, SOURCES_HEADING_LABELS, HEADER_SUBTITLE_LABELS, THEME_TOGGLE_LABELS, FOOTER_ABOUT_HEADING_LABELS, FOOTER_ABOUT_TEXT_LABELS, FOOTER_QUICK_LINKS_LABELS, FOOTER_BUILT_BY_LABELS, FOOTER_LANGUAGES_LABELS, FOOTER_HOME_LABELS, FOOTER_SITEMAP_LABELS, FOOTER_RSS_LABELS, FOOTER_GITHUB_REPO_LABELS, FOOTER_LICENSE_LABELS, FOOTER_EUROPARL_LABELS, FOOTER_LINKEDIN_LABELS, FOOTER_SECURITY_POLICY_LABELS, FOOTER_CONTACT_LABELS, FOOTER_DISCLAIMER_LABELS, FOOTER_REPORT_ISSUES_LABELS, FOOTER_ARTICLES_AVAILABLE_LABELS, FOOTER_POLITICAL_INTELLIGENCE_LABELS, TOC_ARIA_LABELS, RELATED_ANALYSIS_LABELS, ANALYSIS_TRANSPARENCY_LABELS, ANALYSIS_SUMMARY_LABELS, METHODOLOGY_LABELS, TRANSPARENCY_DISCLOSURE_LABELS, CLASSIFICATION_ANALYSIS_LABELS, THREAT_ASSESSMENT_LABELS, RISK_SCORING_LABELS, DEEP_ANALYSIS_LABELS, VIEW_SOURCE_LABELS, OPEN_SOURCE_NOTE_LABELS, AI_ANALYSIS_GUIDE_LABELS, SWOT_FRAMEWORK_LABELS, RISK_METHODOLOGY_LABELS, THREAT_FRAMEWORK_LABELS, CLASSIFICATION_GUIDE_LABELS, STYLE_GUIDE_LABELS, SIGNIFICANCE_CLASSIFICATION_LABELS, ACTOR_MAPPING_LABELS, FORCES_ANALYSIS_LABELS, IMPACT_MATRIX_LABELS, POLITICAL_THREAT_LANDSCAPE_LABELS, ACTOR_THREAT_PROFILING_LABELS, CONSEQUENCE_TREES_LABELS, LEGISLATIVE_DISRUPTION_LABELS, RISK_MATRIX_LABELS, QUANTITATIVE_SWOT_LABELS, POLITICAL_CAPITAL_RISK_LABELS, LEGISLATIVE_VELOCITY_RISK_LABELS, AGENT_RISK_WORKFLOW_LABELS, STAKEHOLDER_IMPACT_LABELS, COALITION_DYNAMICS_LABELS, VOTING_PATTERNS_LABELS, CROSS_SESSION_INTELLIGENCE_LABELS, SYNTHESIS_SUMMARY_LABELS, DOCUMENT_ANALYSIS_LABELS, SIGNIFICANCE_SCORING_LABELS, } from './language-ui.js';
 export type { AISection, RelationshipLabels, RelatedAnalysisStrings } from './language-ui.js';
 export { WEEK_AHEAD_TITLES, MONTH_AHEAD_TITLES, WEEKLY_REVIEW_TITLES, MONTHLY_REVIEW_TITLES, MOTIONS_TITLES, BREAKING_NEWS_TITLES, COMMITTEE_REPORTS_TITLES, PROPOSITIONS_TITLES, PROPOSITIONS_STRINGS, EDITORIAL_STRINGS, MOTIONS_STRINGS, WEEK_AHEAD_STRINGS, WEEK_AHEAD_STAKEHOLDER_STRINGS, BREAKING_STRINGS, DEEP_ANALYSIS_STRINGS, COMMITTEE_ANALYSIS_CONTENT_STRINGS, SWOT_STRINGS, DASHBOARD_STRINGS, SWOT_BUILDER_STRINGS, DASHBOARD_BUILDER_STRINGS, LOCALIZED_KEYWORDS, MONTH_IN_REVIEW_STRINGS, ANALYSIS_QUALITY_LABELS, ANALYSIS_INSIGHTS_HEADING, } from './language-articles.js';
 //# sourceMappingURL=languages.d.ts.map

package/scripts/constants/languages.js

@@ -10,6 +10,6 @@
  * - **language-articles** — Article-type title generators and body-text strings
  */
 export { ALL_LANGUAGES, LANGUAGE_PRESETS, LANGUAGE_FLAGS, LANGUAGE_NAMES, getLocalizedString, isSupportedLanguage, getTextDirection, } from './language-core.js';
-export { PAGE_TITLES, PAGE_DESCRIPTIONS, SECTION_HEADINGS, NO_ARTICLES_MESSAGES, SKIP_LINK_TEXTS, ARTICLE_TYPE_LABELS, READ_TIME_LABELS, BACK_TO_NEWS_LABELS, ARTICLE_NAV_LABELS, RELATED_ARTICLES_NAV_LABELS, BREADCRUMB_HOME_LABELS, BREADCRUMB_NEWS_LABELS, TIMELINE_HEADINGS, COMPARISON_BEFORE_LABELS, COMPARISON_AFTER_LABELS, KEY_FIGURES_HEADINGS, AI_SECTION_CONTENT, FILTER_LABELS, SOURCES_HEADING_LABELS, HEADER_SUBTITLE_LABELS, THEME_TOGGLE_LABELS, FOOTER_ABOUT_HEADING_LABELS, FOOTER_ABOUT_TEXT_LABELS, FOOTER_QUICK_LINKS_LABELS, FOOTER_BUILT_BY_LABELS, FOOTER_LANGUAGES_LABELS, FOOTER_HOME_LABELS, FOOTER_SITEMAP_LABELS, FOOTER_RSS_LABELS, FOOTER_GITHUB_REPO_LABELS, FOOTER_LICENSE_LABELS, FOOTER_EUROPARL_LABELS, FOOTER_LINKEDIN_LABELS, FOOTER_SECURITY_POLICY_LABELS, FOOTER_CONTACT_LABELS, FOOTER_DISCLAIMER_LABELS, FOOTER_REPORT_ISSUES_LABELS, FOOTER_ARTICLES_AVAILABLE_LABELS, TOC_ARIA_LABELS, RELATED_ANALYSIS_LABELS, ANALYSIS_TRANSPARENCY_LABELS, ANALYSIS_SUMMARY_LABELS, METHODOLOGY_LABELS, TRANSPARENCY_DISCLOSURE_LABELS, CLASSIFICATION_ANALYSIS_LABELS, THREAT_ASSESSMENT_LABELS, RISK_SCORING_LABELS, DEEP_ANALYSIS_LABELS, VIEW_SOURCE_LABELS, OPEN_SOURCE_NOTE_LABELS, AI_ANALYSIS_GUIDE_LABELS, SWOT_FRAMEWORK_LABELS, RISK_METHODOLOGY_LABELS, THREAT_FRAMEWORK_LABELS, CLASSIFICATION_GUIDE_LABELS, STYLE_GUIDE_LABELS, SIGNIFICANCE_CLASSIFICATION_LABELS, ACTOR_MAPPING_LABELS, FORCES_ANALYSIS_LABELS, IMPACT_MATRIX_LABELS, POLITICAL_THREAT_LANDSCAPE_LABELS, ACTOR_THREAT_PROFILING_LABELS, CONSEQUENCE_TREES_LABELS, LEGISLATIVE_DISRUPTION_LABELS, RISK_MATRIX_LABELS, QUANTITATIVE_SWOT_LABELS, POLITICAL_CAPITAL_RISK_LABELS, LEGISLATIVE_VELOCITY_RISK_LABELS, AGENT_RISK_WORKFLOW_LABELS, STAKEHOLDER_IMPACT_LABELS, COALITION_DYNAMICS_LABELS, VOTING_PATTERNS_LABELS, CROSS_SESSION_INTELLIGENCE_LABELS, SYNTHESIS_SUMMARY_LABELS, DOCUMENT_ANALYSIS_LABELS, SIGNIFICANCE_SCORING_LABELS, } from './language-ui.js';
+export { PAGE_TITLES, PAGE_DESCRIPTIONS, SECTION_HEADINGS, NO_ARTICLES_MESSAGES, SKIP_LINK_TEXTS, ARTICLE_TYPE_LABELS, READ_TIME_LABELS, BACK_TO_NEWS_LABELS, ARTICLE_NAV_LABELS, RELATED_ARTICLES_NAV_LABELS, BREADCRUMB_HOME_LABELS, BREADCRUMB_NEWS_LABELS, TIMELINE_HEADINGS, COMPARISON_BEFORE_LABELS, COMPARISON_AFTER_LABELS, KEY_FIGURES_HEADINGS, AI_SECTION_CONTENT, FILTER_LABELS, SOURCES_HEADING_LABELS, HEADER_SUBTITLE_LABELS, THEME_TOGGLE_LABELS, FOOTER_ABOUT_HEADING_LABELS, FOOTER_ABOUT_TEXT_LABELS, FOOTER_QUICK_LINKS_LABELS, FOOTER_BUILT_BY_LABELS, FOOTER_LANGUAGES_LABELS, FOOTER_HOME_LABELS, FOOTER_SITEMAP_LABELS, FOOTER_RSS_LABELS, FOOTER_GITHUB_REPO_LABELS, FOOTER_LICENSE_LABELS, FOOTER_EUROPARL_LABELS, FOOTER_LINKEDIN_LABELS, FOOTER_SECURITY_POLICY_LABELS, FOOTER_CONTACT_LABELS, FOOTER_DISCLAIMER_LABELS, FOOTER_REPORT_ISSUES_LABELS, FOOTER_ARTICLES_AVAILABLE_LABELS, FOOTER_POLITICAL_INTELLIGENCE_LABELS, TOC_ARIA_LABELS, RELATED_ANALYSIS_LABELS, ANALYSIS_TRANSPARENCY_LABELS, ANALYSIS_SUMMARY_LABELS, METHODOLOGY_LABELS, TRANSPARENCY_DISCLOSURE_LABELS, CLASSIFICATION_ANALYSIS_LABELS, THREAT_ASSESSMENT_LABELS, RISK_SCORING_LABELS, DEEP_ANALYSIS_LABELS, VIEW_SOURCE_LABELS, OPEN_SOURCE_NOTE_LABELS, AI_ANALYSIS_GUIDE_LABELS, SWOT_FRAMEWORK_LABELS, RISK_METHODOLOGY_LABELS, THREAT_FRAMEWORK_LABELS, CLASSIFICATION_GUIDE_LABELS, STYLE_GUIDE_LABELS, SIGNIFICANCE_CLASSIFICATION_LABELS, ACTOR_MAPPING_LABELS, FORCES_ANALYSIS_LABELS, IMPACT_MATRIX_LABELS, POLITICAL_THREAT_LANDSCAPE_LABELS, ACTOR_THREAT_PROFILING_LABELS, CONSEQUENCE_TREES_LABELS, LEGISLATIVE_DISRUPTION_LABELS, RISK_MATRIX_LABELS, QUANTITATIVE_SWOT_LABELS, POLITICAL_CAPITAL_RISK_LABELS, LEGISLATIVE_VELOCITY_RISK_LABELS, AGENT_RISK_WORKFLOW_LABELS, STAKEHOLDER_IMPACT_LABELS, COALITION_DYNAMICS_LABELS, VOTING_PATTERNS_LABELS, CROSS_SESSION_INTELLIGENCE_LABELS, SYNTHESIS_SUMMARY_LABELS, DOCUMENT_ANALYSIS_LABELS, SIGNIFICANCE_SCORING_LABELS, } from './language-ui.js';
 export { WEEK_AHEAD_TITLES, MONTH_AHEAD_TITLES, WEEKLY_REVIEW_TITLES, MONTHLY_REVIEW_TITLES, MOTIONS_TITLES, BREAKING_NEWS_TITLES, COMMITTEE_REPORTS_TITLES, PROPOSITIONS_TITLES, PROPOSITIONS_STRINGS, EDITORIAL_STRINGS, MOTIONS_STRINGS, WEEK_AHEAD_STRINGS, WEEK_AHEAD_STAKEHOLDER_STRINGS, BREAKING_STRINGS, DEEP_ANALYSIS_STRINGS, COMMITTEE_ANALYSIS_CONTENT_STRINGS, SWOT_STRINGS, DASHBOARD_STRINGS, SWOT_BUILDER_STRINGS, DASHBOARD_BUILDER_STRINGS, LOCALIZED_KEYWORDS, MONTH_IN_REVIEW_STRINGS, ANALYSIS_QUALITY_LABELS, ANALYSIS_INSIGHTS_HEADING, } from './language-articles.js';
 //# sourceMappingURL=languages.js.map

package/scripts/generators/news-enhanced.js

@@ -49,7 +49,7 @@ import { ensureDirectoryExists } from '../utils/file-utils.js';
 import { initializeMCPClient, fetchEPFeedData } from './pipeline/fetch-stage.js';
 import { createStrategyRegistry, generateArticleForStrategy, setAIMetadata, } from './pipeline/generate-stage.js';
 import { writeGenerationMetadata } from './pipeline/output-stage.js';
-import { runAnalysisStage, ALL_ANALYSIS_METHODS, VALID_ANALYSIS_METHODS, hasSubstantiveData, deriveArticleTypeSlug, } from './pipeline/analysis-stage.js';
+import { runAnalysisStage, ALL_ANALYSIS_METHODS, VALID_ANALYSIS_METHODS, hasSubstantiveData, deriveArticleTypeSlug, isResolvedAnalysisDir, } from './pipeline/analysis-stage.js';
 import { discoverAnalysisFileEntries } from '../utils/file-utils.js';
 // ─── Content-module imports (bounded contexts) ───────────────────────────────
 import { parsePlenarySessions, parseEPEvents, parseCommitteeMeetings, parseLegislativeDocuments, parseLegislativePipeline, parseParliamentaryQuestions, buildWeekAheadContent, buildKeywords, PLACEHOLDER_EVENTS, buildWhatToWatchSection, buildStakeholderImpactMatrix, computeWeekPoliticalTemperature, } from './week-ahead-content.js';
@@ -208,6 +208,56 @@ function parseAnalysisMethods() {
     }
     return methods;
 }
+/**
+ * Fetch EP feed data (month-level timeframe for month-level article types,
+ * one-week otherwise), populate `fetchedData` with the result, and enforce
+ * the "substantive data required" check.
+ *
+ * Extracted from {@link maybeRunAnalysis} to keep that function's cognitive
+ * complexity under the repo's SonarJS limit. Mutates `fetchedData` in place
+ * and throws when no substantive EP data is available.
+ *
+ * @param fetchedData - Target record to populate (mutated)
+ * @param client - Connected MCP client or null
+ * @param articleTypes - Requested article types (drives timeframe selection)
+ */
+async function fetchAndValidateEPData(fetchedData, client, articleTypes) {
+    const MONTH_LEVEL_TYPES = ['month-ahead', 'month-in-review', 'committee-reports', 'motions'];
+    const needsMonthData = articleTypes
+        .map((t) => t.trim())
+        .some((t) => MONTH_LEVEL_TYPES.includes(t));
+    const feedTimeframe = needsMonthData ? 'one-month' : 'one-week';
+    // fetchEPFeedData handles a null client gracefully (returns undefined) and
+    // also loads from EP_FEED_DATA_FILE when set, so we call it unconditionally.
+    const feedData = await fetchEPFeedData(client, feedTimeframe);
+    if (feedData) {
+        fetchedData['events'] = feedData.events ?? [];
+        fetchedData['documents'] = feedData.documents ?? [];
+        fetchedData['adoptedTexts'] = feedData.adoptedTexts ?? [];
+        fetchedData['procedures'] = feedData.procedures ?? [];
+        fetchedData['mepUpdates'] = feedData.mepUpdates ?? [];
+        fetchedData['plenaryDocuments'] = feedData.plenaryDocuments ?? [];
+        fetchedData['committeeDocuments'] = feedData.committeeDocuments ?? [];
+        fetchedData['plenarySessionDocuments'] = feedData.plenarySessionDocuments ?? [];
+        fetchedData['externalDocuments'] = feedData.externalDocuments ?? [];
+        fetchedData['questions'] = feedData.questions ?? [];
+        fetchedData['declarations'] = feedData.declarations ?? [];
+        fetchedData['corporateBodies'] = feedData.corporateBodies ?? [];
+    }
+    if (!fetchedData['events']) {
+        // No MCP or feed-data file available — populate empty arrays so builders don't fail
+        fetchedData['events'] = [];
+        fetchedData['sessions'] = [];
+        fetchedData['documents'] = [];
+    }
+    // Agentic workflows must not proceed with empty data — analysis on empty
+    // data produces hollow output that should never feed article generation.
+    if (!hasSubstantiveData(fetchedData)) {
+        throw new Error('❌ Analysis aborted: no substantive EP data was fetched. ' +
+            'MCP data fetch must succeed before analysis can run. ' +
+            'Check MCP connection, feed data file, or EP API availability.');
+    }
+}
 /**
  * Run the analysis discovery stage (Fetch → Discover) before article generation.
  *
@@ -248,16 +298,24 @@ async function maybeRunAnalysis(date, client) {
     console.log(`   Output dir: ${analysisDirBase}/${date}`);
     console.log(`   Methods: ${enabledMethods.length} enabled`);
     console.log('');
-    // Derive the feed timeframe from the requested article types so the analysis
-    // window matches the generation window.  Month-level types need 'one-month'.
-    const MONTH_LEVEL_TYPES = ['month-ahead', 'month-in-review', 'committee-reports', 'motions'];
-    const normalizedArticleTypes = articleTypes.map((t) => t.trim());
-    const needsMonthData = normalizedArticleTypes.some((t) => MONTH_LEVEL_TYPES.includes(t));
-    const feedTimeframe = needsMonthData ? 'one-month' : 'one-week';
-    // Fetch comprehensive EP feed data.  fetchEPFeedData handles a null client
-    // gracefully (returns undefined) and also loads from EP_FEED_DATA_FILE when
-    // set, so we call it unconditionally.
-    //
+    // Detect whether `--analysis-dir` already points at a fully-resolved
+    // per-run analysis directory (agentic workflows pre-populate
+    // `analysis/daily/<date>/<slug>-run<N>` with AI-authored artifacts and
+    // pass it verbatim).  When so, honour the path as-is; otherwise treat it
+    // as a base and compose `<base>/<date>/<slug>` below.
+    const analysisDirIsResolved = isResolvedAnalysisDir(analysisDirBase);
+    if (analysisDirIsResolved) {
+        console.log(`   Analysis dir treated as pre-resolved run directory`);
+    }
+    // Short-circuit for `--analysis-only` wrap-up on a pre-resolved dir:
+    // the agent has already completed Stage A (data collection) and Stage B
+    // (artifact authoring); runAnalysisStage with outputDirIsResolved=true
+    // performs pure filesystem discovery and does not need EP data.  Skip
+    // the expensive fetchEPFeedData call — a slow one-month feed pull here
+    // can hang the pipeline wrap-up long enough for the safeoutputs MCP
+    // session to expire, which then blocks PR creation (see failed run
+    // #24802174815 for the cascade).
+    const skipDataFetch = analysisOnlyArg && analysisDirIsResolved;
     // Always initialise voting-derived keys (`patterns`, `votingRecords`) to
     // empty arrays so coalition/voting/cross-session analyses never receive
     // undefined.  These feeds are not yet exposed by fetchEPFeedData, so they
@@ -267,37 +325,19 @@ async function maybeRunAnalysis(date, client) {
         patterns: [],
         votingRecords: [],
     };
-    const feedData = await fetchEPFeedData(client, feedTimeframe);
-    if (feedData) {
-        fetchedData['events'] = feedData.events ?? [];
-        fetchedData['documents'] = feedData.documents ?? [];
-        fetchedData['adoptedTexts'] = feedData.adoptedTexts ?? [];
-        fetchedData['procedures'] = feedData.procedures ?? [];
-        fetchedData['mepUpdates'] = feedData.mepUpdates ?? [];
-        fetchedData['plenaryDocuments'] = feedData.plenaryDocuments ?? [];
-        fetchedData['committeeDocuments'] = feedData.committeeDocuments ?? [];
-        fetchedData['plenarySessionDocuments'] = feedData.plenarySessionDocuments ?? [];
-        fetchedData['externalDocuments'] = feedData.externalDocuments ?? [];
-        fetchedData['questions'] = feedData.questions ?? [];
-        fetchedData['declarations'] = feedData.declarations ?? [];
-        fetchedData['corporateBodies'] = feedData.corporateBodies ?? [];
-    }
-    if (!fetchedData['events']) {
-        // No MCP or feed-data file available — populate empty arrays so builders don't fail
+    if (skipDataFetch) {
+        console.log(`   Skipping EP data fetch — --analysis-only wrap-up on pre-resolved dir (agent owns Stage A/B)`);
+        // Populate empty arrays so downstream builders don't trip on undefined.
         fetchedData['events'] = [];
         fetchedData['sessions'] = [];
         fetchedData['documents'] = [];
     }
-    // Validate that substantive EP data was actually fetched.
-    // Agentic workflows must not proceed with empty data — analysis on empty
-    // data produces hollow output that should never feed article generation.
-    if (!hasSubstantiveData(fetchedData)) {
-        const msg = '❌ Analysis aborted: no substantive EP data was fetched. ' +
-            'MCP data fetch must succeed before analysis can run. ' +
-            'Check MCP connection, feed data file, or EP API availability.';
-        throw new Error(msg);
+    else {
+        await fetchAndValidateEPData(fetchedData, client, articleTypes);
     }
-    const validArticleTypes = normalizedArticleTypes.filter((t) => VALID_ARTICLE_CATEGORIES.includes(t));
+    const validArticleTypes = articleTypes
+        .map((t) => t.trim())
+        .filter((t) => VALID_ARTICLE_CATEGORIES.includes(t));
     // Derive a slug from the article types to scope analysis output per workflow,
     // preventing merge conflicts when multiple workflows run on the same date.
     // When a run ID is provided (e.g. GITHUB_RUN_NUMBER), append it to the slug
@@ -308,8 +348,8 @@ async function maybeRunAnalysis(date, client) {
     console.log(`   Article type slug: ${slug}`);
     if (runId)
         console.log(`   Run ID: ${runId}`);
-    // Pass requireData=true so runAnalysisStage enforces data availability
-    // and aborts when no substantive data is available — discovery on empty data produces no artifacts.
+    // Require data only when we actually fetched it.  The pre-resolved
+    // --analysis-only wrap-up path performs discovery-only and needs no data.
     const ctx = await runAnalysisStage(fetchedData, {
         articleTypes: validArticleTypes,
         date,
@@ -318,7 +358,8 @@ async function maybeRunAnalysis(date, client) {
         enabledMethods,
         skipCompleted: true,
         verbose: analysisVerboseArg,
-        requireData: true,
+        requireData: !skipDataFetch,
+        outputDirIsResolved: analysisDirIsResolved,
     });
     const totalMethods = ctx.manifest.methods.length;
     const completedCount = ctx.manifest.methods.filter((method) => method.status === 'completed').length;

package/scripts/generators/pipeline/analysis-stage.d.ts

@@ -1,5 +1,6 @@
 import type { ArticleCategory } from '../../types/index.js';
 import type { ConfidenceLevel } from '../../types/index.js';
+import { type AnalysisManifestHistoryEntry } from '../../utils/file-utils.js';
 /**
  * Union type of all recognised analysis method identifiers.
  */
@@ -34,7 +35,44 @@ export interface AnalysisStageOptions {
      * Retained for backward compatibility with agentic workflow invocations.
      */
     readonly requireData?: boolean;
+    /**
+     * When true, treat {@link AnalysisStageOptions.outputDir} as a fully
+     * resolved analysis directory and skip the `<outputDir>/<date>/<slug>`
+     * composition.
+     *
+     * This supports agentic workflows that pre-populate a per-run directory
+     * (e.g. `analysis/daily/<date>/<slug>-run<N>`) with AI-authored artifacts
+     * and then invoke `news-enhanced.ts --analysis-dir=<that dir>` for the
+     * discovery + article-generation phase.
+     */
+    readonly outputDirIsResolved?: boolean;
+    /**
+     * Optional stable run identifier used to record a history entry in the
+     * manifest when `outputDirIsResolved` is true. Enables repeated analysis
+     * runs against the same `analysis/daily/${DATE}/${TYPE}/` folder to
+     * accumulate an audit trail via `manifest.json.history[]` instead of
+     * triggering the `-2` suffix. When unset, a UUID-based run id is used.
+     */
+    readonly runId?: string;
+    /**
+     * Optional Stage-C gate result recorded in the manifest history entry
+     * written after discovery. Defaults to `'PENDING'` — the Stage-C
+     * validator or the caller updates this later.
+     */
+    readonly gateResult?: AnalysisManifestHistoryEntry['gateResult'];
 }
+/**
+ * Detect whether `candidate` looks like a pre-populated, fully-resolved
+ * analysis run directory.
+ *
+ * Returns `true` when the directory exists AND either contains a
+ * `manifest.json` from a prior run or at least one of the canonical
+ * analysis subdirectories in {@link RESOLVED_ANALYSIS_SUBDIRS}.
+ *
+ * @param candidate - Directory path to inspect.
+ * @returns `true` when the directory is a resolved analysis run dir.
+ */
+export declare function isResolvedAnalysisDir(candidate: string): boolean;
 /** Status record written into the manifest for each method */
 export interface AnalysisMethodStatus {
     readonly method: AnalysisMethod;
@@ -44,15 +82,60 @@ export interface AnalysisMethodStatus {
     readonly duration: number;
     readonly summary: string;
 }
+/**
+ * `manifest.files.*` structure — artifact paths grouped by subdirectory.
+ *
+ * Mirrors the shape consumed by
+ * `src/utils/validate-analysis-completeness.ts:extractListedPaths` (nested
+ * `{ category: string[] }` variant). Each key is the first path segment of
+ * an artifact's relative path (e.g. `intelligence`, `classification`,
+ * `risk-scoring`), and the value is the list of relative paths under that
+ * subdir.
+ *
+ * Hyphenated keys (e.g. `risk-scoring`, `threat-assessment`) match the
+ * canonical on-disk subdirectory names defined in
+ * `scripts/resolve-analysis-dir.sh` and `DISCOVERY_SUBDIRS` /
+ * `RESOLVED_ANALYSIS_SUBDIRS`. They must be quoted in TypeScript because
+ * `-` is not a valid identifier character.
+ */
+export interface AnalysisManifestFiles {
+    readonly classification?: readonly string[];
+    readonly 'risk-scoring'?: readonly string[];
+    readonly 'threat-assessment'?: readonly string[];
+    readonly intelligence?: readonly string[];
+    readonly documents?: readonly string[];
+    readonly existing?: readonly string[];
+    readonly data?: readonly string[];
+    readonly runs?: readonly string[];
+    readonly [key: string]: readonly string[] | undefined;
+}
 /** Metadata record written to manifest.json for each analysis run */
 export interface AnalysisManifest {
     readonly runId: string;
     readonly date: string;
+    /**
+     * Top-level article-type slug (e.g. `committee-reports`, `breaking`).
+     *
+     * Required by the Stage-C completeness gate (see
+     * `03-analysis-completeness-gate.md` §2 item 8 and
+     * `src/utils/validate-analysis-completeness.ts:loadManifest`). Kept in
+     * addition to the legacy `articleTypeSlug` field for backward compatibility.
+     */
+    readonly articleType?: string | undefined;
     readonly articleTypeSlug?: string | undefined;
     readonly startTime: string;
     readonly endTime: string;
     readonly articleTypes: readonly ArticleCategory[];
     readonly methods: readonly AnalysisMethodStatus[];
+    /**
+     * Artifact paths grouped by subdirectory (e.g.
+     * `{ intelligence: ['intelligence/pestle-analysis.md', ...] }`).
+     *
+     * Required by the Stage-C completeness gate — see
+     * `src/utils/validate-analysis-completeness.ts:loadManifest` which rejects
+     * any manifest without a top-level `files` object.
+     */
+    readonly files?: AnalysisManifestFiles;
     readonly overallConfidence: ConfidenceLevel;
     readonly dataSourcesUsed: readonly string[];
     readonly documentsAnalyzed?: number;
@@ -92,6 +175,12 @@ export declare function deriveArticleTypeSlug(articleTypes: readonly (ArticleCat
  * (if one doesn't already exist) so downstream consumers that check for
  * the manifest continue to work.
  *
+ * When `options.outputDirIsResolved` is true, `outputDir` is honoured
+ * verbatim and the uniqueness-suffix step is bypassed — agentic workflows
+ * pre-populate `analysis/daily/<date>/<slug>-run<N>/` with `manifest.json`
+ * plus artifacts during Stage B, and discovery must consume that exact
+ * path rather than being redirected to a `-2` suffix.
+ *
  * @param fetchedData - Raw EP data (used only for the requireData check)
  * @param options - Analysis stage configuration
  * @returns Analysis context with discovered methods