Epic: syner.md Core

[rbadillap]

Objective

Serve markdown files from GitHub with multiple formats, zero-trust by default, and MCP server for agents.

Context

syner.md is the content registry of the Syner ecosystem. It serves markdown files as the shared surface for humans and agents.

This epic focuses on the core functionality: reading from GitHub, serving in multiple formats, and exposing an MCP server. The editor UI is a separate future effort.

Scope

In Scope

• Basic routing in apps/md/
• Proxy to GitHub repos (consumes extensions/github/ from Epic Epic: GitHub App Integration #35)
• Rewrite .json: Registry format (shadcn-style)
• Rewrite .md: Raw markdown
• Zero-trust first: Nothing public by default, user must explicitly authorize
• MCP server: Tools for reading markdown files
• Proper GitHub API handling (cache, rate limit from Epic Epic: GitHub App Integration #35)

Out of Scope

• Editor UI (existing PoC, will be integrated later)
• Local filesystem API
• Push to GitHub
• Vercel connect for hosting
• Versioning

URL Structure

syner.md/{user}/{file}      → default (HTML rendered)
syner.md/{user}/{file}.md   → raw markdown
syner.md/{user}/{file}.json → registry format

Zero-Trust Model

• User connects GitHub via syner.dev (Epic Epic: GitHub App Integration #35)
• User explicitly selects which repos/files to make public
• syner.md acts as a proxy, not a cache/mirror
• No static infrastructure per user

MCP Server

Expose tools for agents to:

• Read markdown files
• List available files
• Query metadata

Follows the philosophy: "Markdown is paper — shared surface for humans and agents"

Deliverables

1. apps/md/ with basic routing
2. GitHub proxy using extensions/github/
3. .json rewrite endpoint
4. .md rewrite endpoint
5. MCP server with read tools
6. Zero-trust authorization layer

Dependencies

• Epic Epic: GitHub App Integration #35 (GitHub App Integration)

Labels

epic, syner.md, mcp