Found while building lofty-pm-cli (which copied the pattern and then fixed it): lofty config show --json emits the bare config object with no "schema" tag, and lofty config path prints a raw string even in --json mode. SPEC §1.4 requires every top-level JSON DTO to carry "schema": "<name>/v1".
lofty-pm-cli's resolution (adoptable as-is): config show --json → object tagged config/v1; config path --json → {"schema": "config-path/v1", "path": "..."}; text mode unchanged for both. Ref: piekstra/lofty-pm-cli commit 922de89. conformance.md's lofty row should note the gap until fixed.
Found while building lofty-pm-cli (which copied the pattern and then fixed it):
lofty config show --jsonemits the bare config object with no"schema"tag, andlofty config pathprints a raw string even in--jsonmode. SPEC §1.4 requires every top-level JSON DTO to carry"schema": "<name>/v1".lofty-pm-cli's resolution (adoptable as-is):
config show --json→ object taggedconfig/v1;config path --json→{"schema": "config-path/v1", "path": "..."}; text mode unchanged for both. Ref: piekstra/lofty-pm-cli commit 922de89. conformance.md's lofty row should note the gap until fixed.