[P6] Emit machine-readable authoring metadata

[KayleeWilliams]

Problem

Leadtype validates frontmatter and custom MDX tags, but external tools cannot easily discover the authoring contract.

This does not mean Leadtype should become a CMS or Studio. It means Leadtype can emit machine-readable metadata that other tools can consume.

Proposal

Emit optional authoring metadata describing:

• Collections.
• Frontmatter schema.
• Allowed groups.
• Custom MDX tag inventory.
• Required fields.
• Generated artifact paths.
• Lint rules or lint result categories.

Potential output:

public/docs/authoring-manifest.json

or, in package bundle mode:

docs/authoring-manifest.json

Use Cases

• Editor integrations.
• Docs review tooling.
• CI checks with richer reporting.
• Future UI/editor experiments without making Leadtype own an editor.

Acceptance Criteria

• leadtype generate can optionally emit an authoring manifest.
• The manifest describes collections, groups, fields, and artifact paths.
• The manifest is stable enough for external tools to consume.
• The feature does not introduce a Studio/editor UI.
• Bundle mode behavior is documented.

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[coderabbitai]

🔗 Related PRs

#35 - Add v1 headless integration surface and polish docs [closed]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!