paput-mcp 4.2.21 → 4.2.23

package/dist/handlers/update-skill-sheet-project-episodes/tool.js

@@ -0,0 +1,58 @@
+import { handler } from './handler.js';
+export const updateSkillSheetProjectEpisodesTool = {
+    definition: {
+        name: 'paput_update_skill_sheet_project_episodes',
+        description: 'Full-replace the AI-generated design-and-judgment episodes for a PaPut skill sheet project. Use only after the user explicitly approves the episode draft.',
+        inputSchema: {
+            type: 'object',
+            properties: {
+                project_id: {
+                    type: 'number',
+                    description: 'Project ID',
+                },
+                episodes: {
+                    type: 'array',
+                    description: 'Episodes to save. Pass an empty array to clear all project episodes. Maximum 5 episodes.',
+                    maxItems: 5,
+                    items: {
+                        type: 'object',
+                        properties: {
+                            claim: {
+                                type: 'string',
+                                maxLength: 200,
+                                description: 'Required one-line claim for the episode, grounded in public linked memos.',
+                            },
+                            situation: {
+                                type: 'string',
+                                maxLength: 1000,
+                                description: 'Optional situation context, 1-2 sentences.',
+                            },
+                            decision: {
+                                type: 'string',
+                                maxLength: 1000,
+                                description: 'Optional decision description, 1-2 sentences.',
+                            },
+                            reason: {
+                                type: 'string',
+                                maxLength: 1000,
+                                description: 'Optional reason, 1-2 sentences.',
+                            },
+                            supporting_memo_ids: {
+                                type: 'array',
+                                minItems: 1,
+                                description: 'Public memo IDs returned by the project episodes context tool that support this episode.',
+                                items: {
+                                    type: 'number',
+                                },
+                            },
+                        },
+                        required: ['claim', 'supporting_memo_ids'],
+                    },
+                },
+            },
+            required: ['project_id', 'episodes'],
+        },
+    },
+    handler,
+};
+//# sourceMappingURL=tool.js.map

package/dist/handlers/update-skill-sheet-project-episodes/tool.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"tool.js","sourceRoot":"","sources":["../../../src/handlers/update-skill-sheet-project-episodes/tool.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,OAAO,EAAE,MAAM,cAAc,CAAC;AAEvC,MAAM,CAAC,MAAM,mCAAmC,GAAgB;IAC9D,UAAU,EAAE;QACV,IAAI,EAAE,2CAA2C;QACjD,WAAW,EACT,4JAA4J;QAC9J,WAAW,EAAE;YACX,IAAI,EAAE,QAAQ;YACd,UAAU,EAAE;gBACV,UAAU,EAAE;oBACV,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,YAAY;iBAC1B;gBACD,QAAQ,EAAE;oBACR,IAAI,EAAE,OAAO;oBACb,WAAW,EACT,0FAA0F;oBAC5F,QAAQ,EAAE,CAAC;oBACX,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;wBACd,UAAU,EAAE;4BACV,KAAK,EAAE;gCACL,IAAI,EAAE,QAAQ;gCACd,SAAS,EAAE,GAAG;gCACd,WAAW,EACT,2EAA2E;6BAC9E;4BACD,SAAS,EAAE;gCACT,IAAI,EAAE,QAAQ;gCACd,SAAS,EAAE,IAAI;gCACf,WAAW,EAAE,4CAA4C;6BAC1D;4BACD,QAAQ,EAAE;gCACR,IAAI,EAAE,QAAQ;gCACd,SAAS,EAAE,IAAI;gCACf,WAAW,EAAE,+CAA+C;6BAC7D;4BACD,MAAM,EAAE;gCACN,IAAI,EAAE,QAAQ;gCACd,SAAS,EAAE,IAAI;gCACf,WAAW,EAAE,iCAAiC;6BAC/C;4BACD,mBAAmB,EAAE;gCACnB,IAAI,EAAE,OAAO;gCACb,QAAQ,EAAE,CAAC;gCACX,WAAW,EACT,0FAA0F;gCAC5F,KAAK,EAAE;oCACL,IAAI,EAAE,QAAQ;iCACf;6BACF;yBACF;wBACD,QAAQ,EAAE,CAAC,OAAO,EAAE,qBAAqB,CAAC;qBAC3C;iBACF;aACF;YACD,QAAQ,EAAE,CAAC,YAAY,EAAE,UAAU,CAAC;SACrC;KACF;IACD,OAAO;CACR,CAAC"}

package/dist/handlers/upsert-skill-sheet-project/handler.js

