commands:
  name: ssh
  steps:
    - type: shell
      output: raw
      command: "exec aws ssm start-session --target {{ .Arguments.instance_id }}"

base_path: "."

logs:
  level: Info

commands:
  # 1. Basic terminal session (the SSM stand-in).
  #    Expect: a bash prompt; full-screen apps render; exit/Ctrl-D returns you
  #    to your own shell immediately with echo working.
  - name: test-tty
    description: Interactive bash in a tty step (SSM session stand-in)
    steps:
      - type: shell
        tty: true
        interactive: true
        command: "bash --norc -i"

  # 2. Matt's repro - grandchild keeps the PTY open after the session exits
  #    (this is what aws ssm's session-manager-plugin does).
  #    Expect WITH the fix: after `exit`, your prompt is back within ~1 second
  #    and echo works. WITHOUT the fix: hang until a keypress, then no echo.
  - name: test-lingering
    description: Reproduce the SSM teardown hang (background child holds the PTY)
    steps:
      - type: shell
        tty: true
        interactive: true
        command: "sleep 60 & bash --norc -i"

  # 3. Ctrl-C handling - press Ctrl-C while sleep runs.
  #    Expect: the sleep is interrupted (atmos exits 130 from the step), your
  #    terminal is sane afterwards. Atmos itself was NOT killed by the signal -
  #    it returned through normal teardown (terminal restored, exit code clean).
  - name: test-ctrlc
    description: Ctrl-C goes to the step, not atmos
    steps:
      - type: shell
        tty: true
        interactive: true
        command: "echo 'Press Ctrl-C now...'; sleep 30; echo 'not interrupted'"

  # 4. Interactive without tty - prompts work, output still masked/managed.
  - name: test-interactive
    description: Interactive (non-tty) step reads stdin
    steps:
      - type: shell
        interactive: true
        command: "printf 'type something: '; read x; echo \"you typed: $x\""

  # 5. exec step - replaces the atmos process entirely.
  #    Expect: `ps -o ppid= -p $$` inside the shell shows your TERMINAL's shell
  #    as parent (no atmos in the process tree - it was replaced). Ctrl-Z job
  #    control is native. Exit code propagates: run `exit 7`, then `echo $?`
  #    in your own shell shows 7.
  - name: test-exec
    description: Replace the atmos process (shell exec semantics)
    steps:
      - type: exec
        command: "bash --norc -i"

  # 6. Validation - exec must be the final step.
  #    Expect: immediate error, nothing executes.
  - name: test-exec-invalid
    description: Exec step not last - must fail validation
    steps:
      - type: exec
        command: "echo never runs"
      - type: shell
        command: "echo unreachable"

  # 7. Plain step - unchanged behavior (baseline).
  - name: test-plain
    description: Plain shell step (baseline, unchanged behavior)
    steps:
      - "echo plain step ok"

  # 8. Color self-test (non-interactive). tty:true allocates a PTY so the
  #    program sees a real terminal; color should render. Exits on its own.
  - name: test-color
    description: Print a color self-test inside a tty step
    steps:
      - type: shell
        tty: true
        command: |
          echo "TERM=$TERM"
          echo "tput colors: $(tput colors 2>/dev/null)"
          printf '\033[31mRED\033[0m \033[32mGREEN\033[0m \033[33mYELLOW\033[0m \033[34mBLUE\033[0m\n'
          printf '\033[1mBOLD\033[0m \033[4mUNDERLINE\033[0m \033[7mINVERSE\033[0m\n'
          command -v tput >/dev/null && tput setaf 1 && echo "tput red" && tput sgr0

  # 9. Color in an interactive session: drops you into bash to type your own
  #    color checks (see README).
  - name: test-color-interactive
    description: Interactive bash to test color by hand
    steps:
      - type: shell
        tty: true
        interactive: true
        command: 'echo "TERM=$TERM, colors=$(tput colors 2>/dev/null)"; exec bash --norc -i'