rea/.github/ISSUE_TEMPLATE/bug_report.yml

name: Bug report
description: Report a problem in REA with observations or source evidence
title: "[Bug] "
labels:
  - bug
  - triage
body:
  - type: markdown
    attributes:
      value: |
        Report one primary behavior per issue. Keep answers concise and grounded
        in available evidence. Distinguish observed behavior, source-derived
        reasoning, and suspected causes; do not claim a reproduction you did not run.
        If a narrative answer is not known, write `NOT_ENOUGH_INFO` and describe
        what is missing. Intermittent failures and clearly labeled source-only
        reports are welcome. Do not include credentials or sensitive target data.

  - type: checkboxes
    id: before-submitting
    attributes:
      label: Before submitting
      options:
        - label: I searched the open and closed issues for a related report.
          required: true
        - label: I removed credentials, tokens, private paths, and sensitive target data.
          required: true

  - type: dropdown
    id: area
    attributes:
      label: Area
      options:
        - Setup, packaging, or upgrade
        - Provider or capability discovery
        - Process capture or runtime observation
        - Native analysis or decompilation
        - Evidence, artifacts, or reconstruction
        - CLI
        - MCP or agent integration
        - Documentation
        - Other
    validations:
      required: true

  - type: textarea
    id: observed-behavior
    attributes:
      label: Observed behavior
      description: Describe the actual result, including the exact command or MCP request, relevant provider/target, and supporting evidence below. Label source-only findings instead of claiming execution.
    validations:
      required: true

  - type: textarea
    id: reproduction
    attributes:
      label: Reproduction
      description: Give the shortest steps you actually ran, with the relevant input or configuration. State how often they reproduced the problem when known. If reproduction is unavailable, say so and provide the observations or source reference you have.
      placeholder: |
        1. Configure or start ...
        2. Run ...
        3. Observe ...
    validations:
      required: true

  - type: textarea
    id: expected-behavior
    attributes:
      label: Expected behavior
      description: State the expected result, contract, or recovery action. Cite documentation, source, or a known-good version when available; mark an unverified expectation or unknown reference clearly.
    validations:
      required: true

  - type: textarea
    id: impact-scope
    attributes:
      label: Impact and scope
      description: Describe observed impact and frequency, including effects on evidence integrity, process isolation, compatibility, or recovery when known. Leave untested scope and severity unknown rather than guessing.
    validations:
      required: true

  - type: input
    id: rea-version
    attributes:
      label: REA version
      description: Use `rea --version` or provide the source revision.
      placeholder: Exact rea --version output or source commit SHA
    validations:
      required: true

  - type: input
    id: runtime
    attributes:
      label: Runtime and platform
      description: Include Node.js, OS, architecture, and Hopper/Ghidra version when relevant.
      placeholder: Node 24.18; macOS 15 arm64; Hopper 5.15
    validations:
      required: true

  - type: input
    id: target
    attributes:
      label: Target and artifact context
      description: Include binary format, app/container type, artifact kind, or workload details when relevant.
      placeholder: Mach-O arm64 app; Evidence v2 bundle; not applicable

  - type: dropdown
    id: interface
    attributes:
      label: Interface
      options:
        - CLI
        - MCP
        - Python bridge
        - Package or setup
        - Other
    validations:
      required: true

  - type: dropdown
    id: failure-stage
    attributes:
      label: Earliest failure stage
      description: Select where the incorrect behavior first becomes observable. Choose Unknown if this has not been established.
      options:
        - Request parsing or validation
        - Setup or provider admission
        - Capture or observation
        - Artifact or evidence registration
        - Native analysis or reconstruction
        - Transport or result projection
        - Cleanup, cancellation, or lifecycle
        - Unknown
    validations:
      required: true

  - type: textarea
    id: relevant-evidence
    attributes:
      label: Relevant output or evidence
      description: Include the smallest useful output, MCP result, error, screenshot, artifact, or exact source reference. Say how it was obtained and which claim it supports. If unavailable, write NOT_ENOUGH_INFO and explain what is missing. Redact credentials and sensitive target data.
      placeholder: |
        Command or MCP request actually run:
        Relevant result, error, or artifact:
        For source-only findings, link the file/revision and relevant code:
        Missing evidence or remaining uncertainty:
    validations:
      required: true

  - type: textarea
    id: typed-outcome
    attributes:
      label: Typed outcome or recovery expected
      description: Optional. What typed result, error, next tool, cleanup state, or limitation should the caller have received?

  - type: textarea
    id: analysis
    attributes:
      label: Analysis or suspected cause
      description: Optional. Link supporting source and distinguish source-derived reasoning from a hypothesis. A root-cause analysis or proposed fix is not required.

  - type: textarea
    id: additional-context
    attributes:
      label: Additional context
      description: Add reduced fixtures, screenshots, or related issues. For observed regressions, include the last known good and first known bad versions when available. Label untested checks as proposals.