paput-mcp 4.2.1 → 4.2.3

package/dist/cli/skills/paput-dashboard-analysis/SKILL.md

@@ -1,12 +1,14 @@
 ---
 name: paput-dashboard-analysis
-description: Use this to analyze the user's PaPut dashboard, goals, skill sheet, memos, notes, and categories; identify current position, strengths, growing areas, thin areas, missing knowledge, next knowledge to learn, and career-history phrasing; optionally save the generated dashboard analysis when the user asks to save it.
+description: Use this to analyze the user's PaPut dashboard, goals, skill sheet, memos, notes, and categories. Read the user through the judgment axis — the thickness of their decision / operation / principle memos — not raw volume or category counts; identify current position, strengths, thin axes, what to learn next, and career-history phrasing; optionally save the generated dashboard analysis when the user asks to save it.
 ---
 
 # PaPut Dashboard Analysis
 
 Analyze the user's PaPut dashboard and goals. Use this skill when the user asks about dashboard analysis, goals, progress, strengths, weak areas, next learning topics, or career-history phrasing.
 
+Read the user through the JUDGMENT axis, not raw volume. The durable, hard-to-commoditize part of what they accumulate is their judgment and practice — captured as `memo_type`: `decision` (judgment criteria), `operation` (operating practices), `principle` (stated stances). `knowledge` is commodity. `structuredContent.dashboard_summary.memo_type_counts` holds the per-type accumulation; assess the user by how thick those three durable axes are, with categories as a secondary lens for the domains they work in.
+
 ## Workflow
 
 1. Call `paput_get_dashboard_analysis_context`.
@@ -17,15 +19,15 @@ Analyze the user's PaPut dashboard and goals. Use this skill when the user asks
 
 ## Analysis Points
 
-Include these points when relevant:
+Include these points when relevant, read through the decision / operation / principle axes:
 
-- Current position
-- Areas that can be presented as strengths
-- Areas that have been growing recently
-- Thin or underdeveloped areas
-- Knowledge missing against active goals
-- Knowledge to learn next
-- Phrasing suitable for a skill sheet or career history
+- Current position — which judgment axes are thick, which are thin (from `memo_type_counts`).
+- Strengths — the judgment criteria and operating practices the user has accumulated (decision / operation / principle), with the domains (categories) they show up in as supporting context. knowledge alone is not a strength.
+- Areas that have been growing recently.
+- Thin or underdeveloped axes — name the thin memo_type (e.g. principle is thin) and what that means, not just thin categories.
+- Knowledge missing against active goals.
+- What to do next to thicken the thin durable axis (e.g. distill recurring decisions into principles, capture operating practices / eval / review as operation), rather than just "learn more".
+- Phrasing suitable for a skill sheet or career history.
 
 ## Rules
 
@@ -33,8 +35,10 @@ Include these points when relevant:
 - Use active goals as the main analysis basis.
 - Treat archived goals as historical context.
 - Do not recalculate dashboard continuity from activities. Use the dashboard summary values returned by the API.
-- Do not assume the user should write memos next.
-- Focus on how knowledge naturally accumulated through daily development can grow toward the user's goals.
+- Frame current position, strengths, and thin areas by decision / operation / principle thickness — not by how many memos or categories accumulated. Use categories as a secondary lens for the domains, not the main axis.
+- `knowledge`-type memos are commodity. Do not present knowledge volume as a strength on its own.
+- When the thin axis is `principle` or `operation`, say so plainly and make the next step about thickening it (distilling decisions into principles, capturing eval / observability / review as operation).
+- In each saved item's `description`, speak in the judgment/practice/principle axis (which memo_type backs the strength, which type is thin). The output fields are unchanged; the axis is carried in the wording.
 - When saving, map the generated result to:
   - `current_summary`
   - `strengths`

package/dist/cli/skills/paput-principle-synthesizer/SKILL.md

