Skip to content

fix: a blocking question of 'none' with a reason counts as none (v2.27.1) - #93

Merged
cskwork merged 1 commit into
mainfrom
fix/intent-none-note
Nov 17, 2026
Merged

cskwork merged 1 commit into
mainfrom
fix/intent-none-note

Conversation

@cskwork

@cskwork cskwork commented Nov 17, 2026

Copy link
Copy Markdown
Owner

v2.27.1: A blocking question of "none" with a reason counts as none

Problem

The intent parser treated a line under Questions for you (or Blocking questions) as answered only when it was exactly none. An intent that wrote - none (all six areas clear; nothing open) made sdlc.sh status and next report the intent NEEDS-HUMAN with that text as the open question, and approve intent refused it, although nothing was open.

Changes

  • sdlc.sh: a question line reads as none when it is none, any case, alone or followed by a space, tab, ., ,, ;, : or ( and any explanation, e.g. none (all areas clear), None — settled, None.. Any other value is still an open question; none inside a longer word (nonexistent) is too.
  • Selftest: none (reason), None — reason and None. are not open questions; Which output format? is.

Questions for you의 none 뒤에 설명이 붙으면(none (...), None — ..., None.) intent가 NEEDS-HUMAN으로 남던 문제. none 다음 공백·구두점·괄호를 허용하고, 다른 값은 그대로 열린 질문이다.
@cskwork
cskwork merged commit fcbc72f into main Nov 17, 2026
3 checks passed
@cskwork
cskwork deleted the fix/intent-none-note branch November 17, 2026 01:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant