Status Summary
Platform conformance suite 38 marks cli_json_envelopes stable, but its only source is durable-workflow.v2.cli-json-envelopes@catalog-15. That artifact is a JSON Schema for the CLI output-schema manifest shape; it does not contain the command-to-schema manifest or any per-command output schemas.
The current CLI manifest enumerates 79 command mappings. Those mappings use repository-relative schemas/output/*.schema.json locators and identify schemas under https://durable-workflow.com/schemas/cli/output/, but those public routes are not published (/schemas/cli/output/workflow-start.schema.json returns 404). A consumer starting from the live suite therefore cannot resolve the stable CLI envelope fixture set that the suite claims to expose.
How to fix
- Publish a revision-bound CLI output-schema manifest and every referenced per-command schema as directly retrievable HTTPS artifacts.
- Give each published schema a consumer-resolvable identity; do not require a CLI repository checkout or a repository-relative locator.
- Advance the platform suite and bind
cli_json_envelopes to the manifest and its complete dependency closure with versioned artifact ids, immutable resolver URLs, and SHA-256 digests. Keep the human conformance pages aligned with the same authorities.
- Keep the Workflow package authority byte-equivalent to the docs authority.
- Make qualification fetch and validate the manifest and every referenced command schema, including identities and byte digests, so missing, mutable, or incomplete publication fails closed.
- Preserve stable 1.x as the default documentation line.
Delete when
Delete when a consumer starting only from the live platform conformance suite can retrieve the CLI command manifest and every referenced JSON/JSONL envelope schema, verify their identities and bytes, and qualification prevents any part of that published fixture closure from disappearing or drifting.
Required source targets
durable-workflow/cli@main
durable-workflow/durable-workflow.github.io@main
durable-workflow/workflow@v2
Status Summary
Platform conformance suite 38 marks
cli_json_envelopesstable, but its only source isdurable-workflow.v2.cli-json-envelopes@catalog-15. That artifact is a JSON Schema for the CLI output-schema manifest shape; it does not contain the command-to-schema manifest or any per-command output schemas.The current CLI manifest enumerates 79 command mappings. Those mappings use repository-relative
schemas/output/*.schema.jsonlocators and identify schemas underhttps://durable-workflow.com/schemas/cli/output/, but those public routes are not published (/schemas/cli/output/workflow-start.schema.jsonreturns 404). A consumer starting from the live suite therefore cannot resolve the stable CLI envelope fixture set that the suite claims to expose.How to fix
cli_json_envelopesto the manifest and its complete dependency closure with versioned artifact ids, immutable resolver URLs, and SHA-256 digests. Keep the human conformance pages aligned with the same authorities.Delete when
Delete when a consumer starting only from the live platform conformance suite can retrieve the CLI command manifest and every referenced JSON/JSONL envelope schema, verify their identities and bytes, and qualification prevents any part of that published fixture closure from disappearing or drifting.
Required source targets
durable-workflow/cli@main
durable-workflow/durable-workflow.github.io@main
durable-workflow/workflow@v2