@@ -88,6 +88,12 @@ function parseProjectParams(params) {
     if (typeof params.mcp_alias === 'string') {
         project.mcp_alias = params.mcp_alias;
     }
+    if (Array.isArray(params.achievements)) {
+        if (!params.achievements.every((item) => typeof item === 'string')) {
+            return undefined;
+        }
+        project.achievements = params.achievements;
+    }
     return project;
 }
 function isTechnology(value) {

package/dist/handlers/upsert-skill-sheet-project/handler.js.map

@@ -1 +1 @@
-{"version":3,"file":"handler.js","sourceRoot":"","sources":["../../../src/handlers/upsert-skill-sheet-project/handler.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oBAAoB,EACpB,wBAAwB,EACxB,uBAAuB,GACxB,MAAM,mCAAmC,CAAC;AAG3C,MAAM,CAAC,KAAK,UAAU,OAAO,CAC3B,MAA2C,EAC3C,SAAoB;IAEpB,MAAM,OAAO,GAAG,kBAAkB,CAAC,MAAM,CAAC,CAAC;IAC3C,IAAI,CAAC,OAAO,EAAE,CAAC;QACb,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,mCAAmC;iBAC1C;aACF;YACD,OAAO,EAAE,IAAI;SACd,CAAC;IACJ,CAAC;IAED,MAAM,EAAE,GACN,OAAO,OAAO,CAAC,EAAE,KAAK,QAAQ;QAC5B,CAAC,CAAC,OAAO,CAAC,EAAE;QACZ,CAAC,CAAC,MAAM,qBAAqB,CAAC,SAAS,EAAE,OAAO,CAAC,KAAK,CAAC,CAAC;IAE5D,IAAI,EAAE,EAAE,CAAC;QACP,MAAM,uBAAuB,CAAC,SAAS,EAAE,EAAE,GAAG,OAAO,EAAE,EAAE,EAAE,CAAC,CAAC;QAC7D,OAAO;YACL,iBAAiB,EAAE,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,EAAE,EAAE,OAAO,EAAE;YACpE,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,wBAAwB,EAAE,EAAE;iBACnC;aACF;SACF,CAAC;IACJ,CAAC;IAED,MAAM,QAAQ,GAAG,MAAM,oBAAoB,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;IAEhE,OAAO;QACL,iBAAiB,EAAE,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,QAAQ,EAAE;QAC1E,OAAO,EAAE;YACP;gBACE,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE,sBAAsB,QAAQ,CAAC,KAAK,SAAS,QAAQ,CAAC,EAAE,GAAG;aAClE;SACF;KACF,CAAC;AACJ,CAAC;AAED,KAAK,UAAU,qBAAqB,CAClC,SAAoB,EACpB,KAAc;IAEd,IAAI,OAAO,KAAK,KAAK,QAAQ,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC3D,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,QAAQ,GAAG,MAAM,wBAAwB,CAAC,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,CAAC,CAAC;IACzE,MAAM,UAAU,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,KAAK,KAAK,KAAK,CAAC,IAAI,EAAE,CAAC,CAAC;IAE9E,OAAO,UAAU,EAAE,EAAE,CAAC;AACxB,CAAC;AAED,SAAS,kBAAkB,CACzB,MAA2C;IAE3C,IAAI,CAAC,MAAM;QAAE,OAAO,SAAS,CAAC;IAC9B,IACE,OAAO,MAAM,CAAC,IAAI,KAAK,QAAQ;QAC/B,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ;QAChC,OAAO,MAAM,CAAC,YAAY,KAAK,QAAQ;QACvC,OAAO,MAAM,CAAC,WAAW,KAAK,QAAQ;QACtC,OAAO,MAAM,CAAC,IAAI,KAAK,QAAQ;QAC/B,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ;QAChC,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,YAAY,CAAC;QACnC,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,SAAS,CAAC;QAChC,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,EAC5B,CAAC;QACD,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,YAAY,GAAG,MAAM,CAAC,YAAY,CAAC,MAAM,CAAC,YAAY,CAAC,CAAC;IAC9D,MAAM,SAAS,GAAG,MAAM,CAAC,SAAS,CAAC,MAAM,CACvC,CAAC,OAAO,EAAqB,EAAE,CAAC,OAAO,OAAO,KAAK,QAAQ,CAC5D,CAAC;IACF,MAAM,KAAK,GAAG,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,gBAAgB,CAAC,CAAC;IAEpD,IACE,YAAY,CAAC,MAAM,KAAK,MAAM,CAAC,YAAY,CAAC,MAAM;QAClD,SAAS,CAAC,MAAM,KAAK,MAAM,CAAC,SAAS,CAAC,MAAM;QAC5C,KAAK,CAAC,MAAM,KAAK,MAAM,CAAC,KAAK,CAAC,MAAM,EACpC,CAAC;QACD,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,OAAO,GAAkC;QAC7C,IAAI,EAAE,MAAM,CAAC,IAAI;QACjB,KAAK,EAAE,MAAM,CAAC,KAAK;QACnB,YAAY,EAAE,MAAM,CAAC,YAAY;QACjC,WAAW,EAAE,MAAM,CAAC,WAAW;QAC/B,IAAI,EAAE,MAAM,CAAC,IAAI;QACjB,KAAK,EAAE,MAAM,CAAC,KAAK;QACnB,YAAY;QACZ,SAAS;QACT,KAAK;KACN,CAAC;IAEF,IAAI,OAAO,MAAM,CAAC,EAAE,KAAK,QAAQ,EAAE,CAAC;QAClC,OAAO,CAAC,EAAE,GAAG,MAAM,CAAC,EAAE,CAAC;IACzB,CAAC;IACD,IAAI,OAAO,MAAM,CAAC,UAAU,KAAK,QAAQ,IAAI,MAAM,CAAC,UAAU,KAAK,IAAI,EAAE,CAAC;QACxE,OAAO,CAAC,UAAU,GAAG,MAAM,CAAC,UAAU,CAAC;IACzC,CAAC;IACD,IAAI,OAAO,MAAM,CAAC,SAAS,KAAK,QAAQ,EAAE,CAAC;QACzC,OAAO,CAAC,SAAS,GAAG,MAAM,CAAC,SAAS,CAAC;IACvC,CAAC;IAED,OAAO,OAAO,CAAC;AACjB,CAAC;AAED,SAAS,YAAY,CAAC,KAAc;IAClC,OAAO,CACL,OAAO,KAAK,KAAK,QAAQ;QACzB,KAAK,KAAK,IAAI;QACd,MAAM,IAAI,KAAK;QACf,OAAO,KAAK,CAAC,IAAI,KAAK,QAAQ;QAC9B,CAAC,CAAC,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,OAAO,KAAK,CAAC,EAAE,KAAK,QAAQ,CAAC,CACnD,CAAC;AACJ,CAAC;AAED,SAAS,gBAAgB,CACvB,KAAc;IAEd,OAAO,CACL,OAAO,KAAK,KAAK,QAAQ;QACzB,KAAK,KAAK,IAAI;QACd,IAAI,IAAI,KAAK;QACb,OAAO,KAAK,CAAC,EAAE,KAAK,QAAQ;QAC5B,OAAO,IAAI,KAAK;QAChB,OAAO,KAAK,CAAC,KAAK,KAAK,QAAQ,CAChC,CAAC;AACJ,CAAC"}
+{"version":3,"file":"handler.js","sourceRoot":"","sources":["../../../src/handlers/upsert-skill-sheet-project/handler.ts"],"names":[],"mappings":"AACA,OAAO,EACL,oBAAoB,EACpB,wBAAwB,EACxB,uBAAuB,GACxB,MAAM,mCAAmC,CAAC;AAG3C,MAAM,CAAC,KAAK,UAAU,OAAO,CAC3B,MAA2C,EAC3C,SAAoB;IAEpB,MAAM,OAAO,GAAG,kBAAkB,CAAC,MAAM,CAAC,CAAC;IAC3C,IAAI,CAAC,OAAO,EAAE,CAAC;QACb,OAAO;YACL,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,mCAAmC;iBAC1C;aACF;YACD,OAAO,EAAE,IAAI;SACd,CAAC;IACJ,CAAC;IAED,MAAM,EAAE,GACN,OAAO,OAAO,CAAC,EAAE,KAAK,QAAQ;QAC5B,CAAC,CAAC,OAAO,CAAC,EAAE;QACZ,CAAC,CAAC,MAAM,qBAAqB,CAAC,SAAS,EAAE,OAAO,CAAC,KAAK,CAAC,CAAC;IAE5D,IAAI,EAAE,EAAE,CAAC;QACP,MAAM,uBAAuB,CAAC,SAAS,EAAE,EAAE,GAAG,OAAO,EAAE,EAAE,EAAE,CAAC,CAAC;QAC7D,OAAO;YACL,iBAAiB,EAAE,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,EAAE,EAAE,OAAO,EAAE;YACpE,OAAO,EAAE;gBACP;oBACE,IAAI,EAAE,MAAM;oBACZ,IAAI,EAAE,wBAAwB,EAAE,EAAE;iBACnC;aACF;SACF,CAAC;IACJ,CAAC;IAED,MAAM,QAAQ,GAAG,MAAM,oBAAoB,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;IAEhE,OAAO;QACL,iBAAiB,EAAE,EAAE,OAAO,EAAE,IAAI,EAAE,MAAM,EAAE,SAAS,EAAE,OAAO,EAAE,QAAQ,EAAE;QAC1E,OAAO,EAAE;YACP;gBACE,IAAI,EAAE,MAAM;gBACZ,IAAI,EAAE,sBAAsB,QAAQ,CAAC,KAAK,SAAS,QAAQ,CAAC,EAAE,GAAG;aAClE;SACF;KACF,CAAC;AACJ,CAAC;AAED,KAAK,UAAU,qBAAqB,CAClC,SAAoB,EACpB,KAAc;IAEd,IAAI,OAAO,KAAK,KAAK,QAAQ,IAAI,KAAK,CAAC,IAAI,EAAE,CAAC,MAAM,KAAK,CAAC,EAAE,CAAC;QAC3D,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,QAAQ,GAAG,MAAM,wBAAwB,CAAC,SAAS,EAAE,KAAK,CAAC,IAAI,EAAE,CAAC,CAAC;IACzE,MAAM,UAAU,GAAG,QAAQ,CAAC,IAAI,CAAC,CAAC,OAAO,EAAE,EAAE,CAAC,OAAO,CAAC,KAAK,KAAK,KAAK,CAAC,IAAI,EAAE,CAAC,CAAC;IAE9E,OAAO,UAAU,EAAE,EAAE,CAAC;AACxB,CAAC;AAED,SAAS,kBAAkB,CACzB,MAA2C;IAE3C,IAAI,CAAC,MAAM;QAAE,OAAO,SAAS,CAAC;IAC9B,IACE,OAAO,MAAM,CAAC,IAAI,KAAK,QAAQ;QAC/B,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ;QAChC,OAAO,MAAM,CAAC,YAAY,KAAK,QAAQ;QACvC,OAAO,MAAM,CAAC,WAAW,KAAK,QAAQ;QACtC,OAAO,MAAM,CAAC,IAAI,KAAK,QAAQ;QAC/B,OAAO,MAAM,CAAC,KAAK,KAAK,QAAQ;QAChC,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,YAAY,CAAC;QACnC,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,SAAS,CAAC;QAChC,CAAC,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,EAC5B,CAAC;QACD,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,YAAY,GAAG,MAAM,CAAC,YAAY,CAAC,MAAM,CAAC,YAAY,CAAC,CAAC;IAC9D,MAAM,SAAS,GAAG,MAAM,CAAC,SAAS,CAAC,MAAM,CACvC,CAAC,OAAO,EAAqB,EAAE,CAAC,OAAO,OAAO,KAAK,QAAQ,CAC5D,CAAC;IACF,MAAM,KAAK,GAAG,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,gBAAgB,CAAC,CAAC;IAEpD,IACE,YAAY,CAAC,MAAM,KAAK,MAAM,CAAC,YAAY,CAAC,MAAM;QAClD,SAAS,CAAC,MAAM,KAAK,MAAM,CAAC,SAAS,CAAC,MAAM;QAC5C,KAAK,CAAC,MAAM,KAAK,MAAM,CAAC,KAAK,CAAC,MAAM,EACpC,CAAC;QACD,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,OAAO,GAAkC;QAC7C,IAAI,EAAE,MAAM,CAAC,IAAI;QACjB,KAAK,EAAE,MAAM,CAAC,KAAK;QACnB,YAAY,EAAE,MAAM,CAAC,YAAY;QACjC,WAAW,EAAE,MAAM,CAAC,WAAW;QAC/B,IAAI,EAAE,MAAM,CAAC,IAAI;QACjB,KAAK,EAAE,MAAM,CAAC,KAAK;QACnB,YAAY;QACZ,SAAS;QACT,KAAK;KACN,CAAC;IAEF,IAAI,OAAO,MAAM,CAAC,EAAE,KAAK,QAAQ,EAAE,CAAC;QAClC,OAAO,CAAC,EAAE,GAAG,MAAM,CAAC,EAAE,CAAC;IACzB,CAAC;IACD,IAAI,OAAO,MAAM,CAAC,UAAU,KAAK,QAAQ,IAAI,MAAM,CAAC,UAAU,KAAK,IAAI,EAAE,CAAC;QACxE,OAAO,CAAC,UAAU,GAAG,MAAM,CAAC,UAAU,CAAC;IACzC,CAAC;IACD,IAAI,OAAO,MAAM,CAAC,SAAS,KAAK,QAAQ,EAAE,CAAC;QACzC,OAAO,CAAC,SAAS,GAAG,MAAM,CAAC,SAAS,CAAC;IACvC,CAAC;IACD,IAAI,KAAK,CAAC,OAAO,CAAC,MAAM,CAAC,YAAY,CAAC,EAAE,CAAC;QACvC,IAAI,CAAC,MAAM,CAAC,YAAY,CAAC,KAAK,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,OAAO,IAAI,KAAK,QAAQ,CAAC,EAAE,CAAC;YACnE,OAAO,SAAS,CAAC;QACnB,CAAC;QACD,OAAO,CAAC,YAAY,GAAG,MAAM,CAAC,YAAY,CAAC;IAC7C,CAAC;IAED,OAAO,OAAO,CAAC;AACjB,CAAC;AAED,SAAS,YAAY,CAAC,KAAc;IAClC,OAAO,CACL,OAAO,KAAK,KAAK,QAAQ;QACzB,KAAK,KAAK,IAAI;QACd,MAAM,IAAI,KAAK;QACf,OAAO,KAAK,CAAC,IAAI,KAAK,QAAQ;QAC9B,CAAC,CAAC,CAAC,IAAI,IAAI,KAAK,CAAC,IAAI,OAAO,KAAK,CAAC,EAAE,KAAK,QAAQ,CAAC,CACnD,CAAC;AACJ,CAAC;AAED,SAAS,gBAAgB,CACvB,KAAc;IAEd,OAAO,CACL,OAAO,KAAK,KAAK,QAAQ;QACzB,KAAK,KAAK,IAAI;QACd,IAAI,IAAI,KAAK;QACb,OAAO,KAAK,CAAC,EAAE,KAAK,QAAQ;QAC5B,OAAO,IAAI,KAAK;QAChB,OAAO,KAAK,CAAC,KAAK,KAAK,QAAQ,CAChC,CAAC;AACJ,CAAC"}

package/dist/handlers/upsert-skill-sheet-project/tool.js

@@ -85,6 +85,15 @@ export const upsertSkillSheetProjectTool = {
                         required: ['id', 'title'],
                     },
                 },
+                achievements: {
+                    type: 'array',
+                    description: 'Achievement bullets owned by the user. Omit to keep existing values; pass an empty array to clear them. Maximum 10 items, 100 characters each.',
+                    maxItems: 10,
+                    items: {
+                        type: 'string',
+                        maxLength: 100,
+                    },
+                },
             },
             required: [
                 'type',

package/dist/handlers/upsert-skill-sheet-project/tool.js.map

@@ -1 +1 @@
-{"version":3,"file":"tool.js","sourceRoot":"","sources":["../../../src/handlers/upsert-skill-sheet-project/tool.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,OAAO,EAAE,MAAM,cAAc,CAAC;AAEvC,MAAM,CAAC,MAAM,2BAA2B,GAAgB;IACtD,UAAU,EAAE;QACV,IAAI,EAAE,kCAAkC;QACxC,WAAW,EACT,sJAAsJ;QACxJ,WAAW,EAAE;YACX,IAAI,EAAE,QAAQ;YACd,UAAU,EAAE;gBACV,EAAE,EAAE;oBACF,IAAI,EAAE,QAAQ;oBACd,WAAW,EACT,yDAAyD;iBAC5D;gBACD,IAAI,EAAE;oBACJ,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,sCAAsC;iBACpD;gBACD,KAAK,EAAE;oBACL,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,eAAe;iBAC7B;gBACD,SAAS,EAAE;oBACT,IAAI,EAAE,QAAQ;oBACd,WAAW,EACT,gGAAgG;iBACnG;gBACD,YAAY,EAAE;oBACZ,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,gCAAgC;iBAC9C;gBACD,UAAU,EAAE;oBACV,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,8BAA8B;iBAC5C;gBACD,WAAW,EAAE;oBACX,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,qBAAqB;iBACnC;gBACD,IAAI,EAAE;oBACJ,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,MAAM;iBACpB;gBACD,KAAK,EAAE;oBACL,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,uBAAuB;iBACrC;gBACD,YAAY,EAAE;oBACZ,IAAI,EAAE,OAAO;oBACb,WAAW,EAAE,mBAAmB;oBAChC,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;wBACd,UAAU,EAAE;4BACV,EAAE,EAAE;gCACF,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,0CAA0C;6BACxD;4BACD,IAAI,EAAE;gCACJ,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,iBAAiB;6BAC/B;yBACF;wBACD,QAAQ,EAAE,CAAC,MAAM,CAAC;qBACnB;iBACF;gBACD,SAAS,EAAE;oBACT,IAAI,EAAE,OAAO;oBACb,WAAW,EACT,wHAAwH;oBAC1H,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;qBACf;iBACF;gBACD,KAAK,EAAE;oBACL,IAAI,EAAE,OAAO;oBACb,WAAW,EAAE,eAAe;oBAC5B,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;wBACd,UAAU,EAAE;4BACV,EAAE,EAAE;gCACF,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,SAAS;6BACvB;4BACD,KAAK,EAAE;gCACL,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,YAAY;6BAC1B;yBACF;wBACD,QAAQ,EAAE,CAAC,IAAI,EAAE,OAAO,CAAC;qBAC1B;iBACF;aACF;YACD,QAAQ,EAAE;gBACR,MAAM;gBACN,OAAO;gBACP,cAAc;gBACd,aAAa;gBACb,MAAM;gBACN,OAAO;gBACP,cAAc;gBACd,WAAW;gBACX,OAAO;aACR;SACF;KACF;IACD,OAAO;CACR,CAAC"}
+{"version":3,"file":"tool.js","sourceRoot":"","sources":["../../../src/handlers/upsert-skill-sheet-project/tool.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,OAAO,EAAE,MAAM,cAAc,CAAC;AAEvC,MAAM,CAAC,MAAM,2BAA2B,GAAgB;IACtD,UAAU,EAAE;QACV,IAAI,EAAE,kCAAkC;QACxC,WAAW,EACT,sJAAsJ;QACxJ,WAAW,EAAE;YACX,IAAI,EAAE,QAAQ;YACd,UAAU,EAAE;gBACV,EAAE,EAAE;oBACF,IAAI,EAAE,QAAQ;oBACd,WAAW,EACT,yDAAyD;iBAC5D;gBACD,IAAI,EAAE;oBACJ,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,sCAAsC;iBACpD;gBACD,KAAK,EAAE;oBACL,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,eAAe;iBAC7B;gBACD,SAAS,EAAE;oBACT,IAAI,EAAE,QAAQ;oBACd,WAAW,EACT,gGAAgG;iBACnG;gBACD,YAAY,EAAE;oBACZ,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,gCAAgC;iBAC9C;gBACD,UAAU,EAAE;oBACV,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,8BAA8B;iBAC5C;gBACD,WAAW,EAAE;oBACX,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,qBAAqB;iBACnC;gBACD,IAAI,EAAE;oBACJ,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,MAAM;iBACpB;gBACD,KAAK,EAAE;oBACL,IAAI,EAAE,QAAQ;oBACd,WAAW,EAAE,uBAAuB;iBACrC;gBACD,YAAY,EAAE;oBACZ,IAAI,EAAE,OAAO;oBACb,WAAW,EAAE,mBAAmB;oBAChC,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;wBACd,UAAU,EAAE;4BACV,EAAE,EAAE;gCACF,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,0CAA0C;6BACxD;4BACD,IAAI,EAAE;gCACJ,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,iBAAiB;6BAC/B;yBACF;wBACD,QAAQ,EAAE,CAAC,MAAM,CAAC;qBACnB;iBACF;gBACD,SAAS,EAAE;oBACT,IAAI,EAAE,OAAO;oBACb,WAAW,EACT,wHAAwH;oBAC1H,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;qBACf;iBACF;gBACD,KAAK,EAAE;oBACL,IAAI,EAAE,OAAO;oBACb,WAAW,EAAE,eAAe;oBAC5B,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;wBACd,UAAU,EAAE;4BACV,EAAE,EAAE;gCACF,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,SAAS;6BACvB;4BACD,KAAK,EAAE;gCACL,IAAI,EAAE,QAAQ;gCACd,WAAW,EAAE,YAAY;6BAC1B;yBACF;wBACD,QAAQ,EAAE,CAAC,IAAI,EAAE,OAAO,CAAC;qBAC1B;iBACF;gBACD,YAAY,EAAE;oBACZ,IAAI,EAAE,OAAO;oBACb,WAAW,EACT,gJAAgJ;oBAClJ,QAAQ,EAAE,EAAE;oBACZ,KAAK,EAAE;wBACL,IAAI,EAAE,QAAQ;wBACd,SAAS,EAAE,GAAG;qBACf;iBACF;aACF;YACD,QAAQ,EAAE;gBACR,MAAM;gBACN,OAAO;gBACP,cAAc;gBACd,aAAa;gBACb,MAAM;gBACN,OAAO;gBACP,cAAc;gBACd,WAAW;gBACX,OAAO;aACR;SACF;KACF;IACD,OAAO;CACR,CAAC"}

package/dist/plugin/skills/capture/SKILL.md

@@ -41,7 +41,7 @@ Extract reusable knowledge candidates from the current conversation or a user-sp
 
 ## Memo Type
 
-Classify each candidate with one or more memo types via `memo_type_keys`. A memo can have several. This axis is what lets PaPut surface judgment and practices in the public AI summary, so classify deliberately.
+Classify each candidate with one or more memo types via `memo_type_keys`. A memo can have several. This axis is what lets PaPut surface judgment and practices in project episodes, self PR drafting, and analysis, so classify deliberately.
 
 Typing is a reading step, not a writing step. Classify only after the body is final, and only from what the body already says. Never add headings, criteria sections, or choice wording to the body to justify a type — if a type fits only after such an edit, the type does not fit.
 
@@ -53,10 +53,10 @@ Typing is a reading step, not a writing step. Classify only after the body is fi
 Guidance:
 
 - Capture candidates are reusable decision criteria, procedures, or principles, so prefer `decision` / `operation` / `principle` when they fit; use `knowledge` for commodity technical know-how.
-- `decision` / `operation` / `principle` are the primary material for the public AI summary; `knowledge` usually is not.
+- `decision` / `operation` / `principle` are the primary material for durable judgment and working-practice summaries; `knowledge` usually is not.
 - Tagging review — do not under-label. The default failure mode is dropping a judgment memo into `knowledge` and missing `decision` / `operation` / `principle`; this is a main reason the `principle` axis stays thin. Consider the durable three FIRST and use `knowledge` only when none genuinely fit. Quick catches: a stated reason for choosing or avoiding an option → `decision`; an operating practice (how you measure, review, run, or verify) → `operation`; a generalized stance one level above a single decision → `principle`. Before finalizing `memo_type_keys`, re-read the candidate once and ask "is there a judgment here that I labeled as mere knowledge?". Do not over-correct either: `principle` needs an explicitly generalized stance, not a one-off opinion — keep it honest against the Quality Bar.
 - Do not over-label `decision` — it requires a judgment that actually happened, recorded in the body: an option taken, an alternative rejected, or a tradeoff resolved. A criteria-style heading, or a list of options with no record of what was chosen, does not make a memo a `decision`; plain library, API, or service behavior stays `knowledge` even when written as guidance.
-- AI-collaboration practices and stances belong here, not in the reject pile: how you structure a task or spec for an AI, your review discipline for AI-generated changes, where you verify versus trust AI output, when you delegate versus do it yourself. Capture the reusable practice as `operation` or the stated stance as `principle` — generalized so it would hold with a different AI tool, on a different project, for someone else to learn. This is the scarcest, most durable axis; do not drop it as workflow chatter.
+- AI-collaboration practices and postures belong here, not in the reject pile: how you structure a task or spec for an AI, your review discipline for AI-generated changes, where you verify versus trust AI output, when you delegate versus do it yourself. Capture the reusable practice as `operation` or the stated stance as `principle` — generalized so it would hold with a different AI tool, on a different project, for someone else to learn. This is the scarcest, most durable axis; do not drop it as workflow chatter.
 - Leaving a candidate unclassified (no type) is allowed, but classifying it improves analysis and the public profile. Do not force a type when none fits.
 
 ## Eliciting scarce operating practices (eval / observability)
@@ -75,7 +75,7 @@ Generalize one level above the project: drop service, metric, and dashboard name
 
 ## Eliciting prompt-derived judgment
 
-The user's own prompts in the current conversation are first-party evidence of judgment. Corrections, constraints, repeated instructions, and choices among AI-presented options often reveal reusable operating practices or stances before they appear in the final artifact. When the conversation includes this signal, do not treat it as disposable task wording: actively draw out the reusable judgment and capture it as `operation`, `principle`, or `decision` as appropriate.
+The user's own prompts in the current conversation are first-party evidence of judgment. Corrections, constraints, repeated instructions, and choices among AI-presented options often reveal reusable operating practices or postures before they appear in the final artifact. When the conversation includes this signal, do not treat it as disposable task wording: actively draw out the reusable judgment and capture it as `operation`, `principle`, or `decision` as appropriate.
 
 Draw out only what fits the conversation — do not interrogate:
 
@@ -84,7 +84,7 @@ Draw out only what fits the conversation — do not interrogate:
 - Is the user repeating nearly the same boilerplate instruction? If it is project-specific, route it to a project document as a `procedure` through Check 1; if it is cross-project, capture the practice as `operation` in pending through Check 2.
 - Did the AI present options, and did the user choose, reject, or combine them with a reason? That reason is `decision` material.
 
-Generalize one level above the prompt: keep the judgment criterion, operating practice, stance, or repeatable procedure; drop local paths, project names, customer details, and exact task facts. Short verbatim phrasing from the user may be preserved for authenticity, but pending candidates must not include sensitive or project-specific content. A one-off "fix this" or "run tests" instruction is a work log, not knowledge, unless it exposes a reusable judgment criterion, operating practice, or procedure. Project-specific repeated instructions belong in project documents (`procedure`, Check 1); cross-project practices and stances belong in pending candidates (Check 2).
+Generalize one level above the prompt: keep the judgment criterion, operating practice, stance, or repeatable procedure; drop local paths, project names, customer details, and exact task facts. Short verbatim phrasing from the user may be preserved for authenticity, but pending candidates must not include sensitive or project-specific content. A one-off "fix this" or "run tests" instruction is a work log, not knowledge, unless it exposes a reusable judgment criterion, operating practice, or procedure. Project-specific repeated instructions belong in project documents (`procedure`, Check 1); cross-project practices and postures belong in pending candidates (Check 2).
 
 ## Quality Bar
 
@@ -104,7 +104,7 @@ Prefer generalized but concrete writing:
 Do not add these to pending:
 
 - Project-specific specifications, screen names, button names, business workflows, operational rules, or local context.
-- One-off tool mechanics or configuration: editor / OS / CLI settings, keybindings, which button was clicked, model- or version-specific quirks, project-specific CI wiring, or anecdotes about a single session (for example, "the AI got confused here"). These are commodity even when they mention AI tools — capture the reusable practice or stance instead, not the mechanics. Reusable AI-collaboration practices and stances ARE worth capturing (see the AI-collaboration note under Memo Type); do not discard them as workflow chatter.
+- One-off tool mechanics or configuration: editor / OS / CLI settings, keybindings, which button was clicked, model- or version-specific quirks, project-specific CI wiring, or anecdotes about a single session (for example, "the AI got confused here"). These are commodity even when they mention AI tools — capture the reusable practice or stance instead, not the mechanics. Reusable AI-collaboration practices and postures ARE worth capturing (see the AI-collaboration note under Memo Type); do not discard them as workflow chatter.
 - Content that third parties cannot understand from the title and body alone.
 - Rejected designs, anecdotes, work logs, impressions, or decision histories without reusable guidance.
 - Content semantically close to existing memos or pending candidates.

package/dist/plugin/skills/dashboard-analysis/SKILL.md

@@ -6,7 +6,7 @@ description: Use this to analyze the user's PaPut dashboard, goals, skill sheet,
 
 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.
+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 principles). `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.
 
 The judgment axis is the LENS, not a replacement for goal analysis. The dashboard's core job is "where am I against my goals", so keep goals first-class: read each active goal THROUGH the axis — which judgment/practice/principle axis that goal requires, and whether that axis is currently thick or thin. Do not drop the goal overview in favor of axis-only talk.
 

package/dist/plugin/skills/harvest/SKILL.md

@@ -1,5 +1,5 @@
 ---
-description: Use this to harvest reusable knowledge from past local Claude/Codex sessions when the AI client can read local files. Safe to run repeatedly — it skips already-processed sessions and only reviews new ones — so use it both for first-time onboarding and for periodic catch-up. Pay special attention to AI-collaboration practices and stances (operation / principle), the scarce, durable axis.
+description: Use this to harvest reusable knowledge from past local Claude/Codex sessions when the AI client can read local files. Safe to run repeatedly — it skips already-processed sessions and only reviews new ones — so use it both for first-time onboarding and for periodic catch-up. Pay special attention to AI-collaboration practices and postures (operation / principle), the scarce, durable axis.
 ---
 
 # PaPut Harvest
@@ -44,7 +44,7 @@ periodic catch-up. There is no separate "init" step.
    Draft each body first, structured to fit the content itself — do not shape
    it around memo types. Then set `memo_type_keys` from the finalized body
    (see Memo Type below); classify AI-collaboration practices as `operation`
-   and stances as `principle`.
+   and postures as `principle`.
 9. If the session was reviewed but no candidates should be added, call
    `paput_mark_processed_session` with `source`, `session_id`, and
    `source_session_updated_at`.
@@ -83,7 +83,7 @@ Structure each candidate body to fit its content. Do not impose a judgment-memo
 
 ### Capture the AI-collaboration axis
 
-Reusable AI-collaboration practices and stances are first-class material here —
+Reusable AI-collaboration practices and postures are first-class material here —
 they are the scarcest, most durable axis and are easy to discard by mistake.
 Capture them as `operation` (practice) or `principle` (stance). Examples:
 
@@ -148,7 +148,7 @@ but pending candidates must not include sensitive or project-specific content. A
 one-off "fix this" or "run tests" instruction is a work log — exclude it unless
 the prompt reveals a reusable judgment criterion, operating practice, or
 procedure. Route project-specific repeated instructions to project documents
-(`procedure`, Check 1); route cross-project practices and stances to pending
+(`procedure`, Check 1); route cross-project practices and postures to pending
 candidates (Check 2).
 
 ### Do not add these to pending
@@ -169,7 +169,7 @@ Classify each candidate with one or more memo types via `memo_type_keys`:
 
 - `decision`: reusable judgment criteria independent of any project.
 - `operation`: operating practices — observability, eval, testing, review, and how you direct and verify AI collaboration.
-- `principle`: a stance you have explicitly stated, generalized above individual decisions, including stances on how to work with AI.
+- `principle`: a stance you have explicitly stated, generalized above individual decisions, including postures on how to work with AI.
 - `knowledge`: commodity technical know-how, usage, or implementation knowledge.
 
 `decision` / `operation` / `principle` are the primary material for the public

package/dist/plugin/skills/principle-synthesizer/SKILL.md

@@ -1,23 +1,23 @@
 ---
-description: Use this to synthesize cross-cutting principle candidates from the user's accumulated public decision/operation memos (and private design docs) and add them to pending. It surfaces the stances that run through many decisions — the thinnest, most AI-durable memo type — which the per-conversation paput-capture cannot reach. It only proposes to pending; it never saves to PaPut.
+description: Use this to synthesize cross-cutting principle candidates from the user's accumulated public decision/operation memos (and private design docs) and add them to pending. It surfaces the postures that run through many decisions — the thinnest, most AI-durable memo type — which the per-conversation paput-capture cannot reach. It only proposes to pending; it never saves to PaPut.
 ---
 
 # PaPut Principle Synthesizer
 
-Synthesize `principle` candidates by reading the user's accumulated `decision` / `operation` memos (and, as substrate, their private `design_doc` project documents) as a whole, finding the stances that run through many of them, and proposing each as a `principle` pending candidate.
+Synthesize `principle` candidates by reading the user's accumulated `decision` / `operation` memos (and, as substrate, their private `design_doc` project documents) as a whole, finding the postures that run through many of them, and proposing each as a `principle` pending candidate.
 
-A `principle` is a stance explicitly generalized one level above individual decisions — what the person optimizes for and what they reject across cases. It rarely falls out of a single conversation, so `paput-capture` (which works per session) structurally under-produces it. This skill fills that gap by working across the whole accumulated corpus. It is the persistence counterpart of the public-profile ◆ stances: it turns the cross-cutting synthesis into reusable `principle` material.
+A `principle` is a stance explicitly generalized one level above individual decisions — what the person optimizes for and what they reject across cases. It rarely falls out of a single conversation, so `paput-capture` (which works per session) structurally under-produces it. This skill fills that gap by working across the whole accumulated corpus and turns the cross-cutting synthesis into reusable `principle` material.
 
 Use this when the user wants to thicken their `principle` memos, distill recurring decisions into stated principles, or refresh principle candidates from accumulated knowledge.
 
 ## Workflow
 
 1. Gather the material:
-   - Call `paput_get_public_profile_context`. Use `public_summary_memos` — the complete index (id, title, memo_types, updated_at; no bodies) of ALL the user's PUBLIC `decision` / `operation` / `principle` memos. The `decision` / `operation` entries are the synthesis material; the existing `principle` entries are the de-dup baseline.
+   - Use `paput_search_memo` with `is_public: true` and `memo_type: decision`, then repeat with `memo_type: operation` and `memo_type: principle`. Page through results as needed. The `decision` / `operation` entries are the synthesis material; existing `principle` entries are the de-dup baseline.
    - 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.
+   - 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 postures (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.
@@ -29,7 +29,7 @@ Use this when the user wants to thicken their `principle` memos, distill recurri
    - 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.
+   - Also compare against the existing public `principle` entries returned by `paput_search_memo`, and check `paput_list_pending_candidates` so you do not duplicate a pending candidate.
 7. Add only the non-duplicate, mutually-distinct, generalized, project-independent candidates with `paput_add_knowledge_candidates` (memo_type_keys=['principle']). Add to pending only.
 8. Report each added candidate: title, categories, memo type, candidate id, and the source memos it was synthesized from.
 9. Do NOT save to PaPut. Saving a pending candidate is handled by `paput-save`, only when the user explicitly approves it.
@@ -39,7 +39,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.
+- 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 postures, 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): "Advance changes reversibly and in minimal scope, don't rush first-classing until a consumer actually exists, and don't distort the official recommendation for the sake of an immature dependency" bundles three concerns. Split: (1) reversible/incremental change, (2) defer first-classing until a consumer exists. Drop the unrelated "don't distort the official recommendation" to its own memo.
 - Example — overlap (avoid): one principle about "separating retrieval routes by purpose" and another about "AI judgments as soft signals" 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/plugin/skills/project-episodes/SKILL.md

@@ -0,0 +1,60 @@
+---
+description: Use this to draft and optionally save design-and-judgment episodes for a PaPut skill sheet project from the project's public linked memos. Trigger when the user asks to generate, refresh, or save project episodes, project judgment episodes, or the "design and judgment" section for a skill sheet project.
+---
+
+# PaPut Project Episodes
+
+Draft project episodes for the skill sheet project detail page. Episodes explain what the user chose, what they rejected, and why, backed by public linked memos.
+
+## Workflow
+
+1. Identify the target project ID.
+   - If the user gives a project ID, use it.
+   - If the user gives a project name, call `paput_get_skill_sheet` and choose the matching project.
+   - If the user does not specify a project, call `paput_get_skill_sheet`, show concise project candidates, and ask the user to choose one.
+   - Ask a concise clarification only when no project is specified or the match is ambiguous.
+2. Call `paput_get_skill_sheet_project_episodes_context` with `project_id`.
+3. Read `structuredContent.public_memos` and cluster the public linked memos by decision or operating-practice theme.
+4. Draft 2-3 episodes when the material supports them. Generate fewer, or none, when the public memos are thin.
+5. Present the draft in the user's language and tone, together with the achievements draft (see "Achievements Draft" below). Explain that each episode will become the project's "design and judgment" section.
+6. Do not save unless the user explicitly asks to save, update, or apply the episodes.
+7. If the user asks to save, call `paput_update_skill_sheet_project_episodes` with the approved `project_id` and `episodes`.
+8. Report any `dropped_ids` from the save response. If a saved episode has no resolved public supporting memos, tell the user it may be hidden on the public profile.
+9. Verify the saved result with `paput_get_skill_sheet`.
+
+## Episode Shape
+
+Each episode has:
+
+- `claim`: one visible lead line. Use recruiter/interviewer-level vocabulary and preserve the meaningful contrast when the source supports it: what was chosen over what was rejected.
+- `situation`: 1-2 sentences describing the context.
+- `decision`: 1-2 sentences describing the choice.
+- `reason`: 1-2 sentences explaining why that choice was made.
+- `supporting_memo_ids`: one or more public linked memo IDs returned by the context tool.
+
+## Material Rules
+
+- Use only `structuredContent.public_memos` from `paput_get_skill_sheet_project_episodes_context` as episode evidence.
+- Private linked memos are returned only as `private_memo_count`. Do not infer claims from private memo bodies.
+- Prefer `decision` and `operation` memos. Use `knowledge` memos only as background.
+- Do not use unrelated memos, goals, private dashboard analysis, or project documents as episode evidence.
+- Do not invent memo IDs, technologies, responsibilities, impact, dates, or team scale.
+- Do not treat memo count as proof of ability.
+- If public linked memos do not support a claim, drop the claim.
+- If the material is thin, say what is missing and suggest capturing or publishing better project-linked decision/operation memos.
+
+## Achievements Draft (always propose)
+
+Always propose an `achievements` draft alongside the episodes draft: 3-5 factual bullets (max 100 characters each, max 10 total) describing what was built and is running, grounded in the project description and public linked memos.
+
+- Achievements are user-owned source material, not generated evidence. Present them as a draft for the user to edit and approve, and keep them factual: no judgment narrative (that belongs to episodes) and no invented metrics.
+- Use `paput_upsert_skill_sheet_project` to save achievements only after explicit approval. Saving episodes and saving achievements are separate tool calls; the user may approve one and not the other.
+- Omit `achievements` when calling `paput_upsert_skill_sheet_project` if the user wants to keep existing bullets. Pass `achievements: []` only when the user explicitly wants to clear them.
+
+## Rules
+
+- Do not claim that paput-mcp generated the episodes. The MCP client AI performs the drafting.
+- Do not save a draft automatically.
+- Every saved episode must have at least one `supporting_memo_id`.
+- The public API filters supporting memo IDs to the user's own public memos. Dropped IDs mean the evidence was not public, not owned, or unavailable.
+- Keep the tone factual and suitable for a skill sheet or career history.

package/dist/plugin/skills/self-pr-draft/SKILL.md

@@ -0,0 +1,37 @@
+---
+description: Use this to draft a first-person self PR for the PaPut skill sheet from existing profile, skills, projects, project episodes, achievements, and public decision/operation/principle memos. It presents a draft first and saves only when the user explicitly asks.
+---
+
+# PaPut Self PR Draft
+
+Draft the `self_pr` section of the PaPut skill sheet. This skill is draft-first: it does not save unless the user explicitly asks to save, update, or apply the final text.
+
+## Workflow
+
+1. Call `paput_get_skill_sheet`.
+2. Review the basic profile, skills, projects, project `episodes`, project `achievements`, and current `self_pr`.
+3. Gather additional public memo evidence only when needed:
+   - Use `paput_search_memo` with `is_public: true` and `memo_type: decision`, `operation`, or `principle`.
+   - Fetch full bodies with `paput_get_memo` only for the memos you actually need.
+4. Draft a first-person self PR in the user's language.
+5. Present the draft and ask the user to edit or approve it.
+6. Do not save unless the user explicitly asks to save, update, or apply it.
+7. If the user asks to save, call `paput_update_skill_sheet_self_pr` with the approved text.
+8. Verify the saved result with `paput_get_skill_sheet`.
+
+## Drafting Guidance
+
+- Target a recruiter or interviewer reading the skill sheet.
+- In Japanese, aim for about 300-600 characters unless the user asks for a different length. Use a comparable short professional length in other languages.
+- Write in first person when that fits the user's language and tone.
+- Anchor the text in projects, episodes, achievements, and public decision/operation/principle memos.
+- Emphasize judgment, trade-offs, and operating practices when the evidence supports them.
+- Keep technologies and domains concrete, but do not turn the self PR into a stack inventory.
+
+## Rules
+
+- Do not use private dashboard analysis, goals, or private memos unless the user explicitly provides them in the conversation.
+- Do not invent outcomes, metrics, responsibilities, or years of experience.
+- Do not present memo counts as proof of ability.
+- Do not save automatically.
+- If the material is thin, produce a conservative draft and say what evidence would improve it.

package/dist/schemas/tool-input.js

@@ -57,6 +57,37 @@ const skillSheetProjectSchema = z.object({
         .array(z.number())
         .describe('Development process IDs: 1 requirements, 2 basic design, 3 detailed design, 4 implementation, 5 testing, 6 maintenance'),
     memos: z.array(skillSheetMemoSchema).describe('Related memos'),
+    achievements: z
+        .array(z.string().max(100).describe('Achievement bullet, max 100 characters'))
+        .max(10)
+        .describe('Achievement bullets owned by the user. Omit to keep existing values; pass an empty array to clear them.')
+        .optional(),
+});
+const skillSheetProjectEpisodeSchema = z.object({
+    claim: z
+        .string()
+        .min(1)
+        .max(200)
+        .describe('Required one-line claim for the episode, grounded in public linked memos'),
+    situation: z
+        .string()
+        .max(1000)
+        .describe('Optional situation context, 1-2 sentences')
+        .optional(),
+    decision: z
+        .string()
+        .max(1000)
+        .describe('Optional decision description, 1-2 sentences')
+        .optional(),
+    reason: z
+        .string()
+        .max(1000)
+        .describe('Optional reason, 1-2 sentences')
+        .optional(),
+    supporting_memo_ids: z
+        .array(z.number())
+        .min(1)
+        .describe('Public memo IDs returned by the project episodes context tool that support this episode'),
 });
 const knowledgeCandidateSchema = z.object({
     title: z.string(),
@@ -138,6 +169,10 @@ const toolInputSchemas = {
     paput_search_memo: z.object({
         word: z.string().describe('Search keyword').optional(),
         category_id: z.number().describe('Category ID').optional(),
+        memo_type: z
+            .enum(['knowledge', 'decision', 'operation', 'principle'])
+            .describe('Memo type filter')
+            .optional(),
         ids: z.array(z.number()).describe('Memo IDs').optional(),
         date: z.string().describe('Date in YYYY-MM-DD format').optional(),
         is_public: z.boolean().describe('Visibility filter').optional(),
@@ -231,68 +266,6 @@ const toolInputSchemas = {
     paput_update_skill_sheet_self_pr: z.object({
         self_pr: z.string().describe('Self PR text').optional(),
     }),
-    paput_update_skill_sheet_public_profile: z.object({
-        headline: z
-            .string()
-            .describe('One-line catchphrase summarizing the user')
-            .optional(),
-        profile_summary: z
-            .string()
-            .describe('Multi-line overall summary of the user')
-            .optional(),
-        strength_labels: z
-            .array(z.object({
-            label: z.string().describe('Strength label name'),
-            description: z.string().describe('Strength description').optional(),
-            category_names: z
-                .array(z.string())
-                .describe('Related category names')
-                .optional(),
-            project_ids: z
-                .array(z.string())
-                .describe('Related project IDs')
-                .optional(),
-            supporting_memo_ids: z
-                .array(z.number())
-                .describe('Public memo IDs that back this strength. Use only public decision/operation/principle memo IDs from the index; non-public or non-owned IDs are dropped server-side.')
-                .optional(),
-        }))
-            .describe('Array of strength labels')
-            .optional(),
-        stances: z
-            .array(z.object({
-            type: z
-                .enum(['decision', 'operation'])
-                .describe('Which axis this stance belongs to'),
-            statement: z
-                .string()
-                .describe('One-line stance synthesized from decision/operation memos, in plain non-expert vocabulary a non-technical recruiter grasps in one read (no domain jargon or English technical terms in the line — those belong in the drill-down memos). Keep the rejected alternative ("B, not A"): weave in what was chosen and what was rejected; dissolve principle into the wording.'),
-            supporting_memo_ids: z
-                .array(z.number())
-                .describe('Public memo IDs backing this stance (the drill-down judgment cards). Use only public decision/operation/principle memo IDs from the index.')
-                .optional(),
-        }))
-            .describe('Stances (judgment and operating practices) shown as the lead of the AI Summary tab. Lead with 3-4 stances total with one clear anchor stance, ordered by strength; keep each line in plain non-expert vocabulary with its rejected-alternative intact.')
-            .optional(),
-        project_highlights: z
-            .array(z.object({
-            project_id: z.string().describe('Related project ID'),
-            title: z.string().describe('Project title'),
-            summary: z
-                .string()
-                .describe('Short public-profile summary for the project'),
-            strength_labels: z
-                .array(z.string())
-                .describe('Strength labels supported by the project')
-                .optional(),
-            achievement_bullets: z
-                .array(z.string())
-                .describe('Top achievement bullets for the project')
-                .optional(),
-        }))
-            .describe('Short project highlights shown on the AI Summary tab')
-            .optional(),
-    }),
     paput_set_skill_sheet_skills: z.object({
         skills: z.array(skillSchema).describe('Skill list'),
     }),
@@ -300,12 +273,15 @@ const toolInputSchemas = {
     paput_delete_skill_sheet_project: z.object({
         project_id: z.number().describe('Project ID to delete'),
     }),
-    paput_get_skill_sheet_project_summary_context: z.object({
+    paput_get_skill_sheet_project_episodes_context: z.object({
         project_id: z.number().describe('Project ID'),
     }),
-    paput_update_skill_sheet_project_ai_summary: z.object({
+    paput_update_skill_sheet_project_episodes: z.object({
         project_id: z.number().describe('Project ID'),
-        ai_summary: z.string().describe('AI-generated project summary to save'),
+        episodes: z
+            .array(skillSheetProjectEpisodeSchema)
+            .max(5)
+            .describe('Episodes to save. Pass an empty array to clear all project episodes.'),
     }),
     paput_list_goals: emptySchema,
     paput_create_goal: goalInputSchema,
@@ -337,7 +313,6 @@ const toolInputSchemas = {
         analyzed_at: z.string().describe('Analysis timestamp in ISO 8601 format'),
     }),
     paput_get_dashboard_analysis_context: emptySchema,
-    paput_get_public_profile_context: emptySchema,
     paput_get_project_context: z.object({
         project: z
             .string()
@@ -455,7 +430,7 @@ const toolInputSchemas = {
             .optional(),
         memo_type_keys: z
             .array(z.enum(['knowledge', 'decision', 'operation', 'principle']))
-            .describe('Memo type classification keys (a memo can have multiple). decision/operation/principle are the primary material for the public AI summary.')
+            .describe('Memo type classification keys (a memo can have multiple). decision/operation/principle are the primary material for durable judgment and working-practice summaries.')
             .optional(),
         confidence: z.number().describe('Confidence score').optional(),
         is_public: z