Doc system test

prompting map

Prompting: map

domain/

  • Answer - The value for one question id - String, StringArray or Bool - its three spellings, which question kind gives which, and why only the id is matched.
  • Deterministic state - The map of d.get values the CLI carries between one template's init calls - where it lives in one run, the four places it is lost, and SDK parity.
  • Prompt outcome - How one template's question loop ends - QnA, Complete, NeedInput or Err - what each carries, and what the executor, composition and CLI do with it.
  • Question - The six kinds of question a template can ask, their fields and ids, how each becomes a terminal prompt, and what Esc does.

architecture/

  • Headless mode - create, update and try without a terminal - the answers file, the two walks, the JSON envelope, exit codes 0/2/1, cleanup, and the stdout contract.
  • Question protocol - The init and validate HTTP calls between the CLI and a template, through the coordinator proxy - routes, ports, JSON, errors and timeouts.

implementation/

  • Answer validation - How an answer is checked - the template's validator by replay for text, password and date, local shape checks in headless, and the discovery walk.
  • Secret redaction - kept off this public page (security-related)
  • Stateless replay - How the CLI asks a template's questions - the script reruns from the top on every call with every answer so far; a 3-question script runs 4 times.