euparliamentmonitor 0.9.16 → 0.9.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -136,7 +136,7 @@ The published site is the audience-facing companion to this npm/TypeScript packa
136
136
 
137
137
  **MCP Server Integration**: The project uses the
138
138
  [European-Parliament-MCP-Server](https://github.com/Hack23/European-Parliament-MCP-Server)
139
- v1.3.6 for accessing real EU Parliament data via the Model Context Protocol.
139
+ v1.3.9 for accessing real EU Parliament data via the Model Context Protocol.
140
140
 
141
141
  - **MCP Server Status**: ✅ Fully operational — 60+ EP data tools available
142
142
  (feeds, direct lookups, analytical tools, intelligence correlation)
@@ -432,7 +432,7 @@ import type { ArticleCategory, LanguageCode } from 'euparliamentmonitor/types';
432
432
 
433
433
  ## 🔌 Data Sources
434
434
 
435
- **Primary — European Parliament MCP Server** ([Hack23/European-Parliament-MCP-Server](https://github.com/Hack23/European-Parliament-MCP-Server) v1.3.6+, fully operational):
435
+ **Primary — European Parliament MCP Server** ([Hack23/European-Parliament-MCP-Server](https://github.com/Hack23/European-Parliament-MCP-Server) v1.3.9+, fully operational):
436
436
 
437
437
  - 🗳️ Plenary sessions, voting records, roll-call votes
438
438
  - 📜 Adopted texts, motions, resolutions, urgency files
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "euparliamentmonitor",
3
- "version": "0.9.16",
3
+ "version": "0.9.17",
4
4
  "type": "module",
5
5
  "description": "European Parliament Intelligence Platform - Monitor political activity with systematic transparency",
6
6
  "main": "scripts/index.js",
@@ -193,7 +193,7 @@
193
193
  "node": ">=26"
194
194
  },
195
195
  "dependencies": {
196
- "european-parliament-mcp-server": "1.3.6",
196
+ "european-parliament-mcp-server": "1.3.9",
197
197
  "markdown-it": "^14.1.1",
198
198
  "markdown-it-anchor": "^9.2.0",
199
199
  "markdown-it-attrs": "^4.3.1",
@@ -168,9 +168,9 @@ export declare class EuropeanParliamentMCPClient extends MCPConnection {
168
168
  *
169
169
  * @remarks
170
170
  * This repository is currently documented/configured against
171
- * `european-parliament-mcp-server@1.3.6`.
171
+ * `european-parliament-mcp-server@1.3.9`.
172
172
  *
173
- * **Upstream date-filter contract (v1.2.14+, active on the pinned v1.3.6 server):** the upstream server
173
+ * **Upstream date-filter contract (v1.2.14+, active on the pinned v1.3.9 server):** the upstream server
174
174
  * applies a server-side post-filter on `dateFrom`/`dateTo` before serialisation, because the
175
175
  * EP Open Data Portal `/meetings` endpoint silently ignores its `date-from`/`date-to` query
176
176
  * parameters (Defect #5). Under this contract:
@@ -179,7 +179,7 @@ export declare class EuropeanParliamentMCPClient extends MCPConnection {
179
179
  * - Per-window session counts are reproducible because the EP-side regression is masked by
180
180
  * the upstream post-filter.
181
181
  *
182
- * No local post-filter is applied here. The repository is pinned to v1.3.6, so the
182
+ * No local post-filter is applied here. The repository is pinned to v1.3.9, so the
183
183
  * date-filter guarantees above apply; consumers running against an older server image
184
184
  * (pre-v1.2.14) must not assume them.
185
185
  */
@@ -405,9 +405,9 @@ export class EuropeanParliamentMCPClient extends MCPConnection {
405
405
  *
406
406
  * @remarks
407
407
  * This repository is currently documented/configured against
408
- * `european-parliament-mcp-server@1.3.6`.
408
+ * `european-parliament-mcp-server@1.3.9`.
409
409
  *
410
- * **Upstream date-filter contract (v1.2.14+, active on the pinned v1.3.6 server):** the upstream server
410
+ * **Upstream date-filter contract (v1.2.14+, active on the pinned v1.3.9 server):** the upstream server
411
411
  * applies a server-side post-filter on `dateFrom`/`dateTo` before serialisation, because the
412
412
  * EP Open Data Portal `/meetings` endpoint silently ignores its `date-from`/`date-to` query
413
413
  * parameters (Defect #5). Under this contract:
@@ -416,7 +416,7 @@ export class EuropeanParliamentMCPClient extends MCPConnection {
416
416
  * - Per-window session counts are reproducible because the EP-side regression is masked by
417
417
  * the upstream post-filter.
418
418
  *
419
- * No local post-filter is applied here. The repository is pinned to v1.3.6, so the
419
+ * No local post-filter is applied here. The repository is pinned to v1.3.9, so the
420
420
  * date-filter guarantees above apply; consumers running against an older server image
421
421
  * (pre-v1.2.14) must not assume them.
422
422
  */
@@ -6,7 +6,7 @@ import type { MCPToolResult } from '../../types/index.js';
6
6
  /**
7
7
  * Classify an error message into a diagnostic error category.
8
8
  *
9
- * Maps EP MCP Server v1.3.6 structured error codes and generic HTTP/network
9
+ * Maps EP MCP Server v1.3.9 structured error codes and generic HTTP/network
10
10
  * errors into one of six broad categories used for logging and retry decisions:
11
11
  *
12
12
  * Returned categories (priority order):
@@ -26,7 +26,7 @@ export declare function classifyToolError(message: string): string;
26
26
  * covering the two shapes historically emitted by the EP MCP server.
27
27
  *
28
28
  * 1. **Uniform envelope** (all feeds as of
29
- * `european-parliament-mcp-server@1.3.6`) —
29
+ * `european-parliament-mcp-server@1.3.9`) —
30
30
  * `{status:"unavailable", items:[], generatedAt:"..."}` established by
31
31
  * Hack23/European-Parliament-MCP-Server#301 and extended to
32
32
  * `get_events_feed`/`get_procedures_feed` by
@@ -4,7 +4,7 @@ import { _parseResultPayload } from './parse.js';
4
4
  /**
5
5
  * Classify an error message into a diagnostic error category.
6
6
  *
7
- * Maps EP MCP Server v1.3.6 structured error codes and generic HTTP/network
7
+ * Maps EP MCP Server v1.3.9 structured error codes and generic HTTP/network
8
8
  * errors into one of six broad categories used for logging and retry decisions:
9
9
  *
10
10
  * Returned categories (priority order):
@@ -55,7 +55,7 @@ export function classifyToolError(message) {
55
55
  * covering the two shapes historically emitted by the EP MCP server.
56
56
  *
57
57
  * 1. **Uniform envelope** (all feeds as of
58
- * `european-parliament-mcp-server@1.3.6`) —
58
+ * `european-parliament-mcp-server@1.3.9`) —
59
59
  * `{status:"unavailable", items:[], generatedAt:"..."}` established by
60
60
  * Hack23/European-Parliament-MCP-Server#301 and extended to
61
61
  * `get_events_feed`/`get_procedures_feed` by