v0.3.0 direction: onboarding and release reliability

[achieve0410]

Goal

Use v0.3.0 to make the project easier to evaluate and contribute to without widening its local-first security, data-minimization, or truthful-graph boundaries.

Candidate work

• document how to add and verify a synthetic analyzer fixture
• publish a framework support and explicit-limitations matrix grounded in current tests
• automate release-metadata consistency checks
• evaluate whether source-only distribution remains the right contract before considering any package or prebuilt artifact

Out of scope

• production, database, non-loopback collector, or external URL access
• telemetry, exports, CORS, TLS bypasses, or persistent capabilities
• turning unsupported or dynamic facts into resolved graph claims
• publishing packages before install, bundled-asset, platform, and provenance contracts are defined

Feedback

Which supported workflow is hardest to understand or contribute to today? Please use only synthetic, non-sensitive examples and do not include absolute local roots or analyzed-project data.