implement-componentlisted

# Implement Component ## Purpose Execute Lego-style Component development without changing upstream intent or declaring unverified code complete. ## Trigger Run when a Component/task is ready with sufficient Requirements, design, Contract, write scope, and Definition of Done. ## Inputs - Task/Component ID, allowed write scope, current state, target revision, and DoD. - Validated Requirements, architecture/design, versioned Contract, Project Constraints, and acceptance criteria. - Existing code/tests, build commands, risks, Workflow Level, and required Gate/review. ## Prerequisites - Required dependencies are `VALID`; upstream material decisions are resolved. - Parallel work has non-overlapping scopes, stable Contracts, correct base visibility, and an integration owner. - Set the Component to `IMPLEMENTING`; any changed `STABLE` Component becomes `UNVERIFIED`. ## Procedure 1. Read the Contract, constraints, acceptance criteria, and existing implementation before editing. 2. Confirm task scope, base revision, workspace, dependencies, and validation commands. 3. Reproduce a bug before fixing when feasible. 4. Stop if implementation exposes a Requirement, architecture, or Contract gap. 5. Implement the smallest cohesive change within the Component boundary. 6. Add or update focused tests and traceability required by the change. 7. Build or run the project's equivalent compile/static validation. 8. Execute Adaptive Testing for the affected risk and regression scope. 9. P