refactor: remove links, tags, and status fields from TPMJS spec

These fields are redundant as they already exist in package.json:
- links: Use package.json repository/homepage fields
- tags: Use package.json keywords field
- status: Not needed in tool metadata

Changes:
- Remove TpmjsLinksSchema type definition
- Remove links, tags, and status from TpmjsRichSchema
- Update validation logic to not check these fields
- Update all documentation (spec page, publish page, HOW_TO_PUBLISH_A_TOOL.md)
- Update example tool package.json
- Simplify field reference tables

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

packages/tools/createBlogPost/package.json

@@ -80,13 +80,6 @@
       "description": "A structured blog post object with frontmatter, content, and metadata including slug, wordCount, readingTime, and formattedOutput"
     },
     "frameworks": ["vercel-ai", "langchain"],
-    "links": {
-      "documentation": "https://tpmjs.com/tools/createblogpost",
-      "repository": "https://github.com/ajaxdavis/tpmjs/tree/main/packages/tools/createBlogPost",
-      "homepage": "https://tpmjs.com"
-    },
-    "tags": ["blog", "content", "markdown", "mdx", "writing", "seo"],
-    "status": "stable",
     "aiAgent": {
       "useCase": "Use this tool when users need to generate blog posts, articles, or structured content with proper frontmatter and metadata. Ideal for content management systems, static site generators, and documentation sites.",
       "limitations": "Does not include AI content generation - you must provide the content. Only formats and structures existing content.",