pmpt-cli 1.14.3 → 1.14.5

package/dist/commands/export.js

@@ -58,6 +58,8 @@ export async function cmdExport(path, options) {
             version: snapshots[i].version,
             timestamp: snapshots[i].timestamp,
             files,
+            changedFiles: snapshots[i].changedFiles,
+            note: snapshots[i].note,
             git: snapshots[i].git,
         });
     }

package/dist/commands/publish.js

@@ -345,6 +345,8 @@ export async function cmdPublish(path, options) {
         version: snapshot.version,
         timestamp: snapshot.timestamp,
         files: resolveFullSnapshot(snapshots, i),
+        changedFiles: snapshot.changedFiles,
+        note: snapshot.note,
         git: snapshot.git,
     }));
     const docs = readDocsFolder(docsDir);

package/dist/commands/update.js

@@ -99,6 +99,8 @@ export async function cmdUpdate(path) {
         version: snapshot.version,
         timestamp: snapshot.timestamp,
         files: resolveFullSnapshot(snapshots, i),
+        changedFiles: snapshot.changedFiles,
+        note: snapshot.note,
         git: snapshot.git,
     }));
     const docs = readDocsFolder(docsDir);

package/dist/lib/pmptFile.js

@@ -47,6 +47,8 @@ const VersionSchema = z.object({
     version: z.number().min(1),
     timestamp: z.string(),
     summary: z.string().optional(),
+    note: z.string().optional(),
+    changedFiles: z.array(z.string()).optional(),
     files: z.record(safeFilenameKey, z.string()), // filename -> content
     git: GitInfoSchema,
 });

package/dist/mcp.js

@@ -12,7 +12,7 @@ import { resolve, join } from 'path';
 import { existsSync, readFileSync, writeFileSync } from 'fs';
 import glob from 'fast-glob';
 import { createRequire } from 'module';
-import { isInitialized, loadConfig, getDocsDir, getHistoryDir } from './lib/config.js';
+import { isInitialized, loadConfig, saveConfig, getDocsDir, getHistoryDir } from './lib/config.js';
 import { createFullSnapshot, getAllSnapshots, getTrackedFiles, resolveFullSnapshot } from './lib/history.js';
 import { computeQuality } from './lib/quality.js';
 import { getPlanProgress, savePlanProgress, savePlanDocuments, PLAN_QUESTIONS } from './lib/plan.js';
@@ -98,7 +98,7 @@ function formatDiffs(diffs) {
     return lines.join('\n');
 }
 // ── Tools ───────────────────────────────────────────
-server.tool('pmpt_save', 'Save a snapshot of .pmpt/docs/ files. Call after completing features, fixes, or milestones. IMPORTANT: Always provide a summary describing what was accomplished — this gets recorded in the project development log.', {
+server.tool('pmpt_save', 'Save a snapshot of .pmpt/docs/ files. Call after completing features, fixes, or milestones. CRITICAL: Always provide a summary parameter — it becomes the version description shown on pmptwiki.com. Without a summary, the version appears empty on the project page. Write a concise description of what was accomplished (e.g. "Added user authentication with JWT").', {
     projectPath: z.string().optional().describe('Project root path. Defaults to cwd.'),
     summary: z.string().optional().describe('What was accomplished since the last save. This is recorded in pmpt.md as a development log entry. Examples: "Implemented user auth with JWT", "Fixed responsive layout on mobile", "Added search filtering by category".'),
 }, async ({ projectPath, summary }) => {
@@ -582,7 +582,7 @@ server.tool('pmpt_log_decision', 'Record an architectural or technical decision
         return { content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }], isError: true };
     }
 });
-server.tool('pmpt_publish', 'Publish the project to pmptwiki.com. This tool handles everything non-interactively — just provide the slug and optional metadata. Note: the user must have run `pmpt login` once before (check if auth exists). If not logged in, ask the user to run `pmpt login` in their terminal, then retry this tool.', {
+server.tool('pmpt_publish', 'Publish the project to pmptwiki.com. Non-interactive — just provide slug and optional metadata. BEFORE publishing, verify: (1) Run pmpt_history to check all snapshots have meaningful summaries — empty versions look bad on the project page. (2) If any versions lack descriptions, run pmpt_save with a summary or update pmpt.md Snapshot Log section with ### vN — Title entries. (3) Run pmpt_quality to check publish readiness. Note: user must have run `pmpt login` once before.', {
     projectPath: z.string().optional().describe('Project root path. Defaults to cwd.'),
     slug: z.string().describe('Project slug (3-50 chars, lowercase alphanumeric and hyphens).'),
     description: z.string().optional().describe('Project description (max 500 chars).'),
@@ -656,6 +656,13 @@ server.tool('pmpt_publish', 'Publish the project to pmptwiki.com. This tool hand
             productUrl,
             productUrlType,
         });
+        // Save publish state to config so `pmpt update` works
+        if (config) {
+            config.lastPublished = new Date().toISOString();
+            config.lastPublishedSlug = slug;
+            config.lastPublishedVersionCount = snapshots.length;
+            saveConfig(pp, config);
+        }
         return {
             content: [{
                     type: 'text',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pmpt-cli",
-  "version": "1.14.3",
+  "version": "1.14.5",
   "description": "Record and share your AI-driven product development journey",
   "type": "module",
   "bin": {