Add fallback-free real intake clarification templates

[SoundBlaster]

Summary

• Add workspace-bound, browser-answerable real idea clarification templates with explicit lifecycle outcomes.
• Link related issue/task (if any): proposal 0210_fallback_free_real_intake_clarification_templates.

Motivation

• The standard UI-started product demo still depended on a deterministic clarification fixture when producer artifacts were not safely answerable in the browser.
• Missing clarification and clarification-not-required were not distinct machine states, and a no-answer continuation needed a trustworthy producer contract.

Goals

• Emit answers_required, clarification_not_required, or clarification_blocked with workspace identity and source digests.
• Require policies in the real-intake event-storming frame and provide a digest-bound no-answer continuation target. Canonical spec mutation, ontology writes, approval, and Git promotion remain out of scope.

Changes

• Add proposal 0210, registry tracking, DocC/roadmap updates, explicit outcomes, workspace binding, source digests, and strict browser-answerability validation.
• Add real-idea-intake-continue-without-answers with source-artifact digest verification and regression coverage for unsupported, stale, foreign, and no-clarification inputs.

Spec Evidence

Spec-ID: N/A
Proposal-ID: 0210
Spec-Impact: schema
Spec-Rationale: Extends real-intake clarification artifacts and lifecycle orchestration so browser consumers can distinguish answer, skip, and blocked outcomes safely.

Validation

• Tests added/updated for changed behavior
• Local checks passed

Commands run:

make test
make publish-bundle
make proposal-tracking-gate
make docc-sync
.venv/bin/ruff check ...

Results:

• 1835 passed.
• Public bundle built with safety gate passed.
• Proposal tracking, DocC sync, ruff check, and ruff format passed.
• Real no-clarification execution produced candidate support-triage-log without answer state or raw/private trace leakage.

Risks / Notes

• Backward compatibility impact: template contract advances to v0.2; Platform and SpecSpace retain legacy behavior when the explicit outcome is absent.
• Migration/config changes required: none.
• Known limitations: browser form presentation screenshots remain a SpecSpace harness follow-up; producer behavior is covered by execution-backed E2E.

Checklist

• PR title clearly describes the change
• Scope is focused and minimal
• Documentation updated (or N/A)
• Workflow/artifact changes distinguish presence from readiness/status
• Consumers prefer authoritative repaired/promoted/latest artifacts where relevant
• Temporary or intermediate paths are scoped to the current run/task where relevant
• No secrets or sensitive data added

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c8bb51e388

ℹ️ 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".