Possible complementary direction: LongHorizon-Harness for sustained agent tasks

Hi, I'd like to suggest a complementary direction for rtk.

Project:
https://github.com/AMAP-ML/LongHorizon-Harness

Your project focuses on coding-agent and software-engineering workflows.

LongHorizon-Harness focuses on carrying one task across many rounds without state drift. It keeps the goal and verified progress in durable state, starts each execution round with a fresh context, and uses an independent Auditor before accepting progress.

Why this may be useful here:

• A small integration note could clarify how the existing execution layer can sit inside a recoverable, independently checked long-running task.
• it adds an outer task-lifecycle layer without claiming to replace the project's existing agent or runtime

If this direction fits, I can prepare a small documentation or example contribution following the repository's conventions.

I am part of the team behind LongHorizon-Harness, so I wanted to disclose that connection.

Paper:
https://arxiv.org/abs/2608.01964

Project page:
https://lh-harness.pages.dev

The issue names no repository files, tests, or entry points. Start by reading the existing execution layer and the repository's contribution conventions, then determine whether an integration note or example is appropriate. Done would be a maintainer-approved documentation or example contribution with a clearly scoped relationship to LongHorizon-Harness.