> For the complete documentation index, see [llms.txt](https://docs.devsolve.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devsolve.app/km/researchers/report-lifecycle.md).

# វដ្តជីវិត Report និង Retest

Researcher Interface បង្ហាញ Status សាមញ្ញ ខណៈ Backend អាចរក្សា Workflow State លម្អិតជាងនេះ។

```mermaid
flowchart LR
    A[Submitted] --> B[Triaging]
    B --> C[Accepted]
    B --> D[Rejected]
    B --> E[Needs More Information]
    C --> F[Resolved]
    F --> G[Retesting]
    G --> F
    G --> C
```

| Displayed state | អត្ថន័យ                                                              |
| --------------- | -------------------------------------------------------------------- |
| Submitted       | Platform បានទទួល Report                                              |
| Triaging        | Organization កំពុង Review; អាចរួមបញ្ចូល Request for More Information |
| Accepted        | Finding ត្រូវបានបញ្ជាក់ថាត្រឹមត្រូវ                                  |
| Rejected        | Report បិទដោយមិនទទួលយក; មូលហេតុអាចជា Duplicate ឬ Rejection ផ្សេង     |
| Resolved        | Organization បានកត់ថាបញ្ហាត្រូវបានដោះស្រាយ                           |
| Retesting       | Organization ស្នើ Researcher ឱ្យផ្ទៀងផ្ទាត់លទ្ធផល                    |

## ឆ្លើយតប Retest

1. បើក Report និងផ្នែក **Retest**។
2. អាន Environment, Instructions, Due Date និង Bonus ដែលបានកត់ បើមាន។
3. ដំណើរការ PoC ដែលបានអនុញ្ញាតឡើងវិញ។
4. បន្ថែម Sanitized Evidence។
5. Submit **Verified fixed** ឬ **Still vulnerable** ជាមួយការពន្យល់ត្រឹមត្រូវ។

**Verified fixed** ទុក Report ជា Resolved។ **Still vulnerable** បញ្ជូនវាត្រឡប់ទៅ Valid Confirmed សម្រាប់ការងារបន្ត។


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devsolve.app/km/researchers/report-lifecycle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.