forkfeed-mcp 1.0.10 → 1.0.11

package/dist/guide-content.js

@@ -197,7 +197,7 @@ Casual, cheeky, technically accurate. Like your funniest friend reviewing your c
 - Humor is the default
 
 ### Incremental updates
-Always call **forkfeed_status** before generating content. It lists published feeds by their externalFeedId (which contains the commit SHA, e.g. \`tfip-owner-repo-abc1234\`).
+Always call **forkfeed_status** before generating content. It lists published feeds by their externalFeedId (which contains the commit SHA, e.g. \`tfip-owner-repo-abc1234\`). When presenting commits to the user, cross-reference with status results: match the 7-char SHA in each feed ID against commit SHAs to show which commits already have feeds.
 
 - **New commit**: Generate only the new feed and cards. The fork's feedIds must include ALL existing feed IDs plus the new one. Missing old IDs causes them to be deleted.
 - **Existing commit**: Warn the user that this commit already has a feed. Only regenerate if they confirm. The old cards will be replaced.

package/dist/index.js

@@ -233,7 +233,7 @@ server.prompt('forkfeed', 'Turn GitHub commits into swipeable forkfeed content.
 2. Call **forkfeed_images** to get the IT Scenes image catalog (200 scenes + 30 backgrounds).
 3. Call **forkfeed_status** to check for existing content. Note which feeds (commits) are already published.
 4. Detect the current repo from the working directory. Use git to get commit data.
-5. Ask which commits to process (default: latest). Do NOT ask about image style (always use IT Scenes). If any selected commits already have feeds, warn the user and ask for confirmation before regenerating them.
+5. Ask which commits to process (default: latest). Do NOT ask about image style (always use IT Scenes). Show a table of commits with a column indicating whether each already has a published feed (match the 7-char SHA from forkfeed_status feed IDs against the commit SHAs). If the user selects a commit that already has a feed, warn and ask for confirmation before regenerating.
 6. Fetch the diff, analyze it, and generate the 8-card manifest following the guide exactly. Include ALL existing feed IDs in the fork's feedIds array (see "Incremental updates" in the guide).
 7. Match images from the catalog to card content by tags and semantic similarity.
 8. Validate the manifest against the checklist in the guide.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "forkfeed-mcp",
-  "version": "1.0.10",
+  "version": "1.0.11",
   "description": "MCP server for pushing GitHub commits to forkfeed",
   "type": "module",
   "bin": {