Add build artifact manifest and SEO quality gate

[madawei2699]

Context

MinePilot's product route is shifting toward SEO utility pages and tools rather than a SaaS-first blank prompt generator.

MinePilot issue #43 defines a quality bar for public build pages:

• preview/screenshots;
• dimensions and block count;
• material list;
• layer guide;
• schematic/export artifact where possible;
• import guide;
• tags/categories;
• related builds;
• optional remix/customization affordance;
• verification/provenance status.

CraftDAG already produces many of these pieces separately, but it does not yet provide one stable artifact manifest or quality-gate output that MinePilot can consume for curated SEO pages.

Goal

Add a build artifact manifest and quality gate for generated ComponentPlan/VoxelPlan outputs.

This should make it easy for MinePilot to decide whether a build is publishable as a utility page.

Proposed output shape

Exact schema can be designed during implementation, but MinePilot needs something like:

{
  "id": "small-oak-starter-base",
  "title": "Small Oak Starter Base",
  "dimensions": { "width": 16, "height": 12, "length": 16 },
  "blockCount": 1234,
  "materials": [],
  "layers": [],
  "exports": {
    "schem": { "available": true }
  },
  "diagnosticsSummary": {
    "blocking": 0,
    "warnings": 3
  },
  "verification": {
    "status": "previewed",
    "notes": []
  },
  "tags": ["starter-base", "oak", "survival"],
  "provenance": {
    "source": "curated-component-plan"
  }
}

Requirements

• Derive dimensions and block count from compiled VoxelPlan.
• Include material list and layer guide references or embedded summaries.
• Include schematic/export availability and exporter warnings.
• Include diagnostics summary with machine-readable severity.
• Include enough tags/provenance hooks for MinePilot page metadata.
• Be usable from CLI for batch content generation.
• Avoid coupling CraftDAG to MinePilot page routes, SEO copy, analytics, or UI.

Quality gate

Provide a deterministic way to answer:

Can this build become a public utility page artifact?

The gate should consider:

• validation success;
• compile success;
• export success if schematic is required;
• blocking diagnostics;
• material/layer generation success;
• optional support warning thresholds;
• explicit unverified status when preview/export has not been manually checked.

Non-goals

• Do not generate SEO page copy in CraftDAG.
• Do not own MinePilot routes, canonical URLs, or analytics.
• Do not create thousands of pages.
• Do not decide monetization or ads.
• Do not require screenshots inside CraftDAG core; MinePilot can own rendering screenshots.

Acceptance criteria

• A documented manifest schema exists.
• CLI can emit the manifest for a ComponentPlan.
• Tests cover at least one valid sample and one sample with warnings.
• MinePilot can consume the manifest without reimplementing CraftDAG internals.
• Docs explain how this supports MinePilot docs: clarify CraftDAG positioning and terminology #43 without creating thin programmatic SEO pages.

Related

• Living reference: Minecraft build demand coverage and v1.0 readiness matrix #81 build-demand coverage matrix
• MinePilot Design hierarchical ComponentPlan assemblies for large builds #40 SEO content-page MVP
• MinePilot docs: clarify CraftDAG positioning and terminology #43 SEO content clusters and page taxonomy