foxctl integrations are split by maturity so operators and agents know which
surfaces are current behavior and which remain plan-backed work.
| Status | Meaning |
|---|
| Current | Documented behavior that can be used as operator guidance |
| In progress | Active plan or experimental work; do not treat as canonical behavior |
| Planned | Known direction with no production contract yet |
| Area | Status | Tracking |
|---|
| Durable execution recovery | In progress | Progress |
| Runtime side-effect safety | In progress | Progress |
| RLM helper runtime and eval loop | In progress | Progress |
| OpenSandbox workspace integration | In progress | Progress |
| Refactor intelligence and slop detection | In progress | Progress |
| ACA memory and retrieval ensemble | In progress | Progress |
Current integration pages describe behavior that should match the repository.
In-progress pages describe intended direction and validation work. When an
in-progress feature becomes default behavior, promote the stable contract into
the matching current docs page and update this status table in the same change.
