fix: make classification and regression outputs single-select

[singyichen]

Purpose

Make Classification and Regression output types mutually exclusive in the New Task Step 1 prototype while preserving valid multi-output composition.

Reason

Classification and Regression output chips were rendered as checkboxes, allowing invalid same-category combinations and diverging from the intended single-choice interaction.

Result

Category	Before	After
Classification	Single label and Multi-label could both be selected	Radio group; exactly one option remains selected
Regression	Single dimension and Multi-dimension could both be selected	Radio group; exactly one option remains selected
Sequence	Checkbox multi-selection	Unchanged; valid combinations remain available
Cross-category composition	Multiple categories could be combined	Unchanged

Selection behavior is driven by taxonomy outputSelection metadata rather than category-specific selector branches. The task-new specification is updated to v4.1.0 with SC-002e coverage.

Changed Files

File	Change
design/prototype/pages/task-management/task-new.html	Add taxonomy selection metadata and render accessible radio or checkbox groups from configuration
design/prototype/tests/task-management/task-new-taxonomy-cascade.spec.ts	Add SC-002e coverage for roles, visual indicators, mutual exclusion, and sequence multi-selection
specs/task-management/013-task-new/spec.md	Document the selection contract and bump the spec to v4.1.0
specs/STATUS.md	Synchronize the task-management-013 version and status history

Test Plan

• Run pnpm typecheck from design/prototype/
• Run pnpm playwright test from design/prototype/ — 358 passed
• Run git diff --check
• Confirm CI Prototype — Type Check passes
• Confirm CI Prototype — Playwright Tests passes

Impact Scope

• Frontend pages (New Task Step 1 prototype)
• Admin pages
• API
• Scheduled jobs / Queue
• Other (task-management-013 specification)

Related

• Issue: None

Checklist

• I have tested locally and confirmed functionality and stability
• I have added necessary comments, especially for hard-to-understand parts
• My PR title follows the format: <type>: <description>

Type Reference

Type	Description
feat	New feature
fix	Bug fix
docs	Documentation only
refactor	Code restructuring without behavior change
test	Adding or updating tests only
style	Formatting, whitespace, lint fixes
chore	Tooling, config, dependency updates
perf	Performance improvement
ci	CI/CD pipeline changes

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[amazon-q-developer]

The changes correctly implement radio-based single selection for Classification and Regression outputs while preserving checkbox multi-selection for Sequence outputs. The implementation is driven by taxonomy outputSelection metadata as specified, includes comprehensive test coverage (SC-002e), and properly handles mutual exclusivity within output groups while allowing cross-category selection. No blocking issues found.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →