Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Pipeline Design 4

ezigus edited this page Feb 25, 2026 · 1 revision

The ADR is ready for your review in .claude/plan.md. It covers:

  • Context: Why --json is needed (programmatic consumption by CI, dashboards, fleet orchestrators)
  • Decision: Early-exit code path with independent data collection per section, jq-based assembly, graceful degradation to []/null
  • Alternatives rejected: Shared data path (coupling risk), JSONL (not queryable), Python/Node helper (architecture mismatch)
  • Risk areas: Subshell variable loss in pipe loops (mitigated correctly), curl timeout (3s cap), unbounded completions (capped at 20)
  • Validation: All 12 criteria checked — the feature is already fully implemented and all 30 tests pass

Since the implementation is complete, the pipeline can proceed directly to PR.

Clone this wiki locally

AltStyle によって変換されたページ (->オリジナル) /