@@ -18,6 +18,7 @@ Use this when the user wants to thicken their `principle` memos, distill recurri
    - As substrate, call `paput_get_project_context` and read the `design_doc` documents in the index with `paput_get_project_document(id)`. Design docs hold decisions with reasons and rejected alternatives — strong principle material — but they are private and project-specific.
 2. Read the bodies of the memos you plan to cluster with `paput_get_memo` (index first, fetch on demand — do not bulk-fetch everything).
 3. Cluster across documents by theme. Look for a stance that runs through SEVERAL decisions/operations (and design-doc decisions), not a single memo restated.
+   - First, sweep the WHOLE index and enumerate EVERY distinct cross-cutting theme the corpus supports — do not stop at the few most obvious (e.g. security / concurrency) clusters. Aim to cover the corpus. Commonly-missed but high-value axes include: operating practices (observability, eval, testing validity), AI / automation collaboration stances (treating model output as a soft signal, where to delegate generation), retrieval / routing separation, reversibility and incremental change, error-handling and failure semantics. Scan for these explicitly so the scarce axes are not dropped.
    - Make the clusters DISJOINT: assign each source memo to the ONE principle it best anchors, not to several. If two themes overlap heavily or keep pulling the same memos, treat them as ONE cluster, or draw a sharp line so each cluster owns a distinct slice.
 4. Synthesize each qualifying cluster into one `principle` candidate:
    - One cluster → one coherent stance with a SINGLE throughline (one "optimize X over Y"). Every sub-point in the body must be a facet of that one posture. If you find yourself writing "and also…" about a different concern, that is a second principle — split it out or drop the weaker thread. Do not bundle two or three loosely-related ideas under an umbrella title.
@@ -26,7 +27,7 @@ Use this when the user wants to thicken their `principle` memos, distill recurri
    - Default `is_public: false`; set `memo_type_keys: ['principle']` (add `decision` as a second label only if it is genuinely also a reusable judgment criterion).
 5. Self-review the draft set for MUTUAL distinctness before de-dup:
    - Compare every pair of your own draft candidates. If two share most of their source memos, or their statements overlap, they are not distinct — MERGE them into one sharper principle, or re-scope so each owns a disjoint slice and each memo anchors only one of them.
