Summary
When Amico presents a free-form text input card (via the question tool with kind: "text"), the user types their answer and presses Enter, but the response registers as "(no answer)" — as if the input was empty. The user's text is discarded.
Context
harmoniqs.amicode@0.3.0; Darwin 25.6.0 arm64; engine base v1.18.10-amicode.17 (harmoniqs/opencode). Observed with a question card asking "For the Julia package structure, what do you want the package to be called?" — user typed an answer, pressed Enter, result shown as "(no answer)".
Expected vs actual
- Expected: The typed text is captured and sent as the user's response to the question card.
- Actual: The submission registers as "(no answer)" despite the user having typed text into the input field.
Diagnostics
intake: not-ready — mature per the maturity contract before picking up
suggested_path: B
diagnostics: inline
upstream: n/a
Summary
When Amico presents a free-form text input card (via the question tool with kind: "text"), the user types their answer and presses Enter, but the response registers as "(no answer)" — as if the input was empty. The user's text is discarded.
Context
harmoniqs.amicode@0.3.0; Darwin 25.6.0 arm64; engine base v1.18.10-amicode.17 (harmoniqs/opencode). Observed with a question card asking "For the Julia package structure, what do you want the package to be called?" — user typed an answer, pressed Enter, result shown as "(no answer)".
Expected vs actual
Diagnostics
intake: not-ready — mature per the maturity contract before picking up
suggested_path: B
diagnostics: inline
upstream: n/a