v0.2-M7: corpus CLI/MCP surfaces and PICS rendering

[luofang34]

Parent epic: #157. Design anchors: DD-14 and DD-17.

Objective

Expose the corpus through stable human and agent interfaces without granting agents approval, source-snapshot mutation, lock replacement, or baseline-overwrite authority.

Human CLI scope

• corpus source add|inspect backed by the M3 source store and transition validator.
• Human-authorized source capture and canonical sources.lock writing without silent overwrite.
• corpus ingest backed by M4 ingesters and drift contracts.
• corpus validate, queue, context, review, trace, and render workflows as their backing contracts become available.
• Complete PICS form modeling and rendering with requirement/profile bindings.

MCP and agent scope

• Read-only corpus validation, source-context, extraction-queue, requirement-context, and trace tools.
• Restricted append-only candidate-proposal API backed by M2.
• No MCP operation for approval, review mutation, source acquisition/mutation, lock replacement, or baseline overwrite.

Surface contract

• Register every new command/tool in KNOWN_SURFACES with matching HLR coverage.
• Preserve JSONL single-terminal and stdout-strict invariants.
• Preserve crate-root API discipline.
• Add parity tests across CLI, MCP, doctor, and underlying core semantics.
• Make human-vs-agent authority visible through available typed capabilities, not a caller-supplied actor string.

Dependencies

• M2 lifecycle, review, and proposal authority: complete.
• M3 frozen source identity, transition validation, locking, and offline verification: complete under v0.2-M3: frozen source identity and offline baseline verification #166.
• M4 ingestion and drift contracts: v0.2-M4: structure-preserving Markdown, HTML, and PDF ingestion #167.
• M5 extraction, profile, decision, and PICS semantics: v0.2-M5: extraction semantics, ambiguities, decisions, and profiles #168.
• M6 corpus baseline and mandatory cert/record enforcement: v0.2-M6: corpus cutover and legacy-loader removal behind parity #169.
• Schema-valid, adoption-honest initialization (init must produce a schema-valid, doctor-complete, non-fake scaffold #142): complete.
• v0.2-M5 design: explicit standard-pack selection and standard-agnostic profiles #90 owns explicit standard-pack selection before standards-related surfaces are exposed.

Delivery discipline

This is a milestone tracker. Source commands and lock writing, ingestion commands, validation/context/queue/review families, MCP read tools, proposal exposure, and PICS rendering each require dedicated child issues and independently revertible PRs.

Done when

Humans can manage and review the corpus through explicit authorized workflows; agents can inspect and append candidates only; PICS output is complete; every surface is trace-covered; and approval/source/baseline authority remains unavailable to agents by construction.