[HoungDev]

Summary

• add a stable JSON envelope to title, tags, rename, and undo
• keep human-readable output as the default
• send JSON success responses only to stdout and structured errors only to stderr
• require explicit dry-run or yes mode for non-interactive rename and undo JSON calls
• document schemas, statuses, exit codes, and automation examples
• add process-level integration tests for success, errors, and non-mutating previews
• include the JSON reference in source distributions

Why

Creator workflows often need to pass CLI results into scripts and CI pipelines. Human-oriented
text is useful interactively but difficult to parse reliably. A versioned envelope and stable
exit-code contract make the toolkit composable without weakening the safe confirmation behavior
added to file operations.

User impact

• Add --json to any scriptable subcommand.
• Rename and undo JSON calls never prompt or hang; they require --dry-run or --yes.
• Runtime errors return exit code 1 with JSON on stderr.
• Unsafe or incomplete JSON invocations return exit code 2.

Validation

• ruff check .
• ruff format --check .
• pytest — 44 passed, 93.79% coverage
• process-level JSON success, error, and preview tests
• installed executable JSON parse smoke test
• python -m build --no-isolation
• python -m twine check
• verified docs/json-output.md is included in the sdist
• python -m pip_audit — no known vulnerabilities
• python -m pip check

Closes #4