-   - Prefer fewer, sharper, non-overlapping principles over many overlapping ones.
+   - Merging is only for OVERLAPPING themes. It must NOT shrink the number of distinct themes you cover. "Fewer per theme" (no duplicates within a theme) is not "fewer themes" — never drop a genuine distinct cross-cutting stance just to keep the count small. Then re-check against the enumeration in step 3: if a distinct theme you found is not represented by any candidate, add it.
 6. De-dup against existing memos before adding:
    - For each candidate, call `paput_find_similar_memos` (it searches all of the user's memos, public and private). Treat a top score of ~0.85 or higher against an existing memo as a near-duplicate and skip it.
    - Also compare against the existing `principle` entries in `public_summary_memos`, and check `paput_list_pending_candidates` so you do not duplicate a pending candidate.
@@ -39,6 +40,7 @@ Use this when the user wants to thicken their `principle` memos, distill recurri
 - A `principle` must run through at least two or three decisions/operations. A single decision reworded is NOT a principle — drop it (or leave it as the decision memo it already is).
 - One principle = one throughline. The title must name ONE posture, not an umbrella over several. If the body covers two or three loosely-related concerns, it is a grab-bag — split it into separate principles or drop the weakest thread. Test: can you state it as a single "optimize X, reject Y"? If you need "and also…" about an unrelated concern, it is two principles.
 - Make principles mutually distinct. Do NOT emit two candidates that share most of their source memos or whose statements overlap. When that happens, merge them, or assign each shared memo to the single principle it best anchors and keep the two scopes disjoint. A source memo should anchor one principle, not back two.
+- Cover the corpus. Surface EVERY distinct cross-cutting stance the material supports, not just the first few strong clusters. The disjointness and merge rules reduce duplicates WITHIN a theme; they must not reduce the number of themes. Watch for the scarce, high-value axes that are easy to skip once the security / concurrency clusters are formed — AI / automation collaboration stances, operating practices (observability, eval, testing), and reversibility / incremental change. If the corpus clearly supports such a stance and no candidate covers it, that is under-coverage — add it.
 - Example — grab-bag (avoid): "変更は可逆・最小範囲から段階的に進め、消費側が実在するまで第一級化を急がず、未成熟な依存のために公式推奨を歪めない" bundles three concerns. Split: (1) reversible/incremental change, (2) defer first-classing until a consumer exists. Drop the unrelated "公式推奨を歪めない" to its own memo.
 - Example — overlap (avoid): one principle about "目的ごとに取得経路を分ける" and another about "AI 判定は soft signal" both leaning on the same memos. Keep route-separation in the first and move all AI-judgment material to the second so neither bleeds.
 - Generalize. Remove project-specific specifications, screen names, code, identifiers, and secrets. The body must be reusable in another project from its title and text alone.

package/dist/handlers/get-dashboard-analysis-context/handler.js

@@ -32,6 +32,7 @@ export async function handleGetDashboardAnalysisContext(_args, apiClient) {
         const prompt = buildPrompt({
             dashboardSummary,
             goals,
+            memoTypeCounts: dashboardSummary.memo_type_counts || [],
             recentMemoCount: recentMemos.length,
             noteCount: notes.length,
             categoryCount: categories?.length || 0,
@@ -90,15 +91,20 @@ async function safeFetch(fetcher) {
 function buildPrompt(context) {
     const activeGoals = context.goals.filter((goal) => goal.status === 'active');
     const archivedGoals = context.goals.filter((goal) => goal.status === 'archived');
+    const countOf = (key) => context.memoTypeCounts.find((entry) => entry.key === key)?.count ?? 0;
+    const memoTypeLine = `decision ${countOf('decision')}, operation ${countOf('operation')}, principle ${countOf('principle')}, knowledge ${countOf('knowledge')}`;
     return `Create a dashboard analysis as the MCP client AI, using the PaPut data in structuredContent. paput-mcp does not contain analysis logic, so you should read the source data and adapt the analysis to the user's goals and context. Write the final output in the user's language and match the user's tone when possible.
 
+Lead with the judgment axis, not raw volume. The durable, hard-to-commoditize part of what the user accumulates is their JUDGMENT and PRACTICE — captured as memo_type: decision (judgment criteria), operation (operating practices: observability, eval, testing, review), and principle (stated stances). knowledge is commodity. So assess the user by how thick those three axes are, not by how many memos or categories they have. structuredContent.dashboard_summary.memo_type_counts holds the per-type accumulation.
+
 Assumptions:
 - Do not recalculate dashboard continuity from activities. Use the summary values returned by the API.
 - Treat active goals as the current basis for analysis and archived goals as historical context.
-- Do not assume that the user should write memos next. Analyze how knowledge that naturally accumulates through daily development can grow toward the goals.
+- Frame current position, strengths, and thin areas in terms of decision / operation / principle thickness — not "how much knowledge has accumulated". Categories describe the domains the user works in; use them as a secondary lens, not the main axis. knowledge is commodity and is not a strength on its own.
 - If existing skill sheet or project AI summaries are available, use them as references for career-history phrasing.
 
 Context summary:
+- Memo type accumulation (the main axis): ${memoTypeLine}
 - Total memo count: ${context.dashboardSummary.total_memo_count}
 - Total note count: ${context.dashboardSummary.total_note_count}
 - Recent memo count: ${context.dashboardSummary.recent_memo_count}
@@ -112,14 +118,14 @@ Context summary:
 - Saved analysis: ${context.hasSavedAnalysis ? 'available' : 'not available'}
 
 Include these analysis points:
-1. The user's current position
-2. Areas that can be presented as strengths
-3. Areas that have been growing recently
-4. Thin or underdeveloped areas
-5. Knowledge missing against the user's goals
-6. Knowledge the user should learn next
-7. Phrasing that can be used in a skill sheet or career history
+1. The user's current position, read through the judgment/practice/principle axes (which axes are thick, which are thin).
+2. Strengths — the judgment criteria and operating practices the user has accumulated (decision / operation / principle), with the domains (categories) they show up in as supporting context.
+3. Areas that have been growing recently.
+4. Thin or underdeveloped axes — name the memo_type that is thin (e.g. principle is thin) and what that means, not just thin categories.
+5. Knowledge missing against the user's goals.
+6. What to do next to thicken the thin durable axis (e.g. distill recurring decisions into principles, capture operating practices), rather than just "learn more".
+7. Phrasing that can be used in a skill sheet or career history.
 
-If saving the result, build values suitable for paput_update_dashboard_analysis: current_summary, strengths, growing_areas, weak_areas, next_knowledge_suggestions, and analyzed_at. strengths, growing_areas, and weak_areas should include title, description, category_names, memo_count, and goal_ids. next_knowledge_suggestions should include title, reason, priority, category_names, and goal_ids.`;
+If saving the result, build values suitable for paput_update_dashboard_analysis: current_summary, strengths, growing_areas, weak_areas, next_knowledge_suggestions, and analyzed_at. strengths, growing_areas, and weak_areas should include title, description, category_names, memo_count, and goal_ids — and in each description speak in the judgment/practice/principle axis (e.g. which memo_type backs the strength, which type is thin). next_knowledge_suggestions should include title, reason, priority, category_names, and goal_ids.`;
 }
 //# sourceMappingURL=handler.js.map

package/dist/handlers/get-dashboard-analysis-context/handler.js.map

@@ -1 +1 @@
-{"version":3,"file":"handler.js","sourceRoot":"","sources":["../../../src/handlers/get-dashboard-analysis-context/handler.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,aAAa,EAAE,MAAM,gCAAgC,CAAC;AAC/D,OAAO,EAAE,mBAAmB,EAAE,MAAM,iCAAiC,CAAC;AACtE,OAAO,EAAE,oBAAoB,EAAE,MAAM,0CAA0C,CAAC;AAChF,OAAO,EAAE,SAAS,EAAE,MAAM,4BAA4B,CAAC;AACvD,OAAO,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AACzD,OAAO,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AACzD,OAAO,EAAE,aAAa,EAAE,MAAM,mCAAmC,CAAC;AAElE,MAAM,iBAAiB,GAAG,EAAE,CAAC;AAE7B,MAAM,CAAC,KAAK,UAAU,iCAAiC,CACrD,KAA0C,EAC1C,SAAoB;IAEpB,IAAI,CAAC;QACH,MAAM,CAAC,gBAAgB,EAAE,KAAK,CAAC,GAAG,MAAM,OAAO,CAAC,GAAG,CAAC;YAClD,mBAAmB,CAAC,SAAS,CAAC;YAC9B,SAAS,CAAC,SAAS,CAAC;SACrB,CAAC,CAAC;QAEH,MAAM,CACJ,UAAU,EACV,iBAAiB,EACjB,WAAW,EACX,UAAU,EACV,aAAa,EACd,GAAG,MAAM,OAAO,CAAC,GAAG,CAAC;YACpB,SAAS,CAAC,GAAG,EAAE,CAAC,aAAa,CAAC,SAAS,CAAC,CAAC;YACzC,SAAS,CAAC,GAAG,EAAE,CACb,WAAW,CAAC,SAAS,EAAE;gBACrB,IAAI,EAAE,CAAC;gBACP,KAAK,EAAE,iBAAiB;aACzB,CAAC,CACH;YACD,SAAS,CAAC,GAAG,EAAE,CACb,WAAW,CAAC,SAAS,EAAE;gBACrB,IAAI,EAAE,CAAC;gBACP,KAAK,EAAE,iBAAiB;aACzB,CAAC,CACH;YACD,SAAS,CAAC,GAAG,EAAE,CAAC,aAAa,CAAC,SAAS,CAAC,CAAC;YACzC,SAAS,CAAC,GAAG,EAAE,CAAC,oBAAoB,CAAC,SAAS,CAAC,CAAC;SACjD,CAAC,CAAC;QAEH,MAAM,WAAW,GACf,iBAAiB,IAAI,iBAAiB,CAAC,OAAO;YAC5C,CAAC,CAAC,iBAAiB,CAAC,KAAK,IAAI,EAAE;YAC/B,CAAC,CAAC,EAAE,CAAC;QACT,MAAM,KAAK,GACT,WAAW,IAAI,WAAW,CAAC,OAAO,CAAC,CAAC,CAAC,WAAW,CAAC,KAAK,IAAI,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;QACpE,MAAM,MAAM,GAAG,WAAW,CAAC;YACzB,gBAAgB;YAChB,KAAK;YACL,eAAe,EAAE,WAAW,CAAC,MAAM;YACnC,SAAS,EAAE,KAAK,CAAC,MAAM;YACvB,aAAa,EAAE,UAAU,EAAE,MAAM,IAAI,CAAC;YACtC,aAAa,EAAE,OAAO,CAAC,UAAU,CAAC;YAClC,gBAAgB,EAAE,OAAO,CAAC,aAAa,CAAC;SACzC,CAAC,CAAC;QAEH,OAAO;YACL,iBAAiB,EAAE;gBACjB,iBAAiB,EAAE,gBAAgB;gBACnC,KAAK;gBACL,WAAW,EAAE,UAAU;gBACvB,YAAY,EAAE,WAAW;gBACzB,KAAK;gBACL,UAAU,EAAE,UAAU,IAAI,EAAE;gBAC5B,wBAAwB,EAAE,aAAa;gBACvC,MAAM;aACP;YACD,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;iCACiB,gBAAgB,CAAC,gBAAgB,iBAAiB,gBAAgB,CAAC,gBAAgB,kBAAkB,gBAAgB,CAAC,iBAAiB,iCAAiC,gBAAgB,CAAC,2BAA2B;SAC5O,KAAK,CAAC,MAAM;eACN,UAAU,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;gBACzC,WAAW,CAAC,MAAM;SACzB,KAAK,CAAC,MAAM;cACP,UAAU,EAAE,MAAM,IAAI,CAAC;4BACT,aAAa,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;;EAEvE,MAAM,EAAE;iBACD;aACF;SACF,CAAC;IACJ,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,YAAY,GAChB,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,eAAe,CAAC;QAE3D,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,oDAAoD,YAAY,EAAE;iBACzE;aACF;YACD,OAAO,EAAE,IAAI;SACd,CAAC;IACJ,CAAC;AACH,CAAC;AAED,KAAK,UAAU,SAAS,CAAI,OAAyB;IACnD,IAAI,CAAC;QACH,OAAO,MAAM,OAAO,EAAE,CAAC;IACzB,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,IAAI,CAAC;IACd,CAAC;AACH,CAAC;AAED,SAAS,WAAW,CAAC,OAapB;IACC,MAAM,WAAW,GAAG,OAAO,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,QAAQ,CAAC,CAAC;IAC7E,MAAM,aAAa,GAAG,OAAO,CAAC,KAAK,CAAC,MAAM,CACxC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,UAAU,CACrC,CAAC;IAEF,OAAO;;;;;;;;;sBASa,OAAO,CAAC,gBAAgB,CAAC,gBAAgB;sBACzC,OAAO,CAAC,gBAAgB,CAAC,gBAAgB;uBACxC,OAAO,CAAC,gBAAgB,CAAC,iBAAiB;qCAC5B,OAAO,CAAC,gBAAgB,CAAC,2BAA2B;kBACvE,WAAW,CAAC,MAAM;oBAChB,aAAa,CAAC,MAAM;4BACZ,OAAO,CAAC,eAAe;qBAC9B,OAAO,CAAC,SAAS;0BACZ,OAAO,CAAC,aAAa;iBAC9B,OAAO,CAAC,aAAa,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;oBAClD,OAAO,CAAC,gBAAgB,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;;;;;;;;;;;4YAWgU,CAAC;AAC7Y,CAAC"}
+{"version":3,"file":"handler.js","sourceRoot":"","sources":["../../../src/handlers/get-dashboard-analysis-context/handler.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,aAAa,EAAE,MAAM,gCAAgC,CAAC;AAC/D,OAAO,EAAE,mBAAmB,EAAE,MAAM,iCAAiC,CAAC;AACtE,OAAO,EAAE,oBAAoB,EAAE,MAAM,0CAA0C,CAAC;AAChF,OAAO,EAAE,SAAS,EAAE,MAAM,4BAA4B,CAAC;AACvD,OAAO,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AACzD,OAAO,EAAE,WAAW,EAAE,MAAM,4BAA4B,CAAC;AACzD,OAAO,EAAE,aAAa,EAAE,MAAM,mCAAmC,CAAC;AAElE,MAAM,iBAAiB,GAAG,EAAE,CAAC;AAE7B,MAAM,CAAC,KAAK,UAAU,iCAAiC,CACrD,KAA0C,EAC1C,SAAoB;IAEpB,IAAI,CAAC;QACH,MAAM,CAAC,gBAAgB,EAAE,KAAK,CAAC,GAAG,MAAM,OAAO,CAAC,GAAG,CAAC;YAClD,mBAAmB,CAAC,SAAS,CAAC;YAC9B,SAAS,CAAC,SAAS,CAAC;SACrB,CAAC,CAAC;QAEH,MAAM,CACJ,UAAU,EACV,iBAAiB,EACjB,WAAW,EACX,UAAU,EACV,aAAa,EACd,GAAG,MAAM,OAAO,CAAC,GAAG,CAAC;YACpB,SAAS,CAAC,GAAG,EAAE,CAAC,aAAa,CAAC,SAAS,CAAC,CAAC;YACzC,SAAS,CAAC,GAAG,EAAE,CACb,WAAW,CAAC,SAAS,EAAE;gBACrB,IAAI,EAAE,CAAC;gBACP,KAAK,EAAE,iBAAiB;aACzB,CAAC,CACH;YACD,SAAS,CAAC,GAAG,EAAE,CACb,WAAW,CAAC,SAAS,EAAE;gBACrB,IAAI,EAAE,CAAC;gBACP,KAAK,EAAE,iBAAiB;aACzB,CAAC,CACH;YACD,SAAS,CAAC,GAAG,EAAE,CAAC,aAAa,CAAC,SAAS,CAAC,CAAC;YACzC,SAAS,CAAC,GAAG,EAAE,CAAC,oBAAoB,CAAC,SAAS,CAAC,CAAC;SACjD,CAAC,CAAC;QAEH,MAAM,WAAW,GACf,iBAAiB,IAAI,iBAAiB,CAAC,OAAO;YAC5C,CAAC,CAAC,iBAAiB,CAAC,KAAK,IAAI,EAAE;YAC/B,CAAC,CAAC,EAAE,CAAC;QACT,MAAM,KAAK,GACT,WAAW,IAAI,WAAW,CAAC,OAAO,CAAC,CAAC,CAAC,WAAW,CAAC,KAAK,IAAI,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;QACpE,MAAM,MAAM,GAAG,WAAW,CAAC;YACzB,gBAAgB;YAChB,KAAK;YACL,cAAc,EAAE,gBAAgB,CAAC,gBAAgB,IAAI,EAAE;YACvD,eAAe,EAAE,WAAW,CAAC,MAAM;YACnC,SAAS,EAAE,KAAK,CAAC,MAAM;YACvB,aAAa,EAAE,UAAU,EAAE,MAAM,IAAI,CAAC;YACtC,aAAa,EAAE,OAAO,CAAC,UAAU,CAAC;YAClC,gBAAgB,EAAE,OAAO,CAAC,aAAa,CAAC;SACzC,CAAC,CAAC;QAEH,OAAO;YACL,iBAAiB,EAAE;gBACjB,iBAAiB,EAAE,gBAAgB;gBACnC,KAAK;gBACL,WAAW,EAAE,UAAU;gBACvB,YAAY,EAAE,WAAW;gBACzB,KAAK;gBACL,UAAU,EAAE,UAAU,IAAI,EAAE;gBAC5B,wBAAwB,EAAE,aAAa;gBACvC,MAAM;aACP;YACD,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE;iCACiB,gBAAgB,CAAC,gBAAgB,iBAAiB,gBAAgB,CAAC,gBAAgB,kBAAkB,gBAAgB,CAAC,iBAAiB,iCAAiC,gBAAgB,CAAC,2BAA2B;SAC5O,KAAK,CAAC,MAAM;eACN,UAAU,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;gBACzC,WAAW,CAAC,MAAM;SACzB,KAAK,CAAC,MAAM;cACP,UAAU,EAAE,MAAM,IAAI,CAAC;4BACT,aAAa,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;;EAEvE,MAAM,EAAE;iBACD;aACF;SACF,CAAC;IACJ,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,MAAM,YAAY,GAChB,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,eAAe,CAAC;QAE3D,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,oDAAoD,YAAY,EAAE;iBACzE;aACF;YACD,OAAO,EAAE,IAAI;SACd,CAAC;IACJ,CAAC;AACH,CAAC;AAED,KAAK,UAAU,SAAS,CAAI,OAAyB;IACnD,IAAI,CAAC;QACH,OAAO,MAAM,OAAO,EAAE,CAAC;IACzB,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,IAAI,CAAC;IACd,CAAC;AACH,CAAC;AAED,SAAS,WAAW,CAAC,OAcpB;IACC,MAAM,WAAW,GAAG,OAAO,CAAC,KAAK,CAAC,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,QAAQ,CAAC,CAAC;IAC7E,MAAM,aAAa,GAAG,OAAO,CAAC,KAAK,CAAC,MAAM,CACxC,CAAC,IAAI,EAAE,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,UAAU,CACrC,CAAC;IAEF,MAAM,OAAO,GAAG,CAAC,GAAW,EAAU,EAAE,CACtC,OAAO,CAAC,cAAc,CAAC,IAAI,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,GAAG,KAAK,GAAG,CAAC,EAAE,KAAK,IAAI,CAAC,CAAC;IACxE,MAAM,YAAY,GAAG,YAAY,OAAO,CAAC,UAAU,CAAC,eAAe,OAAO,CAAC,WAAW,CAAC,eAAe,OAAO,CAAC,WAAW,CAAC,eAAe,OAAO,CAAC,WAAW,CAAC,EAAE,CAAC;IAEhK,OAAO;;;;;;;;;;;4CAWmC,YAAY;sBAClC,OAAO,CAAC,gBAAgB,CAAC,gBAAgB;sBACzC,OAAO,CAAC,gBAAgB,CAAC,gBAAgB;uBACxC,OAAO,CAAC,gBAAgB,CAAC,iBAAiB;qCAC5B,OAAO,CAAC,gBAAgB,CAAC,2BAA2B;kBACvE,WAAW,CAAC,MAAM;oBAChB,aAAa,CAAC,MAAM;4BACZ,OAAO,CAAC,eAAe;qBAC9B,OAAO,CAAC,SAAS;0BACZ,OAAO,CAAC,aAAa;iBAC9B,OAAO,CAAC,aAAa,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;oBAClD,OAAO,CAAC,gBAAgB,CAAC,CAAC,CAAC,WAAW,CAAC,CAAC,CAAC,eAAe;;;;;;;;;;;khBAWsc,CAAC;AACnhB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "paput-mcp",
-  "version": "4.2.1",
+  "version": "4.2.3",
   "description": "PaPut MCP Server",
   "main": "dist/index.js",
   "type": "module",