You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a schema subcommand that prints the published JSON Schema for --json output (schema/json-output/v1.json) to stdout, so a consumer — a script, CI, or an agent in Claude Code — can fetch the contract at runtime instead of reading it out of the repo.
Why
--json (#12) is now a versioned, drift-guarded contract (schema_version: 1, validated in tests against schema/json-output/v1.json). Making the schema self-serve from the binary means an agent can validate markfluence's own output, or generate types, without knowing the repo layout.
Shape
markfluence schema — print the current (latest) schema.
Embed the file via go:embed so it ships in the binary and can't drift from the tested copy.
Consider --schema-version N later if/when a v2 exists; for now there is only v1.
Notes
Tiny command; the schema file and its conformance tests already exist.
Add a
schemasubcommand that prints the published JSON Schema for--jsonoutput (schema/json-output/v1.json) to stdout, so a consumer — a script, CI, or an agent in Claude Code — can fetch the contract at runtime instead of reading it out of the repo.Why
--json(#12) is now a versioned, drift-guarded contract (schema_version: 1, validated in tests againstschema/json-output/v1.json). Making the schema self-serve from the binary means an agent can validate markfluence's own output, or generate types, without knowing the repo layout.Shape
markfluence schema— print the current (latest) schema.go:embedso it ships in the binary and can't drift from the tested copy.--schema-version Nlater if/when a v2 exists; for now there is only v1.Notes
checkcommand and the Claude skill (Write a Claude skill for driving markfluence #36): the skill can point Claude atmarkfluence schemato learn the output shape.