docs(contributor): mark GH-C88 as needing design

[mikamikasuki]

Goal And Delivered Outcome

• Outcome basis / optional anchor: Contributor task board status correction.
• Goal/source and gap: The task board defines Available as ready to claim. GH-C88 is marked Available, while the latest discussion on issue #2881 still leaves the default-output direction unresolved.
• Observable before → after, with the validation row that proves it: GH-C88 changes from Available to Needs design; the issue discussion contains unresolved design questions, and the targeted public-boundary check passes.
• Issue/task and intended base: Related to [Feature]: loopx 命令返回都是成串json，虽然很全，但是重点不突出，翻页麻烦，能不能返回更简洁 #2881; main.

Author Declaration

• Written by: model_agent — GPT-6 model family, OpenAI Codex

Implemented against

• Specification and revision: docs/development/contributor-tasks.md status legend at 2f68e3b835c3bfc0e3718373cdb6c72eea99291e; issue [Feature]: loopx 命令返回都是成串json，虽然很全，但是重点不突出，翻页麻烦，能不能返回更简洁 #2881 discussion through 2026-09-15.
• Criteria:

Criterion (spec clause)	Disposition	Symbol / path	Test or command
Available means the linked outcome is ready to claim	implemented	docs/development/contributor-tasks.md, GH-C88	mise exec node@24.18.0 -- uv run --extra test loopx check --scan-path docs/development/contributor-tasks.md
Unresolved design direction is identified before implementation	implemented	issue #2881 and GH-C88 status	Read current issue comments and search open PRs for #2881

• Self-check before submission: Read the current task-board status definition, the latest [Feature]: loopx 命令返回都是成串json，虽然很全，但是重点不突出，翻页麻烦，能不能返回更简洁 #2881 comments, and matching open PRs. Confirmed the one-line diff changes only GH-C88's status.

Scope And Continuation

• Completed scope and remaining work: The board now reflects that GH-C88 needs a design decision. The CLI output design and implementation remain open in [Feature]: loopx 命令返回都是成串json，虽然很全，但是重点不突出，翻页麻烦，能不能返回更简洁 #2881.
• Slice boundary / successor: Complete within this scope; the issue owner must settle the output direction before the feature task is claimable.

Validation

• Tested revision: 24c885c37f2188698af134ee76651e842aaf2261
• Run state: finished
• Input classes: none

Check kind	Result	Public-safe evidence / limitation
static	passed	uv run --extra test loopx check --scan-path docs/development/contributor-tasks.md; public-boundary scan clean for the changed file.
static	failed	uv run --extra test python examples/docs-governance-smoke.py stops at the RFC status-index check because two dated headings remain in external-evidence-research-capability-v0.md and its Chinese counterpart. The same failure reproduces on base 2f68e3b835c3bfc0e3718373cdb6c72eea99291e.
manual	passed	Compared the board's status definition to the current #2881 discussion and confirmed no open PR is addressing that design decision.

• Coverage and gaps: Runtime validation is not applicable to a task-status documentation change. The full docs-governance smoke remains red for the same unrelated RFC status-index issue on base and this commit.

Frontend / Visual Evidence

• UI impact: none
• Before: N/A
• After: N/A
• States and viewports shown: N/A
• Source data: none
• Attention review: N/A

Type of Change

• Documentation update

LoopX Area

• Public docs or presentation surface (README, protocols, dashboard)

Technical Direction

• Direction / acceptance reference, when applicable: S12, issue [Feature]: loopx 命令返回都是成串json，虽然很全，但是重点不突出，翻页麻烦，能不能返回更简洁 #2881.

Shared-authority RFC fixture impact

• N/A — this PR does not claim progress against the shared-authority RFC.

Boundary Checklist

• No private state, credentials, raw traces, internal links, or local machine paths are included.
• No maintainer-owned benchmark work is duplicated.
• The change is scoped to the GH-C88 task-board status.
• UI impact is none.
• The commit includes a DCO Signed-off-by trailer.