[tteon]

What
Standardizes the help text for all --json CLI arguments to be exclusively "Emit JSON".

Why
The previous CLI definitions for the --json output flag had inconsistent help strings (e.g., "JSON output", "Emit JSON output", missing descriptions entirely, or "Emit JSON"). This standardization simplifies the CLI help surface, providing a more consistent operator experience per the repository's UX constraints.

Accessibility / UX Impact
Minor but clear UX improvement: Reduces cognitive load for CLI users by guaranteeing that the identical functional flag (--json) is described identically across every single command and subcommand.

Validation

• Validated via bash scripts/ci/run_basic_ci.sh locally. The basic CI suite completed, and the only failures were 3 tests in extraction/tests/test_tools.py which are an unrelated, pre-existing issue on the main branch regarding RunContextWrapper. My modifications do not cause functional regressions.
• Validated via bash scripts/pm/lint-agent-docs.sh, which confirms the agent docs/CLI contracts remain solid.

Risks
Extremely low risk. This change exclusively alters static CLI help string literals. It does not modify flag names, target destinations, defaults, boolean action flags, or underlying runtime logic.

Modified Files:

• src/seocho/cli/ontology.py
• src/seocho/cli/options.py
• src/seocho/cli/parsers.py
• src/seocho/cli/runs.py
• .jules/palette.md

(Note: Created as a Draft PR as requested by repository issue guidelines.)

---

PR created automatically by Jules for task 1760517736953239750 started by @tteon

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-15T17:26:17.772192Z	f0bcd48	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 90dfcd8b09

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".